A security maturity assessment rates each domain of a program on a scale, usually from ad hoc to optimized. The natural next step is to sort the domains by score and start at the bottom. That is a mistake. A maturity score tells you where a gap is. It does not tell you how much that gap is costing you right now, and the two are often different.

This article explains why the lowest score is not always the first priority, gives a method for ranking remediation by risk and urgency, and walks through a worked example in which Awareness Training and Incident Response scored the same and ended up at opposite ends of the list.

What a maturity score measures

Maturity models rate process quality, not threat exposure. A simple five-level model asks whether a control is ad hoc, documented, repeatable, managed, or optimized. Two domains can score 1 for the same reason, no documented process, while one of them is the thing standing between the organization and an undetected breach and the other is not.

Maturity models also treat domains as equal. A model with 17 domains gives you 17 scores and no weights. Weighting is the assessor’s job, and it comes from risk.

What priority measures

NIST SP 800-30 Rev. 1 describes risk as a function of the likelihood that a threat event occurs and the impact if it does. Priority adds a third element, urgency: how soon the gap is likely to be exploited and how fast the harm compounds once it is. A domain scores high on priority when its gap is exposed to a current threat, affects sensitive data or revenue, and would let an incident run unnoticed.

Maturity score compared with remediation priority
Maturity scoreRemediation priority
AsksHow well defined and repeatable is this process?What happens if we do not fix this next?
InputDocumentation, evidence of practice, consistencyThreat likelihood, business impact, data sensitivity, time to harm
ComparesThis domain against an idealThis domain against every other domain
Changes whenThe process improvesThe threat landscape or the business changes
Used forMeasuring progress over timeDeciding what to fund this quarter

A method for ranking

  1. Score every domain first, so that the list is complete before you argue about order. A ranking built from a partial assessment is a guess.
  2. For each domain, write one sentence on what the gap exposes. “No incident response process means a breach could run for weeks unnoticed.” “No awareness training means staff are more likely to click a phishing email.” The sentence makes the exposure concrete.
  3. Weigh exposure against the business. What data does the organization hold, what revenue depends on which systems, what regulation applies? A retailer storing card data weighs logging and boundary control higher than a firm with no customer data.
  4. Add urgency. Gaps that let an attack succeed silently rank above gaps that make an attack somewhat more likely. Detection and response gaps are usually the most urgent because every other control is assumed to fail eventually.
  5. Check the top of the list for dependencies. Some fixes unlock others: you cannot review logs you are not collecting, and you cannot respond to events you cannot detect.

Worked example: same score, opposite priority

The case study linked below assessed an AWS-hosted online retailer that stores customer payment data. The company had made real technical progress: Active Directory with job-based access, a new firewall, antivirus on every device, backups, and remote monitoring. The assessment rated all 17 domains of the model it used, which was the earlier 17-domain Cybersecurity Maturity Model Certification (CMMC) structure, on a simple maturity scale.

Five domains scored 1, the weakest level: Incident Response, Risk Management, Awareness and Training, Media Protection, and Personnel Security. Sorting by score would have put all five at the top in no particular order. Ranking by risk produced a different list. Incident Response went first, because the company had no way to detect or respond to an attack, so a breach of stored card data could go unnoticed. Risk Management went second, because without it there was no structured way to decide anything else. Audit and Accountability, which had scored a 2, went third, because logging is what makes detection possible.

Awareness and Training, with the same score of 1 as Incident Response, went last of 17. Not because it does not matter, but because training reduces the likelihood of some attacks while incident response limits the damage of all of them. With stored payment data and no detection, damage limitation was the urgent problem.

Domains with the same maturity score and their final priority in the worked example
DomainMaturity scorePriority (of 17)Why
Incident Response11No ability to detect or respond; stored card data at risk
Risk Management12No structured way to identify and rank threats
Audit & Accountability23Logging is the precondition for detection
Media Protection115Low exposure relative to the network and data gaps
Awareness & Training117Reduces likelihood of some attacks; does not limit damage

Turning priorities into work

A ranked list still needs a next step per item. In the example, four priority domains were mapped to the practice in the model that represented the next best move: detect and report events, create and retain audit logs, control communications at system boundaries, and manage backups. Each practice then got concrete actions: define what counts as a security event, aggregate logs centrally, segment the database holding customer data, test restores.

The models change; the method does not. The CMMC program itself has moved on from the 17-domain structure. As of the Department of War’s July 2026 announcement, Phase II of CMMC is suspended and the program is under review, with Level 1 self-assessments against the 15 requirements of FAR 52.204-21 and Level 2 self-assessments against the 110 requirements of NIST SP 800-171 Rev. 2 remaining in place. Whatever model you rate against, the ranking still comes from exposure and urgency, not from the score.

Signs the ranking is wrong

  • The priority order is the score order. Either the organization has unusually uniform risk, or nobody applied risk.
  • Detection and response are not in the top five. Almost every organization that has not built them should start there.
  • The top item depends on a lower item. Log review above log collection is a sequencing error.
  • The list ignores what the organization sells. Priority should read differently for a hospital, a retailer, and a software vendor.
  • Nothing is ranked last. A list where everything is a priority is a list where nothing is.

Frequently asked questions

What is a security maturity assessment?
A structured rating of each domain of a security program on a scale of process quality, such as ad hoc, documented, repeatable, managed, and optimized. It measures how well defined and consistent the practices are, not how exposed the organization is.
Should I fix the lowest-scoring domain first?
Not automatically. Rank by what the gap exposes, how sensitive the affected data or systems are, and how fast harm would compound. Detection and response gaps usually outrank others with the same score.
How do you prioritize security remediation?
Score every domain, write what each gap exposes, weigh that exposure against the business and its data, add urgency, then check the top items for dependencies such as log collection before log review.
Is CMMC still in effect?
As of July 2026 the Department of War suspended Phase II of CMMC pending a review. Phase I self-assessment requirements remain in place: Level 1 against 15 FAR requirements and Level 2 against the 110 requirements of NIST SP 800-171 Rev. 2.

Sources