Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

AI agents (utilizing LLMs and RAG) are being used within SOCs and SIEMS to both help identify attacks and assist analysts with working more efficiently; however, I’ve done a little bit of research one sunny British afternoon and found that these agents can be abused by attackers and made to go rogue. They can be made to modify the details of an attack, hide attacks altogether, or create fictitious events to cause a distraction while the real target is attacked instead.

As the summer winds down and conversation around AI Security heats up, the Snyk team is in full swing planning mode for a double-header this October—with the return of DevSecCon’s Flagship conference, focusing this year on Securing the Shift to AI Native, and serving as the founding partner of the inaugural AI Security Summit.

Future hacks won’t trigger alarms or leave traces. No security measures will be violated. The systems are functioning normally – but the loss is real. As automated defenses improve, attackers must target what machines can’t: the business processes. By exploiting flaws in workflow logic, hackers can steal data and funds in a way no one expected. Business logic vulnerabilities are now a serious cybersecurity blind spot, and a leading method for breaching even the most secure systems.

Not too long ago I read an interesting blogpost by SpecterOps about Microsoft EPM that got my attention as I was not aware of this Microsoft product/feature. It was interesting to learn that Microsoft expanded into the realm of Endpoint Privilege Management and since this means that there must be some service/driver running with high privileges that elevates low-privileged processes, I thought there could be potential vulnerabilities and bugs.

PHILADELPHIA (Aug 25, 2025) – Outpost24, a leading provider of exposure management solutions, today announced it has been named as a Major Player in the IDC MarketScape: Worldwide Exposure Management 2025 Vendor Assessment. The Outpost24 team believes this recognition underscores our comprehensive exposure management solutions and commitment to delivering exceptional customer service.

A critical vulnerability, identified as CVE-2025-29927, has shaken the Next.js development community. Rated with a severity score of 9.1 (Critical), this flaw allows attackers to completely bypass authorization checks in middleware, potentially granting unauthorized access to sensitive data and protected routes. The issue is a powerful reminder that even a small design flaw in a popular framework can have widespread and dangerous consequences.