Posts

Featured Post

Zero Trust for AI Tools: How to Grant Exactly the Authority Required, and Nothing More

Image
Zero Trust for AI Tools: How to Grant Exactly the Authority Required, and Nothing More | AXEC Zero Trust for AI Tools: How to Grant Exactly the Authority Required, and Nothing More Date: 14 November 2026 Executive Summary AI tools can read sensitive data, invoke APIs, modify records, execute code, and trigger business processes. The central risk is not only that an AI model may produce an incorrect answer. It is that an AI system may use valid credentials to take an action outside the user’s intent, the tool’s purpose, or the organization’s risk tolerance. The security decision is therefore clear: treat every AI-initiated tool call as a separate authorization decision. Do not grant an agent broad standing access because it may need that access later. Bind authority to the user, agent, task, resource, action, context, and time window, then enforce and record the decision at the tool boundary. Contents The problem with broad AI authority Reference architecture and t...
Read more

Your AI Agent Should Not Inherit Your Environment

Image
The most dangerous secret in an AI agent runtime may be the one nobody deliberately gave the agent. A hypothetical example: a support agent runs inside a container with access to a ticketing system, a database, and an internal API. The platform injects several credentials through environment variables because that is how the existing services authenticate. The agent only needs one read-only token to resolve tickets. But the runtime exposes every environment variable to the process. A prompt injection hidden in a customer attachment instructs the agent to inspect its environment and send configuration data to an external endpoint using an available tool. No database exploit is required. No administrator account needs to be compromised. The agent simply turns broad runtime access into delegated authority. This is the control many teams miss: A secret should not be available merely because the process could technically use it. Inspect the runtime, not just the prompt Security re...
Read more

Latest Agentic AI, AI Agents & Agent Governance News – 14 November 2026

Image
🤖 Top Agentic AI, AI Agents & Governance Articles Your twice-weekly roundup of the latest in Agentic AI , AI agents , and agent access, permission, governance & audit — covering agent frameworks, MCP/tool-use, agent identity, non-human access control, AI governance and agent security. Introducing ChatGPT Wallet Source : OpenAI News Introducing ChatGPT Wallet, a secure way for agents in ChatGPT Work, Codex, and dots to complete purchases with user approval and existing card protections. How Amplitude ships product improvements in 1–2 days with OpenAI Source : OpenAI News Built primarily on OpenAI models, Amplitude’s proactive product agent, Wave, identifies what to build, helps teams ship changes with coding agents, and measures the impact. JioStar’s chief architect on AI discovery at 500M-user scale Source ...
Read more

Preventing Tool Exploitation: Centralizing Policy Across Repositories, APIs, and MCP Servers

Image
Preventing Tool Exploitation: Centralizing Policy Across Repositories, APIs, and MCP Servers Preventing Tool Exploitation: Centralizing Policy Across Repositories, APIs, and MCP Servers Date: 13 November 2026 Executive Summary AI systems increasingly act through tools that read repositories, call APIs, execute workflows, and access MCP servers. Each tool expands the system’s authority and creates another location where an attacker, compromised identity, malicious instruction, or policy mistake can produce unauthorized impact. The business risk is not limited to prompt injection. The larger problem is fragmented control: one service validates identity, another interprets permissions, and a third records incomplete logs. Security teams should make a deliberate architectural decision to centralize authorization policy and policy evaluation while keeping enforcement close to each tool boundary. Centralization does not mean giving one component unrestricted control. It mea...
Read more

Before an AI Agent Changes Production Data, Test the Action, Not the Intent

Image
An agent can have the right identity and still make the wrong change. That’s the production risk many teams miss. They verify who the agent is, then assume its requested action is safe. But identity answers only one question: which agent is acting? It doesn’t answer whether this action is justified, scoped correctly, or appropriate for the current context. Consider a hypothetical support agent with permission to update customer records. A ticket says: “Correct the customer’s billing region and apply the standard account update.” The agent retrieves the customer record, calls an internal update tool, and changes the billing region. The request sounds routine. But the agent has interpreted “standard account update” as permission to modify a field that affects downstream billing logic. The failure isn’t that the agent was compromised. The failure is that the control boundary trusted the agent’s interpretation. A role such as support-agent is too broad to authorize a production mut...
Read more