TheArtOfService
AWS Well-Architected Security PillarC5 (Germany)

AWS Well-Architected Security Pillar covers 30.6% of C5 (Germany)

37 of the 121 controls in C5 (Germany) are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 84 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

30.6%
of the target already covered
37
controls evidenced
84
genuine gaps
0
claims rejected in review

This number is directional. It says how much of C5 (Germany) your AWS Well-Architected Security Pillar evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

85 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. 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.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

C5: Cryptography and Key Management4 of 4 evidenced
C5: Communication Security5 of 8 evidenced, 3 to do
C5: Security Incident Management3 of 5 evidenced, 2 to do
C5: Identity and Access Management5 of 9 evidenced, 4 to do
C5: Procurement, Development and Modification of Information Systems5 of 10 evidenced, 5 to do
C5: Product Safety and Security4 of 12 evidenced, 8 to do
C5: Operations7 of 24 evidenced, 17 to do
C5: Organisation of Information Security2 of 7 evidenced, 5 to do
C5: Compliance1 of 4 evidenced, 3 to do
C5: Asset Management1 of 6 evidenced, 5 to do
C5: Business Continuity Management0 of 4 evidenced, 4 to do
C5: Human Resources0 of 6 evidenced, 6 to do
C5: Dealing with Investigation Requests from Government Agencies0 of 4 evidenced, 4 to do
C5: Portability and Interoperability0 of 3 evidenced, 3 to do
C5: Physical Security0 of 7 evidenced, 7 to do
C5: Security Policies and Instructions0 of 3 evidenced, 3 to do
C5: Control and Monitoring of Service Providers and Suppliers0 of 5 evidenced, 5 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

SEC 7: How do you classify your data? | SEC07-BP01C5-AM-06argued against and upheld
Asset Classification and Labelling

Documented classification scheme with handling requirements and owners is the labelling basis.

SEC 1: How do you securely operate your workload? | SEC01-BP03C5-COM-01argued against and upheld
Identification of applicable legal, regulatory, self-imposed or contractual requirements

Derives and documents control objectives from compliance, regulatory and business requirements.

SEC 5: How do you protect your network resources? | SEC05-BP03C5-COS-01argued against and upheld
Technical safeguards

Inspection based protection detects and filters irregular and hostile traffic patterns.

SEC 5: How do you protect your network resources? | SEC05-BP02C5-COS-03argued against and upheld
Monitoring of connections in the Cloud Service Provider's network

Restricting each layer to only needed flows re-justifies every permitted service and port.

SEC 5: How do you protect your network resources? | SEC05-BP01C5-COS-03argued against and upheld
Monitoring of connections in the Cloud Service Provider's network

Public, private and restricted subnets per tier is exactly risk based zone separation.

SEC 5: How do you protect your network resources? | SEC05-BP02C5-COS-04argued against and upheld
Cross-network access

Controls traffic entering from external systems at each network perimeter.

SEC 2: How do you manage identities for people and machines? | SEC02-BP01C5-COS-05argued against and upheld
Networks for administration

MFA is enforced for all human access to management consoles.

SEC 9: How do you protect your data in transit? | SEC09-BP02C5-COS-08argued against and upheld
Policies for data transmission

Mandatory TLS 1.2 or higher protects transferred data from interception and manipulation.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk