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 1–17 of 17 evidence records

Clear all filters
RunlayerUnapproved AI use discoverySource checkedStrong public support for this requirement

Runlayer claims discovery of unmanaged agents, MCPs, skills, plugins, and client configurations with visibility into agent sessions.

Surface Shadow AI from unmanaged agents, MCPs, skills, plugins, and client configs
RunlayerControls for unapproved AI useSource checkedStrong public support for this requirement

Runlayer claims policy over what users and agents may access under identity, budget, OAuth grant, and runtime conditions.

Set what users and agents can access, under which identity, budget, OAuth grant, and runtime conditions.
RunlayerSensitive-data protection for generative AISource checkedLimited public support for this requirement

Runlayer claims pre-action runtime scanning of tool calls, outputs, intent, and sensitive data.

scan tool calls, outputs, intent, and sensitive data before risky actions reach company systems
RunlayerBrowser and business-application controlsNo supporting claim found

Runlayer materials reviewed did not provide a public claim for browser or software as a service (SaaS)-session controls for employee AI use.

No quoted source text is recorded for this claim.
RunlayerAI gateway, tool-connection, and runtime controlsSource checkedStrong public support for this requirement

Runlayer claims an approved Model Context Protocol (MCP) catalog and governed Model Context Protocol (MCP) gateway across major AI clients.

serve them through a governed MCP gateway across every major AI client
RunlayerAction-taking agent monitoringSource checkedStrong public support for this requirement

Runlayer claims visibility, policy, and audit across agent sessions, MCPs, skills, plugins, memory, triggers, and scoped permissions.

full visibility into every agent session
RunlayerNon-human identity and service-account securityNo supporting claim found

Runlayer materials reviewed did not provide a public claim for non-human identity, service-account, secret, or workload credential lifecycle controls.

No quoted source text is recorded for this claim.
RunlayerAI coding-agent and workstation securitySource checkedLimited public support for this requirement

Runlayer claims centralized controls for employees using Claude, Cursor, ChatGPT, Codex, internal agents, Model Context Protocol (MCP) servers, and existing AI clients.

employees are adopting Claude, Cursor, ChatGPT, Codex, and internal agents
RunlayerAI cost and usage controlsSource checkedLimited public support for this requirement

Runlayer claims centralized AI cost monitoring, spend attribution to teams and workflows, and budget-conditioned access for users and agents.

Monitor AI usage, cost, adoption, and agent activity in one place, then tie spend back to the teams and workflows getting real value.