NIST SP 800-171 Rev. 3·Requirement 3.7.4·high·Component: Maintenance

What this control requires

This control ensures that the use of system Maintenance tools is approved, controlled, and monitored. It requires checking diagnostic and test media for malicious code before use and prevents the removal of Maintenance equipment containing Controlled Unclassified Information (CUI) by sanitizing or retaining it within the facility. This control supports the Maintenance Tool Management capability within the Maintenance (3.7) family.
— NIST SP 800-171 Rev. 3, Requirement 3.7.4

In plain English

This control ensures that the use of system Maintenance tools is approved, controlled, and monitored. In practice, this means you can prove you information management-level controls on a defined cadence.

Why it matters

DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement.

Within Maintenance, the assessor will trace your implementation back to the catalogue reference (Requirement 3.7.4) and look for objective evidence on the latest two assessment cycles.

How to implement

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Physical Security

Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

Operational checklist

  • Information. Document the trigger, the owner and the cadence.
  • System. Document the trigger, the owner and the cadence.
  • Maintenance. Document the trigger, the owner and the cadence.
  • Media. Document the trigger, the owner and the cadence.
  • Physical. Document the trigger, the owner and the cadence.
  • Scope: management, cui, security, tools, maintenance, code, development.

Evidence to collect

  • Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Maintenance Tools.

Common pitfalls

  • CI security checks set to warn-only; the merge button is faster than the security feedback.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in NIST SP 800-171 Rev. 3

References

Topics: application securitycode review testingsecure developmentdevsecopsphysical security