Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

When AI Agents Create Their Own Reddit: Moltbook Highlights Security Risks in the Agentic Action Layer

A new platform, Moltbook, has attracted significant attention within the AI community. It is not famous because humans are posting there, but because autonomous AI agents are. Moltbook is a social network designed for AI agents to post, comment, upvote, and even form communities. Humans can observe these interactions but cannot participate. This experiment reveals a striking reality. AI agents are coordinating, sharing code, and developing complex cultures without human visibility.

Why Your WAF Missed It: The Danger of Double-Encoding and Evasion Techniques in Healthcare Security

If you ask most organizations how they protect their APIs, they point to their WAF (Web Application Firewall). They have the OWASP Top 10 rules enabled. The dashboard is green. They feel safe. But attackers know exactly how your WAF works, and, more importantly, how to trick it. We recently worked with a major enterprise customer, a global leader in healthcare technology, who experienced this firsthand.

Fast, Secure, Resilient: Modernizing Application Security at Scale

Software release cycles are now too fast for traditional security tools. Rapid iterations and reliance on open-source and cloud-native tech increase vulnerabilities, challenging AppSec teams to keep up. Attackers are taking advantage, targeting applications and exploiting misconfigurations, excessive permissions, and vulnerable plug-ins.

Measuring Agentic AI Posture: A New Metric for CISOs

In cybersecurity, we live by our metrics. We measure Mean Time to Respond (MTTR), Dwell Time, and Patch Cadence. These numbers indicate to the Board how quickly we respond when issues arise. But in the era of Agentic AI, reaction speed is no longer enough. When an AI Agent or an MCP server is compromised, data exfiltration happens in milliseconds rather than days. If you are waiting for an incident to measure your success, you have already lost.

Fast, Secure, Resilient: Modernizing Application Security at Scale

Software release cycles are now too fast for traditional security tools. Rapid iterations and reliance on open-source and cloud-native tech increase vulnerabilities, challenging AppSec teams to keep up. Attackers are taking advantage, targeting applications and exploiting misconfigurations, excessive permissions, and vulnerable plug-ins.

AI is Actively LEAKING Your Data (And You Don't Know It) #apisecurity #airisks #dataprotection #ai

AI agents don't think. They pattern-match. Critical to understand: Generative AI (ChatGPT, Claude, etc.) does NOT reason like humans. It: The API Security problem: When you give an AI agent access to an API, it will: AI agents can't reason. They recreate patterns based on weights. You need to be very careful: data in, data out. Practical example: text User: "Show me the account balance for user" AI agent → calls GET /api/account/123 API → returns { balance: 5000, name: "John", SSN: "123-45-6789" } AI agent → outputs EVERYTHING to user (including SSN!)

Why API Security Is No Longer an AppSec Problem - And What Security Leaders Must Do Instead

APIs are one of the most important technologies in digital business ecosystems. And yet, the responsibility for their security often falls to AppSec teams – and that’s a problem. This organizational mismatch creates systemic risk: business teams assume APIs are “secured,” while attackers exploit logic flaws, authorization gaps, and automated attacks in production. As Tim Erlin noted recently, “These are not exploits of a specific vulnerability, but abuse of an API.”

What is API Security Management? A Complete Guide

The fact that you’re here is proof enough that API is somewhere disturbing your or your security team’s sleep. Whether it is 99% of organizations reporting API security issues in recent surveys, or it’s a compliance/client mandate. We know you are (fear you soon will be) grappling with shadow APIs, misconfigured endpoints leaking sensitive data, BOLAs, unauthorized access, and more.

Stop Staring at JSON: How GenAI is Solving the API "Context Crisis"

There is a moment that happens in every SOC (Security Operations Center) every day. An alert fires. An analyst looks at a dashboard and sees a UR: POST /vs/payments/proc/77a. And then they stop. They stare. And they ask the question that kills productivity: "What does this thing actually do?" Is it a critical payment gateway? A test function? Does it handle credit card numbers or just transaction IDs?