# BSI C5 DEV-01 — Policies for the development/procurement of information systems

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_dev01_e37673ce95-bsi-c5-dev-01-policies-for-the-developmentprocurement-of-information-systems
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Development & Change Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_developmentchangemanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control DEV-01 · Priority: high · Component: Development & Change Management

### What this control covers

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.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### GitHub

Apply **branch protection** on default and release branches: require PR review, status checks, signed commits, linear history, and dismiss stale reviews on new commits. Use **CODEOWNERS** for required reviewers, **Dependabot** + **CodeQL** for SAST, and the **Dependency graph / SBOM** export for vendor disclosures.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Policies for the development/procurement of information systems.

### Quick checklist

-   Information — Development / Management
-   Risk — Development / Management
-   Review — Development / Management
-   Security — Development / Management
-   Data — Development / Management
-   Policy — Development / Management

### Related articles on this site

-   [NIST 800-171 3.2.1 Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to](https://support.icompaas.com/support/solutions/articles/62000229264-nist-800-171-3-2-1-ensure-that-managers-systems-administrators-and-users-of-organizational-systems-)
-   [NIST 800-171 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.](https://support.icompaas.com/support/solutions/articles/62000229335-nist-800-171-3-13-2-employ-architectural-designs-software-development-techniques-and-systems-engine)
-   [CMMC 2.0 AT.2.056 Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to t](https://support.icompaas.com/support/solutions/articles/62000229422-cmmc-2-0-at-2-056-ensure-that-managers-systems-administrators-and-users-of-organizational-systems-a)
-   [CMMC 2.0 SC.3.180 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.](https://support.icompaas.com/support/solutions/articles/62000229741-cmmc-2-0-sc-3-180-employ-architectural-designs-software-development-techniques-and-systems-engineer)

## 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.