AI Governance & Security Vendor Wiki

4 min read

Red Access

Agentless “secure browsing” platform that adds enterprise security to any existing browser via a session-based architecture — pitched as a lightweight SSE alternative with no agents or network overhaul. Primary category: enterprise-browser.

One-liner — Secures web/SaaS/GenAI sessions inside the browsers people already use, without deploying a dedicated browser, endpoint agent, or rerouting traffic through a network stack.

What it does

Red Access protects browsing sessions across browsers, web apps, and SaaS/GenAI tools: data-loss prevention, secure access to corporate assets, and protection for remote workers on untrusted networks and unmanaged/BYOD devices. It markets itself as “the world’s first agentless secure browsing platform” and as a way to extend Security Service Edge (SSE)–style controls “beyond the perimeter” without the heavy infrastructure, agents, or rollout delays of traditional SSE/proxy stacks.

Where it sits in the stack

enterprise-browser category, UX layer. Like other browser-security tools it primarily controls the egress leg (what data can leave a session — uploads, downloads, paste-into-GenAI) and the untrusted-input leg (hostile web content) at the user’s last mile, sitting on the boundary between the untrusted web (red zone) and corporate apps/data. Its session-based design integrates with existing firewalls/SSE rather than replacing them.

Deployment & architecture

Delivered as SaaS with an agentless, session-based architecture — no endpoint agent and no network re-architecture; it integrates with existing infrastructure such as firewalls and extends SSE capabilities. This positions it against both inline-proxy/RBI designs and dedicated-browser approaches. (Exact in-browser delivery mechanism — extension vs injected runtime — to verify against current docs.)

Positioning & differentiators

Red Access plays in the “secure any browser, agentless” segment:

  • vs seraphic — closest peer; both secure existing browsers without rerouting traffic. Red Access emphasizes an agentless, SSE-extension/session framing; Seraphic emphasizes browser-runtime protection and was acquired by CrowdStrike.
  • vs layerx — both deliver browser-layer security on existing browsers (LayerX via extension); direct competitors.
  • vs island and prisma-access-browser — those ship a dedicated managed Chromium browser; Red Access avoids deploying a new browser.
  • vs menlo-security — Menlo’s heritage is remote browser isolation/proxy; Red Access avoids the proxy/network overhaul.
  • vs chrome-enterprise / microsoft-edge-business — native browser-management from the browser makers; Red Access is browser-agnostic with added security/DLP.

Ownership, funding & M&A

  • Independent / venture-backed as of 2026-06-28. No acquisition found.
  • Founded 2021 in Tel Aviv, Israel; CEO and co-founder Dor Zvi.
  • $17M Series A announced 2025-09-10, led by Norwest Venture Partners, with Ten Eleven Ventures, SentinelOne’s S Ventures, Elron Ventures, and Singtel Innov8 Ventures. Total funding $23M.
  • The research brief flagged checking for a Palo Alto Networks (or other) acquisition; none was found. SentinelOne appears only as a financial investor (S Ventures), not an acquirer — no contradiction.

CTO / hedge-fund lens

Priority: optional. For a hedge fund whose sensitive work lives in the browser and SaaS, an agentless browser-security layer is an attractive low-friction control, especially for contractors, BYOD, and remote access on untrusted networks, and for governing GenAI usage/data egress. The agentless framing means fast pilots without endpoint/agent rollout. Caveats for a buyer: smaller, earlier-stage vendor (Series A, ~$23M raised) — weigh vendor-maturity and longevity risk, and verify depth of DLP/GenAI controls in a pilot. No direct SR 11-7 / model-risk role; relevance is data egress and AI-usage governance, not model validation.

Competitors / alternatives

seraphic, layerx, island, menlo-security, prisma-access-browser, chrome-enterprise, microsoft-edge-business

Open questions / to verify

  • Exact in-browser delivery mechanism behind the “agentless” claim (extension vs injected runtime vs network session).
  • Customer traction / named references and depth of GenAI DLP controls.
  • Whether the ~$6M pre–Series A capital was a formal seed round (date/lead unverified).

Sources

History

  • [2026-06-28] Stub created from seed registry.
  • [2026-06-28] Researched; established founded 2021 (Tel Aviv), CEO Dor Zvi, $17M Series A 2025-09-10 led by Norwest, $23M total. Confirmed company is independent (no acquisition); SentinelOne is an investor not an acquirer. Set ownership=independent, confidence high. No HARD contradiction (no Palo Alto / other acquirer found).

Graph View

Backlinks