Fieldwork from NexNith Fieldwork · Agents pathway · Briefs
Agents pathway

Briefs

Each brief stands alone and sets out one idea in full. Together they are the reasoning behind Module 1, The tool surface. Every one is free, carries no gate, and ends with check questions put against a real artifact rather than against a description of one.

The tool is the control surface

The exposure of an AI agent is set by the functions it can invoke and the permissions those functions hold, not by the model’s accuracy.

What an AI agent can actually do

Authority is the union of the permissions the agent’s service identities hold, and it is not the set of tools the design document lists.

A limit written in the system instructions is not a control

A limit written into the system instructions is advisory, because the model reads it alongside everything else in its context and nothing rejects the action when the limit is not observed.

Binding the caller’s identity to the tool call

An agent either acts on behalf of the requester, carrying a token derived from their session, or acts as itself, carrying a service identity and a record selector the model chose.

Retrieval is part of the authority surface

A retrieval index is a read capability with a scope, so whatever it contains the agent can surface, whether or not anyone asked.

Handoffs, and why your agent inventory is wrong

A handoff makes the receiving agent’s entire tool set reachable from the originating conversation, so the effective authority of the first agent includes the second.

Scoping an assurance engagement over an AI agent

Scope is decided in the first conversation, and access conceded there cannot be recovered later without spending more than it would have cost to hold.

What evidence supports an assertion about an agent

An assertion about what an agent can do is supported by configuration, and an assertion about what it did is supported by the log.

When a finding cannot wait for the report

Interim escalation requires three conditions together, being that the exposure is live, that the reachable consequence is material, and that waiting changes the outcome.

Switching a control off is a change

A control disabled through a settings screen deploys no code, so it enters no change process and appears in no change record.

Fieldwork is independent educational material produced by NexNith. It is not affiliated with, endorsed by, or connected to ISACA or the International Association of Privacy Professionals (IAPP). AAIA, AAISM, AAIR, CISA, CISM, and CRISC are trademarks of ISACA. AIGP and CIPT are trademarks of the IAPP. No examination content is reproduced. Every organization and person named in this material is fictional.