Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Today we’re announcing the beginning of the next phase of our journey. We’re launching our Vulnerability Intelligence feed, Nucleus Insights. As we’ve worked with many companies, partners, and clients over the years, this became an obvious next step for Nucleus, and I want to share with you why. Fixing vulnerabilities is expensive. Not just in terms of patching costs or system downtime, but in people, time, and lost focus.

Vulnerability prioritization isn’t just an important piece of any organization’s vulnerability management process. It’s a requirement. With the volume so high, and growing, it’s simply impossible to address every vulnerability an organization encounters. Prioritization comes at a price. Many organizations focus on a small number of the most critical vulnerabilities in their environment, which leads to an important question: What happens to the rest?

When vulnerability scans return thousands or even millions of findings, leading to an avalanche of tickets to evaluate, the real challenge begins: figuring out what to fix first. Exposure prioritization is the critical next phase of a mature exposure management program. After defining what exposure management is and establishing a normalized foundation of aggregated data, the question becomes: how do we cut through the noise and focus on what truly matters?

This release raises the bar for enterprise-grade vulnerability and exposure management. We’re delivering on the promise of smarter, faster risk reduction powered by automation, enriched data, and operational depth. From fix-level SLA tracking to scalable API workflows and stakeholder-ready reporting, every enhancement is designed to help teams do more with less, and prove it. Here’s a breakdown of some of the major product updates from Q2 2025.

In our recent webinar featuring Enterprise Strategy Group Principal Analyst, Tyler Shields, we discussed the widening gap between vulnerabilities organizations know about and what they can realistically fix. Most teams are swamped. Too much data, too many tools, and not enough people. Naturally, automation and AI come up as potential solutions. One comment from Tyler has stuck with me since watching and subsequently reviewing the webinar recording.

Let’s get this out of the way: the term vulnerability management has always been misleading. It evokes the idea that we’re wrangling a tidy list of software flaws, checking boxes, patching holes, and keeping things humming. But anyone who’s worked in the trenches or tried to explain this chaos to an executive board knows the truth. What we call “vulnerability management” isn’t a single discipline, or even a well-contained function.

Today, we’re excited to announce a preview of the Model Context Protocol (MCP) Server for Nucleus. This marks an important step towards AI-native workflows for vulnerability and exposure management. Model Context Protocol (MCP) is an emerging industry standard enabling seamless integration between enterprise applications and AI models. Backed by leading organizations like OpenAI, Microsoft, and Google, MCP servers are quickly becoming the foundation for AI-enablement across the enterprise.

In our first article exploring vulnerability management vs. exposure management, we explored the growing recognition that exposure management is not just a rebranding of vulnerability management. Rather, it’s a strategic evolution. Where traditional vulnerability management often focuses narrowly on CVEs and technical severity, exposure management demands a broader, more integrated understanding of risk across assets, environments, and attack vectors.

Vulnerability management has hit a wall. Exposure management is how forward-looking teams break through it. According to Gartner, by 2026, organizations that adopt a continuous exposure management approach to guide security investments will be three times less likely to experience a breach. a more advanced and iterative approach to vulnerability management. Despite growing interest, confusion remains around what exposure management is and how it differs from vulnerability management.