Threat-modeling wiki confidentiality after GROWI CVE-2026-105272
A threat model for the confidentiality boundary broken by GROWI CVE-2026-105272.
Tag archive
A threat model for the confidentiality boundary broken by GROWI CVE-2026-105272.
A trust-zone and reachability model for prioritizing CVE-2026-79868 remediation.
Draw the data flow in OWASP Threat Dragon, then go through each element and flow with STRIDE: the boundary, the data, each threat and its control.
Threat model for CVE-2026-106931: what AV:L and PR:L mean on shared web servers, which SiteGuard versions matter, and how to prioritise hosts after confirmed exploitation.
Traditional threat modelling frameworks were built for a world where software did what it was told....
A structured way to find the security holes in a design before they become bugs in production. The four questions, data-flow diagrams with trust bound
In my last article https://dev.to/aws-builders/the-secret-ingredient-is-a2a-3dpp, I talked about...
A threat model for MCP tool servers using OAuth: how tool impersonation and audience mismatch happen, how tokens get replayed, and what to validate and log in 2026.

Back in June I shipped P2 Threat Model Generator — a Python tool that reads Docker Compose, OpenAPI,...

Threat Modeling vs. Penetration Testing: The $80 Million Lesson From Capital One In 2019,...
Money has a weird property: it's the easiest goal to state and the hardest one to specify. "Make more...
Learn a practical 5-step threat modeling framework for containerized microservices using STRIDE and DREAD. Covers Kubernetes trust boundaries, CI/CD a