AM-03·high·Component: Asset ManagementWhat this control requires
Implements an approval process for hardware commissioning, identifying and mitigating risks per applicable policies. Verifies secure configuration of error handling, logging, encryption, and authentication to ensure safe operation of systems handling cloud customer data.
In plain English
Implements an approval process for hardware commissioning, identifying and mitigating risks per applicable policies. In practice, this means you can prove you risk hardware-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 Asset Management, the assessor will trace your implementation back to the catalogue reference (Criterion AM-03) and look for objective evidence on the latest two assessment cycles.
How to implement
Cloud Posture
CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.
Configuration Management
Policy-as-code. Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises.
IaC. Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production.
Drift. Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register.
Operational checklist
- Risk. Document the trigger, the owner and the cadence.
- Asset. 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.
- Authentication. Document the trigger, the owner and the cadence.
- Scope: hardware, protection, - configuration, cloud customer data, management.
Evidence to collect
- Policy Document. A signed and version-controlled policy / standard / procedure document.
- Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.
Signed policy or standard documents the safeguard. Focus: Commissioning of Hardware.
Common pitfalls
- Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.
- Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation.
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-171 Rev. 3 3.14.8 — Information Management and Retention
- CIS Controls v8 3.9 — Encrypt Data on Removable Media
- NIST SP 800-53 Rev. 5 SC-4(1) — Security Levels
Related controls in BSI C5:2020
- Criterion AM-02 — Acceptable Use and Safe Handling of Assets Policy
- Criterion AM-04 — Decommissioning of Hardware
- Criterion AM-06 — Asset Classification and Labelling
- Criterion CRY-01 — Policy for the use of encryption procedures and key management
- Criterion CRY-02 — Encryption of data for transmission (transport encryption)
- Criterion CRY-04 — Secure key management
References
- Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020
- Catalogue identifier:
Criterion AM-03
Topics: governance riskdata protectioncloud postureconfiguration managementencryption at restidentity management