Start hereAgree service boundary and examination scope
~147 days leftOpen step
Guide library
Audit report Europe

BSI C5 cloud attestation

Cloud Computing Compliance Criteria Catalogue (C5)

Define the cloud service and build evidence for an independent C5 assurance report.

Who it applies to

Cloud service providers whose customers or procurement arrangements ask for a C5 report, and customer assurance teams reviewing one.

What you’ll produce

An independent assurance report on the in-scope cloud service, with the agreed period and criteria.

Use the catalogue edition stated in the contract and engagement. Review subservice organizations and customer responsibilities when relying on the report.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What will reviewers test, and for which period?
Confirm scope, report purpose, testing period or as-of date and the evidence the reviewer expects. Reserve time for delayed records, walkthroughs and retesting.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk through one recent transaction or control with the owner and a reviewer. Pull the full source list and trace an item back to original evidence.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor missing populations, controls without a reviewer and overdue fixes. Bring potential issues with the reporting period to the sponsor.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

BSI C5 cloud attestation kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Agree service boundary and examination scope · Cloud compliance + customer owner [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk through one recent transaction or control with the owner and a reviewer. Pull the full source list and trace an item back to original evidence.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which exact cloud service and locations appear in the procurement requirement?
  • Is a report over an operating period needed, and which provider controls must be assessed?

Worked scenario

A German customer asks for C5 coverage of a hosted service used for records management. It checks the service and regions in the report, then assigns internal controls that the provider expects the customer to implement.

What to read next

The whole journeyabout 147 days across 4 steps
  1. 01Agree service boundary and examination scopeCloud compliance + customer owner · ~21 days
  2. 02Describe the service and map controlsService owners + security · ~42 days
  3. 03Collect operating evidence and support testingControl owners + independent examiner · ~70 days
  4. 04Evaluate the final report and keep it currentAssurance lead + procurement · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Agree service boundary and examination scopeCloud compliance + customer ownerBefore engagementSet a start dateScope memo; Responsibility matrix; Agreed engagementOpen
Describe the service and map controlsService owners + securityBefore evidence collectionSet a start dateSystem description draft; Control matrix; Evidence indexOpen
Collect operating evidence and support testingControl owners + independent examinerDuring the agreed period and fieldworkSet a start dateSampling populations; Assessment evidence; Remediation trackerOpen
Evaluate the final report and keep it currentAssurance lead + procurementAfter issuance and during supplier reviewSet a start dateIssued report; Customer control dependencies; Audit calendarOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Agree service boundary and examination scope

    Who Cloud compliance + customer owner When Before engagement

    Confirm providers, services, locations, optional criteria, edition and period. Document shared controls and downstream provider treatment.

    What to produce

    Scope memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Responsibility matrixMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Agreed engagementMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  2. 02

    Describe the service and map controls

    Who Service owners + security When Before evidence collection

    Describe contractual commitments, system boundaries and control operation. Map evidence to the requested C5 criteria using the agreed edition.

    What to produce

    System description draftMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

    Control matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Evidence indexSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Collect operating evidence and support testing

    Who Control owners + independent examiner When During the agreed period and fieldwork

    Capture real changes, reviews and recurring operations in scope. Reconcile evidence populations and document exceptions and fixes.

    What to produce

    Sampling populationsSpreadsheet

    Gather first

    • Authoritative ticket, event or transaction system
    • Exact scope, time zone and date window
    • Auditor’s population and sampling request

    How to prepare it

    1. Define what counts as one row and agree start and end cutoffs with the auditor. Export all in-scope activity, including failed or cancelled records when relevant.
    2. Save the query and export timestamp. Keep stable source IDs and reconcile totals to an independent report. Explain any legitimate exclusions.
    3. Give the full population to the auditor before sampling. Link selected items to underlying records as requested.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    CHG-0742
    Occurred at
    2026-09-22 15:08 UTC
    System and event
    Billing API, production deploy
    State
    Completed
    Evidence key
    Release job 7242, linked approval PR-881
    Population filter
    Production deploys, Jul through Sep 2026 UTC

    Check before handing it over

    The reviewer can reproduce the count and trace any selected item back to the original system.

    Transfer the export, query, reconciliation and any exclusions to the independent tester.

    Assessment evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Remediation trackerSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  4. 04

    Evaluate the final report and keep it current

    Who Assurance lead + procurement When After issuance and during supplier review

    Verify dates, report uses, criteria, scope and customer responsibilities. Plan the next reporting cycle and communicate remaining responsibilities.

    What to produce

    Issued reportIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Customer control dependenciesMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Audit calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes