Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

If you've been following the cybersecurity conversation over the last several weeks, you've heard some version of the phrase “Claude Mythos changes everything.” It’s dominated the industry news cycles since early April. While the capabilities these stories tout are very much real, I have an issue with the framing being wrong when it comes to vulnerability management. There’s a narrative that Mythos and other frontier models will find too many vulnerabilities to deal with.

In the span of six weeks this summer, the United States government issued three separate security directives that, on the surface, appear to address completely different problems. One tightens how federal agencies patch software vulnerabilities. Another creates a government-industry clearinghouse to triage AI-discovered bugs. The third restructures how defense contractors source the raw materials that go into missiles, aircraft, and military electronics. Different agencies. Different languages.

When Anthropic revealed Claude Mythos and Project Glasswing, the industry did what the industry always does with a frontier-AI story: it reached for the alarm. The headlines, Reddit threads, and back-channel conversations all focused on the same things: All of that is real, and none of it is the part that should keep a security leader up at night. Here is the part that should.

If you've ever pulled an asset count from one tool and compared it to another, you've probably noticed they don't match. The discrepancy isn’t minor, either. The difference is likely to be substantial. One scanner says you have 4,200 assets. Your CMDB says 3,800. Your cloud inventory says 1,100. None of them agree, and none of them are right. That's not a data hygiene problem you can solve with a spreadsheet cleanup.

At the executive level, vulnerability management stops being a technical exercise and becomes a question of risk ownership, operational tradeoffs, and organizational accountability. When a vulnerability leads to a breach, it has a personal effect on security leaders along with its broader organizational impact. According to Proofpoint’s Voice of the CISO Report, a majority of CISOs claim they are personally blamed ‘always or often’ when a breach occurs, even when defenses were in place.

CISA Binding Operational Directive 26-04: Prioritizing Security Updates Based on Risk requires Federal Civilian Executive Branch (FCEB) agencies to prioritize security updates based on operational risk, not just severity. It builds on earlier Cybersecurity and Infrastructure Security Agency (CISA) directives by combining exposure, exploitation, impact, and prioritization logic into a more actionable remediation model.

Most vulnerability management programs don’t struggle because they lack visibility. They struggle because they generate more security decisions than humans can realistically process at scale. Modern security teams already have most of the tools they need to find and assess vulnerabilities. Their real operational challenge is determining which vulnerabilities matter, which teams own them, which findings deserve escalation, and which can safely wait.

Every year, the Verizon Data Breach Investigations Report (DBIR) gives the security industry a chance to step back from the noise and look at what happened. Not what vendors predicted. Not what attackers threatened. Not what defenders feared. What happened. This year’s report makes one point hard to ignore: vulnerability exploitation became attackers’ initial leading access vector.

Don't wait for KEV listing Waiting for CISA KEV may be too late. Across six months of Nucleus research, public PoCs gave defenders a median 5.5 days of runway before KEV listing, every single time.

EPSS: Early warning or not? EPSS is a predictive scoring model, and security teams assume it is an early warning signal. Nucleus research across 18% of CISA KEV-listed CVEs over 6 months found it isn’t.