# BSI C5:2020 DEV-02 — Outsourcing of the development - Source: https://support.icompaas.com/compliance/bsi-c5-2020/dev-02-outsourcing-of-the-development - 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-02`·high·Component: **Development & Change Management** ## What this control requires > Contractually specifies security requirements for outsourced development, including standards compliance, acceptance testing, and vulnerability verification. Ensures third-party deliverables meet CSP security standards, protecting cloud customer data integrity. > > — BSI C5:2020, Criterion DEV-02 ### In plain English Contractually specifies security requirements for outsourced development, including standards compliance, acceptance testing, and vulnerability verification. 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. 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-02) 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. ### Operational checklist - **Risk.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Verification.** 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:** cloud customer data, development, standards compliance, vulnerability verification, management. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Outsourcing of the development. ## 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. ## 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. - [**CIS Controls v8 16.2** — Establish and Maintain a Process to Accept and Address Software Vulnerabilities](https://support.icompaas.com/compliance/cis-controls-v8/16-2-establish-and-maintain-a-process-to-accept-and-address-software-vulnerabilities) - [**ISO/IEC 27001:2022 A.8.30** — Outsourced development](https://support.icompaas.com/compliance/iso-27001-2022/a-8-30-outsourced-development) ## Related controls in BSI C5:2020 - [**Criterion COS-03** — Monitoring of connections in the Cloud Service Provider's network](https://support.icompaas.com/compliance/bsi-c5-2020/cos-03-monitoring-of-connections-in-the-cloud-service-provider-s-network) - [**Criterion SSO-01** — Policies and instructions for controlling and monitoring third parties](https://support.icompaas.com/compliance/bsi-c5-2020/sso-01-policies-and-instructions-for-controlling-and-monitoring-third-parties) - [**Criterion SSO-03** — Directory of service providers and suppliers](https://support.icompaas.com/compliance/bsi-c5-2020/sso-03-directory-of-service-providers-and-suppliers) - [**Criterion SSO-04** — Monitoring of compliance with requirements](https://support.icompaas.com/compliance/bsi-c5-2020/sso-04-monitoring-of-compliance-with-requirements) - [**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) ## 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-02` Topics: vendor riskvendor managementsupply chain securitycloud posturecode review testing ## 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.