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.

Related controls in BSI C5:2020

References

Topics: incident responseawareness trainingchange managementcloud posturesecurity training