FedRAMP High
CM - Configuration Management

FedRAMP High CM-8: System Component Inventory

Develop and document inventory of system components; review and update at least monthly (FedRAMP).

What else in your programme already covers this

This control maps to 48 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 10 controls

  • 1.2.3 Network diagrams maintained
  • 11.2.2 Authorized wireless AP inventory
  • 12.3.4 Hardware and software technologies reviewed annually
  • 12.5.1 Inventory of system components in scope
  • 12.5.2 PCI DSS scope documented and confirmed annually
  • 12.8.1 Third-party service provider inventory
  • 9.4.5 Inventory logs of electronic media
  • 9.5.1.1 POI inventory maintained
  • 5.2.3 Any system components that are not at risk for malware are evaluated periodically to include the following: • A documented list of all system components not at risk for malware. • Identification and evaluation
  • 6.3.2 An inventory of bespoke and custom software, and third-party software components incorporated into bespoke and custom software is maintained to facilitate vulnerability and patch management

CIS Controls v8 · 4 controls

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-2.1 Establish and Maintain a Software Inventory
  • CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems

ACSC Essential Eight · 3 controls

  • NIST-CSF-ID.AM-01 Inventories of hardware managed by the organization are maintained
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram
  • ANSSI-HYG-07 Authorise Network Connection Only for Managed Equipment
  • AM-3 Ensure security of asset lifecycle management
  • ASBv3-AM-1 Track asset inventory and their risks

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-CM-8 System component inventory
  • NIST800-SR-4 Provenance. Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: [organization-defined]
  • CPS230-P25 Information and Technology Capability and Asset Health
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.9 Inventory of information and other associated assets

ISO 27002:2022 · 1 control

  • 5.9 Inventory of information and other associated assets

ISO 27701:2019 · 1 control

  • 6.5.1 Responsibility for assets

ISO/IEC 42001:2023 · 1 control

  • A.4.5 System and computing resources

NIS2 Directive · 1 control

  • Art.21.2.i Human resources security, access control policies and asset management

NIST SP 800-172 · 1 control

  • 3.4.3e Automated Inventory of System Components

NIST SP 800-218 · 1 control

UK Cyber Essentials · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CM - Configuration Management

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High CM-8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

The graph holds this control, the 48 it maps to, and the evidence behind each claim, over MCP and REST.