← Files Data Engineering CopilotARCHIVED FILE
references/security-governance.md
816 Bytes · Nov 21, 2026 · 12:53 UTC
# Governance and access safety Classify datasets by sensitivity and ownership, identify tenant boundaries, data region/residency and allowed downstream consumers. Apply least-privilege identities and secret stores; never display credentials in code or logs. Validate row/column policies, network restrictions, encrypted paths, service identities and release approval. Data samples and debugging logs can themselves contain sensitive values; use representative redacted fixtures and bounded inspection. Ensure deletes/retention requests propagate into materialized tables, extracts, backups and analytics outputs as required. For OneLake shortcuts and cross-warehouse sharing, note the effective identity/credential and read permissions. Do not assume workspace membership alone implies authorized source access.
SHA-256: 79c5bddcd2d4c951580e781639b8d20e590643ddc2777922b4b4bab70ba916bf