CDMC-KC1 | Data Control Compliance | 2 |
CDMC-KC10 | Data Protection Impact Assessments | 1 |
CDMC-KC11 | Data Retention, Archiving and Purging | 0 |
CDMC-KC12 | Data Quality Measurement | 1 |
CDMC-KC13 | Cost Metrics | 0 |
CDMC-KC14 | Data Lineage | 1 |
CDMC-KC2 | Ownership Field | 1 |
CDMC-KC3 | Authoritative Data Sources and Provisioning Points | 0 |
CDMC-KC4 | Data Sovereignty and Cross-Border Movement | 0 |
CDMC-KC5 | Cataloguing | 1 |
CDMC-KC6 | Classification | 2 |
CDMC-KC7 | Entitlements and Access for Sensitive Data | 0 |
CDMC-KC8 | Data Consumption Purpose | 0 |
CDMC-KC9 | Security Controls | 3 |
1 | 1 Governance and Accountability | 0 |
1.1 | 1.1 Cloud Data Management Business Cases are Defined and Governed | 0 |
1.1.1 | 1.1.1 Cloud data management business cases are defined | 0 |
1.1.2 | 1.1.2 Cloud data management business cases are syndicated and governed | 0 |
1.2 | 1.2 Data Ownership is Established for both Migrated and Cloud-Generated Data | 0 |
1.2.1 | 1.2.1 Data owner role and responsibilities are defined | 0 |
1.2.2 | 1.2.2 Data ownership is established in the cloud | 0 |
1.3 | 1.3 Data Sourcing and Consumption are Governed and Supported by Automation | 0 |
1.3.1 | 1.3.1 Data sourcing is managed and authorized | 0 |
1.3.2 | 1.3.2 Data consumption is governed and supported by automation | 0 |
1.4 | 1.4 Data Sovereignty and Cross-Border Data Movement are Managed | 0 |
1.4.1 | 1.4.1 Sovereignty of data is tracked | 0 |
1.4.2 | 1.4.2 Data sovereignty and cross-border data movement risks are managed | 0 |
2 | 2 Cataloging and Classification | 0 |
2.1 | 2.1 Data Catalogs are Implemented, Used and Interoperable | 0 |
2.1.1 | 2.1.1 Data cataloging is defined | 0 |
2.1.2 | 2.1.2 Metadata is discoverable, enriched, managed, and exposed in data catalogs | 0 |
2.1.3 | 2.1.3 Data catalogs are interoperable across multi and hybrid cloud environments | 0 |
2.2 | 2.2 Data Classifications are Defined and Used | 0 |
2.2.1 | 2.2.1 Data classifications are defined | 0 |
2.2.2 | 2.2.2 Data classifications are applied and used | 0 |
3 | 3 Accessibility and Usage | 0 |
3.1 | 3.1 Data Entitlements are Managed, Enforced, and Tracked | 0 |
3.1.1 | 3.1.1 Data entitlement rights and obligations are captured as metadata | 0 |
3.1.2 | 3.1.2 Data entitlement rights are enforced | 0 |
3.1.3 | 3.1.3 Access and entitlement tracking is automated | 0 |
3.2 | 3.2 Ethical Access, Use, and Outcomes of Data are Managed | 0 |
3.2.1 | 3.2.1 Data ethics organization structures are established | 0 |
3.2.2 | 3.2.2 Data ethics processes are operational | 0 |
4 | 4 Protection and Privacy | 0 |
4.1 | 4.1 Data is Secured, and Controls are Evidenced | 0 |
4.1.1 | 4.1.1 Encryption policies are defined and enforced | 0 |
4.1.2 | 4.1.2 Implementation of data security controls is evidenced | 0 |
4.1.3 | 4.1.3 Data obfuscation techniques are defined and applied | 0 |
4.1.4 | 4.1.4 A Data Loss Prevention program is established | 0 |
4.2 | 4.2 A Data Privacy Framework is Defined and Operational | 0 |
4.2.1 | 4.2.1 A Data Privacy framework is defined | 0 |
4.2.2 | 4.2.2 The Data Privacy framework is operational | 0 |
5 | 5 Data Lifecycle | 0 |
5.1 | 5.1 The Data Lifecycle is Planned and Managed | 0 |
5.1.1 | 5.1.1 A data lifecycle management framework is defined | 0 |
5.1.2 | 5.1.2 The data lifecycle is implemented and managed | 0 |
5.2 | 5.2 Data Quality is Managed | 0 |
5.2.1 | 5.2.1 Data quality rules are managed | 0 |
5.2.2 | 5.2.2 Data quality is measured | 0 |
5.2.3 | 5.2.3 Data Quality metrics are reported | 0 |
5.2.4 | 5.2.4 Data Quality Issues are managed | 0 |
6 | 6 Data and Technical Architecture | 0 |
6.1 | 6.1 Technical Design Principles are Established and Applied | 0 |
6.1.1 | 6.1.1 Optimization of cloud use and cost efficiency is facilitated | 0 |
6.1.2 | 6.1.2 Principles for data availability and resilience are established and applied | 0 |
6.1.3 | 6.1.3 Backups and point-in-time recovery are supported | 0 |
6.1.4 | 6.1.4 Portability and exit planning are established | 0 |
6.2 | 6.2 Data Provenance and Lineage are Understood | 0 |
6.2.1 | 6.2.1 Multi-environment lineage discovery is automated | 0 |
6.2.2 | 6.2.2 Data lineage changes are tracked and managed | 0 |
6.2.3 | 6.2.3 Data lineage reporting and visualization are implemented | 0 |
FRAMEWORK | The CDMC Framework: purpose, structure, use cases and scoring | 0 |
KC1 | Key Control 1: Data Control Compliance | 0 |
KC10 | Key Control 10: Data Protection Impact Assessments | 0 |
KC11 | Key Control 11: Data Retention, Archiving and Purging | 0 |
KC12 | Key Control 12: Data Quality Measurement | 0 |
KC13 | Key Control 13: Cost Metrics | 0 |
KC14 | Key Control 14: Data Lineage | 0 |
KC2 | Key Control 2: Ownership Field | 0 |
KC3 | Key Control 3: Authoritative Data Sources and Provisioning Points | 0 |
KC4 | Key Control 4: Data Sovereignty and Cross-Border Movement | 0 |
KC5 | Key Control 5: Cataloging | 0 |
KC6 | Key Control 6: Classification | 0 |
KC7 | Key Control 7: Entitlements and Access for Sensitive Data | 0 |
KC8 | Key Control 8: Data Consumption Purpose | 0 |
KC9 | Key Control 9: Security Controls | 0 |
KEYCONTROLS | Key controls and automations: scope and sensitive data | 0 |
STATUS | Edition status: v1.1.1 is the published framework; CDMC+ work extends it | 0 |