Enforce least privilege

Give each agent only what its task needs.

Least privilege turns an access review into concrete restrictions. Define the smallest set of systems, records and actions needed for a task, then enforce that scope in the underlying tools and services.

What to change

• Use dedicated identities with narrowly scoped permissions instead of shared administrator accounts.
• Remove unused tools and prefer specific operations over unrestricted command execution.
• Require approval for high-impact actions such as deleting records or exporting sensitive files.

A practical example

An agent that summarises invoices can read the relevant invoice records without permission to edit payment details or delete documents. Enforce those restrictions in the database and tool configuration so that they do not depend solely on instructions given to the model.

The result

A set of proposed permission changes and a validation plan. Apply changes with system owners, check that the intended workflow still works and record any exceptions.

A focused aioscope audit helps identify gaps and define next steps. Implementation, ongoing monitoring and any testing are agreed separately within an authorised scope.