Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Conditional Level 2
Governance, Ownership & Risk

Conditional Level 2

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Governance, Ownership & Risk

Conditional Level 2 is a limited CMMC status that allows certain organisations to proceed while some eligible control gaps remain open. It depends on meeting the minimum readiness thresholds, including an acceptable SPRS score, and it still requires completion of all permitted POA&Ms within the defined deadline.

What Conditional Level 2 Means in CMMC

Conditional Level 2 is not a full pass, it is a constrained status that recognises partial readiness while still leaving some eligible control gaps open. The key idea is that an organisation has met the minimum threshold to continue, but the remaining gaps are time-bound and must be closed within the permitted POA&M window.

This makes the status operationally useful but fragile. It signals that compliance posture is acceptable for now, yet the organisation is still carrying acknowledged weaknesses that can affect contract eligibility, audit confidence, and security assurance if they are not remediated on schedule.

Readiness Thresholds and POA&M Limits

Conditional Level 2 depends on satisfying the minimum entry criteria, including the required SPRS score, and on limiting open items to the specific weaknesses that are permitted to remain on a POA&M. It is therefore a threshold-based state, not an open-ended exception process.

The practical consequence is that the organisation must treat the conditional status as temporary. Each approved gap has to be understood, owned, and tracked against the deadline, because once the POA&M period expires the status can no longer stand on deferred remediation alone.

Why Conditional Status Exists

The status exists to distinguish between organisations that are not ready at all and those that are close enough to proceed while finishing narrowly defined remediation. In that sense, it acknowledges that security programmes often mature in phases, especially where control implementation spans multiple systems or business units.

It also creates accountability. A conditional state is only meaningful when the remaining gaps are visible, bounded, and actively managed, rather than being treated as a general exemption from the underlying control requirements.

How Organisations Should Interpret It

Conditional Level 2 should be read as a compliance checkpoint, not a destination. It tells reviewers that the organisation has not fully completed the control set, but has reached a limited status that can support continued progress if remediation stays on track.

For practitioners, the important question is whether the open items are genuinely eligible for deferment and whether the team can finish them before the deadline without creating new exposure elsewhere. If either assumption is weak, the conditional status becomes a warning sign rather than a comfort signal.

Risk and Threat Considerations

Conditional Level 2 carries a real exposure risk because unresolved control gaps still exist while the organisation is operating under a limited compliance status. If those gaps involve access control, monitoring, configuration, or credential handling, they can create a window in which adversaries benefit from known weaknesses before remediation is complete.

Failure mechanism: Deferred remediation leaves a gap between “acceptable for now” and “actually fixed,” and that gap can be exploited if the weakness is reachable or if the organisation loses track of the POA&M deadline.

Impact: The result can be control failure, loss of assurance, missed deadlines, and, in the worst case, preventable compromise or loss of eligibility if the organisation cannot close the gaps in time.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.RM-01 — Risk Management StrategyConditional status depends on managing residual control gaps and deadlines.
ID.AM-01 — Physical Devices and Systems InventoryReadiness depends on knowing which assets and systems still carry open control gaps.
PR.AA-01 — Identities and Credentials Are Issued, Managed, Verified, Revoked, and AuditedCMMC gaps often include access and credential controls that must be closed before full compliance.
Recommendation — Track remaining POA&M items as risk exceptions with explicit owners and closure dates. Inventory affected systems so open gaps are tied to specific assets and owners. Close access and credential gaps with verified lifecycle management and audit evidence.
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareConditional readiness often hinges on unresolved configuration weaknesses.
Recommendation — Harden configurations and verify closure of deferred configuration weaknesses.
ISO/IEC 27001:2022A.8.8 — Management of technical vulnerabilitiesPOA&M-backed gaps map to vulnerability handling and time-bound remediation.
Recommendation — Maintain a remediation record and close technical vulnerabilities within the approved timeline.

Practitioner Guidance

Governance implication: Treat the conditional status as a managed exception state with explicit ownership, milestone tracking, and deadline discipline. The organisation should know exactly which controls remain open, why they were deferred, and what evidence will prove closure.

What to watch for: Watch for POA&M items that are too broad, repeatedly extended, or disconnected from a clear remediation owner, because those are the cases most likely to turn a temporary status into a persistent control weakness.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org