AppSec & staff engineers: harden every stage of the SDLC and pass your SOC 2 audit.
Reach for this when you own security for an engineering team and need to harden the whole software lifecycle, not just run a scanner. It walks you from design-time threat modeling and supply-chain/dependency risk, through secrets hygiene and security-focused code review, to triaging real exploitable findings out of scanner noise and assembling the evidence that gets you through a SOC 2 audit. Opinionated, senior-level defaults so you ship with confidence and survive the audit without the busywork.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Applies STRIDE threat modeling to a feature or system design and produces a prioritized threat table with concrete mitigations ranked by exploitability and impact.
Audits third-party dependencies for exploitable CVEs, abandonment, license exposure, and supply-chain hygiene, and delivers a ranked findings report with a remediation order.
Guides detection, emergency rotation, and prevention of leaked secrets and credentials across source code, git history, CI pipelines, logs, and infrastructure config.
Maps engineering controls to SOC 2 Trust Service Criteria, builds a continuous evidence-collection plan with cadences per control family, and produces the control-to-evidence table auditors work from.
Prioritizes vulnerability findings from scanners, pentest reports, and bug bounty submissions by real-world exploitability rather than raw CVSS, assigning internal severity tiers with fix SLAs.
Reviews code for the security flaw classes that cause the most breaches – broken authorization and IDOR, injection, SSRF, mass assignment, and unsafe deserialization – and returns a short, focused findings list with concrete fixes.
Runs a whole-application security audit – threat-model-lite scoping, dependencies and supply chain, secrets, authentication and authorization, input handling, transport and headers, logging, and infrastructure config.
Detects and redacts personally identifiable information from text, logs, datasets, and LLM prompts using layered pattern, checksum, and NER detection, then picks the right redaction mode for each downstream use.