Cross-Framework Mapping

SOC 2vsAWS Well-Architected Security Pillar

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

81
Controls Mapped
0
Gaps Found
51%
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:

SOC 2 maps to AWS Well-Architected Security Pillar with 51% coverage across 31 directly mapped controls. Analysis of 61 SOC 2 controls identifies 30 compliance gaps, primarily concentrated in P - Privacy.

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

Control Mappings

Showing 20 of 81 mapped controls across 4 domains. Sign up to explore all 310K+ mappings across 686 frameworks.

A - Availability(1 mappings)

SOC2-A1.3Recovery plan procedures support system recovery from failures
SEC10-BP07Run simulations

C - Confidentiality(5 mappings)

SOC2-C1.1Confidential information is identified and protected during receipt, processing, storage4 targets
SEC07-BP01Understand your data classification scheme
SEC07-BP02Apply data protection controls based on data sensitivity
SEC07-BP03Automate identification and classification
SEC07-BP04Define scalable data lifecycle management
SOC2-C1.2Confidential information is disposed of securely
SEC07-BP04Define scalable data lifecycle management

CC - Common Criteria (Security)(14 mappings)

SOC2-CC1.3COSO principle 3: Management establishes structures, reporting lines, and authorities
SEC11-BP08Build a program that embeds security ownership in workload teams
SOC2-CC1.4COSO principle 4: Demonstrates commitment to attract and retain competent individuals
SEC11-BP01Train for application security
SOC2-CC1.5COSO principle 5: Holds individuals accountable for internal control responsibilities
SEC11-BP08Build a program that embeds security ownership in workload teams
SOC2-CC2.1COSO principle 13: Obtains and generates relevant, quality information
SEC04-BP02Capture logs, findings, and metrics in standardized locations
SOC2-CC3.1COSO principle 6: Specifies objectives to identify and assess risks
SEC01-BP03Identify and validate control objectives
SOC2-CC3.2COSO principle 7: Identifies risks and analyzes to determine how managed
SEC01-BP07Identify threats and prioritize mitigations using a threat model
SOC2-CC3.4COSO principle 9: Identifies and assesses changes that could impact internal controls
SEC01-BP07Identify threats and prioritize mitigations using a threat model
SOC2-CC4.1COSO principle 16: Selects and develops ongoing and separate evaluations2 targets
SEC02-BP05Audit and rotate credentials periodically
SEC11-BP03Perform regular penetration testing
SOC2-CC4.2COSO principle 17: Evaluates and communicates deficiencies in a timely manner
SEC04-BP04Initiate remediation for non-compliant resources
SOC2-CC5.1COSO principle 10: Selects and develops control activities to mitigate risks
SEC01-BP07Identify threats and prioritize mitigations using a threat model
SOC2-CC5.2COSO principle 11: Selects and develops general controls over technology2 targets
SEC01-BP06Automate deployment of standard security controls
SEC03-BP05Define permission guardrails for your organization
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets
SEC01-BP01Separate workloads using accounts

+61 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 SOC 2 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 SOC 2 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. SOC 2 into AWS Well-Architected Security Pillar lands at 39.7%, while AWS Well-Architected Security Pillar into SOC 2 lands at 29.5%, 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 SOC 2 evidence buys you for AWS Well-Architected Security Pillar, the other asks the reverse.

SOC 2 into AWS Well-Architected Security Pillar
39.7%

25 of 63 AWS Well-Architected Security Pillar controls are evidenced by work you have already done for SOC 2. 38 are genuine gaps.

54.5%Data Protection
33.3%Identity & Access Management
55.6%Infrastructure Protection
50%Incident Response
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 58 candidate mappings were examined and 2 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-BP01 Identify key personnel and external resources

Responding through defined procedures requires named responders and responsibilities.

Grounded in SOC2-CC7.4 Responds to identified security incidents through defined procedures. Confidence high, survived the refutation pass.

Gap: SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP03 Prepare forensic capabilities

Pre-provision a forensic account, isolated VPC, tooling AMIs, IAM roles and EBS snapshot procedures so responders can acquire and analyse evidence quickly.

Every one of the 25 evidenced controls and 38 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 SOC 2
29.5%

18 of 61 SOC 2 controls are evidenced by work you have already done for AWS Well-Architected Security Pillar. 43 are genuine gaps.

45.5%CC - Common Criteria (Security)
100%C - Confidentiality
5.6%P - Privacy
0%A - Availability
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 63 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: SOC2-C1.1 Confidential information is identified and protected during receipt, processing, storage

Automated discovery and classification maintains an accurate inventory of confidential information.

Grounded in SEC07-BP03 Automate identification and classification. Confidence high, survived the refutation pass.

Gap: SOC2-A1.1 Maintains capacity to meet availability commitments

Maintains, monitors, and evaluates current processing capacity and use of system components (infrastructure, data, and software) to manage capacity demand and to enable the implementation of additional capacity to help meet its objectives

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

SOC 2 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 51% in the header counts how many SOC 2 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 (310K+)
  • 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 SOC 2 and AWS Well-Architected Security Pillar?

SOC 2 has 61 controls across its framework, while AWS Well-Architected Security Pillar covers 63 controls. Direct mapping analysis identifies 31 overlapping controls (51% coverage). The frameworks diverge most significantly in P - Privacy, where 16 SOC 2 controls have no direct AWS Well-Architected Security Pillar equivalent.

How many controls map between SOC 2 and AWS Well-Architected Security Pillar?

Of 61 total SOC 2 controls, 31 map directly to AWS Well-Architected Security Pillar controls, representing 51% coverage. The remaining 30 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping SOC 2 to AWS Well-Architected Security Pillar?

30 SOC 2 controls have no direct equivalent in AWS Well-Architected Security Pillar. The highest concentration of gaps is in P - Privacy with 16 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 SOC 2 and AWS Well-Architected Security Pillar?

The domain with the highest gap count is P - Privacy (16 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.