Agent Governance Register

Reviewed

GOV-22: Data access boundaries

In short: Define which data classes each agent may read or write, and enforce those limits at the data source or gateway. Tool permissions alone do not stop an agent from reading a whole customer table. Data boundaries keep sensitive records out of prompts and outputs.

1GOV-22

What does GOV-22 require?

Define which data classes each agent may read or write, and enforce those limits at the data source or gateway.

Why does it matter?

Tool permissions alone do not stop an agent from reading a whole customer table. Data boundaries keep sensitive records out of prompts and outputs.

How do you test it?

  1. Ask for the data classes allowed for three agents.
  2. Request restricted data through an agent and confirm refusal.
  3. Check boundary decisions appear in the audit log.

Which platforms document GOV-22?

No platform in the register documents this control in full.

Which framework references apply?

No framework mapping is confirmed for this control yet. See the framework crosswalks for what we checked.

Which controls are related?

Reviewed by The Register desk