# BSI C5 AM-04 — Decommissioning of Hardware

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_am04_a267b0ef80-bsi-c5-am-04-decommissioning-of-hardware
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Asset Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_assetmanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control AM-04 · Priority: critical · Component: Asset Management

### What this control covers

Requires approval for hardware decommissioning, ensuring complete and permanent data deletion or media destruction per policies. Prevents residual data exposure, protecting cloud customer data confidentiality during the disposal of system components.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### GitHub

Subscribe to **secret-scanning** alerts and **Dependabot** security advisories; require triage SLAs by severity. For exposed secrets, rotate at the cloud provider FIRST then revoke at GitHub — order matters.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `ticketing_workflow` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Decommissioning of Hardware.

### Quick checklist

-   Risk — Hardware / Cloud Customer Data
-   Confidentiality — Hardware / Cloud Customer Data
-   Asset — Hardware / Cloud Customer Data
-   Data — Hardware / Cloud Customer Data

### Related articles on this site

-   [Microsoft Cloud Security Posture Management (CSPM)](https://support.icompaas.com/support/solutions/articles/62000234105-microsoft-cloud-security-posture-management-cspm-)
-   [Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs](https://support.icompaas.com/support/solutions/articles/62000084027-ensure-a-log-metric-filter-and-alarm-exist-for-disabling-or-scheduled-deletion-of-customer-created-cm)
-   [Ensure storage for critical data are encrypted with Customer Managed Key](https://support.icompaas.com/support/solutions/articles/62000219790-ensure-storage-for-critical-data-are-encrypted-with-customer-managed-key)
-   [Data Retention & Destruction](https://support.icompaas.com/support/solutions/articles/62000225143-data-retention-destruction)

## 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.