Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Your developers are shipping agents, MCP servers, and APIs faster than security can see them. GitHub Connect changes that. Salt scans your repositories and surfaces every agent, MCP server, and API hiding in your codebase, then maps them into the Agentic Security Graph. You see the agentic infrastructure forming in code, before it ever reaches production. No more waiting for runtime to find out what shipped. No more blind spots between dev and prod. Govern what's being built from day one.

Zero wait. Agentless. With Salt Cloud Connect for AWS, organizations can instantly discover APIs, MCP servers, and agentic activity across AWS environments (without deploying sensors or routing traffic). Because in the agentic era, you can’t secure what you can’t see. See it in action.

Secure your Agentic Action Layer and see where your Databricks MCP servers are communicating with detailed descriptions of what they do.

Secure your Agentic Action Layer and see where your Databricks MCP servers are communicating with detailed descriptions of what they do.

Your developers are shipping agents, MCP servers, and APIs faster than security can see them. GitHub Connect changes that. Salt scans your repositories and surfaces every agent, MCP server, and API hiding in your codebase, then maps them into the Agentic Security Graph. You see the agentic infrastructure forming in code, before it ever reaches production. No more waiting for runtime to find out what shipped. No more blind spots between dev and prod. Govern what's being built from day one.

As enterprises shift from conversational to agentic AI, the real risk moves from model outputs to the action layer; the MCP servers and APIs through which agents execute real-world tasks. The Agentic Security Graph frames this risk across three interconnected layers (LLM, MCP servers, APIs), showing how compromises at any layer can propagate and why existing LLM-focused controls leave the most consequential surface unmonitored.

Most enterprise AI security investment is focused on the model layer—guardrails, output filtering, LLM governance. That's necessary. It's not sufficient. AI agents take actions: they call APIs, invoke MCP servers, access databases, and trigger downstream workflows. The Salt Security Agentic Security Platform was built to secure that action layer (the infrastructure your agents actually operate across).

Zero wait. Agentless. With Salt Cloud Connect for AWS, organizations can instantly discover APIs, MCP servers, and agentic activity across AWS environments (without deploying sensors or routing traffic). Because in the agentic era, you can’t secure what you can’t see.

AI agents are operating inside your enterprise; querying databases, triggering workflows, and taking action through APIs. As AI agents are adopted, organizations cannot see, track, or control what these agents are actually doing. In this session, Roey Eliyahu, Co-Founder and CEO of Salt Security, challenges the industry’s narrow focus on LLM safety and exposes the much larger, invisible attack surface created by agentic systems.

Sisense powers analytics experiences inside the applications businesses rely on every day. As an API-first platform, securing those connections is critical, especially as AI agents increasingly operate through APIs to access data and trigger workflows. In this conversation, Sangram, CISO and VP of IT at Sisense, and Michael Callahan, CMO at Salt Security, discuss how Sisense approached API security strategically to protect their platform, maintain customer trust, and support innovation in the Agentic AI era.