Posts

Featured Post

Moving Beyond Chatbots: Securing AI Agents That Actually Modify Code and Execute Workflows

Image
Moving Beyond Chatbots: Securing AI Agents That Actually Modify Code and Execute Workflows Date: 10 November 2026 Moving Beyond Chatbots: Securing AI Agents That Actually Modify Code and Execute Workflows Executive Summary AI agents create a different security problem from chatbots. A chatbot mainly returns information. An agent can read repositories, change files, open pull requests, run commands, deploy infrastructure, and update business systems. A flawed response is inconvenient. A flawed tool call can become an incident. The security decision is clear: treat an agent as a software actor with constrained authority, not as a trusted employee with unrestricted access. Assign it a distinct identity, authorize every meaningful action, enforce policy outside the model, record decisions and results, and require human approval where the impact cannot be safely reversed. Contents Architecture and Trust Boundaries Threat Model Controls That Matter Implementation Patte...

Your AI Agent Should Not Borrow the Requester’s Identity

Image
An AI agent can receive a legitimate request and still perform an unauthorized action. The failure happens when the system treats the human requester and the agent as the same principal. Consider a hypothetical example. An employee asks an internal AI agent to prepare a supplier payment. The employee is allowed to view supplier records, but payment release requires a second approval. The agent calls the finance system using the employee’s access token. The finance system sees an authorized user and accepts the request. It has no way to tell whether the employee clicked “Release payment” or whether an autonomous process made the call on their behalf. The original request may have been valid. The resulting action still bypasses the control designed for payment release. That distinction matters because intent and authority are different things. The human requester establishes context: who asked, what they wanted, and when the request began. The agent needs its own identity to repres...

AXEC Cyber Security Weekly #4: Identity Bypass and Agentic Automation Turn Small Gaps Into Enterprise Incidents

Image
1. Executive Brief This week’s strongest pattern is the convergence of identity weakness, exposed secrets, and autonomous tooling. CISA added a SonicWall SonicOS vulnerability that can bypass SAML-enforced MFA to its Known Exploited Vulnerabilities catalog on November 6, 2026, with a federal remediation deadline of November 20. CISA KEV catalog Microsoft also reported threat actors using agentic tooling to find exposed OAuth secrets and perform authenticated actions inside compromised tenants. Microsoft Threat Intelligence Separately, reported incidents involving connected vehicles, crypto wallets, cloud services, and AI testing environments show how a narrow control failure can create a much wider blast radius. 2. Threats and Active Exploitation SonicWall SSL-VPN MFA bypass. CISA added CVE-2026-19868 to the KEV catalog on November 6. The vulnerability affects SonicWall SonicOS SSLVPN and may allow a user with valid credentials for an alternate authentication method to bypass SAML...

Latest Agentic AI, AI Agents & Agent Governance News – 10 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. CodeRabbit scales agentic software development and ships 20x more Source : OpenAI News CodeRabbit uses OpenAI models to govern and trust AI-generated code and Codex to ship 20 times more software with the same engineering team. Measuring how AI agents handle everyday wet-lab science Source : OpenAI News OpenAI introduces BioBasicsBench, a 100-task benchmark measuring how well AI agents interpret raw experimental data and handle everyday wet-lab science. GPT‑6 Cyber: Advancing the frontier of aligned cybersecurity agents Source :...

The Identity Crisis of Agentic Workflows: Handling Task-Specific Risk at Machine Speed

Image
The Identity Crisis of Agentic Workflows: Handling Task-Specific Risk at Machine Speed The Identity Crisis of Agentic Workflows: Handling Task-Specific Risk at Machine Speed Date: 08 November 2026 Executive Summary Agentic workflows create a security problem that traditional identity models do not solve well: one agent may perform many tasks, use different tools, handle different data, and operate with different levels of risk during a single session. The business risk is not simply that an AI model may produce an incorrect answer. The greater risk is that an agent may convert an incorrect, manipulated, or unauthorized decision into an external action: changing production configuration, disclosing sensitive data, approving a payment, or modifying a customer record. The security decision is clear: do not authorize an agent solely because it is authenticated, trusted by its host application, or operating within an approved workflow. Authorize each mate...