The Agent-to-Agent (A2A) protocol is emerging as the de-facto standard for how autonomous AI agents talk to each other. While most of the interest around A2A has been around stateful messaging, one of its most powerful ideas remains largely unexplored: discovery, naming, and resolution. While the A2A specification provides the critical first steps toward discovery with Agent Cards, the infrastructure for truly dynamic, scalable agent ecosystems requires additional components that the spec int...| ceposta Technology Blog
Creating MCP Servers to connect functionality to LLM applications / AI agents is fairly straight forward. Most of the examples you see, however, are the simple stdio-transport MCP servers. If you wish to build MCP shared services that are exposed to applications in the enterprise, they MUST be secured. The MCP community has been iterating on a specification for Authorization, and in its recent release (ie, June 18, 2025) we have an updated Authorization spec that fixes a lot of the challenges...| ceposta Technology Blog
At first glance, AI agents seem very similar to microservices when it comes to security and identity. You need to secure the channel and authorize who is calling whom. Communication happens over the network through some HTTP transport. When a user is involved, you can potentially leverage the user’s identity. The same is true for AI agents, but with one big caveat: we can no longer be as sloppy as we’ve been with microservices when deploying AI agents.| ceposta Technology Blog
New research on simulated blackmail, industrial espionage, and other misaligned behaviors in LLMs| www.anthropic.com
Learn how to protect Model Context Protocol (MCP) servers from confused deputy attacks when implementing Dynamic Client Registration, and how Azure API Management can help mitigate these security risks.| den.dev
As organizations start to deploy AI agents in earnest, we are discovering just how easy it is to attack these kind of systems. I went into quite some detail about how “natural language” introduces new attack vectors in one of my recent blogs. These vulnerabilities aren’t merely theoretical. We’ve seen how a malicious Model Context Protocol (MCP) server could trick AI agents into leaking sensitive data like WhatsApp chat histories and SSH keys without user awareness. An Agent Mesh lays...| ceposta Technology Blog
The Model Context Protocol (MCP) and Agent 2 Agent (A2A) specification are similar RPC style protocols that specify interaction between Agents and Tools (MCP) and Agents and other Agents (A2A). They both focus on client/server remote function invocations but do not specify protocol-specific security. MCP started to dip its toes into specifying an Authorization framework, but that has been a bumpy ride so far.| ceposta Technology Blog
The Model Context Protocol has created quite the buzz in the AI ecosystem at the moment, but as enterprise organizations look to adopt it, they are confronted with a hard truth: it lacks important security functionality. Up until now, as people experiment with Agentic AI and tool support, they’ve mostly adopted the MCP stdio transport, which means you end up with a 1:1 deployment of MCP server and MCP client. What organizations need is a way to deploy MCP servers remotely and leverage autho...| ceposta Technology Blog