FORENSIC LIABILITY PRE-MORTEM
REFERENCE: EXECUTIVE LIABILITY DIAGNOSTIC
RESTRICTED: EXECUTIVE DIAGNOSIS ONLY
INSTRUCTIONS: Evaluate your current compliance architecture honestly. Any reliance on manual sampling, draft policies, or informal approvals must be marked as 'NO/UNSURE'.
DIAGNOSIS: CATEGORY 1
GOVERNANCE HOLDS AT FIRST SAMPLING CONTACT
Based on what you've reported, your architecture survives this first pass. No binary breaks were flagged across the seven vectors tested.
That doesn't mean nothing would surface under real surveillance sampling — this is a self-reported 7-question screen, not a forensic artifact review. But it means the obvious, most common failure patterns aren't present.
Maintain this. Resample periodically, especially after any change in headcount, budget, or scope.
VECTOR RESULTS
All seven tested vectors — secure
If you want a deeper, artifact-based sweep across all 25 collapse vectors rather than this 7-question self-report, the full diagnostic goes further than self-assessment can.
See the Collapse Vector Diagnostic →DIAGNOSIS: CATEGORY 4
THE CORPORATE LIABILITY SHIELD
Read below for explanation
Listen carefully. Your documentation proves the architecture exists. It doesn't prove the architecture survives sampling.
You're carrying personal liability for a system you were never fully resourced to run. That's not a personal failing — it's structural. 78% of CISOs report being personally concerned about their own liability for security incidents, and the gap between what auditors expect and what internal teams can produce under pressure is exactly where that concern becomes real.
Surveillance and recertification auditors don't operate on intent. If your team cannot produce unbroken, attributable evidence on demand, the auditor records a gap — and that gap doesn't ask whether you had the budget or headcount to close it.
When that gap becomes a finding, the board's "plausible deniability" activates by default. They retain Business Judgment protection while you absorb the liability. Under NIS2 Article 20, that can extend beyond a corporate fine to personal administrative measures against management — the exact severity depends on member state implementation, but the direction of travel is consistent: accountability increasingly attaches to the named individual.
FORENSIC LIABILITY HEATMAP
Generating vulnerability vectors based on your inputs...
This is what happens when a security function is under-resourced relative to what it's accountable for. Your controls exist on paper; under real sampling pressure, paper alone doesn't hold.
You cannot stop the audit. You can control whether these gaps are documented and escalated before it happens, or discovered during it.
Map exactly where the gaps sit. Pull the specific findings into writing and put them in front of the board now. Until that's done and acknowledged, the exposure defaults to you — not because anyone decided that deliberately, but because nobody else's name is on the line.
> DIRECTIVE: PEER ESCALATION
You're not the only executive carrying this exposure. If a peer in your network is relying on a clean ISO 27001 certificate or a verbal board nod to protect them under NIS2, send them this. Better they find their own gaps in private than have an auditor find them first.
This page is informational and does not constitute legal advice. NIS2 and DORA enforcement mechanisms vary by member state and regulatory body. Statistics cited are drawn from named third-party industry research as noted.