PCI DSS 4.0
Req 2: Secure Configurations

PCI DSS 4.0 2.2.3: Primary functions isolated or secured to highest level

Primary functions requiring different security levels are managed so that only one primary function exists per component, or different security levels are isolated, or all are secured to the highest level.

Other controls in Req 2: Secure Configurations

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

PCI DSS 4.0 2.2.3 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 249 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202255.8% covered · 110 gapsIf you hold FedRAMP Moderate55.4% covered · 111 gapsIf you hold NIST SP 800-53 Rev 553.4% covered · 116 gapsIf you hold ISO 27002:202248.6% covered · 128 gapsIf you hold CIS Controls v843% covered · 142 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.141% covered · 147 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 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls