NIS2
Identify your national implementation and prepare governance, security controls and incident reporting.
Cloud Computing Compliance Criteria Catalogue (C5)
Define the cloud service and build evidence for an independent C5 assurance report.
Cloud service providers whose customers or procurement arrangements ask for a C5 report, and customer assurance teams reviewing one.
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.
Monitor missing populations, controls without a reviewer and overdue fixes. Bring potential issues with the reporting period to the sponsor.
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.
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.
Compare what a SOC 2 examination covers and what evidence could be reused.
Map responsibilities for cloud-specific controls.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Agree service boundary and examination scope | Cloud compliance + customer owner | Before engagement | Set a start date | Scope memo; Responsibility matrix; Agreed engagement | Open |
| Describe the service and map controls | Service owners + security | Before evidence collection | Set a start date | System description draft; Control matrix; Evidence index | Open |
| Collect operating evidence and support testing | Control owners + independent examiner | During the agreed period and fieldwork | Set a start date | Sampling populations; Assessment evidence; Remediation tracker | Open |
| Evaluate the final report and keep it current | Assurance lead + procurement | After issuance and during supplier review | Set a start date | Issued report; Customer control dependencies; Audit calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Confirm providers, services, locations, optional criteria, edition and period. Document shared controls and downstream provider treatment.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Describe contractual commitments, system boundaries and control operation. Map evidence to the requested C5 criteria using the agreed edition.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Capture real changes, reviews and recurring operations in scope. Reconcile evidence populations and document exceptions and fixes.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Verify dates, report uses, criteria, scope and customer responsibilities. Plan the next reporting cycle and communicate remaining responsibilities.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.