Cybersecurity
Cybersecurity
Risks, controls and practices to protect digital and AI systems.
Publications
Articles in this category
MCP explained: how it connects AI assistants with tools and data
MCP offers a common way to connect AI applications with servers that expose tools and data. Understanding its components helps separate what the protocol defines from the risks of each implementation.
MCP securityRead articleWhere the risk really is: client, server, agent, permissions and integrations
Evaluating MCP is not limited to the protocol. The real surface includes who runs each component, what it can see and which actions it can perform.
MCP securityRead articleIndirect prompt injection: how an external response can manipulate an agent
An agent can interpret as instructions content that arrived as data. The defense requires separating authority, limiting capabilities and controlling actions.
MCP securityRead articleTool poisoning: when a seemingly trustworthy tool hides instructions
A tool can include descriptions or results that steer the model toward unexpected actions. Review must cover behavior, capabilities and changes.
MCP securityRead articleRug pull: what happens when a tool changes after being approved
Approving a tool should not mean trusting all of its future versions indefinitely. Change control closes that gap.
MCP securityRead articleExcessive permissions: applying least privilege to MCP servers
Least privilege reduces how much an integration can do if an instruction, configuration or component fails.
MCP securityRead articleTokens, OAuth and the “confused deputy”: preventing unauthorized access
When a server acts on behalf of a person toward another service, it must preserve the identity, consent and scope of each authorization.
MCP securityRead articleSSRF and local MCP servers: network risks and defense against DNS rebinding
A local server or a tool that fetches URLs can open unexpected access paths. The defense combines network limits, validation and transport controls.
MCP securityRead articleCommand injection and input validation: protecting tools that perform actions
Parameters proposed by a model must be treated as untrusted input. Security depends on validating the type, scope and effect of each operation.
MCP securityRead articleSupply chain and unapproved MCP servers: dependencies, installation and shadow IT
Each MCP server adds code, configuration and dependencies to an organization’s supply chain. A proportionate approval process makes that surface visible.
MCP securityRead articleInformation leakage through context, responses and logs
Information can leak before, during or after a call: from the context the model receives to tool responses and logs.
MCP securityRead articleMCP security checklist: a central guide for developers and organizations
This guide brings together controls to evaluate MCP servers before and after integrating them. Use it alongside the series’ articles to go deeper into each topic.
MCP securityRead article