Cross-Framework Mapping

FedRAMP ModeratevsPCI DSS 4.0

See exactly how FedRAMP Moderate controls map to PCI DSS 4.0. Pre-computed mappings, identified gaps, and coverage analysis.

872
Controls Mapped
0
Gaps Found
82%
Coverage

A reviewed coverage crosswalk for this pair is available. See which PCI DSS 4.0 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

FedRAMP Moderate maps to PCI DSS 4.0 with 82% coverage across 265 directly mapped controls. Analysis of 323 FedRAMP Moderate controls identifies 58 compliance gaps, primarily concentrated in CP - Contingency Planning.

Source: TheArtOfService Knowledge Graph | 323 controls analysed | 868 frameworks | 315K+ cross-framework mappings

Control Mappings

Showing 20 of 872 mapped controls across 18 domains. Sign up to explore all 315K+ mappings across 868 frameworks.

AC - Access Control(20 mappings)

AC-1Policy and Procedures6 targets
→1.1.11.1.1 Requirement 1 policies and procedures governed
→12.1.112.1.1 Overall information security policy established and disseminated
→12.1.212.1.2 Security policy reviewed annually and updated as needed
→7.1.17.1.1 Requirement 7 policies and procedures maintained
→7.1.27.1.2 Requirement 7 roles and responsibilities assigned
→pci-dss-4-0::8.1.18.1.1 Requirement 8 policies and procedures maintained
AC-11Device Lock
→8.2.88.2.8 Re-authentication after 15 minutes idle
AC-12Session Termination
→8.2.88.2.8 Re-authentication after 15 minutes idle
AC-17Remote Access7 targets
→1.3.11.3.1 Inbound CDE traffic restricted
→1.4.41.4.4 Cardholder data stores not reachable from untrusted networks
→8.2.18.2.1 Unique ID assigned to every user
→8.2.38.2.3 Service provider unique factors per customer
→8.2.78.2.7 Third-party remote access accounts controlled
→8.3.18.3.1 Access authenticated with at least one factor
→8.4.38.4.3 MFA for remote access that could reach CDE
AC-17(1)Monitoring and Control4 targets
→10.2.110.2.1 Audit logging enabled on all system components
→10.4.1.110.4.1.1 Automated mechanisms used for audit log review
→11.5.111.5.1 IDS/IPS monitoring of CDE traffic
→8.4.38.4.3 MFA for remote access that could reach CDE
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
→2.2.72.2.7 Non-console administrative access encrypted

+852 more mappings

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

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

The FedRAMP Moderate to PCI DSS 4.0 crosswalk

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

FedRAMP Moderate into PCI DSS 4.0
49.3%

138 of 280 PCI DSS 4.0 controls are evidenced by work you have already done for FedRAMP Moderate. 142 are genuine gaps.

PCI DSS 4.0 into FedRAMP Moderate
51.1%

165 of 323 FedRAMP Moderate controls are evidenced by work you have already done for PCI DSS 4.0. 158 are genuine gaps.

FedRAMP Moderate to PCI DSS 4.0
$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 82% in the header counts how many FedRAMP Moderate controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many PCI DSS 4.0 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

Cross-framework mappings across 868 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • ✓ 868 framework browser
  • ✓ Cross-framework mappings (315K+)
  • ✓ 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 FedRAMP Moderate and PCI DSS 4.0?

FedRAMP Moderate has 323 controls across its framework, while PCI DSS 4.0 covers 280 controls. Direct mapping analysis identifies 265 overlapping controls (82% coverage). The frameworks diverge most significantly in CP - Contingency Planning, where 12 FedRAMP Moderate controls have no direct PCI DSS 4.0 equivalent.

How many controls map between FedRAMP Moderate and PCI DSS 4.0?

Of 323 total FedRAMP Moderate controls, 265 map directly to PCI DSS 4.0 controls, representing 82% coverage. The remaining 58 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping FedRAMP Moderate to PCI DSS 4.0?

58 FedRAMP Moderate controls have no direct equivalent in PCI DSS 4.0. The highest concentration of gaps is in CP - Contingency Planning with 12 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 FedRAMP Moderate and PCI DSS 4.0?

The domain with the highest gap count is CP - Contingency Planning (12 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.