# BSI C5:2020 OPS-15 — Logging and Monitoring - Accountability - Source: https://support.icompaas.com/compliance/bsi-c5-2020/ops-15-logging-and-monitoring-accountability - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Operations Security (OPS) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `OPS-15`·high·Component: **Operations Security** ## What this control requires > Generates log data enabling tenant-level user access identification for forensic analysis. Provides interfaces for backups and network communication analysis, supporting incident response and ensuring accountability for cloud customer data security. > > — BSI C5:2020, Criterion OPS-15 ### In plain English Generates log data enabling tenant-level user access identification for forensic analysis. In practice, this means you can prove you interfaces - accountability-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-15) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. ### Operational checklist - **Interfaces.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Identification.** Document the trigger, the owner and the cadence. - **Scope:** - accountability, cloud customer data, management. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Logging and Monitoring - Accountability. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. ## 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 AU-2** — Event Logging](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-2-event-logging) - [**SOC 2 (2017 TSC) CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response) - [**NIST SP 800-171 Rev. 3 3.3.6** — Audit Record Reduction and Report Generation](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-6-audit-record-reduction-and-report-generation) - [**CIS Controls v8 17.9** — Establish and Maintain Security Incident Thresholds](https://support.icompaas.com/compliance/cis-controls-v8/17-9-establish-and-maintain-security-incident-thresholds) - [**ISO/IEC 27001:2022 A.5.27** — Learning from information security incidents](https://support.icompaas.com/compliance/iso-27001-2022/a-5-27-learning-from-information-security-incidents) ## Related controls in BSI C5:2020 - [**Criterion OPS-21** — Involvement of Cloud customers in the event of incidents](https://support.icompaas.com/compliance/bsi-c5-2020/ops-21-involvement-of-cloud-customers-in-the-event-of-incidents) - [**Criterion OPS-10** — Logging and Monitoring - Concept](https://support.icompaas.com/compliance/bsi-c5-2020/ops-10-logging-and-monitoring-concept) - [**Criterion OPS-12** — Logging and Monitoring - Access, Storage and Deletion](https://support.icompaas.com/compliance/bsi-c5-2020/ops-12-logging-and-monitoring-access-storage-and-deletion) - [**Criterion HR-03** — Security training and awareness programme](https://support.icompaas.com/compliance/bsi-c5-2020/hr-03-security-training-and-awareness-programme) - [**Criterion AM-04** — Decommissioning of Hardware](https://support.icompaas.com/compliance/bsi-c5-2020/am-04-decommissioning-of-hardware) - [**Criterion COM-02** — Policy for planning and conducting audits](https://support.icompaas.com/compliance/bsi-c5-2020/com-02-policy-for-planning-and-conducting-audits) ## 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 OPS-15` Topics: logging monitoringincident responsechange managementcloud posture ## 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.