Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

In a fast-moving threat landscape, finding the answers to complex security challenges can be fraught with unknowns. Asking the right questions can make all the difference, as Steven Escobar and Ben Habing know well through their work in the Assessments and Advisory practice within Cyber and Data Resilience at Kroll.

Every major tournament cycle, ticketing platforms brace for a traffic spike. Most security teams plan for volume. The attack data tells a different story: the traffic that does the most damage isn’t the loudest traffic. It’s the traffic that looks like a real fan, on a real device, doing something a real fan would plausibly do, just millions of times, in a pattern no single fan ever would.

Applications using MongoDB have a common pitfall of treating the ObjectId() function as cryptographically secure. Recently, we found Rocket.Chat, an open source Slack-like application, to be a victim of this. At Aikido, we run AI Pentests on various open source applications to test our agents and identify their strengths and improvement points. During the pentest, one of the agents reported that an unauthenticated Rocket.Chat user can access any uploaded file if they know its ID.

Every certificate renewal automation tool has to answer one architecture question before it does anything else: where does the private key get generated? A reader who used to be “the certificate guy” at his organization emailed me this week to ask about exactly that: It’s the right instinct. It’s also how most automation tools work. Certbot generates the key on the server, builds a certificate signing request, and the private key never leaves the machine.

From Chaos to Compliance: Mastering Your SOC 2 Audit Preparing for a SOC 2 audit usually starts the same way. A customer asks for your report, sales says the deal is blocked without it, engineering already has half the controls in place, and nobody can prove any of it cleanly. The problem usually isn't a total lack of security. It's fragmented evidence, inconsistent ownership, and controls that exist in practice but not in auditor-ready form.

It was time to write another book. That’s what I thought when I heard that Corelight wanted to update its 2021 book on network detection and response (NDR). Tamara Crawford, who owned the project, scheduled a meeting with me and asked if I might be interested in helping, depending on who might write the text.

IBM’s 2025 Cost of a Data Breach Report found that 97% of organizations that experienced an artificial intelligence (AI)-related security incident lacked proper access controls on AI systems. The same report highlighted that 63% of organizations lacked governance policies to manage AI or prevent shadow AI. Despite those statistics, AI is now deeply embedded in workflows across critical business functions. Employees are using public AI tools to work faster.

SCA tools are good at identifying vulnerabilities in your dependencies. They’re not built for the harder part of vulnerability risk management: telling you whether those vulnerabilities are actually reachable in your application, or which assets are running an affected component the moment a zero-day drops. Seemplicity’s SCA Analyst solves both problems inside a single centralized vulnerability management platform.

Static application security testing (SAST) tools are intentionally conservative. Traditional scanners identify code that appears exploitable and flag the snippet for review, even when protections elsewhere in the application prevent exploitation. Although that approach helps teams catch vulnerabilities, it also creates false positives that consume developer time, slow remediation efforts, and make future alerts easier to dismiss.