01
One accountable owner
Every domain and material lifecycle gap has a named decision owner, delivery lead and escalation path.
Operating framework
A lightweight management model for assigning ownership, testing controls, strengthening evidence and making enterprise-security decisions on a repeatable cadence.
01 · Design principles
Use the model as a decision aid. Tailor it to organizational context, applicable law, contractual obligations and the professional standards relevant to each domain.
01
Every domain and material lifecycle gap has a named decision owner, delivery lead and escalation path.
02
Assess what can be demonstrated today—not what a policy says should happen or what a future project might deliver.
03
Apply deeper assurance where criticality, exposure, regulatory duties or credible harm justify it.
04
Bring security, operations, people, legal, technology, safety and continuity into the same operating picture.
05
Use exercises, incidents, inspections and control tests to reveal weak coordination and false confidence.
06
Turn every material event, near miss and review finding into owned corrective action and verified learning.
02 · Maturity
Score each lifecycle phase independently. A domain is only as resilient as its weakest material phase, so do not average away a critical blind spot.
Material exposure is not consistently known, owned or addressed.
Response depends on individuals and is activated mainly after events.
Minimum controls, ownership and escalation paths are documented.
Controls operate consistently and are tested with credible evidence.
Signals, learning and changing conditions continuously shape decisions.
03 · Assessment
The maturity level describes the observed capability. The confidence score describes how strongly the assessment is supported. Report both; never let a polished score hide weak evidence.
Current records, configurations, logs, inspections or observed practice.
Review by a competent party outside the delivery owner’s direct line.
Evidence from a recent test, incident, exercise or operational disruption.
This scoring model is an original, non-normative management aid. It does not certify compliance with any cited standard and should be adapted before formal assurance use.
04 · Governance
Keep oversight distinct from delivery and independent challenge. Small organizations may combine roles, but decision rights and conflicts should remain explicit.
BOARD / OVERSIGHT
EXECUTIVE SPONSOR
FRAMEWORK LEAD
DOMAIN OWNER
INDEPENDENT ASSURANCE
WORKFORCE / PARTNERS
05 · Operating cadence
The cadence below is a baseline. Increase frequency for high-hazard operations, major transformation, elevated threat conditions or active remediation.
WEEKLY
Triage material incidents, near misses, threat changes, control failures and overdue emergency actions.
MONTHLY
Review exposure, evidence, dependencies, action progress and decisions that require cross-functional support.
QUARTERLY
Challenge systemic gaps, resource trade-offs, residual risk and preparedness for priority scenarios.
ANNUALLY
Refresh context, materiality, ownership, source mappings, maturity targets and the assurance plan.
06 · Adoption path
Begin with the scenarios and dependencies that could cause the greatest harm. Do not attempt to score every entry before ownership and assessment criteria are agreed.
Name the sponsor and owners. Select priority domains. Agree materiality, terms and escalation routes.
Assess priority lifecycle phases. Record evidence and uncertainty. Fund urgent gap reduction.
Test cross-domain scenarios. Validate decision rights, communications, dependencies and recovery assumptions.
Complete independent challenge, refresh targets and publish an evidence-backed improvement roadmap.
Apply the framework
Use the matrix to frame the exposure, compare lifecycle coverage and identify the next decision that needs an owner.
Open the matrix