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

What this control covers

Top management adopts and communicates an information security policy to employees and customers, detailing the importance of security, objectives aligned with business goals, key security strategy aspects, and organizational structure for ISMS implementation to safeguard cloud customer data and meet protection requirements.

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

Use VPC Service Controls to draw a perimeter around sensitive APIs and a hierarchical Firewall policy at the org/folder level so projects inherit a deny-by-default posture. Front HTTP workloads with the global Cloud Load Balancer + Cloud Armor.

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

  • infra_scan — See the iCompaas Evidence library for the canonical source for this evidence type.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Information Security Policy.

Quick checklist

  • Information — Security Policy / Protection
  • Risk — Security Policy / Protection
  • Security — Security Policy / Protection
  • Protection — Security Policy / Protection
  • Data — Security Policy / Protection
  • Policy — Security Policy / Protection

Related articles on this site