Foundations of Data Governance and the DAMA DMBOK

What Is Data Governance?

Data governance is the exercise of authority, control, and shared decision-making over data assets. Every organization—whether a hospital, a bank, or a city government—collects and stores data. Without a deliberate plan for who owns that data, who can change it, and how its quality is maintained, organizations end up with duplicate records, contradictory reports, and serious compliance risks. Data governance is the framework that prevents those problems.

The authoritative reference for data governance and all related data management disciplines is the DAMA DMBOK, published by DAMA International (the Data Management Association). The second edition, released in 2017, defines eleven knowledge areas organized around a central concept called the governance wheel.

The DAMA DMBOK Governance Wheel

The governance wheel places Data Governance at the hub, because every other knowledge area depends on governance decisions. The ten surrounding knowledge areas are the spokes. Think of governance as the policy layer that sets standards, assigns accountability, and resolves conflicts across all data activities in an organization.

The Eleven DMBOK Knowledge Areas

1. Data Governance – Establishes strategy, policies, standards, and accountabilities for managing data as an enterprise asset.

2. Data Architecture – Defines the blueprint for how data structures, flows, and integrations support business goals.

3. Data Modeling & Design – Covers the techniques for representing data in conceptual, logical, and physical models.

4. Data Storage & Operations – Addresses database technology selection, implementation, backup, recovery, and performance tuning—core DBA tasks.

5. Data Security – Defines policies and controls that protect data from unauthorized access, corruption, or loss, including user authentication and encryption.

6. Data Integration & Interoperability – Manages how data is moved, transformed, and synchronized across systems (ETL pipelines, APIs, replication).

7. Document & Content Management – Governs unstructured data: documents, emails, images, and other content outside traditional relational databases.

8. Reference & Master Data – Ensures that shared data—customer records, product codes, geographic codes—is consistent and authoritative across the enterprise.

9. Data Warehousing & Business Intelligence – Covers analytical databases, data marts, reporting, and dashboards that support decision-making.

10. Metadata – Manages data about data: data dictionaries, lineage records, and catalog entries that help users find and trust data.

11. Data Quality – Defines dimensions of quality (completeness, accuracy, consistency, timeliness, validity, uniqueness) and the processes to measure and improve them.

Key Governance Roles

Three roles appear in virtually every governance framework. Understanding the distinctions is critical for the DAMA CDMP exam and for daily work.

Data Owner

The data owner is a business executive or senior manager who has formal accountability for a data domain. Owners approve data definitions, authorize access levels, and accept risk on behalf of the business. For example, the Chief Financial Officer is typically the data owner for financial records. Ownership is a business role, not a technical one.

Data Steward

The data steward is a subject-matter expert—often a business analyst or experienced user—who manages data quality and meaning within a domain on a day-to-day basis. Stewards write and maintain business glossary definitions, resolve data disputes, and act as the liaison between the business and the technical teams. A single domain may have one lead steward and several contributing stewards.

Data Custodian

The data custodian is the technical practitioner—commonly a database administrator or systems engineer—who implements the controls and procedures that the owner and steward define. Custodians create user accounts, configure access permissions, run backups, and enforce encryption. They carry out the technical work; they do not set policy.

A simple way to remember the distinction: the owner decides what rules apply, the steward clarifies what the data means, and the custodian executes how the rules are enforced.

Why This Matters for DBAs and Data Analysts

As a database administrator or data analyst, you will most often function as a custodian, and sometimes as a steward. You will rarely hold the owner role unless you move into management. However, you need to understand all three roles because:

• You must know whose approval is required before changing a schema or granting access.
• You must escalate data quality issues to the correct steward rather than silently fixing data without authorization.
• Unauthorized changes to production data—even well-intentioned ones—can violate governance policies, audit requirements, or regulatory obligations (such as HIPAA or SOX).

Data Safety and Access Control

Data governance intersects directly with security and safety. Before performing any administrative action on a production system, confirm that you have documented authorization from the data owner or an authorized delegate. Follow the principle of least privilege: grant users only the access they need to perform their job, and no more. Maintain an audit log of all changes. In regulated environments, some changes require a second approver—never bypass that control even under time pressure. Proper change management protects both the organization and your professional standing.

Connecting Governance to Your Credential Exams

The DAMA CDMP Associate exam draws heavily on DMBOK concepts. Questions test your ability to define knowledge areas, identify correct role assignments, and apply governance principles to scenarios. The Microsoft DP-300 and Oracle DBA certifications also test governance-adjacent topics such as access control, auditing, and data security—all of which are grounded in the governance framework you are learning here.