# BSI C5:2020 DEV-04 — Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools. - Source: https://support.icompaas.com/compliance/bsi-c5-2020/dev-04-safety-training-and-awareness-programme-regarding-continuous-software-delivery-and - 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-04`·medium·Component: **Development & Change Management** ## What this control requires > Provides regular security training for employees on secure development standards and tools, updated per policies. Ensures personnel are equipped to develop and deploy secure software, protecting cloud customer data from development-related risks. > > — BSI C5:2020, Criterion DEV-04 ### In plain English Provides regular security training for employees on secure development standards and tools, updated per policies. In practice, this means you can prove you risk cloud customer data-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. ## 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-04) 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. #### 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. #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. ### Operational checklist - **Risk.** 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. - **Policy.** Document the trigger, the owner and the cadence. - **Secure.** Document the trigger, the owner and the cadence. - **Scope:** cloud customer data, development, management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Safety training and awareness programme regarding continuous software delivery and associated systems, components or.... ## 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. - [**NIST SP 800-171 Rev. 3 3.12.3** — Continuous Monitoring](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-12-3-continuous-monitoring) - [**ISO/IEC 27001:2022 A.8.27** — Secure system architecture and engineering principles](https://support.icompaas.com/compliance/iso-27001-2022/a-8-27-secure-system-architecture-and-engineering-principles) - [**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-53 Rev. 5 PM-13** — Security And Privacy Workforce](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pm-13-security-and-privacy-workforce) ## Related controls in BSI C5:2020 - [**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 HR-02** — Employment terms and conditions](https://support.icompaas.com/compliance/bsi-c5-2020/hr-02-employment-terms-and-conditions) - [**Criterion PI-01** — Documentation and safety of input and output interfaces](https://support.icompaas.com/compliance/bsi-c5-2020/pi-01-documentation-and-safety-of-input-and-output-interfaces) - [**Criterion COM-01** — Identification of applicable legal, regulatory, self-imposed or contractual requirements](https://support.icompaas.com/compliance/bsi-c5-2020/com-01-identification-of-applicable-legal-regulatory-self-imposed-or-contractual) - [**Criterion PSS-12** — Locations of Data Processing and Storage](https://support.icompaas.com/compliance/bsi-c5-2020/pss-12-locations-of-data-processing-and-storage) - [**Criterion DEV-01** — Policies for the development/procurement of information systems](https://support.icompaas.com/compliance/bsi-c5-2020/dev-01-policies-for-the-development-procurement-of-information-systems) ## 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-04` Topics: governance riskawareness trainingcloud posturecontinuous monitoringpolicy managementsecure development ## 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.