ASAI Security ResearchIndependent public-source research
Public reviewread only

Public-source research

Vendor evidence

Review what vendors say publicly, the exact quoted source text, the security requirement each statement may support, and what still needs verification.

Research library coverageCounts describe the research workflow, not vendor quality or product effectiveness.View details
Evidence records1280
Source checked863
Needs verification0
Source captured0
No supporting claim found411
Excluded from evidence6

Showing 21–40 of 72 evidence records

Clear all filters
Microsoft Purview DSPM for AINon-human identity and service-account securityNo supporting claim found

Microsoft Purview AI protection materials reviewed did not provide a clear non-human identity or service-account lifecycle security claim.

No quoted source text is recorded for this claim.
Noma SecurityNon-human identity and service-account securitySource checkedLimited public support for this requirement

Noma claims it supports identity and access controls for AI applications and agents as part of pre-deployment boundaries.

setting proper identity and access controls for every AI application and agent
JetStream SecurityNon-human identity and service-account securitySource checkedStrong public support for this requirement

JetStream claims every AI workflow is tied to a provable owner by binding people, agents, NHIs, and model usage into an accountable identity fabric.

Every AI workflow is tied to a provable owner by binding people, agents, NHIs, and model usage into one accountable identity fabric. Raw model provider secrets are replaced with virtual, revocable keys scoped to the approved Blueprint design, so you can rotate, rate‑limit, or kill access without code changes.
Netskope AI SecurityNon-human identity and service-account securitySource checkedLimited public support for this requirement

Netskope claims visibility into non-human activity for AI agent interactions through Model Context Protocol (MCP) traffic monitoring.

Monitor the MCP traffic that enables your AI agent interactions, giving visibility into non‑human activity and preventing unauthorized data access or risky connections.
Singulr AINon-human identity and service-account securitySource checkedLimited public support for this requirement

Singulr Agent Pulse claims auditable records of agent actions, data access, and policy enforcement, with controls based on agent type, tool access, and scope.

Agent Pulse provides auditable records of agent actions, data access, and policy enforcement
Prompt Security / SentinelOneNon-human identity and service-account securitySource checkedLimited public support for this requirement

Prompt Security from SentinelOne claims visibility into agents and Model Context Protocol (MCP) servers plus least-privilege access enforcement for AI agents.

Enforce least-privilege access so agents operate only within their defined scope
AIM Security / Cato NetworksNon-human identity and service-account securitySource checkedLimited public support for this requirement

Cato AI Security claims it discovers and analyzes enterprise AI agent activity and monitors interactions between agents, models, and Model Context Protocol (MCP) servers.

monitor every interaction between agents, models, and MCP servers
Oasis SecurityNon-human identity and service-account securitySource checkedStrong public support for this requirement

Oasis Security claims it secures AI agents and non-human identities across IaaS, software as a service (SaaS), PaaS, and on-prem environments.

Oasis secures AI agents and non-human identities across IaaS, SaaS, PaaS, and on-prem environments
Grip SecurityNon-human identity and service-account securitySource checkedLimited public support for this requirement

Grip Security claims visibility into non-human identities and over-permissioned tools as part of AI and software as a service (SaaS) exposure management.

Surface over-permissioned tools and non-human identities (NHIs)
WitnessAINon-human identity and service-account securitySource checkedLimited public support for this requirement

WitnessAI claims governance across human and AI-agent workforces, including visibility into agent tools and data access.

human and digital workforce
Lasso SecurityNon-human identity and service-account securitySource checkedLimited public support for this requirement

Lasso Security claims AI agent inventory includes exposed actions and sensitive data reachability to support agent risk analysis.

what actions they can perform, what sensitive data can they reach
RecoNon-human identity and service-account securitySource checkedLimited public support for this requirement

Reco claims it makes agents, integrations, and non-human identities visible and maps what they can access.

Every day, your business deploys more agents, integrations, and non-human identities. Most of them operate invisibly. Reco makes them visible, maps what they can access, and tells you when they deviate from policy, before they become a liability.
ZenityNon-human identity and service-account securitySource checkedLimited public support for this requirement

Zenity claims visibility into AI-agent ownership, permissions, integrations, access paths, and least-privilege posture.

ownership, permissions, integrations, and runtime behavior
Nightfall AINon-human identity and service-account securityExcluded from evidenceNo supporting claim found

Nightfall claims detection of secrets, credentials, application programming interface (API) keys, and certificates in generative AI prompts and AI workflows.

credentials and secrets such as passwords or API keys
Astrix Security / CiscoNon-human identity and service-account securitySource checkedStrong public support for this requirement

Astrix Security claims it discovers, secures, and manages AI agents and NHIs and remediates excessive privileges and vulnerable configurations.

Identify and remediate AI agents and NHIs with excessive privileges, vulnerable configurations, abnormal activity, and policy violations.