MNT-16: Maintain Configuration Control During Maintenance
Mechanisms exist to maintain proper physical security and configuration control over technology assets awaiting service or repair.
Renumbered: Formerly MNT-07 in SCF 2025.4.
Control Question: Does the organization maintain proper physical security and configuration control over technology assets awaiting service or repair?
General (12)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R5.2 | SR-11(02) |
| NIST 800-53B R5 (low) (source) | SR-11(02) |
| NIST 800-53B R5 (moderate) (source) | SR-11(02) |
| NIST 800-53B R5 (high) (source) | SR-11(02) |
| NIST 800-82 R3 | SR-11(02) |
| NIST 800-82 R3 LOW OT Overlay | SR-11(02) |
| NIST 800-82 R3 MODERATE OT Overlay | SR-11(02) |
| NIST 800-82 R3 HIGH OT Overlay | SR-11(02) |
| NIST 800-161 R1 | SR-11(2) |
| NIST 800-161 R1 C-SCRM Baseline | SR-11(2) |
| NIST 800-161 R1 Level 2 | SR-11(2) |
| NIST 800-161 R1 Level 3 | SR-11(2) |
US (4)
| Framework | Mapping Values |
|---|---|
| USA Federal FedRAMP R5 (low) | SR-11(02) |
| USA Federal FedRAMP R5 (moderate) | SR-11(02) |
| USA Federal FedRAMP R5 (high) | SR-11(02) |
| USA Federal IRS 1075 2021 | SR-11(CE-2) |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Maintenance (MNT) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with MNT domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with MNT domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with MNT domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Maintenance-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT personnel, in conjunction with asset custodians, develop and maintain facilitate localized/regionalized procedures to conduct controlled and timely maintenance activities throughout the lifecycle of the Technology Asset, Application and/or Service (TAAS). ▪ Maintenance operations may be centralized for certain locations (e.g., datacenters) and decentralized for other locations, both in terms of change management and execution.
Level 3 — Well Defined
Maintenance (MNT) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with MNT domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with MNT domain capabilities (e.g., maintenance pans) are documented and maintained by process owners. ▪ A centralized Change Management Office (CMO), or similar function, is appropriately staffed and supported to implement and maintain MNT domain capabilities. ▪ Technical procedures (e.g., ITIL change enablement) are utilized along with change management governance capabilities to ensure successful, efficient and secure maintenance operations. ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with MNT domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to maintain proper physical security and configuration control over technology assets awaiting service or repair.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- MNT-16_A01 system components requiring configuration control are defined.
- MNT-16_A02 configuration control over organization-defined system components awaiting service or repair is maintained.
- MNT-16_A03 configuration control over serviced or repaired organization-defined system components awaiting return to service is maintained.
Technology Recommendations
Micro/Small
- Document maintenance activities in a log
Small
- Maintenance log
- Authorized maintenance personnel list
Medium
- Formal maintenance management program
- CMMS or ticketing system
Large
- CMMS (e.g., Maximo, ServiceNow)
- Scheduled maintenance program
- Vendor access controls
Enterprise
- Enterprise CMMS platform
- Automated maintenance scheduling
- Vendor access controls
- Remote access controls