This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Maturity assessments: where does your security really stand, and where should it be?
This quarter, pick one model that fits your company and run a five-week assessment that rates each outcome only on evidence you sampled. Set a target per function from your risks, not the top level everywhere, and show management gaps and decisions, not one maturity number.
If you only do five things
Pick one model and keep it.
Use the model your regulator or sector expects; otherwise NIST CSF 2.0 Profiles with the CIS Controls underneath. Keep the model, scale and scope from year to year, so results compare.
Scope by business service.
Assess the services the company can't do without, with their cloud tenants, OT, suppliers and subsidiaries. A CSF Profile can cover the whole organization or one part, such as the financial systems1.
Rate only what you saw working.
Interview the people who run each control, then check a sample: settings, tickets, a restore record. NIST's assessment methods are examine, interview and test4. No evidence means not achieved.
Set a target per function.
Decide where each function must be from your risks and duties. NIST encourages higher Tiers when risks or mandates are greater or a cost-benefit analysis supports it1.
Report gaps and decisions, not a score.
Show current against target per function, the gaps that matter and what you need decided. A "level 3" is a set of qualities, not a numerical value, as NIST notes5.
Choose a model by company type
Do you run UK essential services?
Use the NCSC CAF v4.0: 41 outcomes, judged achieved, partially achieved or not achieved6, against the cross-sector Core Profile8.
Do you run energy or OT?
Use C2M2 v2.1: 356 practices in 10 domains, for IT and OT. DOE's tools are free to any organization, and its self-evaluation is designed to cover one function in a day9.
A German company under 50 staff?
Book a CyberRisikoCheck (DIN SPEC 27076): an IT service provider checks 27 requirements in a 1 to 2 hour interview and reports a score and ranked recommendations18. It rests on your answers, so ask for spot checks.
Is your ISMS built on IT-Grundschutz?
Use the IT-Grundschutz-Check: interviews plus spot checks against each requirement15. Grundschutz++ marks each requirement met, not met or not applicable, with evidence16.
Everyone else?
Build CSF 2.0 Current and Target Profiles in NIST's free template2, with CIS Controls as the checklist: IG1's 56 safeguards for small firms, IG2's 74 more once you have IT staff and sensitive data11.
Run one in five weeks
Week 1: what's in scope, and who answers?
List services, sites, tenants, OT and suppliers, in the fewest assessments that still give an accurate picture9. Name one contact per area15.
Weeks 2 and 3: interviews and samples.
Interview in pairs, one asking and one taking notes15. For each outcome, collect one record and check one live sample.
Week 4: calibrate and set targets.
Review the ratings with the interviewees9 and one person outside the control's team. Agree targets with management.
Week 5: report and hand over.
Present gaps and decisions; the security program sheet turns gaps into a roadmap.
Evidence over self-scoring
- Write the rule first. In the CAF, one "not achieved" indicator normally decides the rating; "achieved" normally needs every achieved indicator6.
- Sample, don't ask. Check five leavers' accounts, three servers' patch levels and the last restore record. The BSI suggests checking interview answers against documents, sites and system settings15.
- Record each rating's source. Grundschutz++ assigns evidence to each measure and, for automated checks, records tool, time and result16.
- Count coverage where you can. CIS's Assessment Specification defines measures and metrics per safeguard, such as how many endpoints implement it12.
Current and target profiles
- One row per outcome. NIST's template has columns for practices, status, rating, priority and goals2. Add evidence and an owner.
- Targets per function. Set Tiers overall or per Function or Category, not per Subcategory3. Tiers rate the rigor of risk governance and management1; per-outcome ratings show whether practices work.
- A floor everywhere. C2M2 is built so every company can reach MIL1 in all domains9. For US critical infrastructure, CISA's CPG 2.0 sets a foundational level10. Go higher where your risks need it.
- Reassess every 12 months and, as DOE advises, after major business, technology or threat changes9. NIS2 entities in Germany need policies and procedures to assess their measures' effectiveness (BSIG § 30(2) no. 6)20.
Presenting results to management
- No average. An overall 2.7 hides a zero in Recover. Show current and target side by side for each function.
- Say how you know. Name the model version, profile and scope, whether it was self-assessed or independently reviewed, and its limits, as the NCSC asks for CAF results7.
- Tie each top gap to a risk. Give its entry in the risk register (see the risk register sheet), the cost to close it and your recommendation.
- Ask for a decision. Fund it, accept it with an end date where the law allows, or defer it. Track it on the security metrics sheet's quarterly page.
- Show what moved. Next year, show what changed and why, on the same scale.
External assessor or your own team
- Run the yearly cycle yourself. Your people know where the evidence is; C2M2 is built for facilitated self-evaluation9.
- Buy independence where it counts. Independent audit or testing generally gives more confidence, the NCSC says7. Use it every 2 to 3 years and when customers or regulators rely on the result, never from the firm selling the fixes.
- Keep reviewers out of the line. Under 2024/2690, digital providers need reviewers with audit competence; staff reviewers must sit outside the reviewed area's line of authority19. Others can copy the rule.
- Check the licenses. The CIS Controls are free for any company improving its own security; a consultant who assesses you with them or CSAT needs a CIS commercial license, such as SecureSuite membership1314.
What changed in 2026
- The UK set a cross-sector CAF minimum. The NCSC's Core Profile, published 30 October 2026, sets the expected level for each CAF v4.0 outcome against moderately sophisticated attackers8.
- Grundschutz++ drops "partially". BSI-Standard 300-1, dated 20 October 2026, marks each requirement met, not met or not applicable16; the IT-Grundschutz-Check also allowed partially15. The BSI plans performance indicators for the method's requirements by 31 March 202717.
What you can skip
- A second framework for comparison. Map once through informative references to ISO/IEC 27001 or SP 800-532.
- Tiers for every Subcategory. NIST says Function or Category level gives a better picture3.
- Peer benchmark scores. Ratings from different assessors, scopes and scales don't compare. Compare yourself with last year.
- A maturity platform before the first cycle. NIST's spreadsheet template and your ticket system will do2.
Mistakes that cost the most
- Scoring the paper. The BSI rates "yes" only for measures implemented fully, effectively and appropriately15, not for a signed policy.
- Chasing the top level everywhere. MIL3 or Tier 4 costs most where risk is lowest; DOE calls the top MIL in all domains not typically optimal9.
- Buying a score. Tools that turn questionnaires or external scans into a maturity number measure answers or the perimeter, not practice.
- Taking "implemented" for "works". CIS's specification checks only whether a safeguard is implemented12. Test a restore or an alert.
- Changing the yardstick. A new model, scale or scope breaks the trend.
What this looks like at your size
Small team, no security staff
- In Germany, book a CyberRisikoCheck18 yearly, ideally not from the provider that runs your IT.
- Elsewhere, rate yourself against CIS IG1 with one piece of evidence per safeguard.
- Take the managing directors through the top five gaps in one hour.
Growing, with IT or security staff
- Build Current and Target Profiles per CSF Function in NIST's template, with CIS IG2 as the checklist.
- Have someone outside IT operations, such as internal audit, recheck a sample.
- Finish the assessment before budget planning.
Enterprise or regulated
- Use the model your regulator expects, such as the CAF Core Profile for UK essential services. In energy and OT, use C2M2.
- Assess each subsidiary or business unit with the same scale and evidence rules.
- Report independent reviews to management, as 2024/2690 requires of digital providers19.