# Metano launches AI agent security platform with $12m seed
> Coverage and response depend on the deployment and identity connection.
By BIGCHANGE.AI Editorial
Published: 2026-11-20T01:10:38.183Z
Updated: 2026-11-20T01:10:38.183Z
Canonical: https://bigchange.ai/blog/metano-agent-runtime-governance

AI-generated conceptual illustration for BIG CHANGE.
Metano emerged from stealth on November 19 and announced $12 million in seed funding led by Sierra Ventures. The company says its AI agent security platform is generally available. [Launch announcement](https://metano.ai/resources/metano-emerges-from-stealth)
## The big change
- Metano describes following an agent through a work session, linking its task, identity and actions. That context is meant to help security teams judge what the agent does with its access.
- A response can involve a running process, a person's application session or a delegated access token. Metano's integration documentation gives those objects different lifecycles, making the exact target important when checking a shutdown claim.
- NIST's proposed identity principles call for bounded authority, human review at defined thresholds and records independent of the agent. Those provide a framework for deciding what an evaluation should demonstrate about a particular task.
## Deployment determines what is covered
Metano calls its linking layer Hive. Its deployment page specifies software sensors delivered through device-management systems, browser extensions, a development kit for cloud agents and connectors to hosted applications. Companion software running alongside agents in containers provides discovery and monitoring. Enforcing controls during their own agents' actions requires developers to integrate its software development kit. [Deployment description](https://metano.ai/how-it-works)
The company describes about a week of observation before tailored behavioural guardrails, starting in audit mode before gradual enforcement. Data defaults to its cloud, with analysis in a customer's environment offered as an option. [Deployment description](https://metano.ai/how-it-works)
## Which access is being ended?
Metano's September 22 integration post says its kill switch stops a running agent or Model Context Protocol tool-server process while Okta revokes associated access. Its setup guide requires administrators in both systems. The guide describes people signing into Metano through Okta and revoking their Metano sessions. It says revocation makes their issued user tokens fail on the next request. Connections using the SAML sign-in standard need the identifier of their Okta app instance before logout requests can be verified. [Integration account](https://metano.ai/resources/metano-integrates-with-okta) · [Setup guide](https://docs.metano.ai/integrations/okta)
The guide also describes Cross App Access, which lets an agent call Metano on a user's behalf. Deactivating that agent or removing its resource connection stops new grants. The token, a credential issued to the agent, remains valid until it expires. Evaluators should record those outcomes separately. [Setup guide](https://docs.metano.ai/integrations/okta)
## What a logout response establishes
Okta's catalog lists Metano with single sign-on, account creation and updates, and Universal Logout. The entry was last updated September 22. [Okta catalog](https://www.okta.com/integrations/metano/)
Okta's developer guidance explains that Universal Logout sends a request to an application to revoke a user's sessions. The application must implement an endpoint that receives the request and performs its own revocation. Okta says an immediate end to every session and token is often impossible. A successful response indicates that the application is attempting logout. The protocol does not require revocation of access tokens for success. [Protocol documentation](https://developer.okta.com/docs/guides/oin-universal-logout-overview/)
This gives an evaluator a concrete distinction to preserve. Receiving a successful logout response and observing that subsequent application access has ended are separate findings. The team needs to examine the receiving application's behaviour and token handling when interpreting its result. [Protocol documentation](https://developer.okta.com/docs/guides/oin-universal-logout-overview/)
## A task with a human decision
NIST published its proposed agent identity design tenets on October 27, drawing on public comments and stakeholder engagement. It calls for authority limited to the task, human review when defined risk thresholds are reached, and evidence logs the agent cannot alter. These are design proposals to apply according to risk and environment. [NIST design tenets](https://www.nist.gov/blogs/cybersecurity-insights/design-tenets-agent-identity-management-systems)
Consider a hypothetical support agent allowed to read a case and draft a reply, while a person approves sending it. The team would define that boundary before evaluation. A useful record would connect the assigned task, delegated identity and resulting actions, allowing the reviewer to see whether the decision requiring human approval actually reached them. [NIST design tenets](https://www.nist.gov/blogs/cybersecurity-insights/design-tenets-agent-identity-management-systems)
NIST proposes separating access decisions from agent reasoning and making predictable rules the primary control. These principles frame an evaluation of the product, without certifying its effectiveness. [NIST design tenets](https://www.nist.gov/blogs/cybersecurity-insights/design-tenets-agent-identity-management-systems)
BIG CHANGE reviewed public documentation. We did not install Metano or test its effectiveness.
## Sources
- [Metano launch](https://metano.ai/resources/metano-emerges-from-stealth) — Funding and availability.
- [Metano deployment](https://metano.ai/how-it-works) — Deployment conditions.
- [Metano and Okta](https://metano.ai/resources/metano-integrates-with-okta) — September 22 integration claim.
- [Metano Okta setup](https://docs.metano.ai/integrations/okta) — Session and delegated-token scope.
- [Okta Metano catalog](https://www.okta.com/integrations/metano/) — Listed integration.
- [Okta Universal Logout](https://developer.okta.com/docs/guides/oin-universal-logout-overview/) — Protocol response and revocation limits.
- [NIST agent identity design tenets](https://www.nist.gov/blogs/cybersecurity-insights/design-tenets-agent-identity-management-systems) — October 27 proposed principles.
The BIG CHANGE newsletter
The big picture. At your pace.
Recent stories on AI and robotics, the shifts worth watching and practical ideas to use. Choose a daily briefing, weekly digest or monthly perspective.
Next scheduled send (UTC): . Your first edition arrives at the next scheduled send after you confirm.
Your privacy, your choice.
Necessary storage supports site security and remembers your choices. Optional Google Analytics stays off until you allow it. You can read every story with necessary storage only. Privacy details