# NIST SP 800-171 Rev. 3 3.7.6 — Maintenance Personnel - Source: https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-7-6-maintenance-personnel - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-171 Rev. 3 Requirements](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3) › Maintenance — §3.7 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-171 Rev. 3**·Requirement `3.7.6`·high·Component: **Maintenance** ## What this control requires > This control requires establishing a process for authorizing Maintenance personnel, maintaining a list of authorized personnel or organizations, and verifying that non-escorted personnel have the necessary access authorizations. It also mandates the designation of qualified personnel to supervise Maintenance activities for those without the required access. This control supports the Authorization Management capability within the Maintenance (3.7) family. > > — NIST SP 800-171 Rev. 3, Requirement 3.7.6 ### In plain English This control requires establishing a process for authorizing Maintenance personnel, maintaining a list of authorized personnel or organizations, and verifying that non-escorted personnel have the necessary access authorizations. In practice, this means you can prove you access 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.6) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Authorized.** Document the trigger, the owner and the cadence. - **Maintenance.** Document the trigger, the owner and the cadence. - **Personnel.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Scope:** management, maintenance, personnel, access authorizations, authorization. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Maintenance Personnel. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**NIST SP 800-53 Rev. 5 MA-5** — Maintenance Personnel](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ma-5-maintenance-personnel) - [**HIPAA (45 CFR Part 164) 164.308(a)(4)(ii)(B)** — Information Access Management - Access Authorization](https://support.icompaas.com/compliance/hipaa/164-308-a-4-ii-b-information-access-management-access-authorization) - [**ISO/IEC 27001:2022 A.7.13** — Equipment maintenance](https://support.icompaas.com/compliance/iso-27001-2022/a-7-13-equipment-maintenance) - [**SOC 2 (2017 TSC) CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters) ## Related controls in NIST SP 800-171 Rev. 3 - [**Requirement 3.7.1** — Recategorized as NCO.](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-7-1-recategorized-as-nco) - [**Requirement 3.4.8** — Authorized Software - Allow by Exception](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-8-authorized-software-allow-by-exception) - [**Requirement 3.1.5** — Least Privilege](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-5-least-privilege) - [**Requirement 3.15.1** — Policy and Procedures](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-15-1-policy-and-procedures) - [**Requirement 3.3.4** — Response to Audit Logging Process Failures](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-4-response-to-audit-logging-process-failures) - [**Requirement 3.1.1** — Account Management](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-1-account-management) ## References - [NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3](https://csrc.nist.gov/pubs/sp/800/171/r3/final) - Catalogue identifier: `Requirement 3.7.6` Topics: governance riskpolicy management ## Related compliance guidance - [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): Start with the full NIST SP 800-171 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The catalogue 800-171 is tailored from, and the basis of the FedRAMP Moderate baseline your cloud providers must meet for CUI. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): If commercial customers ask for a certificate as well, most 800-171 controls can be evidenced once and mapped to Annex A.