AI Agent Security

Approved, Unknown, or Unowned? A Practical Framework for AI Agent Governance

A useful governance process distinguishes what is approved, what lacks an accountable owner, and what still needs investigation—without treating missing evidence as proof of wrongdoing.

An AI agent inventory becomes more useful when it helps teams decide what to review next. But classification can create confusion if labels are vague or if missing information is treated as proof that an agent is unsafe.

A practical governance model starts with a small number of questions: do we know who is accountable for this agent, and can we verify that its model or deployment is approved under our policy?

These questions do not cover every risk. They provide a manageable first layer for sorting an inventory and directing follow-up.

Start with two dimensions

Ownership

An owner is a person or team accountable for the agent's purpose, maintenance, access, and review. A resource creator is not necessarily its long-term owner. Ownership should be supported by reliable evidence and should remain valid when people change roles.

Model or deployment approval

Approval should refer to a documented organizational policy. Depending on the environment, it may cover the model provider, model version, deployment route, data handling, and use case. An approved model does not automatically make every application built with it safe.

Keep these dimensions separate. A known owner does not prove that the agent is approved, and an approved model does not prove that someone is accountable for the agent.

A simple classification matrix

Owner identifiedModel/deployment approval verifiedSuggested classificationNext step
YesYesApproved, subject to ongoing reviewConfirm controls and review date
NoYesOrphaned or ownership gapIdentify an accountable owner
YesNoApproval review neededVerify policy status and use case
NoNoUnclassifiedInvestigate identity, purpose, and provenance

These labels are suggested terminology, not a universal standard. Adapt them to your policy and make the definitions visible to the people using the inventory.

Keep evidence and confidence visible

Every classification should answer: what evidence supports this status? A record might show an owner from a cloud tag, model information from a resource definition, or approval from an internal registry.

Record the source, timestamp, and confidence. If a scanner cannot read a property because it lacks permission, label the field as unavailable or unknown. Do not silently convert missing data into “not approved.”

This distinction matters operationally. A confirmed policy violation may require containment, while an incomplete record may simply need a better data source or an owner to confirm details.

Add risk context after the first classification

Ownership and approval are only a starting point. Add other dimensions as your program matures:

  • What data can the agent access?
  • Which tools and actions are available?
  • Is the agent exposed to external users or untrusted content?
  • Does it operate in a critical workflow?
  • Are actions logged and reversible?
  • When was the agent last reviewed?

Use this context to prioritize investigations. An unowned agent with broad access to sensitive systems may warrant more urgent attention than an unowned experiment isolated in a test environment. Verify the access before drawing that conclusion.

Define a governance workflow

A classification system needs an operating process.

  1. Discover: Collect agent records from approved sources and document coverage limitations.
  2. Enrich: Gather ownership, model, environment, access, and source evidence where available.
  3. Classify: Apply documented rules and keep unknown states explicit.
  4. Assign: Route each gap to an accountable team with a due date appropriate to the risk.
  5. Resolve: Confirm ownership, complete approval, restrict access, or retire the resource.
  6. Review: Reassess after significant changes and on a defined schedule.

Provide a way for teams to correct incorrect ownership or approval data. Without a correction path, inventories become stale and users lose trust in the classification.

Avoid turning labels into verdicts

“Shadow AI” is a useful shorthand for AI use outside established visibility or governance, but it can cover very different situations. A team may have an approved model but no registered owner. Another may have a known owner using a model that has not completed review. A third may be an abandoned experiment.

Those situations need different responses. Clear subcategories help teams investigate the underlying issue instead of applying the same action to every record.

Measure governance by resolution

Track how many agents have verified owners, how many have completed required approval, how long gaps remain open, and whether high-risk access issues are resolved. Also track inventory coverage and the age of collected evidence.

The goal is not to make every record green. It is to make the state of the environment understandable and the next action clear.

Good AI governance turns uncertain inventory data into accountable decisions—without pretending uncertainty is certainty.

Back to insights