Cross-Framework Mapping

PCI DSS 4.0vsISO 27002:2022

See exactly how PCI DSS 4.0 controls map to ISO 27002:2022. Pre-computed mappings, identified gaps, and coverage analysis.

571
Controls Mapped
0
Gaps Found
99%
Coverage

A reviewed coverage crosswalk for this pair is available. See which ISO 27002:2022 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

PCI DSS 4.0 maps to ISO 27002:2022 with 99% coverage across 247 directly mapped controls. Analysis of 249 PCI DSS 4.0 controls identifies 2 compliance gaps, primarily concentrated in Req 11: Test Security Regularly.

Source: TheArtOfService Knowledge Graph | 249 controls analysed | 685 frameworks | 306K+ cross-framework mappings

Control Mappings

Showing 20 of 571 mapped controls across 12 domains. Sign up to explore all 306K+ mappings across 685 frameworks.

Req 1: Network Security Controls(20 mappings)

1.1.1NSC policies and procedures documented3 targets
iso-27002-2022::5.1Policies for information security
iso-27002-2022::5.37Documented operating procedures
iso-27002-2022::8.20Networks security
1.1.2Roles and responsibilities for Requirement 1
iso-27002-2022::5.2Information security roles and responsibilities
1.2.1NSC configuration standards defined3 targets
iso-27002-2022::5.37Documented operating procedures
iso-27002-2022::8.20Networks security
iso-27002-2022::8.9Configuration management
1.2.2Changes to NSC reviewed and approved
iso-27002-2022::8.32Change management
1.2.3Network diagrams maintained4 targets
iso-27002-2022::5.37Documented operating procedures
iso-27002-2022::5.9Inventory of information and other associated assets
iso-27002-2022::8.20Networks security
iso-27002-2022::8.22Segregation of networks
1.2.4Data flow diagram of account data4 targets
iso-27002-2022::5.9Inventory of information and other associated assets
iso-27002-2022::8.20Networks security
iso-27002-2022::8.22Segregation of networks
iso-27002-2022::8.27Secure system architecture and engineering principles
1.2.5Services, protocols, ports inventoried and justified
iso-27002-2022::8.21Security of network services
1.2.6Security features for insecure services defined3 targets
iso-27002-2022::8.20Networks security
iso-27002-2022::8.21Security of network services
iso-27002-2022::8.8Management of technical vulnerabilities

+551 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 685 frameworks.

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

The PCI DSS 4.0 to ISO 27002:2022 crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which ISO 27002:2022 controls your existing PCI DSS 4.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

PCI DSS 4.0 into ISO 27002:2022
52.7%

49 of 93 ISO 27002:2022 controls are evidenced by work you have already done for PCI DSS 4.0. 44 are genuine gaps.

ISO 27002:2022 into PCI DSS 4.0
48.6%

121 of 249 PCI DSS 4.0 controls are evidenced by work you have already done for ISO 27002:2022. 128 are genuine gaps.

PCI DSS 4.0 to ISO 27002:2022
$299
per framework pair, one time
  • Every evidenced control, with the reasoning behind it
  • Every gap, with what it requires
  • Its level of review stated plainly, not a bare number

Why this page shows two different percentages. The 99% in the header counts how many PCI DSS 4.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many ISO 27002:2022 controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.

A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 685 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 685 framework browser
  • Cross-framework mappings (306K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between PCI DSS 4.0 and ISO 27002:2022?

PCI DSS 4.0 has 249 controls across its framework, while ISO 27002:2022 covers 93 controls. Direct mapping analysis identifies 247 overlapping controls (99% coverage). The frameworks diverge most significantly in Req 11: Test Security Regularly, where 1 PCI DSS 4.0 controls have no direct ISO 27002:2022 equivalent.

How many controls map between PCI DSS 4.0 and ISO 27002:2022?

Of 249 total PCI DSS 4.0 controls, 247 map directly to ISO 27002:2022 controls, representing 99% coverage. The remaining 2 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping PCI DSS 4.0 to ISO 27002:2022?

2 PCI DSS 4.0 controls have no direct equivalent in ISO 27002:2022. The highest concentration of gaps is in Req 11: Test Security Regularly with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between PCI DSS 4.0 and ISO 27002:2022?

The domain with the highest gap count is Req 11: Test Security Regularly (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.