FOR IMMEDIATE RELEASE Ethosure publishes “Would Ethosure have caught this?” – a technical autopsy of 24 of the latest AI-agent hacks, failures, compromises, and general disclosures of 2026, each mapped to policy-as-code Series walks through the Hugging Face, Anthropic, Google, OpenAI, Meta, and AI Safety Institute incidents with the specific Read more
Google Threat Intelligence Group disclosed a financially motivated actor that wired an AI coding chatbot, a prompt, and a set of markdown playbooks into an autonomous framework and harvested thousands of third-party credentials in under six hours. The intrusion needed no human operator between planning and payout. Ethosure treats an unattended multi-agent loop as a governed workload, not a tolerated one.
When an organization deploys software to govern its AI agents, a natural question follows: how do you know the governance software itself is trustworthy? How do you know the version you installed is the version the developers built and signed? How do you know it does not contain a vulnerable Read more
Ask a financial institution’s chief information security officer whether they are comfortable routing AI agent governance decisions through a cloud service operated by a third party, and the answer will usually be no – or at minimum, a long conversation about data residency, vendor risk, and regulatory compliance. Ask the Read more
An AI coding agent that encounters a policy violation for the first time might need several attempts to understand and fix it. An AI coding agent that has seen the same violation three times before should not need to rediscover the solution. More broadly, an organization running AI agents across Read more
Governance problems in software organizations often share a root cause: rules defined in one place are enforced differently in another, not enforced at all in a third, and unknown to a fourth. A security policy lives in a Confluence page; the Git hook that supposedly enforces it was written two Read more
Most organizations have a set of engineering principles – stated values that describe how software should be built. Things like “fail early and loudly,” “no undocumented dependencies,” “security is everyone’s responsibility.” These principles typically live in documentation, onboarding guides, and the institutional knowledge of experienced engineers. What they rarely do Read more
Git hooks and agent hooks catch problems at commit time and during active tool calls. But a complete governance picture for AI agents also needs visibility into the traffic flowing between the agent and the AI provider – the prompts being sent, the responses coming back, the tool calls being Read more
Version control is the foundation of every software project. It is where code goes from “written” to “official.” For organizations deploying AI coding agents, it is also one of the most critical enforcement points – because a commit that lands in the main branch is, in many senses, a fact. Read more
A well-governed AI agent should not need to discover its limits by hitting them. If an agent is about to propose a command that will be blocked by policy, it is better for the agent – and for the organization – if the agent can ask first, adjust its plan, Read more
