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

What this control requires

Maintain a current, complete, accurate, and available system component inventory using automated mechanisms. Track hardware, software, firmware, and virtual machines to minimize risks. This control supports the Automation capability within the Configuration Management family.
— NIST SP 800-53 Rev. 5, Control CM-8(2)

In plain English

Maintain a current, complete, accurate, and available system component inventory using automated mechanisms. In practice, this means you can prove you security 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-8(2)) 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.

Asset Inventory

AWS. AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub.

Azure. Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting.

GCP. Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance.

Endpoints. Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources.

Operational checklist

  • Security. Document the trigger, the owner and the cadence.
  • Configuration. Document the trigger, the owner and the cadence.
  • Maintenance. Document the trigger, the owner and the cadence.
  • Protection. Document the trigger, the owner and the cadence.
  • Hardware. Document the trigger, the owner and the cadence.
  • Scope: management, system, protection, configuration, hardware, software, firmware, virtual machines.

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: Automated Maintenance.

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
  • Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start.

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 protectionasset inventory