Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Data marketplaces: what IAM and data teams need to govern


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 8151
Topic starter  

TL;DR: Data marketplaces help organisations discover, request and use trusted data products faster, but they only work when ownership, meaning, lineage and access policy are built into the publishing model, according to Collibra. The governance challenge is less about finding data and more about making trust, accountability and approval rules operational.

NHIMG editorial — based on content published by Collibra: What is a data marketplace? How leading teams discover and share trusted data

By the numbers:

Questions worth separating out

Q: How should teams govern access to data products in a marketplace model?

A: Teams should govern access to data products by combining approval workflow with context.

Q: Why do data marketplaces change IAM and governance design?

A: Data marketplaces change IAM and governance design because access is no longer the whole control story.

Q: What breaks when data products do not have clear ownership?

A: When data products do not have clear ownership, requests stall, quality issues linger and no one is accountable for definitions or lifecycle changes.

Practitioner guidance

What's in the full article

Collibra's full blog post covers the operational detail this post intentionally leaves for the source:

  • How the Collibra Data Marketplace structures ownership, definitions and approved-use metadata for published data products
  • The specific workflow elements used to request access and route approvals across teams
  • How data product management supports reuse, quality review and business-facing consumption
  • Examples of how trusted data products connect to analytics and AI use cases in practice

👉 Read Collibra's analysis of trusted data discovery and data marketplaces →

Data marketplaces: what IAM and data teams need to govern?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 1 month ago
Posts: 6095
 

Data marketplaces are now a governance problem, not a discovery feature. The article frames the marketplace as a way to remove friction, but the real discipline shift is that trust has to be publishable and reusable, not reconstructed at each request. When ownership, quality and permitted use travel with the data product, the organisation can govern consumption instead of chasing exceptions. The practitioner conclusion is that marketplace design is a governance architecture decision.

A few things that frame the scale:

  • The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
  • Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the same study.

A question worth separating out:

Q: How can security and data teams tell whether a marketplace is actually working?

A: A marketplace is working when users can find the right product, understand what it means, see whether it is fit for purpose and get approved access without extra interpretation work. If teams still rely on tickets, tribal knowledge or repeated clarification, the marketplace is only accelerating discovery, not improving governance.

👉 Read our full editorial: Data marketplaces need context, ownership and control to work



   
ReplyQuote
Share: