SF

Santi Friquet

Security engineer · Maintainer of sochub

Before starting sochub, I managed security programs at an enterprise firm in Argentina and worked across multiple startups at different growth stages — seed-stage teams building their first controls, Series A companies hardening cloud infrastructure, and everything in between. That range shapes how I think: I understand the structured rigor that regulated environments demand and the speed that startups actually operate at.

My technical focus is cloud detection and response, incident simulation, and AI/ML security. These are the areas where the threat landscape is moving fastest and where most programs are still weakest. I build tools to fill those gaps — like SIRAS, an open-source framework for simulating incidents and stress-testing detection before a real attack does it for you.

I started sochub for security teams that have outgrown Jira but can't justify the enterprise platforms: open source, self-hosted, with a copilot that asks before it writes anything. The articles here are the build log: how it gets made, and the detection and response thinking behind it.

Areas of focus

Cloud Detection & ResponseIncident ResponseDetection EngineeringAI / ML SecurityAWS / GCPSecurity Architecture

How sochub is built

The same three rules decide every feature.

Every feature is open source

No paid tier and no gated features. Read the code, run it, change it.

Your infrastructure, your model

sochub runs where you deploy it. The copilot uses a local Ollama model by default, or a provider you choose.

The analyst decides

AI proposes, people confirm. Nothing is written to a case until you approve it.

Let's talk

Questions about sochub, something I wrote, or a security problem you're working through: reach out directly. I also take on advisory and consulting work selectively.

Follow the build

Release notes and build-log articles when something ships. Free, and you can unsubscribe any time.

Get the build log