Architectural Risk Assessments
summary
An architectural risk assessment is a periodic, project-start activity that maps data flows, threat agents and controls to quantify risk; it’s used to remove credit cards as identifiers in a 20–30 year hotel legacy and to build a third‑party commerce API that disallows OAuth2 account creation, preventing privilege escalation. Practices include static analysis (FindBugs, PMD, Fortify), secure centralized logging, velocity checks, and threat modeling; memorable metrics: losses climb from ~$1B to ~$3.5B, Heartbleed leaks ~64KB, and high-profile breaches cost CEOs their jobs. Use the BSIMM maturity model as an implementation guide.
AI-written summary · about
chapters (21)
- 0:00Introduction and welcome
- 1:05What are architectural risk assessments
- 2:49Security as a core requirement
- 5:40Target breach case study
- 7:28Defining security across stakeholders
- 9:16Architecture as a security bridge
- 12:47Risk equation and threat modeling
- 15:38Abuse cases and attacker mindset
- 18:04Software security mindset
- 20:31Bugs vs design flaws in security
- 23:00Three pillars of software security
- 26:31Architecture-driven security practices
- 31:26Risk assessments in legacy systems
- 34:12Secure logging and defense in depth
- 38:08Authentication and authorization models
- 41:00Server-side validation necessity
- 43:28Artifacts and security processes
- 46:17Code review and static analysis
- 48:25Risk-based security testing
- 50:53BSIMM and maturity model
- 53:18Closing and resources
related talks
27mThe Architect's Guide to Fortifying Software Security
51mAnalyzing Architectural Risk
45mSecurity Architecture, An Adventure?
57mUnlocking Threat Modeling
50mThreat Modeling With Architectural Risk Patterns
32mThe Art of Secure Architecture
53mEnterprise Application Risk Profiling
51mSecure Applications, By Design