Defender Impact
Enterprises have been deploying AI agents with user-level permissions but without any systematic runtime control over what those agents actually do — a gap that sits squarely between identity governance (which covers provisioning) and endpoint detection (which rarely models agent behaviour). Bay directly addresses this gap with a control plane that acts at the moment of action, not after the fact.
Capability Overview
Bay emerged from stealth in November 2026 with $50 million in funding, founded by three alumni of IDF Unit 8200. Its core value proposition is a single control plane for agentic AI that spans discovery, understanding, and enforcement.
On deployment, Bay automatically builds a full inventory of AI agents, coding assistants, MCP servers, skills, extensions, and local models across the organisation, mapping how they interconnect and flagging risky tool combinations. This inventory is continuous, not point-in-time.
Bay then follows each agent session from first prompt to final action. Its Enforcer component evaluates every proposed action in the context of the full session — not just the individual request — and decides in milliseconds whether to allow, refer, redirect, or deny the action. The session-level context is significant: it allows Enforcer to detect behavioural sequences that look benign in isolation but represent drift or manipulation in aggregate.
Policy for Enforcer is generated and maintained automatically by Lighthouse, Bay’s embedded AI system, which builds baselines from the organisation’s own activity history. This reduces the cold-start problem that has historically made runtime enforcement impractical: security teams no longer need to manually author agent behaviour policies from scratch.
By operating at the action layer, Bay claims protection regardless of whether problematic behaviour originates from prompt injection, misconfiguration, or organic purpose drift — covering both adversarial and non-adversarial failure modes.
Defensive Advances
- Shadow agent visibility: Defenders can now discover AI agents that were never formally inventoried — including MCP servers and local models that bypass centralised procurement.
- Runtime least-privilege enforcement: For the first time, enterprises can enforce what an agent is allowed to do at the point of action, not just at the point of access provisioning.
- Session-aware anomaly detection: By tracking the full session arc, defenders gain the ability to identify purpose drift and multi-step manipulation that per-request monitoring cannot surface.
- Reduced policy authorship burden: Auto-generated baselines mean smaller security teams can operate governance programmes that previously required specialist agent-security expertise.
- Unified governance surface: A single control plane across heterogeneous agent environments replaces fragmented, per-tool audit processes.
Residual Gaps
Several maturity questions will determine how quickly organisations realise Bay’s full value:
- Framework coverage breadth: It is not yet publicly documented which agent frameworks, orchestrators, and MCP server implementations Bay supports natively. Organisations running bespoke or less common frameworks should validate coverage before committing.
- Policy quality at cold start: Auto-generated policies derived from activity history will only be as good as the baseline data. Organisations with immature or inconsistent agent usage histories may generate permissive initial policies that require substantial manual review.
- Enforcer latency at scale: Millisecond enforcement decisions are claimed, but production validation at high agent concurrency has not been independently assessed. Teams running latency-sensitive agentic workflows should benchmark before deploying in blocking mode.
- Integration with existing IAM and SIEM stacks: The value of a control plane compounds when its signals feed into broader security operations. The maturity of Bay’s integration ecosystem with SIEM, SOAR, and PAM tooling is not yet established.
- Policy governance lifecycle: Auto-generated policy is a starting point, not a substitute for formal policy review. Organisations will need processes to audit, approve, and version Lighthouse-generated policies over time.
Framework Mapping
Bay most directly addresses LLM08 (Excessive Agency) by enforcing constraints on what agents can do beyond their intended scope. It provides runtime detection relevant to LLM01 (Prompt Injection) by evaluating actions in session context rather than trusting agent output at face value. The discovery and inventory capability helps close LLM07 (Insecure Plugin Design) gaps by surfacing risky tool combinations. ATLAS techniques addressed include AML.T0051 (LLM Prompt Injection), AML.T0080 (AI Agent Context Poisoning), AML.T0086 (Exfiltration via AI Agent Tool Invocation), and AML.T0103 (Deploy AI Agent).
Deployment Considerations
Organisations should sequence Bay adoption as follows: (1) run discovery-only mode first to build an accurate agent inventory before enabling enforcement; (2) review Lighthouse-generated policies against your least-privilege standards before activating Enforcer in blocking mode; (3) integrate Bay’s action logs with your SIEM before go-live to ensure enforcement events are captured in existing detection workflows; (4) define escalation paths for Enforcer’s referral decisions so that human-in-the-loop reviews do not become bottlenecks.
Defender Checklist
- Conduct a pre-deployment audit of all known AI agents, MCP servers, coding assistants, and local models in your environment
- Deploy Bay in discovery-only mode and validate the auto-generated inventory against your CMDB
- Review Lighthouse-generated policies with your least-privilege policy owner before enabling blocking enforcement
- Define and test Enforcer referral workflows so human review decisions are operationalised, not ad hoc
- Integrate Bay action logs with your SIEM and set alerts for high-frequency deny events and novel tool combinations
- Benchmark Enforcer latency against your most time-sensitive agentic workflows before full production rollout
- Establish a quarterly policy review cadence for Lighthouse-generated baselines