Study guide
14.1 DMBoK Data Ethics Framework
DAMA Certified Data Management Professional CDMP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & DMBoK Framework
1.1 CDMP Exam Details & Strategy 1.2 The DMBoK Framework 1.3 Data Management Organization & Roles
2 Chapter 2: Data Governance (Part A)
2.1 Data Governance Principles & Drivers 2.2 Operating Models & Structures 2.3 Policies, Standards, and Procedures
3 Chapter 2: Data Governance (Part B)
2.4 Data Stewardship 2.5 Governance Metrics & Implementation
4 Chapter 3: Data Modeling and Design (Part A)
Section 3.1: Conceptual, Logical, and Physical Models Section 3.2: ERD Notations & Relational Modeling Section 3.3: Normalization
5 Chapter 3: Data Modeling and Design (Part B)
3.4 Dimensional Modeling 3.5 Naming Standards & Modeling Best Practices
6 Chapter 4: Data Quality (Part A)
Section 4.1: Data Quality Dimensions Section 4.2: Data Quality Policy & Rules Section 4.3: DMAIC & DQ Improvement Lifecycle
7 Chapter 4: Data Quality (Part B)
4.4 Root-Cause Analysis & Remediation 4.5 DQ Metrics, Tools, and Reporting
8 Chapter 5: Metadata Management (Part A)
5.1 Business, Technical, and Operational Metadata 5.2 Metadata Lineage & Impact Analysis 5.3 Repository Architectures
9 Chapter 5: Metadata Management (Part B)
5.4 Standards and Semantics 5.5 Metadata Governance & Integration
10 Chapter 6: Master and Reference Data Management
6.1 Master vs Reference Data 6.2 MDM Repository Architectures 6.3 Match-Merge & Identity Resolution 6.4 Reference Data Governance & Standards
11 Chapter 7: Data Warehousing and Business Intelligence
7.1 DW Architectures: Inmon vs Kimball 7.2 Data Warehousing Storage & Load Patterns 7.3 BI Delivery & OLAP 7.4 Data Marts & Enterprise Data Warehouses
12 Chapter 8: Data Architecture
8.1 Enterprise Data Architecture & Zachman Framework 8.2 Data Flow Diagrams & Value Chains 8.3 Architecture Frameworks & Standards
13 Chapter 9: Document and Content Management
9.1 Records Management & ECM 9.2 Retention, Disposal, and E-Discovery 9.3 ARMA GARP Principles & Taxonomies
14 Chapter 10: Data Integration and Interoperability
Section 10.1: Integration Patterns & Technologies Section 10.2: Replication & Virtualization Section 10.3: Canonical Models & Integration Standards
15 Chapter 11: Data Security
Section 11.1: Security Principles: CIA Triad & Privacy Section 11.2: Access Control & Encryption Section 11.3: Security Regulations & Standards
16 Chapter 12: Data Storage and Operations
Section 12.1: Database Technologies & DBA Roles Section 12.2: Backup, Recovery, and High Availability Section 12.3: Performance Tuning & Operations
17 Chapter 13: Big Data and Data Science
13.1 Big Data V's & Technologies
18 Chapter 14: Data Ethics
14.1 DMBoK Data Ethics Framework
19 Chapter 15: Data Management Process and Maturity
15.1 Maturity Assessment Frameworks
14.1 DMBoK Data Ethics Framework
Key Takeaways Explain This Topic AI
Data ethics goes beyond legal compliance; laws set the baseline of what is permitted, whereas ethics define what is right, bridging the gap created by technology outpacing law.
The Belmont Principles form the core of data ethics: Respect for Persons (autonomy and informed consent), Beneficence (do no harm and maintain data quality), and Justice (fair distribution of risks and benefits).
Algorithmic bias occurs when predictive models codify and perpetuate historical human prejudices due to unrepresentative training data, biased design, or proxy variables.
Ethical data programs require establishing concrete governance structures, including a Data Ethics Review Board (DERB), clear ethical policies, training, and whistleblower protections.
Last updated: July 2026
- 14.1 DMBoK Data Ethics Framework
- Introduction to Data Ethics
Data management is not merely a technical or regulatory challenge; it is fundamentally rooted in data ethics . According to the Data Management Body of Knowledge ( DAMA-DMBOK2 ), data ethics concerns the ethical collection, storage, processing, analysis, and use of data and algorithms. Compliance with the law is only a baseline. While laws (such as GDPR or CCPA ) define what is legally permissible, data ethics defines what is morally right.
This distinction is critical due to regulatory lag —the delay between rapid technological advancements (like machine learning or biometrics) and the passage of governing laws. To bridge this gap, organizations must move from a compliance-focused mindset ("Is it legal?") to an ethical one ("Is it right?"). Fostering an ethical data culture is vital for securing customer trust, preserving brand equity, and preventing discriminatory outcomes.
Foundational Principles: The Belmont Report
The ethical foundations of data handling in the DMBoK are derived from the Belmont Report (1979). Originally protecting human subjects in biomedical research, its three principles now serve as the ethical pillars for data management:
Respect for Persons : This principle asserts that individuals should be treated as autonomous agents with the right to self-determination. In data management, this is operationalized through informed consent (seeking explicit, active opt-in agreement rather than relying on deceptive opt-out defaults) and individual privacy controls. It requires clear disclosures of data usage, ensuring individuals understand how their information is processed, and respecting their right to access, restrict, or delete their data.
Beneficence : This principle establishes an obligation to minimize harm and maximize benefits, encapsulated by the directive to "Do no harm." In practice, beneficence requires implementing robust data security protocols (e.g., encryption, de-identification, and data masking) to prevent breaches. It also highlights data quality as an ethical imperative : processing inaccurate, outdated, or incomplete data can directly harm individuals, such as when flawed data leads to incorrect medical diagnoses or erroneous credit rejections.
Justice : This principle concerns fairness and the equitable distribution of both the benefits and the burdens of data usage. It asks: Who benefits from the data, and who bears the risk? Justice is applied by ensuring that predictive models do not unfairly discriminate against specific demographics, enforcing representative sampling in datasets, and preventing the exploitation of vulnerable populations.
Belmont Principle Core Focus Operational Data Management Application CDMP Exam Trap
Respect for Persons Individual autonomy & dignity Explicit consent mechanisms, preference portals, transparent disclosures. Assuming regulatory compliance (e.g., checking boxes for GDPR) is sufficient; respect requires proactive transparency.
Beneficence Risk reduction & benefit optimization Cyber-security, data quality controls, PII masking, impact assessments. Overlooking data quality; poor quality is an ethical failure if it leads to harmful decisions.
Justice Fairness & non-discrimination Algorithmic audits, diverse training data, anti-redlining proxy checks. Believing that removing demographic identifiers alone guarantees fairness (proxies can still cause bias).
Algorithmic Bias and Model Opacity
As automated decision-making and machine learning scale, managing algorithmic bias has become a critical data governance responsibility. Algorithmic bias occurs when a system systematically generates prejudiced or unfair outcomes. It arises primarily from:
Training Data Bias : Models learn from historical data; if historical decisions contained human bias (e.g., gender-biased hiring practices), the algorithm will codify and perpetuate those prejudices.
Sampling Bias : If the training dataset fails to represent the target population (e.g., facial recognition trained mostly on light-skinned faces), the system will perform poorly on underrepresented groups.
Proxy Variables : Designers may remove protected attributes (like race), but other features (like ZIP codes or browsing history) act as proxies, leading to indirect discrimination, historically known as redlining .
To mitigate these risks, organizations must address model opacity. Complex algorithms, such as deep neural networks, often operate as black-box models , where internal logic is hidden. Data ethics requires transparency and explainability, granting individuals the right to understand how automated decisions affecting them were made. Organizations should employ Explainable AI (XAI) techniques to ensure models remain auditable.
Unethical Data Manipulation and Presentation
Data ethics also governs how analysts communicate findings. The DMBoK identifies several deceptive practices that constitute unethical data manipulation:
Misleading Visualizations : Altering graphical displays to distort the truth, such as truncating the Y-axis (starting at a non-zero value to exaggerate differences), using dual Y-axes with non-proportional scales, or omitting inconvenient data points.
Unclear Definitions : Shifting definition criteria over time to artificially boost performance metrics (e.g., redefining a "daily active user" to hide a decline in engagement).
Invalid Comparisons : Comparing non-equivalent datasets or omitting confounding variables to imply a false correlation or causal relationship.
Establishing an Ethical Data Handling Program
Operationalizing data ethics requires integrating ethical checks into existing governance structures. A formal ethical data handling program includes:
Ethical Data Handling Policy : A written policy setting boundaries for data acquisition, usage, and sharing, integrated into regular staff training.
Data Ethics Review Board (DERB) : A cross-functional committee (governance, legal, data science, and ethicists) that reviews high-risk data uses, such as AI model deployments or sensitive customer profiling.
Ethics by Design : Integrating ethical risk and data protection impact assessments (DPIAs) directly into the System Development Life Cycle ( SDLC ).
Data Stewardship Integration : Empowering data stewards to monitor lineage, maintain high data quality standards, and audit access permissions.
Whistleblower Protections : Providing secure, anonymous channels for staff to report unethical data manipulation or reporting demands.