Enduring Exception
Under CMMCCybersecurity Maturity Model Certification and NIST SP 800-171, a special circumstance or system where full remediation of a security requirement is not feasible, such as medical devices, test equipment, operational technologyProgrammable systems or devices that interact with the physical environment, or manage devices that do, by monitoring or controlling devices, processes and events. Examples include industrial control systems, building management systems, fire control systems and physical access control mechanisms. or systems that replicate fielded configurations. It is documented in the system security planA formal document describing a system's security requirements and the controls in place or planned to meet them, including its boundary, environment and connections. CMMC incorporates NIST SP 800-171 Revision 2, where the SSP requirement is 3.12.4; Revision 3 uses identifier 03.15.02. and does not require an operational plan of actionUnder CMMC, a document required by security requirement CA.L2-3.12.2 that identifies temporary vulnerabilities and deficiencies and how the organisation will mitigate, correct or eliminate them. It is distinct from an assessment POA&M subject to the conditional-status 180-day closeout mechanism; operational plans can still set appropriate remediation milestones and completion dates. under the CMMCCybersecurity Maturity Model Certification definition.
Where you meet it
Specialised assets in CMMCCybersecurity Maturity Model Certification and NIST SP 800-171 scopes.
Used in
Related terms
A term on your desk with a deadline attached?
Thirty minutes on what it means for you and what to do first.