# BSI C5 OIS-01 — Information Security Management System (ISMS)

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_ois01_76fb3a312d-bsi-c5-ois-01-information-security-management-system-isms
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Information Security Governance](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_informationsecuritygovernance)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control OIS-01 · Priority: high · Component: Information Security Governance

### What this control covers

Operates an ISO/IEC 27001-compliant ISMS covering CSP organizational units, locations, and cloud service procedures. Documents setup, implementation, and continuous improvement, including ISMS scope, declaration of applicability, and recent management review results to ensure robust security governance for cloud customer data protection.

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

#### Google Workspace

Forward the **Admin, Login, Drive, Token and Mobile** audit logs to Cloud Logging (Workspace BigQuery export). Alert on impossible-travel logins, OAuth-scope grants for high-risk scopes, and external Drive sharing of sensitive labels.

#### GitHub

Stream the **Enterprise audit log** to your SIEM and enable **Audit Log API** alerting on key events: owner changes, IP allowlist edits, secret deletions, repo visibility flips.

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

Signed policy or standard documents the safeguard. Focus: Information Security Management System (ISMS).

### Quick checklist

-   Information — Security Management System (Isms) / Isms Scope
-   Risk — Security Management System (Isms) / Isms Scope
-   Review — Security Management System (Isms) / Isms Scope
-   Security — Security Management System (Isms) / Isms Scope
-   Protection — Security Management System (Isms) / Isms Scope
-   Data — Security Management System (Isms) / Isms Scope

### Related articles on this site

-   [Microsoft Cloud Security Posture Management (CSPM)](https://support.icompaas.com/support/solutions/articles/62000234105-microsoft-cloud-security-posture-management-cspm-)
-   [NIST 800-171 3.1.1 Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).](https://support.icompaas.com/support/solutions/articles/62000229223-nist-800-171-3-1-1-limit-information-system-access-to-authorized-users-processes-acting-on-behalf-of)
-   [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.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.](https://support.icompaas.com/support/solutions/articles/62000229280-nist-800-171-3-4-1-establish-and-maintain-baseline-configurations-and-inventories-of-organizational-s)

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