Notifications
Clear all
Topic starter
24/06/2026 9:12 pm
TL;DR: Deployment friction and technical lineage capture across hybrid and multi-cloud data environments remain persistent challenges, according to Collibra, whose Cloud Sites and OpenLineage integration are intended to reduce deployment friction while improving lineage support for Apache Airflow and AWS Glue. The deeper issue is that governance programmes still struggle when oversight, traceability, and operational agility are treated as trade-offs rather than one control problem.
NHIMG editorial — based on content published by Collibra: Enhancing unified governance with Cloud Sites and OpenLineage integration
Questions worth separating out
Q: How should security teams govern data lineage across hybrid and multi-cloud environments?
A: Security teams should start with the data flows that matter most for compliance, AI, and business reporting, then require traceability across source, transformation, orchestration, and consumption.
Q: Why do governance programmes fail when deployment is too complex?
A: They fail because operational overhead turns policy into partial adoption.
Q: How do teams know if lineage is actually working as a control?
A: A working lineage control lets you answer where the data came from, how it changed, and which downstream reports or models depend on it without manual tracing.
Practitioner guidance
- Audit your highest-value data flows for lineage completeness Start with the pipelines that feed compliance reporting, AI features, and executive dashboards.
- Reduce governance deployment friction before expanding scope Measure how much platform effort is required to onboard new governed systems, maintain connectors, and keep metadata current.
- Treat lineage coverage as a control requirement Define minimum lineage expectations for critical data products, especially where data is used in regulated workflows or AI use cases.
What's in the full article
Collibra's full post covers the operational detail this post intentionally leaves for the source:
- How Cloud Sites changes the deployment workflow for existing Edge users and new deployments.
- The specific Airflow and AWS Glue metadata paths used to extend lineage capture.
- The implementation steps for requesting a Cloud Site directly from platform settings.
- Documentation references for bringing metadata into the platform from supported orchestration tools.
👉 Read Collibra's update on Cloud Sites and OpenLineage integration →
OpenLineage integration and Cloud Sites: what it means for governance?
Explore further
25/06/2026 6:16 am
Governance programmes fail when they assume deployment friction is separate from control quality. This update shows that infrastructure burden and governance coverage are tightly linked. If teams cannot deploy and maintain the control plane easily, lineage and oversight become partial by default. The implication is that governance architecture should be judged on operability as much as on policy design.
A few things that frame the scale:
- 35.6% of organisations cite managing consistent access across hybrid and multi-cloud environments as their top NHI security challenge, according to The 2024 Non-Human Identity Security Report.
- Only 19.6% of security professionals express strong confidence in their organisation's ability to securely manage non-human workload identities.
A question worth separating out:
Q: Who is accountable when data lineage is missing in regulated workflows?
A: Accountability sits with the team that owns the governed data product and the platform team that operates the lineage mechanism. If lineage is absent, ownership is not established enough to prove provenance or change impact. Governance should require named accountability before the data reaches regulated or decision-critical use cases.
👉 Read our full editorial: Data lineage governance is getting simpler across hybrid cloud
