Cross-Framework Mapping

CMMC 2.0vsAWS Well-Architected Security Pillar

See exactly how CMMC 2.0 controls map to AWS Well-Architected Security Pillar. Pre-computed mappings, identified gaps, and coverage analysis.

172
Controls Mapped
0
Gaps Found
70%
Coverage

A reviewed coverage crosswalk for this pair is available. See which AWS Well-Architected Security Pillar controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

CMMC 2.0 maps to AWS Well-Architected Security Pillar with 70% coverage across 77 directly mapped controls. Analysis of 110 CMMC 2.0 controls identifies 33 compliance gaps, primarily concentrated in Access Control.

Source: TheArtOfService Knowledge Graph | 110 controls analysed | 686 frameworks | 309K+ cross-framework mappings

Control Mappings

Showing 20 of 172 mapped controls across 13 domains. Sign up to explore all 309K+ mappings across 686 frameworks.

Access Control(20 mappings)

AC.L2-3.1.1Authorized Access Control5 targets
SEC02-BP04Rely on a centralized identity provider
SEC03-BP01Define access requirements
SEC03-BP02Grant least privilege access
SEC03-BP06Manage access based on lifecycle
SEC08-BP04Enforce access control
AC.L2-3.1.11Session Termination
SEC02-BP02Use temporary credentials
AC.L2-3.1.12Control Remote Access2 targets
SEC02-BP01Use strong sign-in mechanisms
SEC06-BP03Reduce manual management and interactive access
AC.L2-3.1.13Remote Access Confidentiality
SEC09-BP02Enforce encryption in transit
AC.L2-3.1.14Remote Access Routing2 targets
SEC05-BP02Control traffic flow within your network layers
SEC06-BP03Reduce manual management and interactive access
AC.L2-3.1.15Privileged Remote Access2 targets
SEC03-BP03Establish emergency access process
SEC06-BP03Reduce manual management and interactive access
AC.L2-3.1.2Transaction & Function Control4 targets
SEC02-BP06Employ user groups and attributes
SEC03-BP02Grant least privilege access
SEC03-BP05Define permission guardrails for your organization
SEC08-BP04Enforce access control
AC.L2-3.1.20External Connections3 targets
SEC03-BP07Analyze public and cross-account access
SEC03-BP09Share resources securely with a third party
SEC05-BP02Control traffic flow within your network layers

+152 more mappings

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

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

The CMMC 2.0 to AWS Well-Architected Security Pillar crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which AWS Well-Architected Security Pillar controls your existing CMMC 2.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

Coverage does not run both ways. CMMC 2.0 into AWS Well-Architected Security Pillar lands at 31.7%, while AWS Well-Architected Security Pillar into CMMC 2.0 lands at 50%, on the same two control sets. That is not a rounding difference. It is the whole reason these are two separate reports: one asks what your CMMC 2.0 evidence buys you for AWS Well-Architected Security Pillar, the other asks the reverse.

CMMC 2.0 into AWS Well-Architected Security Pillar
31.7%

20 of 63 AWS Well-Architected Security Pillar controls are evidenced by work you have already done for CMMC 2.0. 43 are genuine gaps.

55.6%Infrastructure Protection
26.7%Identity & Access Management
36.4%Data Protection
37.5%Incident Response
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 80 candidate mappings were examined and 0 were removed by a pass whose job was to argue against them.Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

A sample of what the report says

Evidenced: SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP02 Develop incident management plans

An incident handling capability spanning preparation to recovery is the same plan

Grounded in IR.L2-3.6.1 Incident Handling. Confidence high, survived the refutation pass.

Gap: SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP01 Identify key personnel and external resources

Maintain an up to date roster of incident responders, executives, legal, comms, AWS support contacts and external IR retainer firms with on call rotations.

Every one of the 20 evidenced controls and 43 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.

AWS Well-Architected Security Pillar into CMMC 2.0
50%

55 of 110 CMMC 2.0 controls are evidenced by work you have already done for AWS Well-Architected Security Pillar. 55 are genuine gaps.

45.5%Access Control
50%System and Communications Protection
77.8%Configuration Management
66.7%Audit and Accountability
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 151 candidate mappings were examined and 0 were removed by a pass whose job was to argue against them.Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

A sample of what the report says

Evidenced: AC.L2-3.1.1 Authorized Access Control

Least privilege IAM policies evidence that access is limited to authorized users and processes.

Grounded in SEC03-BP02 Grant least privilege access. Confidence high, survived the refutation pass.

Gap: AC.L2-3.1.10 Session Lock

Lock the user session after a defined period of inactivity and conceal previously displayed content behind a pattern hiding display until the user reauthenticates.

Every one of the 55 evidenced controls and 55 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.

CMMC 2.0 to AWS Well-Architected Security Pillar
$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 70% in the header counts how many CMMC 2.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many AWS Well-Architected Security Pillar 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 686 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (309K+)
  • 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 CMMC 2.0 and AWS Well-Architected Security Pillar?

CMMC 2.0 has 110 controls across its framework, while AWS Well-Architected Security Pillar covers 63 controls. Direct mapping analysis identifies 77 overlapping controls (70% coverage). The frameworks diverge most significantly in Access Control, where 8 CMMC 2.0 controls have no direct AWS Well-Architected Security Pillar equivalent.

How many controls map between CMMC 2.0 and AWS Well-Architected Security Pillar?

Of 110 total CMMC 2.0 controls, 77 map directly to AWS Well-Architected Security Pillar controls, representing 70% coverage. The remaining 33 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping CMMC 2.0 to AWS Well-Architected Security Pillar?

33 CMMC 2.0 controls have no direct equivalent in AWS Well-Architected Security Pillar. The highest concentration of gaps is in Access Control with 8 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 CMMC 2.0 and AWS Well-Architected Security Pillar?

The domain with the highest gap count is Access Control (8 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.