# BSI C5:2020 OIS-07 — Application of the Risk Management Policy - Source: https://support.icompaas.com/compliance/bsi-c5-2020/ois-07-application-of-the-risk-management-policy - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Information Security Governance (OIS) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `OIS-07`·high·Component: **Information Security Governance** ## What this control requires > Executes annual risk management processes per OIS-06, addressing data processing with varying protection needs, technical weaknesses, public network attacks, unseparated tasks, and third-party dependencies. Reviews risk analysis and residual risk acceptance to ensure adequate protection of cloud customer data. > > — BSI C5:2020, Criterion OIS-07 ### In plain English Executes annual risk management processes per OIS-06, addressing data processing with varying protection needs, technical weaknesses, public network attacks, unseparated tasks, and third-party dependencies. In practice, this means you can prove you information management policy-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 **Information Security Governance**, the assessor will trace your implementation back to the catalogue reference (Criterion OIS-07) 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. #### Network Security **AWS.** VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation. **Azure.** NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift. **GCP.** VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services. ### Operational checklist - **Information.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Application.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Scope:** management policy, risk management policy, protection, cloud customer data. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Application of the Risk Management Policy. ## 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. - Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth. ## 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-53 Rev. 5 SA-12** — Supply Chain Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-supply-chain-protection) - [**SOC 2 (2017 TSC) CC9.2** — Vendor Risk Management](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc9-2-vendor-risk-management) - [**CIS Controls v8 3.8** — Document Data Flows](https://support.icompaas.com/compliance/cis-controls-v8/3-8-document-data-flows) - [**ISO/IEC 42001:2023 A.10.3** — Suppliers](https://support.icompaas.com/compliance/iso-42001-2023/a-10-3-suppliers) - [**ISO/IEC 27001:2022 A.5.19** — Information security in supplier relationships](https://support.icompaas.com/compliance/iso-27001-2022/a-5-19-information-security-in-supplier-relationships) ## Related controls in BSI C5:2020 - [**Criterion OIS-06** — Risk Management Policy](https://support.icompaas.com/compliance/bsi-c5-2020/ois-06-risk-management-policy) - [**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 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 OIS-05** — Contact with Relevant Government Agencies and Interest Groups](https://support.icompaas.com/compliance/bsi-c5-2020/ois-05-contact-with-relevant-government-agencies-and-interest-groups) - [**Criterion SSO-02** — Risk assessment of service providers and suppliers](https://support.icompaas.com/compliance/bsi-c5-2020/sso-02-risk-assessment-of-service-providers-and-suppliers) ## 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 OIS-07` Topics: governance riskvendor riskvendor managementsupply chain securitycloud posturenetwork security ## 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.