FedRAMP ModerateC5 (Germany)

FedRAMP Moderate covers 71.1% of C5 (Germany)

86 of the 121 controls in C5 (Germany) are already satisfied by evidence you collected for FedRAMP Moderate. 35 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.

71.1%
of the target already covered
86
controls evidenced
35
genuine gaps
6
claims rejected in review

This number is directional. It says how much of C5 (Germany) your FedRAMP Moderate 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.

268 candidate mappings were examined and 9 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: Security Policies and Instructions3 of 3 evidenced
C5: Physical Security6 of 7 evidenced, 1 to do
C5: Product Safety and Security10 of 12 evidenced, 2 to do
C5: Human Resources5 of 6 evidenced, 1 to do
C5: Procurement, Development and Modification of Information Systems8 of 10 evidenced, 2 to do
C5: Security Incident Management4 of 5 evidenced, 1 to do
C5: Identity and Access Management7 of 9 evidenced, 2 to do
C5: Communication Security6 of 8 evidenced, 2 to do
C5: Business Continuity Management3 of 4 evidenced, 1 to do
C5: Cryptography and Key Management3 of 4 evidenced, 1 to do
C5: Organisation of Information Security5 of 7 evidenced, 2 to do
C5: Operations17 of 24 evidenced, 7 to do
C5: Control and Monitoring of Service Providers and Suppliers3 of 5 evidenced, 2 to do
C5: Asset Management3 of 6 evidenced, 3 to do
C5: Compliance2 of 4 evidenced, 2 to do
C5: Portability and Interoperability1 of 3 evidenced, 2 to do
C5: Dealing with Investigation Requests from Government Agencies0 of 4 evidenced, 4 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.

CM-8(1)C5-AM-01argued against and upheld
Asset Inventory

Updating the inventory during installation, removal and update is what keeps asset records complete, accurate and current

CM-8C5-AM-01argued against and upheld
Asset Inventory

Component inventory kept accurate and current with the attributes needed to manage the assets, which is what the criterion requires

MP-6C5-AM-04argued against and upheld
Decommissioning of Hardware

Sanitisation or destruction of media before disposal, release or reuse is the erasure limb the criterion requires

PS-6C5-AM-05argued against and upheld
Commitment to Permissible Use, Safe Handling and Return of Assets

Signed access agreements are the documented commitment to permissible use and handling before assets are issued

PS-4C5-AM-05argued against and upheld
Commitment to Permissible Use, Safe Handling and Return of Assets

Termination processing retrieves organisational property, evidencing the return of assets

CP-2C5-BCM-02argued against and upheld
Business impact analysis policies and instructions

The contingency plan identifies essential functions, recovery objectives, restoration priorities and metrics, which is the documented impact analysis content

CP-2C5-BCM-03argued against and upheld
Planning business continuity

A single documented contingency plan with scope, roles, recovery and restoration procedures and its maintenance is the planning framework required

CP-2(1)C5-BCM-03argued against and upheld
Planning business continuity

Coordination with business continuity, disaster recovery and continuity of operations plans matches the framework.

Claims that did not hold

6 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.

CM-8(1)C5-AM-03
Commissioning of Hardware

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the criterion is an approval gate before hardware enters production, with risk analysis and verification that error handling, logging, encryption, authentication and authorisation are securely configured; updating an inventory during installation records the event and gates nothing

Claimed at high confidence before it was rejected.

PS-5C5-HR-05
Responsibilities in the event of termination or change of employment

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the criterion is about which security obligations continue to bind a person after their employment ends or changes, and for how long; reviewing and modifying access rights on transfer is a different requirement and is already mapped to C5-IDM-04

Claimed at medium confidence before it was rejected.

AC-7C5-IDM-03
Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the title mentions failed logins but the basic criterion covers only dormancy: automatic locking after two months unused, approval to reinstate and revocation after six months; lockout after consecutive invalid logon attempts satisfies none of it

Claimed at high confidence before it was rejected.

AU-3C5-OPS-11
Logging and Monitoring - Metadata Management Concept

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the criterion governs use of usage metadata: purpose limitation to billing, incident and security handling, anonymisation, no commercial use, retention and deletion; specifying the content fields of an audit record addresses none of that and is already mapped to C5-OPS-15

Claimed at high confidence before it was rejected.

AU-2C5-OPS-13
Logging and Monitoring - Identification of Events

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the title says identification of events but the criterion requires automated analysis of logging data, correlation of relationships between events and automatic reporting to the responsible departments; selecting which event types to log is the separate logging concept already mapped to C5-OPS-10

Claimed at high confidence before it was rejected.

PE-3C5-PS-03
Perimeter Protection

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. this criterion is structural: external doors, windows, walls and locking mechanisms that resist a burglary attempt for at least ten minutes; enforcing physical access authorisations at entry points is access control and is already mapped to C5-PS-04

Claimed at high confidence before it was rejected.

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