Overview

Product details compiled from public sources, each with a citation.

Vendor
Silverfort1agent
Description
Discovers AI agents across cloud and SaaS, maps each to its human owner, and enforces least-privilege policy at runtime through platform integrations and an MCP gateway.4agent
Deployment
Not found3agent
Status
Active2agent

Matrix Coverage

Where this product defends, by asset class and NIST CSF function. The Coverage column shows whether each asset is Primary, Secondary, or Adjacent to what the product does. The table omits empty rows and columns.

Asset class IdentifyProtectDetect Coverage Source
AI Traffic Identify: Not covered Detect: Not covered Secondary 3
AI Agent Identities Primary 4

Framework Relevance

These frameworks include controls relevant to the asset classes Silverfort AI Agent Security defends. This is an editorial inference from the AI Defense Matrix asset-level crossmap, not a statement that Silverfort implements these controls or is certified against them.

Expand Collapse
Framework Asset class Relevant controls
NIST IR 8596 AI Traffic AI data flows; APIs; inference endpoints (traffic side); model registries and dataset sources
AI Agent Identities Agents as autonomous principals; Keys; Integrations and permissions
CSA AI Controls Matrix AI Traffic Infrastructure Security; Interoperability and Portability
AI Agent Identities IAM; Governance, Risk and Compliance
ISO 42001 AI Traffic A.8 Information for interested parties; A.9 Use of AI systems; A.10 Third-party and customer relationships
AI Agent Identities A.9 Use of AI systems; A.3 Internal organization; A.5 Assessing impacts of AI systems
Google SAIF AI Traffic Harden and monitor infrastructure; network-level access and egress controls
AI Agent Identities Focus on Agents (explicit SAIF section); identity, authorization, and delegation controls
SANS Critical AI Security Guidelines AI Traffic Conventional Security Controls (authenticate and control access to inference APIs; API key management); Model I/O Handling (rate limiting; egress output filtering); Monitoring (interaction and API-usage logging)
AI Agent Identities Secure Agentic Systems and AI Autonomy Controls (defined function scope; API and function-call gating; escalation and fallback); Limit Model Behavior (least-privilege focused functionality; human oversight; override capabilities)
MITRE ATLAS AI Traffic AML.T0057 LLM Data Leakage; AML.T0024 Exfiltration via AI Inference API (network-side observation)
AI Agent Identities AML.T0053 AI Agent Tool Invocation; credential and delegation-chain abuse
OWASP AI Exchange AI Traffic Runtime threats: data leakage via AI egress; network-level access control gaps
AI Agent Identities Runtime threats: unauthorized agent actions, capability abuse, delegation chain exploitation
OWASP LLM Top 10 AI Traffic LLM10 Unbounded Consumption (cost and rate control); shadow AI egress and output handling
AI Agent Identities LLM06 Excessive Agency; LLM05 Improper Output Handling; unauthorized actions by AI agents
OWASP Agentic Security Top 10 AI Traffic ASI07 Insecure Inter-Agent Communication; ASI02 Tool Misuse and Exploitation (egress and tool-invocation scope); ASI04 Agentic Supply Chain Vulnerabilities (MCP and tool-registry trust)
AI Agent Identities ASI03 Identity and Privilege Abuse; ASI10 Rogue Agents; ASI09 Human-Agent Trust Exploitation; ASI02 Tool Misuse and Exploitation (when tied to agent permissions)

Provenance

Last sourced 2026-10-26.

Expand Collapse

Sources

  1. Silverfort
    Vendor source accessed 2026-10-26
  2. Silverfort Secures AI Agents on Google Cloud Agent Gateway
    Vendor source accessed 2026-10-26
  3. Silverfort AI Agent Security
    Vendor source accessed 2026-10-26
    • “Silverfort evaluates against Authorization Planes and Scopes, and denied calls are blocked at the gateway.”
  4. Secure AI Agents at runtime
    Vendor source accessed 2026-10-26
    • “Enforcement is delivered via MCP Gateway for broad coverage, and via native integrations with leading agentic platforms for deep, platform-level control.”

Changelog

  1. Added at the request of a contributor affiliated with Silverfort, from the Silverfort product pages and blog.

Found an error? Corrections are welcome. Suggest an edit.