Use this discussion checklist to review monitoring, recovery, documentation, automation, security, scaling, cost management and business alignment. Keep evidence with the answers, including recent incidents, restore tests and deployment records.
How scoring works
Each of 15 answers receives the selected editorial value from 0 to 10. Score = sum / 150 Γ 100, rounded to a whole number. Five display bands are used: 0β19 Initial, 20β39 Ad-hoc, 40β59 Defined, 60β79 Managed, 80β100 Optimized. For example, selecting Fair (4) on every question gives 60 / 150 Γ 100 = 40.
These are unvalidated, site-specific labels. They are not NIST tiers, an industry maturity standard, peer percentiles or an estimate of incident probability. A high score does not guarantee low costs, security or recovery. No evidence supports the previous claims about what percentage of businesses occupy each band.
Review individual weaknesses rather than improving the average for its own sake. Automation is useful when it meets your workload needs, not merely because it raises a questionnaire answer. Repeat the same checklist after meaningful changes using consistent evidence.
Sources
NIST CSF 2.0 provides outcomes for governing and managing cybersecurity risk. This short checklist is not a NIST assessment or certification. NISTβs explanation of Framework Tiers distinguishes them from maturity levels. AWS Well-Architected offers a broader architecture review framework. Neither validates this siteβs weights or five bands.
Method and factual claims reviewed 16 October 2026. Sources support the principles described, not the example inputs or this toolβs scoring weights.