Palo Alto, CA, USA
2016
  |  By Michael Callahan
In conversations with CISOs about their agentic environments, the question I ask first is not whether they have agents deployed. Most do. It is not whether those agents are creating value. Most are. The question I ask is whether they have mapped their Agentic Security Graph. Almost none of them have. And that gap, between the agentic infrastructure that exists inside their organizations and the visibility they have into it, is where the most serious AI security risk in the enterprise lives right now.
  |  By Roey Eliyahu
Last week, researchers at OX Security published findings that should stop every security leader in their tracks. They discovered a critical vulnerability baked directly into Anthropic's Model Context Protocol SDK, affecting every supported language: Python, TypeScript, Java, and Rust. The result: remote code execution on any system running a vulnerable MCP implementation, with direct access to sensitive user data, internal databases, API keys, and chat histories. Over 7,000 publicly accessible servers.
  |  By Roey Eliyahu
Anthropic just released Claude Mythos Preview. They did not make it publicly available. That decision alone should tell you everything you need to know about what this model can do. During internal testing, Mythos autonomously discovered and exploited zero-day vulnerabilities across every major operating system and web browser. It found a 27-year-old bug in OpenBSD. A 16-year-old vulnerability in a widely used media codec.
  |  By Michael Callahan
The AI security market is crowded. Vendors are racing to protect prompts, harden models, detect jailbreaks, and scan for data leakage at the LLM layer. The investment is real. The intent is good. And most of it is missing the point. Here is the problem: agents do not just think. They act. They call APIs. They trigger workflows. They write to databases, send emails, move money, and modify production systems.
  |  By Eric Schwake
The recent supply chain attack involving Mercor and the LiteLLM vulnerability serves as a massive wake-up call for enterprise security teams. While the security industry has spent the last year fixating on prompt injections and model jailbreaks, this breach highlights a far more systemic vulnerability. The weakest link in enterprise AI is not necessarily the model itself. It is the middleware connecting the models to your data.
  |  By Eric Schwake
The era of human-centric API consumption is officially ending. Over the past year, enterprises have rapidly transitioned from simply experimenting with Generative AI to deploying autonomous AI agents that drive core business operations. These agents act as digital employees. They utilize Large Language Models (LLMs) for reasoning, Model Context Protocol (MCP) servers for connectivity, and internal APIs for execution. This evolution has fundamentally altered the enterprise attack surface.
  |  By Eric Schwake
The term AI agent is dominant in current cybersecurity discourse. Vendors, analysts, and CISOs all use the label, yet technical confusion remains regarding how agents actually operate and where the security risks reside. Beneath the surface-level familiarity, there is often significant confusion about what an AI agent actually is, how it operates technically, and most importantly for security teams, where the risk actually lives.
  |  By Roey Eliyahu
One constant I hear from CISOs I speak with is that AI agents are not coming. They are already inside organizations, reasoning through goals, selecting tools, and taking action through the same APIs that connect your most sensitive systems. And most security teams have no idea what those agents are doing.
  |  By Roey Eliyahu
This week’s McKinsey incident should be a wake-up call for every enterprise moving fast to deploy AI. Not because AI itself is inherently insecure. But because too many organizations are still thinking about AI security at the model layer, while the real enterprise risk sits in the action layer: the APIs, MCP servers, internal services, and shadow integrations that AI agents can reach, invoke, and manipulate. That is the part most companies still do not see.
  |  By Eric Schwake
When cybersecurity teams talk about risk, they usually speak in technical terms like vulnerabilities, exploits, and attack vectors. But when they walk into the boardroom, they need to speak a different language. They need to speak about cost. In the era of AI, the cost of insecure APIs has shifted from a potential liability to a tangible line item on the balance sheet. It is no longer just about the cost of a data breach.
  |  By Salt Security
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.
  |  By Salt Security
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.
  |  By Salt Security
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).
  |  By Salt Security
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.
  |  By Salt Security
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.
  |  By Salt Security
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.
  |  By Salt Security
As AI adoption accelerates, a new security risk is emerging from inside organizations, driven not by attackers, but by well-intentioned employees. Across the business, teams are rapidly building AI-powered applications, workflows, and automations using low-code/no-code platforms, custom scripts, and MCP servers.
  |  By Salt Security
