BSI C5:2020 OPS-03 — Capacity Management - Controlling of Resources

What this control requires

Enables cloud customers to control and monitor allocated system resources to prevent overcrowding and ensure performance. Supports efficient resource management, maintaining service quality and protecting cloud customer data from resource-related issues.

In plain English

Enables cloud customers to control and monitor allocated system resources to prevent overcrowding and ensure performance. 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 Operations Security, the assessor will trace your implementation back to the catalogue reference (Criterion OPS-03) and look for objective evidence on the latest two assessment cycles.

How to implement

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.

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.
• Security. Document the trigger, the owner and the cadence.
• Capacity. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Scope: cloud customer data, development, management.

Evidence to collect

• Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Capacity Management - Controlling of Resources.

Common pitfalls

• 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
• CIS Controls v8 14.6 — Train Workforce Members on Recognizing and Reporting Security Incidents
• SOC 2 (2017 TSC) CC1.3 — Organizational Structure and Reporting Lines
• GDPR Article 75 — Secretariat
• NIST SP 800-53 Rev. 5 RA-4 — Risk Assessment Update

Related controls in BSI C5:2020

• Criterion OPS-17 — Logging and Monitoring - Availability of the Monitoring Software
• Criterion OPS-19 — Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
• Criterion OPS-13 — Logging and Monitoring - Identification of Events
• Criterion OPS-22 — Testing and Documentation of known Vulnerabilities
• Criterion DEV-04 — Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools.
• Criterion PSS-02 — Identification of Vulnerabilities of the Cloud Service

References

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

Topics: governance risksecure developmentcode review testingdevsecopscapacity management