Describe how least privilege reduces database blast radius and audit friction.
The safest permission is the one the account never had. A database permission is a capability. Capabilities accumulate silently: a dashboard needs a hotfix, an ETL job gets broader access, a developer keeps admin rights after an incident. Least privilege counters that drift by making access specific, owned, reviewed, and removable. Separate identities by job Application, migration, BI, support, and administrator identities should not share one powerful account. When identities match jobs, you can reason about expected behavior and detect unexpected behavior. Scope grants to the smallest useful surface Prefer role-based grants on specific schemas, views, stored procedures, or masked…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in