- Published
- Source
- Help Net Security
- Filed under
- AI for defence
In this Help Net Security interview, Michael Scott, CISO at Immuta, talks about how organizations should handle permissions for AI agents. He argues agents should be treated as lower-trust identities that don’t inherit everything their user can access. Scott explains why agent privilege creep differs from the human kind, how authority should pass to sub-agents, and why authentication alone does not secure what an agent does. He predicts at least two major enterprises outside the … More →…
Using AI safely
- Know which AI tools your organisation uses, and what data goes into them.
- Treat AI agents like any other identity: least privilege, logging and a named owner.
- Test AI features for prompt injection and data leakage before customers reach them.
More helpNCSC: guidelines for secure AI system development (opens in a new tab)
MyCyberWay training
AI security · in both programmes
AI is part of the attack surface now. Learn to watch it.
Blue Team Analyst covers Security Copilot in triage and monitoring the AI itself: inherited permissions, prompt injection and Purview DSPM for AI. Blue Team Engineer secures the deployment: Copilot pre-flight hardening, agent identity and tool allow-lists.
- Security Copilot in triage
- Prompt injection and DSPM for AI
- Agent identity and allow-lists
Headlines and short summaries only, except where a public body publishes under an open licence. Every story links to its publisher, who owns it. MyCyberWay does not edit or endorse third-party reporting.
