
Does Restricting AI Agents to Approved Applications Protect Your Data?
Only partly. An allowlist controls where an agent goes, not what it reads on an approved page. Check what the model receives from each approved screen.
Research topic
Research on Rule of Two: AI agent security, tokenization and checks for sensitive data access before allowing enterprise workflows to run.

Only partly. An allowlist controls where an agent goes, not what it reads on an approved page. Check what the model receives from each approved screen.

By architecture, not instruction: never let an agent hold sensitive data, untrusted input and outward actions at once. Check which one each workflow drops.

Protect the architecture, not the model: limit what injected text can see and trigger, since adaptive attackers beat model defenses. Check what it holds.

Only when the reading agent cannot also hold real sensitive data and act outward in one session, since any page may carry instructions. Check which it has.

Three capabilities in one agent: private data, untrusted content and external communication, which turn a planted instruction into theft. Remove one.