BSI C5:2020 DEV-02 — Outsourcing of the development

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.

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
• ISO/IEC 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
• Criterion SSO-01 — Policies and instructions for controlling and monitoring third parties
• Criterion SSO-03 — Directory of service providers and suppliers
• Criterion SSO-04 — Monitoring of compliance with requirements
• Criterion DEV-09 — Approvals for provision in the production environment
• Criterion DEV-10 — Separation of environments

References

• Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020
• Catalogue identifier: Criterion DEV-02

Topics: vendor riskvendor managementsupply chain securitycloud posturecode review testing