Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

As enterprises adopt AI agents, two control points are becoming common: AI Gateways and MCP Gateways. They sound similar, but they solve different problems. An AI Gateway controls how applications interact with AI models. An MCP Gateway controls how AI agents interact with tools, systems, and data exposed through MCP. Both are useful. Neither is enough on its own.

An account-takeover campaign against Instagram shows why agentic AI inherits every business logic blind spot we already had and then hands it a megaphone. Over the past weekend, a number of Instagram users, including the long-dormant Obama-era White House handle and a U.S. Space Force senior enlisted leader found their accounts hijacked. As reported by TechCrunch, the entry point wasn’t a stolen password, a phishing kit, or a zero-day in Instagram’s code.

Traditional API security protects deterministic systems with known endpoints and explicit actions, while MCP-powered AI agents operate through inferred intent, dynamic tool chaining, and natural language interactions. This requires MCP-specific security controls such as tool governance, behavioral monitoring, and semantic anomaly detection.

The enterprise security world is having two separate conversations that desperately need to collide. On one side, application security (AppSec) teams are scrambling to secure APIs – the connective tissue of every modern application. On the other, a new wave of “AI security” vendors promise to protect your LLMs from prompt injection, data leakage, and hallucinations. Both groups are solving real problems. Both are missing half the picture.

The non-human identity (NHI) problem was always the same problem: too many service accounts, too few owners, too many secrets in too many places. They sat where we left them, quietly piling up privilege, outliving the engineer who created them. Eventually someone, an auditor, sometimes an attacker, went looking and found them. Agents are a different problem.

Let’s start with a scenario. This is illustrative, not a single reported incident. A developer shares a Postman collection in Slack to move faster. “Here’s the Postman collection for the payment API. It has live auth headers so you can test prod endpoints.” The team uses it, work gets done, and the link stays. What no one realizes is that the collection lives inside a public Postman workspace. Weeks later, it is indexed by search engines. The URL requires no login.

A newly disclosed security issue, tracked as CVE-2026-44578, affecting Next.js applications is raising concerns across the developer and security communities after researchers identified multiple authorization bypass and middleware evasion paths that could expose protected application data and credentials. The vulnerabilities impact several versions of Next.js and allow attackers to bypass middleware-based authorization controls using crafted requests and route manipulation techniques.

In September 2022, Australia woke up to the largest data breach in its history. Optus, the country’s second-largest telecom disclosed that the personal information of nearly 10 million people had been exposed. To put that in perspective, that’s almost 40% of the entire population. Among the data spilled were 2.1 million government-issued IDs – passports, driver’s licenses, Medicare cards – the kind of information that isn’t just sensitive, but life-defining.

“Tech giants pay hackers millions to hack them – on purpose.” What once sounded like a risky experiment has now become standard practice in cybersecurity. Bug bounty programs have moved from the fringes into the mainstream because traditional defenses alone can’t keep up with today’s scale and sophistication of attacks.

In today’s hyper-connected world, Web Application Firewalls (WAFs) have become one of the most critical layers in a modern security stack. As businesses shift more operations, data, and user experiences online, web apps and APIs are increasingly under siege – from basic bot scraping to sophisticated logic abuse and zero-day exploits.