# BSI C5:2020 AM-01 — Asset Inventory - Source: https://support.icompaas.com/compliance/bsi-c5-2020/am-01-asset-inventory - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Asset Management (AM) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `AM-01`·high·Component: **Asset Management** ## What this control requires > Establishes automated or manual procedures for inventorying assets throughout their lifecycle, ensuring accuracy and consistency. Records risk management details and logs changes to support OIS-07 processes, protecting assets handling cloud customer data effectively. > > — BSI C5:2020, Criterion AM-01 ### In plain English Establishes automated or manual procedures for inventorying assets throughout their lifecycle, ensuring accuracy and consistency. In practice, this means you can prove you risk inventory-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-01) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Asset Inventory **AWS.** AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub. **Azure.** Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting. **GCP.** Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance. **Endpoints.** Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources. #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Risk.** Document the trigger, the owner and the cadence. - **Asset.** 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. - **Scope:** inventory, cloud customer data, changes, 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: Asset Inventory. ## Common pitfalls - Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start. - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**CIS Controls v8 3.2** — Establish and Maintain a Data Inventory](https://support.icompaas.com/compliance/cis-controls-v8/3-2-establish-and-maintain-a-data-inventory) - [**India DPDP Act 2023 SC-001** — Digital Personal Data Inventory](https://support.icompaas.com/compliance/india-dpdp-act-2023/sc-001-digital-personal-data-inventory) - [**ISO/IEC 27001:2022 A.5.9** — Inventory of information and other associated assets](https://support.icompaas.com/compliance/iso-27001-2022/a-5-9-inventory-of-information-and-other-associated-assets) - [**NIST SP 800-53 Rev. 5 CM-8(6)** — Assessed Configurations And Approved Deviations](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-6-assessed-configurations-and-approved-deviations) - [**SOC 2 (2017 TSC) CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters) ## Related controls in BSI C5:2020 - [**Criterion AM-06** — Asset Classification and Labelling](https://support.icompaas.com/compliance/bsi-c5-2020/am-06-asset-classification-and-labelling) - [**Criterion HR-02** — Employment terms and conditions](https://support.icompaas.com/compliance/bsi-c5-2020/hr-02-employment-terms-and-conditions) - [**Criterion PI-01** — Documentation and safety of input and output interfaces](https://support.icompaas.com/compliance/bsi-c5-2020/pi-01-documentation-and-safety-of-input-and-output-interfaces) - [**Criterion COM-01** — Identification of applicable legal, regulatory, self-imposed or contractual requirements](https://support.icompaas.com/compliance/bsi-c5-2020/com-01-identification-of-applicable-legal-regulatory-self-imposed-or-contractual) - [**Criterion PSS-12** — Locations of Data Processing and Storage](https://support.icompaas.com/compliance/bsi-c5-2020/pss-12-locations-of-data-processing-and-storage) - [**Criterion SP-02** — Review and Approval of Policies and Instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-02-review-and-approval-of-policies-and-instructions) ## 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 AM-01` Topics: governance riskasset inventorycloud posturepolicy management ## 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.