Information & Data Management › Data Governance Management

Data Governance Management

BC-610.10 Level 2 Cross-Industry 20 providers 54 API surfaces 15 rated strong or better

Data ownership, stewardship, policies, standards.

Data Governance Management (BC-610.10) is a level-2 business capability under Information & Data Management in the Cross-Industry model. The catalog holds 54 API surface(s) from 20 provider(s) that can perform some part of it, 15 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Data Ownership and Stewardship BC-610.10.10

Assignment and operation of data owner and steward roles.

no catalog coverage

Data Policy and Standards BC-610.10.20

Definition of data policies, standards, and reference frameworks.

no catalog coverage

Data Cataloguing and Lineage BC-610.10.30

Data catalogue, glossary, and end-to-end data lineage.

no catalog coverage

Data Privacy and Classification BC-610.10.40

Classification of data and enforcement of privacy controls.

no catalog coverage

Data Risk and Compliance Monitoring BC-610.10.50

Monitoring of data risk and regulatory compliance (e.g. BCBS 239, GDPR).

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 8 Complete, well-documented, and agent-ready

ConfluentEntity (v1)1 API86.8 Adobe SuiteEnabled core policiesLabelsMarketing actionsPolicies5 APIs78.3 Confluent | the Data Streaming PlatformEntity (v1)Types (v1)2 APIs77.3 Microsoft AzureAtlasGlossary2 APIs76.2 OneTrustData Asset AttributesData Asset ManagementData AssetsGlossaries6 APIs72.7 SodaData Standards1 API71.9 ClouderaData Catalog1 API70.3 Microsoft PurviewBusiness DomainsClassification RulesCritical Data ElementsData Products7 APIs66.8

Strong 7 Solid coverage with minor gaps

OracledataCatalog1 API66.0 BonitasoftDataRetention1 API65.8 BoxMetadata Templates1 API61.0 ALTRAuto Tagging APIClassification JobsClassifiersData Discovery5 APIs58.6 Amazon DataZoneAssetsDomainsSubscriptions3 APIs56.9 mParticleData PlanData Plan Version2 APIs56.8 Altimate AICONTRACTTABLES2 APIs55.4

Developing 5 Usable, with meaningful gaps to close

BigeyeDataClassService1 API52.5 Select StarCollectionsColumnsDatabasesMetadata6 APIs45.9 OpenMetadataClassificationsDomains2 APIs45.7 Google Cloud Data CatalogEntries1 API44.7 AlationGlossary TermsPoliciesSchemasTables4 APIs40.2

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.

The edge table is a Pro feature. This page shows which providers and tags reach Data Governance Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans → · How the edges are graded →