Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Move over, Mythos. Here comes... pretty much any other model with a good harness

Mythos doesn’t need to be treated as the biggest and baddest in the room. Don’t get me wrong. Depending on the benchmark you’re evaluating against, Mythos is among the top models available today, and generally the best at reasoning. But it’s not leaps and bounds ahead of the race. And when it comes to practical use cases, throwing a general model, even a cutting-edge frontier model, at a problem doesn’t get the best results. Nor is it scalable or cost-effective.

Types of AI Agent Attacks: A Security Team's Taxonomy

A security team running agents in production can already list the ways those agents get attacked: prompt injection, memory poisoning, tool abuse, model tampering, agent-to-agent coercion. The list is not the problem. The problem is that a security architect can recite all five and still not know which ones their detection stack will catch, because the way the field catalogs these attacks says nothing about whether the attack is catchable.

The AI Agent Attack Kill Chain: Which Stages You Can Actually Detect

The early stages of an AI agent attack are silent. The poisoning, the hijacked intent, the reconnaissance: none of it executes, so none of it produces a runtime signal, and the kill-chain instinct every security team runs on says exactly the wrong thing here: break the earliest link. There is no early link to break. You cannot detect a stage that emits nothing.

Tool Call Analysis for AI Attack Detection: Reading What Rides Inside the Call

A compromised agent doesn’t make a single call it isn’t allowed to make. It queries a table it’s authorized to read, calls a tool it’s authorized to use, sends to a domain that’s on the allowlist. Every call is legal. The attack is in the values it passes, and your tool-call log records all of it as a clean day’s work. A tool call has two layers. Almost every tool you run reads the first one: the call itself: which tool, in what order, at what rate.

How to Tell If Your AI Agent Has Been Compromised (When Every Symptom Looks Normal)

Your AI agent just did something it has never done. It called a tool that is not in its usual set, or it opened a connection to a destination you do not recognize, or its output came back subtly wrong. So you do what anyone does: you search for what a compromised agent looks like, and you find a checklist. Unusual tool usage. Unexpected data access. Out-of-context responses. Elevated resource consumption.

Compliance and Regulation Heat Up in 2026: A New Phase of Scrutiny for Financial Services Organisations

The regulatory landscape facing financial services in 2026 is more complex, more demanding, and faster moving than at any point in the past decade. Across the UK, regulators are attempting to strike a delicate balance of stimulating economic growth while maintaining strong consumer protection and financial stability. This balancing act is unfolding against a backdrop of sluggish economic performance, geopolitical uncertainty, and political pressure for "pro-growth" regulation. The result is a regulatory environment where the pace, scope, and intensity of change is accelerating sharply.

How Relay Network Adopted AI Coding Securely and Built the Foundation for Agentic Development

Champion / Spokesperson(s): Brendan Putek, Director of DevOps, and Esaie Batoula, Security Engineer. Relay Network is the innovator behind a secure B2C communications platform that combines SMS with dynamic feed technology to help regulated enterprises deliver personalized, action-oriented mobile experiences for every customer. In an industry where trust, compliance, and data protection are paramount, security has always been central to how the company builds software.

Shadow AI: The Hidden Risk Expanding Across the Enterprise

Companies and employees are racing to capture the value and efficiencies offered by AI, but security is often an afterthought. Employees are using unauthorized GenAI tools to summarize documents, draft emails, and analyze potentially sensitive or proprietary data. Developers are adding AI capabilities before security teams can review them. SaaS platforms are adding AI features that may process sensitive business data by default.

MCP Security: How to Secure MCP Integrations

AI agents are connecting to enterprise systems right now. Whether a developer wired up Claude to an internal Confluence instance, a vendor shipped an agentic workflow that calls the CRM, or an employee enabled a browser-based AI assistant that reads email, Model Context Protocol (MCP) is rapidly becoming the integration layer between large language models (LLMs) and corporate data. Most security teams have no visibility into any of it.