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