Access drift
The gradual, often silent widening of an agent's access beyond what its scoped default granted, through vendor updates, new task requirements handled without a recorded escalation, or well-intentioned shortcuts. Per Section 3N, the reason a scoped tool-access table needs periodic, dated review rather than a one-time pass.
Defined in 2 GAGE programs, which carry 2 distinct definitions of it. The wording above is taught in Certified Agentic AI Governance Professional (CAAGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The gradual, often silent widening of an agent's access beyond what its scoped default granted, through vendor updates, new task requirements handled without a recorded escalation, or well-intentioned shortcuts. Per Section 3N, the reason a scoped tool-access table needs periodic, dated review rather than a one-time pass.
The tendency for granted access to persist and accumulate beyond the period in which it remained justified, because removing access requires someone to notice and act while granting it is a one-time, easily forgotten event.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Least Privilege for Agents · Bounding by Design, Certified Agentic AI Governance Professional (CAAGP)
- Row, column, and purpose: access that follows the data's sensitivity, not the org chart · Access and the Keys, Certified AI Data Governance Professional (CADGP)
Where it shows up at work
A definition is where Access drift starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Classifies information, applies least privilege, sets retention and acceptable-use rules, and controls what may enter a prompt, a log or an embedding.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Privacy Engineerneeds it at depth · 6 open postings this week
- Data Governance Leadneeds it at depth · 2 open postings this week
- Chief Data Officer, data leadership editionneeds working knowledge
- Chief Information Officer, technology leadership editionneeds working knowledge
- Chief Privacy Officer, AI privacy editionneeds working knowledge
- AI Security Architectneeds working knowledge · 8 open postings this week
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: ISO/IEC 27001; GDPR Article 5.
One interview question about it
How do you decide who may access which data for AI work, and how long it is kept?
Asked of candidates for data classification, access and retention. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Privacy and data protection carries it as a claim to back up: Classification and retention rules are familiar territory.
- Cybersecurity and IT carries it as work you can show: Access governance and classification are implemented, not described.
- Human resources and people operations carries it as a claim to back up: Access restriction and retention for personnel data are routine.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.