MNT-02: Maintenance Operations
Mechanisms exist to develop, disseminate, review & update procedures to facilitate the implementation of maintenance controls across the enterprise.
Renumbered: Formerly MNT-01 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, MNT-02 was Controlled Maintenance. That control is now MNT-03.
Control Question: Does the organization develop, disseminate, review & update procedures to facilitate the implementation of maintenance controls across the enterprise?
General (30)
| Framework | Mapping Values |
|---|---|
| CSA IoT SCF 2 | OPA-01 |
| GovRAMP | MA-01 |
| GovRAMP Low | MA-01 |
| GovRAMP Low+ | MA-01 |
| GovRAMP Moderate | MA-01 |
| GovRAMP High | MA-01 |
| ISO 27002 2022 | 7.13 |
| ISO 27017 2015 | 11.2.4 |
| ISO 27018 2025 | 7.13 |
| NIST 800-53 R4 | MA-1 |
| NIST 800-53 R5.2 | MA-01 |
| NIST 800-53B R5 (low) (source) | MA-01 |
| NIST 800-53B R5 (moderate) (source) | MA-01 |
| NIST 800-53B R5 (high) (source) | MA-01 |
| NIST SP 800-66 R2 | 164.310(a) 164.310(d) |
| NIST 800-82 R3 | MA-01 |
| NIST 800-82 R3 LOW OT Overlay | MA-01 |
| NIST 800-82 R3 MODERATE OT Overlay | MA-01 |
| NIST 800-82 R3 HIGH OT Overlay | MA-01 |
| NIST 800-161 R1 | MA-1 |
| NIST 800-161 R1 C-SCRM Baseline | MA-1 |
| NIST 800-161 R1 Flow Down | MA-1 |
| NIST 800-161 R1 Level 1 | MA-1 |
| NIST 800-161 R1 Level 2 | MA-1 |
| NIST 800-161 R1 Level 3 | MA-1 |
| NIST 800-171 R2 (source) | NFO - MA-1 |
| NIST 800-171 R3 (source) | 03.04.03.c 03.07.04.a 03.07.06.a |
| NIST 800-171A R3 (source) | A.03.04.03.c[01] A.03.07.04.a[01] A.03.07.04.a[02] A.03.07.06.a |
| NIST CSF 2.0 (source) | PR.PS PR.PS-02 PR.PS-03 |
| NIST Privacy Framework 1.0 | PR.MA-P PR.MA-P1 |
US (15)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | MA-1 |
| USA Federal DHS CISA TIC 3.0 | 3.UNI.SADMI |
| USA Federal C2M2 2.1 | ARCHITECTURE-3i |
| USA Federal CJIS Security Policy 6.0 | MA-1 |
| USA Federal 21 CFR Part 11 2025 | 11.10 |
| USA Federal FedRAMP R5 (low) | MA-01 |
| USA Federal FedRAMP R5 (moderate) | MA-01 |
| USA Federal FedRAMP R5 (high) | MA-01 |
| USA Federal FedRAMP R5 (LI-SaaS) | MA-01 |
| USA Federal IRS 1075 2021 | MA-1 |
| USA Federal HIPAA Security Rule NIST SP 800-66 R2 | § 164.310(a)(2)(iv) § 164.310(d)(1) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.310(a)(2)(iv) § 164.310(d)(1) |
| USA Texas DIR SCSC 2.2 2025 | MA-01 |
| USA Texas TX-RAMP Level 1 | MA-01 |
| USA Texas TX-RAMP Level 2 | MA-01 |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA Spain CCN-STIC 825 | op.exp.4 |
| EMEA EU DORA RTS 2024 | Article 8.2(a)(i) |
| EMEA EU NIS2 2022 | Article 21.2(e) |
| EMEA EU NIS2 Annex 2024 | 4.3.2(c) |
APAC (6)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0305 |
| APAC Japan ISMAP | 11.2.4 11.2.4.1 11.2.4.3 11.2.4.5 |
| APAC Malaysia RMiT 2025 | 10.26 |
| APAC New Zealand HISF MLHSP 2023 | HHSP15 HML15 |
| APAC New Zealand HISF Suppliers 2023 | HSUP13 |
| APAC New Zealand NZISM 3.9 | 12.5.3.C.01 12.5.3.C.02 12.5.6.C.01 12.5.6.C.02 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.03.C 03.07.04.A 03.07.06.A |
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
Maintenance (MNT) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with MNT domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Maintenance-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Maintenance controls are primarily administrative in nature (e.g., policies & standards) to manage change control processes associated with maintenance operations. ▪ IT and/or cybersecurity personnel use an informal process to implement secure and timely technology asset-specific maintenance operations, including preventative and reactive maintenance operations.
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 develop, disseminate, review & update procedures to facilitate the implementation of maintenance controls across the enterprise.
Level 4 — Quantitatively Controlled
Maintenance (MNT) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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-02_A01 a maintenance policy is developed and documented.
- MNT-02_A02 the maintenance policy is disseminated to organization-defined personnel or roles.
- MNT-02_A03 maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented.
- MNT-02_A04 the maintenance procedures are disseminated to organization-defined personnel or roles.
- MNT-02_A05 personnel or roles to whom the maintenance policy is to be disseminated is/are defined.
- MNT-02_A06 personnel or roles to whom the maintenance procedures are to be disseminated is/are defined.
- MNT-02_A07 one or more of the following organization-defined criteria is/are selected: {organization-level. mission/business process-level. system-level}.
- MNT-02_A08 an official to manage the maintenance policy and procedures is defined.
- MNT-02_A09 the frequency with which the current maintenance policy is reviewed / updated is defined.
- MNT-02_A10 events that would require the current maintenance policy to be reviewed / updated are defined.
- MNT-02_A11 the frequency with which the current maintenance procedures are reviewed / updated is defined.
- MNT-02_A12 events that would require the maintenance procedures to be reviewed / updated are defined.
- MNT-02_A13 the organization's maintenance policy addresses purpose.
- MNT-02_A14 the organization's maintenance policy addresses scope.
- MNT-02_A15 the organization's maintenance policy addresses roles.
- MNT-02_A16 the organization's maintenance policy addresses responsibilities.
- MNT-02_A17 the organization's maintenance policy addresses management commitment.
- MNT-02_A18 the organization's maintenance policy addresses coordination among organizational entities.
- MNT-02_A19 the organization's maintenance policy addresses compliance.
- MNT-02_A20 the organization's maintenance policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.
- MNT-02_A21 the organization-defined official is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures.
- MNT-02_A22 the current maintenance policy is reviewed / updated organization-defined frequency.
- MNT-02_A23 the current maintenance policy is reviewed / updated following organization-defined events.
- MNT-02_A24 the current maintenance procedures are reviewed / updated organization-defined frequency.
- MNT-02_A25 the current maintenance procedures are reviewed / updated following organization-defined events.
- MNT-02_A26 maintenance management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
- MNT-02_A27 resources (e.g., people, processes, technologies, data and/or facilities) required to support maintenance management operations are identified and provided.
- MNT-02_A28 responsibility and authority for the performance of maintenance management-related activities are assigned to designated personnel.
- MNT-02_A29 personnel performing maintenance management-related activities have the skills and knowledge needed to perform their assigned duties.
Evidence Requirements
- E-MNT-02 Maintenance Plan
-
Documented evidence of a Maintenance Plan. This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
Maintenance
Technology Recommendations
Micro/Small
- IT maintenance program
Small
- IT maintenance program
Medium
- IT maintenance program
Large
- IT maintenance program
Enterprise
- IT maintenance program