Build an access request decision record
Convert an access request into a decision record that supports least privilege and auditability.
A project access request says only: Need data warehouse access for project Atlas. The approver knows the requester and is tempted to grant the standard analyst role. Driver -> Approver -> Contributors -> Scope -> Duration The common trap is approving based on familiarity. Recognition of the person is not evidence that the requested permission is scoped to the work. Name the decision roles Driver: requester Sam. Approver: data owner Nia. Contributors: project lead and security reviewer. Informed: Sam's manager. DACI prevents the access decision from becoming a private favor. The approver is the person accountable for the data risk,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in