# NIST800 53 MA-2 — Controlled Maintenance

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist80053_ma2_309c240bc6-nist800-53-ma-2-controlled-maintenance
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST](https://support.icompaas.com/support/solutions/62000112528) › [Maintenance](https://support.icompaas.com/support/solutions/folders/f_gen_62000112528_maintenance)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 53 · Control MA-2 · Priority: high · Component: Maintenance

### What this control covers

Schedule, document, and review Maintenance, repair, and replacement of system components per vendor or organizational requirements, including equipment sanitization and off-site activity approval. This control supports the System Maintenance capability within the Maintenance family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `vendor_risk_management` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Controlled Maintenance.

### Quick checklist

-   Security — Management / System
-   Review — Management / System
-   Maintenance — Management / System
-   Chain — Management / System
-   System — Management / System
-   Control — Management / System

### Related articles on this site

-   [NIST 800-171 3.7.3 Ensure equipment removed for off-site maintenance is sanitized of any CUI.](https://support.icompaas.com/support/solutions/articles/62000229306-nist-800-171-3-7-3-ensure-equipment-removed-for-off-site-maintenance-is-sanitized-of-any-cui-)
-   [NIST 800-171 3.12.4 Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to](https://support.icompaas.com/support/solutions/articles/62000229333-nist-800-171-3-12-4-develop-document-and-periodically-update-system-security-plans-that-describe-sy)
-   [CMMC 2.0 CA.2.157 Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to ot](https://support.icompaas.com/support/solutions/articles/62000229719-cmmc-2-0-ca-2-157-develop-document-and-periodically-update-system-security-plans-that-describe-syst)
-   [Source Code Supply Chain Security](https://support.icompaas.com/support/solutions/articles/62000225179-source-code-supply-chain-security)

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): How the 800-53 catalogue, baselines and the Risk Management Framework fit together, and which controls take the most work in the cloud.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If the driver is a DoD or federal contract handling CUI, 800-171 (and CMMC) is the scope you actually need.