What this control covers
Establish and maintain a data inventory, based on the enterprise's data management process. Inventory sensitive data, at a minimum. Review and update inventory annually, at a minimum, with a priority on sensitive data.
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
Cloud Asset Inventory exports a daily snapshot of every resource and IAM policy to BigQuery; combine with Org Policy for tag enforcement.
GitHub
Dependabot security updates + version updates, plus CodeQL for SAST and a renovate bot for major-version drift management.
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
policy_document— A signed, version-controlled policy stating leadership intent and the named owner.infra_scan— See the iCompaas Evidence library for the canonical source for this evidence type.
Signed policy or standard documents the safeguard. Focus: Establish and Maintain a Data Inventory.
Quick checklist
- Establish And Maintain — Data Management Process / Data Inventory
Related articles on this site
- Ensure IAM password policy requires minimum length of 14 or greater
- NIST 800-171 3.3.3 Review and update logged events.
- NIST 800-171 3.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
- CMMC 2.0 AU.3.045 Review and update logged events.