Regulations · BSI C5

    BSI C5: the cloud criteria catalogue, and how to read a C5 report.

    Independently tested on the EU AI Act: most accurate single-turn answers, second overall of eight.

    C5 is the cloud criteria catalogue of the German Federal Office for Information Security (BSI). This page is for cloud providers asked for a C5 report and for customers who receive one. Ansvar does not serve the BSI's catalogue text. What this page says about C5 comes from Ansvar's own guidance and criterion summaries, quoted as served, and the German statutes are quoted as published.

    What C5 is and who asks for it

    Ansvar's guidance calls C5 “the BSI's answer to the question 'what does the auditor test a cloud provider against'” (bsi_c5). It says C5 “was written by the BSI so that a cloud service provider's security could be attested by an independent auditor against a published, cloud-specific criteria catalogue instead of against each customer's questionnaire” (bsi_c5:C5-PURPOSE).

    German federal bodies. Ansvar's clause-map entries for federal cloud use read: “Federal cloud use follows BSI C5 criteria and the EVB-IT cloud contract, favouring services that carry a C5 attestation” (BUND-CLOUD-01), and “Agencies must evaluate a cloud provider's security before adopting its services, ideally building the review on a C5 attestation” (MS-CLOUD-01).

    German statutory health care. Under § 393 SGB V, service providers under Chapter Four of SGB V, the health and care insurance funds and their processors may process social and health data through a cloud computing service if paragraphs 2 to 4 are met. Paragraph 3 requires, among other things, “ein aktuelles C5-Testat der datenverarbeitenden Stelle im Hinblick auf die C5-Basiskriterien für die im Rahmen des Cloud-Computing-Dienstes eingesetzten Cloud-Systeme und die eingesetzte Technik” (a current C5 attestation of the processing body, covering the C5 basic criteria, for the cloud systems and technology used), and that “die im Prüfbericht des Testats enthaltenen, korrespondierenden Kriterien für Kunden umgesetzt sind” (the customer criteria in the audit report are implemented). § 384 SGB V, point 6, defines a current C5 attestation as “das positive Prüfergebnis über einen sicheren Cloud-Computing-Dienst anhand des Kriterienkatalogs C5 (Cloud Computing Compliance Criteria Catalogue) des Bundesamtes für Sicherheit in der Informationstechnik in der jeweils gültigen Fassung”, so the edition in force applies.

    How the catalogue is built

    Ansvar's guidance lists the areas C5 covers: the provider's “organisation, personnel, asset management, physical security, operations, identity and access management, cryptography, communication security, portability and interoperability, procurement and supplier management, development, incident management, business continuity, compliance and audit, handling of government investigation requests, and product security, each area as a numbered set of criteria” (bsi_c5:C5-PURPOSE).

    Ansvar's German Standards source keeps clause-map entries under C5 criterion identifiers, with an Ansvar summary in German and English. For OIS-01 the summary reads: “The cloud provider runs a management system for information security that accounts for the legal, regulatory and contractual duties tied to the service.” These entries do not name the catalogue edition. Ansvar's control library names two: C5:2020 and C5:2026, with 2026 as the primary edition.

    Basic and additional criteria

    “Each C5 area contains basic criteria that every attested provider must meet and, for many criteria, additional criteria that a provider can elect to be attested against for customers with higher protection needs (stricter cryptography, stronger segregation, tighter logging).” “The report states which additional criteria were in scope” (bsi_c5:C5-BASIC-VS-ADDITIONAL). Ansvar's guidance adds that a controller processing special-category or high-volume personal data “should read the additional-criteria coverage, not just the fact of a C5 report”. The health-care rule in § 393(3) SGB V asks for a current attestation of the processing body covering the basic criteria for the cloud systems and technology used.

    Type 1 and Type 2 attestation

    “A C5 report is the output of an ISAE 3000 engagement (or its German equivalent, IDW PS 951 in its C5 form) performed by an independent auditor on the provider's system description and controls against the C5 criteria, as a Type 1 (design at a date) or Type 2 (design and operating effectiveness over a period, typically twelve months)” (bsi_c5:C5-ATTESTATION-ISAE3000).

    Ansvar's guidance treats a C5 Type 2 report as “the European cloud-native equivalent of a SOC 2 Type 2”, while “a Type 1 evidences design only and should be treated as the SOC 2 Type 1 is treated”. German health law draws the same line in time: § 393(4) SGB V reads “Ab dem 1. Juli 2025 gilt als aktuelles C5-Testat im Sinne des Absatzes 3 Nummer 2 ein aktuelles C5-Typ2-Testat.”

    What a customer should check in a C5 report

    Ansvar's guidance reads a C5 report the way it reads a SOC 2.

    Ansvar's guidance: “a C5 report should be read exactly like a SOC 2 (opinion, description, tests, exceptions)” (bsi_c5:C5-PURPOSE). Four checks follow from the served guidance.

    1. The surrounding information. C5 requires the system description to disclose “the jurisdictions the provider and its sub-service providers operate under, the locations where data is stored and processed, the sub-service providers and what they do, the certifications and attestations held, and the disclosure obligations the provider is subject to”. Ansvar's guidance calls this section “the first thing to read in a C5 report” (bsi_c5:C5-SYSTEM-DESCRIPTION-AND-CCC).
    2. Type 1 or Type 2. A Type 1 covers design at a date; a Type 2 covers operating effectiveness over a period.
    3. Which additional criteria were in scope. The report states them; a basic-only report may not match your protection needs.
    4. The complementary customer controls. The report “also carries complementary customer controls, the C5 equivalent of CUECs”, and Ansvar's guidance treats them as “inherited obligations to confirm on the controller side, as for any service-organisation report” (bsi_c5:C5-SYSTEM-DESCRIPTION-AND-CCC). For service-organisation reports in general, Ansvar's guidance notes that “where a customer does not operate them the assurance does not reach that customer's use of the service” (isae_3402:ISAE3402-CUECS). In German statutory health care this is law: § 393(3) SGB V requires the customer criteria in the audit report to be implemented.

    C5, ISO/IEC 27001 and NIS2

    Ansvar's guidance on certification and attestation: an ISO 27001 certificate “does not give an opinion on the operating effectiveness of specific controls over a period against a fixed control list”, while a SOC 2 Type 2 or C5 Type 2 report “opines on a listed set of controls over a period, with tests disclosed, and says nothing about whether a management system exists”. Its conclusion: “the two are complements, not substitutes” (iso_27001_certification:ISO27001-CERT-VS-ATTESTATION).

    For German statutory health care, § 1(1) C5GleichwV accepts an attestation or certification of the cloud computing service under ISO/IEC 27001 in the version in force, ISO 27001 on the basis of IT-Grundschutz by the BSI, or the Cloud Controls Matrix version 4.0 in the version in force as proof of a security level equivalent to a C5 Type 1 or Type 2 attestation, “sofern zusätzlich die Voraussetzungen nach den Absätzen 2 und 3 erfüllt sind”. Paragraph 2 requires a measures plan that marks the C5 basic criteria the other standard does not cover in substance, documents the measures that close those gaps, sets milestones that close them within twelve months of drawing up the milestone plan, and documents the steps towards a C5 Type 1 attestation within 18 months and a C5 Type 2 attestation within 24 months of that point. Paragraph 3 requires the plan and the existing attestation or certificate to be handed over without delay, on request, to the service providers under Chapter Four of SGB V or the health and care insurance funds that commission the cloud service, and to the competent supervisory authorities.

    On NIS2, Ansvar's C5 guidance cross-references NIS2 Article 21 for cloud providers (bsi_c5:C5-PURPOSE). The NIS2 explainer covers the Article 21 measures.

    What Ansvar gives you on C5

    • Criterion identifiers with an Ansvar summary line, in the German Standards source (standards-de), on the free plan.
    • Ansvar guidance on C5 attestation: basic and additional criteria, Type 1 and Type 2, surrounding information and complementary customer controls, with cross-references to ISAE 3000, SOC 2 and the GDPR (assurance-attestation-expertise), on the free plan.
    • The German statutes that require C5 in health care, quoted as published.
    • On Team plans, the control library maps C5:2020 and C5:2026 identifiers to NIST SP 800-53 controls. Until a licence agreement with the BSI exists, it publishes only the relationship type of each C5 mapping, with no mapping rationale.

    Ansvar does not give you the BSI's criteria text. Read the criteria in the catalogue the BSI publishes, and use Ansvar to find the identifier, the summary and the guidance around it.

    The dates

    German health-care law sets the dates; C5 itself sets none we serve.

    Every date here has passed; the line ends today.
    • 1 July 2024The C5 equivalence regulation for health care, the C5GleichwV, took effect from 1 July 2024 (§ 2 C5GleichwV).
    • 30 June 2025Until 30 June 2025 a C5 Type 1 attestation counted as current for cloud processing of social and health data (§ 393(4) SGB V).
    • 1 July 2025From 1 July 2025 a current C5 Type 2 attestation counts as current. A system first placed on the market after 30 June 2025 can rely on a Type 1 attestation for its first 18 months, and a Type 2 attestation counts from the 19th month. The same paragraph also accepts, in place of a C5 attestation, an attestation or certificate for the cloud systems and cloud technology used under a standard that ensures a comparable or higher security level (§ 393(4) SGB V).

    Questions teams ask about C5

    If your question is not here, email us. Every message gets a human answer.

    No. Ansvar serves criterion identifiers with its own summary lines, its own guidance on C5 attestation, and the German statutes that refer to C5. The criteria themselves are in the catalogue the BSI publishes.

    Ansvar's guidance describes Type 1 as design at a date and Type 2 as design and operating effectiveness over a period, typically twelve months. A Type 1 evidences design only.

    Only the ones in scope. Every attested provider must meet the basic criteria; a provider can elect to be attested against additional criteria, and the report states which additional criteria were in scope.

    Ansvar's guidance treats the two as complements, not substitutes: a certificate does not give an opinion on the operating effectiveness of specific controls over a period. For cloud use in German statutory health care, the C5GleichwV accepts an ISO/IEC 27001 certificate of the cloud service, in the version of the standard in force, only together with the measures plan its § 1(2) requires and the disclosure on request its § 1(3) requires.

    This page explains Ansvar's guidance on BSI C5 and the German statutes that refer to it. It is legal information, not legal advice.

    Ask about C5 with the source attached

    On the free plan, your own AI client searches Ansvar with one value per scope, such as one jurisdiction or one source. Each C5 row Ansvar returns names its source URL, publisher and licence.

    Ask these to see the quality

    Paste one into your agent once Ansvar is connected, and check the entry it cites.

    1. Using Ansvar, what does a BSI C5 report state about additional criteria? Quote Ansvar's assurance guidance entry bsi_c5:C5-BASIC-VS-ADDITIONAL.
    2. Using Ansvar, what are complementary customer controls in a BSI C5 report? Quote Ansvar's assurance guidance entry bsi_c5:C5-SYSTEM-DESCRIPTION-AND-CCC.
    3. Using Ansvar, quote the German Standards clause-map summary for BSI C5 criterion OIS-01.