After four sessions covering the technical realities, business imperatives, and security challenges of agentic AI, Salt Security’s Co-Founder and CEO Roey Eliyahu, and Salt's CMO Michael Callahan, come together for an unfiltered conversation about where the industry actually stands and where it's headed. The gap between AI ambition and operational readiness has never been wider.
  |  By Salt Security
See your Blind Spots in Minutes, not Months: How Salt Security & AWS Simplify API Security AI agents and cloud-native architectures have unleashed a wave of APIs and with them, new attack surfaces. Most security teams are struggling to keep up, especially in dynamic AWS environments where shadow and zombie APIs can easily go undetected. This Salt Security and AWS webinar explores a better approach to API discovery and security in AWS without the burden of in-line traffic collection or sensor deployments.
  |  By Salt Security
No Fluff, Just Real-World Threats This isn’t your typical marketing webinar. We cover what Agentic AI actually looks like in production, how MCP servers work to broker instructions, and what kind of new threats are emerging. Agentic AI isn’t coming. It’s already here. Autonomous agents are now operating in production environments, reasoning, remembering, and taking real actions across your systems. They’re not just generating content. They’re triggering workflows, modifying records, and making decisions. And they’re doing it over APIs.
  |  By Salt Security
API attacks are on the rise, and WAFs and gateways cannot stop them. A few highlights from our latest Salt Labs report on API security: Download the report now to benchmark yourself and use the findings to improve API security for your company.
  |  By Salt Security
API Security for Dummies walks you through how application architecture has evolved, why apps are built on APIs now, the security risk APIs present, and best practices for securing APIs. This eBook: Download this eBook to learn the most critical elements of API security and ten prioritized steps you can follow now to start securing APIs for your organization.
  |  By Salt Security
Securing your APIs is no longer a luxury, but it shouldn't be viewed as just a necessary burden either. Protecting your APIs opens the door to real business value including: Download this eBook to explore the business results customers are uncovering as they embark on their API security journey and how to quantify the value of API security in your organization.
  |  By Salt Security
API attacks include many of the tactics, techniques, and procedures (TTPs) identified in the MITRE ATT&CK framework. This white paper analyzes and maps three common API attack scenarios to the TTPs found in the MITRE Enterprise Matrix. By understanding how the MITRE ATT&CK TTPs relate to API security threats, security leaders can: Download now to learn how to defend against API attacks by leveraging this well-known security framework.
  |  By Salt Security
API security has emerged as a key priority for protecting vital data and services. It's also an area where many companies lack expertise. Salt Security has compiled this list of API security best practices, drawn from field experience and customer feedback, to help guide you on your API security journey. These API security best practices fall into multiple focus areas, including: Download this guide to obtain a comprehensive list of best practices and guidance to secure your APIs throughout their lifecycle.
  |  By Salt Security
With API attacks on the rise, and existing security technology proving to be ineffective at stopping API attacks, organizations need to take a new approach. API security offerings must provide a range of functionality to be useful to organizations, including: Download this white paper to improve awareness of what it takes to adequately secure APIs, how to evaluate a given API security offering, and what API security capabilities are necessary to protect your business.

The leading API security company, providing the context needed to discover APIs, stop attacks, and remediate vulnerabilities to accelerate business innovation.

By correlating activities across millions of APIs and users over time, Salt delivers deep context with real-time analysis and continuous insights for API discovery, attack prevention, and shift-left practices. Deployed quickly and seamlessly integrated within existing systems, the Salt Security platform gives customers immediate value and protection, so they can innovate with confidence and accelerate their digital transformation initiatives.

Complete API security for complete protection:

  • Discover all your APIs: Continuously inventory all your APIs, including shadow and zombie APIs.
  • Prevent sensitive data exposure: Identify the APIs that are exposing PII or other sensitive data.
  • Stop API attacks: Correlate activity to block attackers during reconnaissance.
  • Prevent ATO, Data Exfiltration: Thwart credential stuffing, account takeover, and data theft attacks.
  • “Shift left” with proactive API security Test APIs in pre-production to identify and eliminate vulnerabilities.
  • Accelerate incident response: Reduce the time needed to understand and resolve incidents.
  • Provide remediation insights: Share learnings from runtime analysis with dev teams to harden APIs.
  • Simplify compliance: Tie your API and sensitive data discovery and vulnerability remediation into GRC workflows.

The rich API context you need for robust discovery, attack prevention, and shift left.