# BSI C5:2020 DEV-01 — Policies for the development/procurement of information systems - Source: https://support.icompaas.com/compliance/bsi-c5-2020/dev-01-policies-for-the-development-procurement-of-information-systems - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Development & Change Management (DEV) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `DEV-01`·high·Component: **Development & Change Management** ## What this control requires > Documents secure development policies per SP-01, covering requirements, design, testing, and deployment per industry standards. Ensures security throughout the cloud service lifecycle, protecting customer data from vulnerabilities introduced during development. > > — BSI C5:2020, Criterion DEV-01 ### In plain English Documents secure development policies per SP-01, covering requirements, design, testing, and deployment per industry standards. In practice, this means you can prove you information development-level controls on a defined cadence. ## Why it matters BSI C5 is the default cloud-security baseline German public-sector buyers and many DAX-listed enterprises expect; gaps here directly block procurement in the DACH region and frequently appear as must-have items in EU public-tender documents. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A C5 attesting auditor (under ISAE 3000 / IDW PS 860) tests both the design and — for a Type 2 — the operating effectiveness over the attestation period. For each criterion they look for both the Basic and any in-scope Additional objectives. Within **Development & Change Management**, the assessor will trace your implementation back to the catalogue reference (Criterion DEV-01) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Information.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Scope:** development, management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Policies for the development/procurement of information systems. ## Common pitfalls - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - CI security checks set to warn-only; the merge button is faster than the security feedback. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.8.31** — Separation of development, test and production environments](https://support.icompaas.com/compliance/iso-27001-2022/a-8-31-separation-of-development-test-and-production-environments) - [**SOC 2 (2017 TSC) CC1.2** — Board Independence and Oversight](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc1-2-board-independence-and-oversight) - [**NIST SP 800-171 Rev. 3 3.13.2** — Recategorized as NCO](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-2-recategorized-as-nco) - [**NIST SP 800-53 Rev. 5 SA-8(29)** — Repeatable And Documented Procedures](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-8-29-repeatable-and-documented-procedures) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) ## Related controls in BSI C5:2020 - [**Criterion DEV-08** — Version Control](https://support.icompaas.com/compliance/bsi-c5-2020/dev-08-version-control) - [**Criterion DEV-04** — Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools.](https://support.icompaas.com/compliance/bsi-c5-2020/dev-04-safety-training-and-awareness-programme-regarding-continuous-software-delivery-and) - [**Criterion DEV-03** — Policies for changes to information systems](https://support.icompaas.com/compliance/bsi-c5-2020/dev-03-policies-for-changes-to-information-systems) - [**Criterion DEV-09** — Approvals for provision in the production environment](https://support.icompaas.com/compliance/bsi-c5-2020/dev-09-approvals-for-provision-in-the-production-environment) - [**Criterion DEV-10** — Separation of environments](https://support.icompaas.com/compliance/bsi-c5-2020/dev-10-separation-of-environments) - [**Criterion SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) ## References - [Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020](https://www.bsi.bund.de/EN/Topics/CloudComputing/Compliance_Criteria_Catalogue/Compliance_Criteria_Catalogue_node.html) - Catalogue identifier: `Criterion DEV-01` Topics: governance risksecure developmentcloud posturecode review testingpolicy management ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.