How I Would Lead a Security Engineering Team: Outcomes, Evidence, and Trust
A principal-level operating model for leading security analysts and developers through clear outcomes, decision rights, engineering leverage, and measurable learning.
Nathan Berg
Defining the Security Outcome for Detection Engineering
A practical security engineering field guide to detection engineering, covering risk, implementation, evidence, and team leadership.
Defining the Security Outcome for Software Supply Chain Security
A practical security engineering field guide to software supply chain security, covering risk, implementation, evidence, and team leadership.
A Practical Risk Model for Authorization
A practical security engineering field guide to authorization, covering risk, implementation, evidence, and team leadership.
Leading Security Architecture Through Verifiable Invariants
Connect tenant isolation, release integrity, and incident containment to concrete decisions, team ownership, and investment priorities.
From Incident Timeline to Security Regression Test
Turn a control failure into a deterministic test, an owned engineering change, and evidence that the fix reaches every affected path.
Security Exceptions as Expiring Engineering State
Make exceptions executable and reviewable with scoped predicates, evidence, owners, and explicit expiry behavior.
Security Canaries Must Measure Control Correctness
Pair progressive rollout metrics with synthetic forbidden actions so security regressions do not hide behind healthy latency.
Private API Responses and Shared Cache Leaks
Review cache keys, response directives, and authorization order across browsers, proxies, and application caches.
Password-Hash Migrations Under Real Load
Upgrade password storage with bounded verification costs, compare-and-swap updates, and a plan for inactive accounts.