NIST SP 800-53 Rev. 5·Control CM-7(9)·high·Component: Configuration Management

What this control requires

Identify authorized hardware, prohibit unauthorized connections, and periodically review/update the authorized list. Restrict non-essential hardware using endpoint security and network access controls to minimize the attack surface. This control supports the Inventory capability within the Configuration Management family.
— NIST SP 800-53 Rev. 5, Control CM-7(9)

In plain English

Identify authorized hardware, prohibit unauthorized connections, and periodically review/update the authorized list. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

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 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Configuration Management, the assessor will trace your implementation back to the catalogue reference (Control CM-7(9)) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Network Security

AWS. VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation.

Azure. NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift.

GCP. VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services.

Operational checklist

  • Access. Document the trigger, the owner and the cadence.
  • Restrict. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Configuration. Document the trigger, the owner and the cadence.
  • Network. Document the trigger, the owner and the cadence.
  • Scope: management, controls, protection, configuration, hardware, review, access controls, capability.

Evidence to collect

  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Prohibiting The Use Of Unauthorized Hardware.

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
  • Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.

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-53 Rev. 5

References

Topics: endpoint securityendpoint protectionnetwork securitypatch management