# BSI C5:2020 HR-03 — Security training and awareness programme - Source: https://support.icompaas.com/compliance/bsi-c5-2020/hr-03-security-training-and-awareness-programme - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Human Resources Security (HR) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `HR-03`·medium·Component: **Human Resources Security** ## What this control requires > Operates a regular, target group-oriented security training program for employees, updated based on policy changes and threats. Covers system handling, data protection, threat awareness, and incident response to ensure secure operations and protect cloud customer data. > > — BSI C5:2020, Criterion HR-03 ### In plain English Operates a regular, target group-oriented security training program for employees, updated based on policy changes and threats. In practice, this means you can prove you security protection-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. ## 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 **Human Resources Security**, the assessor will trace your implementation back to the catalogue reference (Criterion HR-03) 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. #### 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 - **Security.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Policy.** Document the trigger, the owner and the cadence. - **Secure.** Document the trigger, the owner and the cadence. - **Scope:** protection, cloud customer data, changes, management. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Security training and awareness programme. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. - 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 CP-3** — Contingency Training](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-3-contingency-training) - [**NIST SP 800-171 Rev. 3 3.6.4** — Incident Response Training](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-6-4-incident-response-training) - [**SOC 2 (2017 TSC) CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response) ## Related controls in BSI C5:2020 - [**Criterion DEV-03** — Policies for changes to information systems](https://support.icompaas.com/compliance/bsi-c5-2020/dev-03-policies-for-changes-to-information-systems) - [**Criterion OPS-15** — Logging and Monitoring - Accountability](https://support.icompaas.com/compliance/bsi-c5-2020/ops-15-logging-and-monitoring-accountability) - [**Criterion DEV-09** — Approvals for provision in the production environment](https://support.icompaas.com/compliance/bsi-c5-2020/dev-09-approvals-for-provision-in-the-production-environment) - [**Criterion AM-04** — Decommissioning of Hardware](https://support.icompaas.com/compliance/bsi-c5-2020/am-04-decommissioning-of-hardware) - [**Criterion SIM-04** — Duty of the users to report security incidents to a central body](https://support.icompaas.com/compliance/bsi-c5-2020/sim-04-duty-of-the-users-to-report-security-incidents-to-a-central-body) - [**Criterion HR-02** — Employment terms and conditions](https://support.icompaas.com/compliance/bsi-c5-2020/hr-02-employment-terms-and-conditions) ## 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 HR-03` Topics: incident responseawareness trainingchange managementcloud posturesecurity training ## 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.