Posts

Featured Post

Latest Agentic AI, AI Agents & Agent Governance News – 18 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 GPT-6.2 Astra and Sol Source : OpenAI News Introducing GPT‑6.2 Astra and Sol, with better professional outputs, coding, computer use, and efficiency at lower cost across ChatGPT Work, Codex, and the API. Introducing AlphaProof Code: a breakthrough in verifying complex software at depth Source : Google DeepMind AlphaProof Code agents wrote three million lines of proofs in Lean to verify Signal’s core encryption. Agentic cheminformatics with Google Antigravity Source : Google DeepMind Learn how Goog...

Auditing the Autonomy: How to Retrieve Decision-Level Authorization Evidence in Minutes

Image
Auditing the Autonomy: How to Retrieve Decision-Level Authorization Evidence in Minutes Auditing the Autonomy: How to Retrieve Decision-Level Authorization Evidence in Minutes Date: 17 November 2026 Executive Summary AI agents can now select tools, call APIs, modify records, and trigger workflows with limited human intervention. That creates a security problem that ordinary application logs do not solve: when an agent takes an action, can your team prove who authorized it, which policy was evaluated, what context was used, and why the action was allowed? The business risk is not limited to an unauthorized action. An organization may also be unable to reconstruct a valid action quickly enough to contain an incident, satisfy an internal review, or explain a control to an auditor. The security decision is straightforward: treat every consequential agent action as an authorization decision that must produce a durable, queryable evidence record. Authentication proves whic...

Your AI Agent’s Job Description Is Not Its Security Boundary

Image
An AI agent shouldn’t receive the permissions of the person who assigned its task. That sounds obvious, but many systems still scope authority by role: finance agent, support agent, operations agent. The label describes the workflow. It doesn’t define what the agent should be allowed to do at each moment. Consider a hypothetical procurement agent. Its task is to review an invoice against a purchase order and flag discrepancies. It has access to the ERP, vendor records, email, and payment workflows because those systems are “relevant” to procurement. The invoice contains an instruction asking the agent to update the vendor’s bank details before approval. The agent treats the instruction as part of the work, finds the update tool, changes the record, and continues. No jailbreak was required. No administrator account was compromised. The control failed because the agent had authority that exceeded its task. The key question for an enterprise buyer is not: “What systems can this ag...

Mitigating the Seams: Overcoming Over-Provisioned Access and Persistent Credentials in AI Runtimes

Image
Mitigating the Seams: Overcoming Over-Provisioned Access and Persistent Credentials in AI Runtimes Mitigating the Seams: Over-Provisioned Access and Persistent Credentials in AI Runtimes Date: 16 November 2026 Executive Summary AI runtimes create a security seam between probabilistic model behavior and deterministic enterprise systems. A model may be permitted to call tools, retrieve data, execute code, or trigger workflows, while the credentials and permissions behind those tools remain valid far beyond the individual request. The business risk is not limited to model hallucination. It includes excessive authority, confused-deputy behavior, credential theft, unsafe tool arguments, weak tenant isolation, incomplete audit trails, and actions that cannot be reliably attributed to a human, application, or model decision. The security decision is clear: treat every model-initiated action as a request crossing a trust boundary. Do not give the runtime broad, persistent a...

AXEC Cyber Security Weekly #5: The Attack Surface Is Moving Into AI Control Planes

Image
1. Executive Brief This week’s strongest pattern was the convergence of exposed infrastructure, stolen identity, and AI-enabled speed. CISA added vulnerabilities in security gateways, AI infrastructure, browsers, communications platforms, and remote-access products to its Known Exploited Vulnerabilities catalog. CISA KEV catalog Reported incidents also showed attackers moving through trusted channels: an AI extension marketplace, cloud providers, support platforms, hardware supply chains, and employee identities. Cursor incident reporting TSMC incident reporting The practical lesson is direct. AI governance cannot sit apart from identity, patching, software supply-chain security, and runtime authorization. 2. Threats and Active Exploitation UnrealIRCd server-level command injection. CISA added CVE-2026-114713 to the KEV catalog on November 13, with a remediation deadline of November 16. The flaw allows a user on a network with at least two linked UnrealIRCd servers to inject serv...