PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.5.1: 12.5.1 Inventory of in-scope system components

The entity must keep a current inventory covering every system component within PCI DSS scope, with a description of each component's function or use. The guidance suggests making in-scope components clearly identifiable within a broader asset inventory, including container images that could be spun up, and giving the inventory an owner. Customized approach objective: every system component within PCI DSS scope is identified and known.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • CM-2 Baseline Configuration
  • CM-8 System Component Inventory
  • CM-8(1) Updates During Installation and Removal
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • RA-9 Criticality Analysis (RA-9)

FedRAMP Moderate · 5 controls

  • CM-2 Baseline Configuration
  • CM-8 System Component Inventory
  • CM-8(1) Updates During Installation and Removal
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • RA-9 Criticality Analysis (RA-9)

SOC 2 · 5 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.4 CC6.4 Restricting physical access to facilities and assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CIS Controls v8 · 4 controls

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory
  • CIS-2.1 Establish and Maintain a Software Inventory
  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-5.5 Establish and Maintain an Inventory of Service Accounts

ISO 27701:2019 · 4 controls

  • 6.3.1 Internal organization
  • 6.5 Asset management
  • 6.5.1 Responsibility for assets
  • 7.2.8 Records related to processing PII

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
  • 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-07 Inventories of data and corresponding metadata for designated data types are maintained

NIST SP 800-53 Rev 5 · 4 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • 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

Australia Consumer Data Right - Banking (CDR) · 2 controls

  • AUCDR-IS-3 Securely manage information assets over their lifecycle
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

NIST SP 800-172 · 2 controls

  • 3.4.1e Authoritative Source for Software and Firmware
  • 3.4.3e Automated Inventory of System Components

NIST SP 800-66 Rev 2 · 2 controls

APRA CPS 234 · 1 control

  • CPS234-20 Information Asset Classification

Azure Security Benchmark · 1 control

C5 (Germany) · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 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

NIS2 Directive · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P1-3.2.2 P1-3.2.2 Current inventory of 3DS system components

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 Req 12: Information Security Policies

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.5.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls