← Back to projects
View architecture artifact
Project dossier
Security & Collapse Audits
Threat modeling + remediation (operational and organizational failure risk)
Audit work for systems that operate under low trust: adversarial access, coercion risk, incentive pressure, and degraded operational reality.
SecurityThreat ModelingAuditSystems
Problem
Most security output fails at the moment it matters: it’s too abstract, too compliance-shaped, or too disconnected from real adversaries and real operator constraints.
This work focuses on exploitability, incentive-driven failure, and operational collapse vectors. The goal is to produce remediation that is testable and survivable, not performative.
Constraints
- •Assume adversarial reality: motivated attackers, not hypothetical ones.
- •Minimize theater: findings must include reproduction paths or falsifiable tests.
- •Threat boundaries are explicit: what is protected, from whom, and under what assumptions.
- •Prioritize operator usefulness: triage order, hard-fail guards, and clear next actions.
- •Respect degraded environments: low trust, partial observability, incident pressure.
Proof
ContactProof pageGitHub ↗Protective Legitimacy Score (PLS) — rubric ↗Redacted threat model excerptThreat boundary mapDefensibility packet flow
Live repo stats may be rate-limited for anonymous requests.
Method
Start with boundaries and incentives: define assets, actors, and the minimum conditions required for safety. If those conditions don’t hold, the system must fail safe.
Model the attack surface (network, dependencies, authn/authz, data flows, key material, privileged paths) and the operational surface (on-call reality, logging, rollback, incident response).
Convert risks into a prioritized remediation plan with verification steps: patches + tests + observable evidence that the failure mode is actually closed.
Architecture diagram
Outputs
- •A bounded risk register prioritized to top findings (typically 10) with triage order.
- •A threat model with explicit assumptions and hard boundaries (what must not fail).
- •Actionable findings: reproduction steps, impact, and recommended fixes.
- •A remediation plan ordered by risk reduction per unit effort.
- •Verification steps: tests or procedures that prove the issue is closed.
- •Operator-ready notes: rollback guidance and failure-mode monitoring suggestions.
- •A redacted artifact sample showing assumptions, adversaries, and closure criteria.
Supporting diagrams
Viewer-first links are primary; raw files are available as mirrors from each artifact page.