liveBook · Manning

AI governance

As explained in AI Governance

AI governance is the system of principles, processes, and oversight used to direct and control the development and use of artificial intelligence.

Giving an AI agent permission to email outsiders may look like a small feature change. If the agent can also read sensitive data and consume external content, that permission changes privacy, security, auditability, and accountability risks at once. Governance makes those risks and the authority to accept them visible before release. section 8.1

AI-specific governance is the structures, leadership, and decision processes used to direct, monitor, and control AI use. Leaders assign ownership and resources, set acceptable risk levels, and translate external requirements into policies and operational controls. The effort should be proportional: a small organization might start with a monthly risk discussion, while a larger one may need formal roles and committees. section 1.2

Approving a model or vendor is not enough. Governance also covers the surrounding system: its data, tools, permissions, users, infrastructure, and vendors. Policies must be enforced, controls tested, and safety problems routed to people who can change the system. section 3.0 section 8.1

Turn a use-case review into operating conditions:

  • Assign an owner and identify the applicable requirements, intended use, available evidence, and remaining risk. section 8.1
  • Limit data access and tool permissions to what the use case needs. Specify which actions require human approval and what records must be kept. section 8.4
  • Test controls before launch, establish what the vendor must fix, and monitor live behavior. Define who responds to problems and what triggers a pause or new review. section 3.0 section 8.4
  • Make approval conditional when necessary: reduce data access, tools, or the affected population, add a human checkpoint, or defer the launch. section 8.4

Reviewing an agent’s email capability

Before enabling third-party email, ask why the function is needed, what information may leave, and which recipients are allowed. Decide whether the agent may send messages or only draft them, when a person must approve, what gets logged, and who acts if a control fails. Revisit the decision if the model, retrieval sources, reviewers, or tool paths change. section 8.1

Governance continues after release. Production evidence may reveal unreliable retrieval, inattentive reviewers, changed model behavior, or effects missed in staging. Access limits, monitoring, and reassessment can reduce risk, but challenges such as prompt injection and explainability remain unsettled. section 8.1 section 8.5

Table 5.2 Privacy Risks and Mitigations in Agentic AI
Pillar
Agentic AI Challenge
Technical/Governance Mitigation
Collection & Purpose
Mission creep from planning/reflection; unvetted tool calls pull new data; hard to keep RoPA current.
Approved tool registry to validate an action’s purpose, data minimization and data storage region; Purpose locks on tools/data; goal-change gates (block, human approval, or just-in-time consent); least-privilege scopes; auto-update RoPA from run traces.
Lawful Basis
The agent may expand a task beyond the purpose the user or organization approved. Consent or legitimate interest may not cover the new data use.
Map lawful basis per task and data type; runtime basis checks; LIAs for legitimate interests; trigger consent or human review when scope expands.
Storage & Erasure
Persistent memories and logs extend retention; hard to honor erasure across tiers and derivatives.
Tiered memory with TTL (short working memory, bounded task logs, scoped long-term); deletion APIs across stores; administrative console to find/purge user data; avoid using erased data in future updates.
Output Integrity / Automated Decision Making
Hallucinations or misalignment lead to harmful actions; “solely automated” significant effects.
Human-in-the-loop approvals for high-risk or irreversible actions; contestation process; meaningful oversight (not rubber-stamp)
Special Category Data (Art. 9)
Incidental collection or inference of sensitive traits during tasks.
Block sensitive inference by default; classify/flag payloads; require explicit consent before processing; dataset filtering; segregate and purge when detected.
Long-term Governance & Monitoring
New failure modes from tool use, memory, and multi step tasks; weak visibility into what the agent did and why.
Agent observability: versioned tool registry; standardized traces of tool calls, data access, destinations, approvals; anomaly alerts; sandboxed networks; periodic audit of runs and metrics; policy guardrails

Compare agentic AI privacy risks with technical and governance mitigations, including purpose controls, least-privilege scopes, and checks when task scope expands. section 5.6.5

How AI Governance covers it

How deep it goes
Develops use-case review questions and operating conditions while identifying prompt injection and explainability as unsettled challenges.
Examples
Uses an agent’s third-party email permission and deployed healthcare AI safety-reporting gaps to illustrate governance decisions.
What you can do after
Evaluate AI use cases and set operating conditions, monitoring responsibilities, and triggers for reassessment.
How it connects
Connects governance with risk management, access control, privacy, monitoring, and prompt injection.

Also explained in

Compare how 5 books explain AI governance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.