# Data Lineage and Provenance One-sentence definition: End-to-end tracing of data origins, transformations, and destinations to ensure trust and compliance. ## Key Facts - Capture pipeline steps: source → transform → store → consume. - Show dependency graphs for impact analysis (changes/incidents). - Validate controls exist at each hop (encryption, access). - Supports eDiscovery, privacy, and data quality remediation. - Automate via ETL/ELT tooling and catalogs. - **Verify:** check official (ISC)² CBK and current exam outline. ## Exam Relevance - Choose lineage evidence to confirm integrity/completeness. **Mnemonic:** “From **where**, to **what**, by **whom**.” ## Mini Scenario Q: Dashboard metric wrong—where to look? A: Lineage to find faulty transformation or stale source. ## Revision Checklist - Name 3 uses of lineage. - Tie lineage to control verification. - Identify an automation source. ## Related [[Data Catalogs and Metadata Management]] · [[Data Quality and Integrity Controls]] · [[Data Warehouse and Data Lake Security]] · [[eDiscovery and Data Retention]] · [[Logs and Telemetry as Sensitive Data]] · [[Domain 2 - Index]]