Least privilege Give every person, program and AI agent the minimum access needed.
Short answer. Least privilege is the security principle that every person, program or AI agent gets only the access needed for its assigned task, and no more. NIST defines it as restricting the access privileges of users, or of processes acting on their behalf, to the minimum necessary to accomplish assigned tasks. The aim is to limit the damage from mistakes, stolen passwords and misbehaving software. In an office: a receptionist does not need the partners’ folder, an intern’s account should not be able to export every client file, and an AI assistant that only summarises mail should not be able to send mail.
01
Least privilege in four places
NIST SP 800-53 makes least privilege a control, AC-6: allow only the accesses that are necessary for users, or processes acting on their behalf, to accomplish assigned tasks, and apply the same rule to system processes, not only to people.
Where
Typical excess
Better
Staff accounts
Everyone can open every shared folder
Access by role, reviewed whenever people move
Administrator accounts
A super-admin account used for daily email and browsing
A separate administrator account, used only for administration, as the UK NCSC advises
Applications and service accounts
A database login that can update and delete when the tool only reads
A read-only login for a read-only job, as in OWASP’s example
AI agents and tools
A mailbox tool that can read, send and delete
A read-only scope, with a person approving any send
02
How to apply it
Write down what each role needs in order to do its work, then remove everything else.
Start new accounts with nothing and add access on request.
Time-limit elevated access. The NCSC says time-based privileged access can reduce the impact of a leaked administrator credential, partly because each grant is audited.
Use tiers for administrators, so that a lower-level administrator cannot reach everything. The NCSC describes a tiering model for this.
Review access at every joiner, mover and leaver event, and every quarter.
Log the use of privileged access, and look at the log.
03
Least privilege for AI
The model is not a security boundary. OWASP’s guidance on excessive agency traces agent failures to excessive functionality, permissions or autonomy. It recommends minimising the tools an agent can call, the functions inside each tool and the permissions each tool holds. It also recommends running tools in the context of the user who asked, and authorising requests in downstream systems rather than trusting the model.
The same logic applies to data. OWASP’s entry on sensitive information disclosure says to limit access to sensitive data on least-privilege lines, granting only the data necessary for the specific user or process, and to restrict the data sources a model can reach. For MCP connectors, the protocol’s security guide describes a progressive least-privilege scope model that starts from a minimal set of scopes.
04
Signs it is missing
Shared logins, or an administrator password kept in a spreadsheet.
Everyone can see every client folder.
A connector asks for access to everything and nobody questioned it.
Leavers keep access for weeks.
The AI assistant can open files that the person asking cannot.
Nobody can say who last changed a setting.
05
Where ANVE stands
ANVE is built for many named users. Its security page (/security) says roles today are administrator and user, with teams and finer roles not on ANVE yet. Cloud models exist only if an administrator adds a provider, connectors only if an administrator approves one, and the tools an agent can use must be approved by an administrator; a tool that changes is switched off, and every tool call is logged. Every model call is logged with the user, the app, the model and whether it ran locally or in the cloud.
06
Questions people ask
Is least privilege the same as role-based access control?
No. Least privilege is the principle. Role-based access control is one way to apply it, by giving each role only the permissions the job needs.
Does least privilege slow people down?
It adds a step when someone needs more access. Fast, logged, time-limited requests keep the delay small, and a stolen account then exposes less.
How does least privilege apply to an AI agent?
Give it only the tools the task needs, with read-only permissions where possible, running as the person who asked, and require a person’s approval for anything that sends, pays or deletes. That is OWASP’s guidance.
Who decides what the minimum is?
The owner of the data or process, with IT. Start from the job and adjust when real work shows a genuine need.
07
What is not real yet
No sealed ANVE unit exists; every image of the appliance on this site is a labelled render. The software runs today on a development machine. No customers yet, no certifications, no delivery date, and the final price is not announced.
Reservations are ₹999 in India or US$12 elsewhere, refundable in full until you confirm an order in writing (terms). Offices that cannot use cloud AI can apply to be one of ten design partners.
