Security Operations

Vulnerability management Findings aren't fixes

Vulnerability management is the recurring work of finding, ranking and fixing weaknesses attackers could exploit in your systems. A federal catalog lists more than 1,700 vulnerabilities that attackers have already exploited. We scan monthly or quarterly, rank the findings, guide and confirm fixes, and list residual risk for your decision.

Who it is for
Critical infrastructure and growing businesses
How it runs
A recurring service on a monthly or quarterly cycle
What you get
Scan report, remediation tracker, residual risk list and summary

What vulnerability management is and why it matters

The National Institute of Standards and Technology (NIST) describes vulnerability management as finding the known flaws on your devices that an attacker could use to get in and then reach the rest of your network.

NIST also notes that risk usually rises once a new flaw becomes publicly known. That is why the work repeats on a schedule instead of ending with one scan.

Mandiant's M-Trends 2026 found that exploits were the most common way attackers got in, at 32% of the intrusions it investigated in 2025.

Fixing lags behind. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) keeps a catalog of Known Exploited Vulnerabilities (KEV). Verizon's 2026 Data Breach Investigations Report found that only 26% of the KEV-listed flaws in its data had been fully fixed, and the median time to a full fix rose to 43 days.

How a vulnerability management cycle runs

  1. 01 ScanWith your authorization, we scan for known weak spots.
  2. 02 RankWe put the findings in order, so the most urgent fixes come first.
  3. 03 FixWe guide each fix, and it goes in during a maintenance window you approve.
  4. 04 ConfirmWe check that each fix took effect and record any exception.
  5. 05 ReportYou receive the records for the cycle, and the next cycle begins.

What you receive after each scan cycle

You get the same four records every cycle, so you can compare each cycle with the last.

  • 01Scan reportThe weak spots this cycle's scans found.
  • 02Remediation trackerEach fix and where it stands, followed until it is closed.
  • 03Residual risk listThe flaws that stay open, for you to accept or reject.
  • 04Executive summaryWhere things stand, written for owners and leadership.

How to tell which vulnerabilities to fix first

Look past the severity score. A high score alone does not show whether attackers are using a flaw, or are likely to soon. Three public signals help you decide:

  • CVSS, the Common Vulnerability Scoring System, rates how severe a flaw is compared with other flaws. Its publisher calls it one input to a vulnerability management process.
  • The KEV catalog lists flaws known to be exploited by attackers. Verizon notes that organizations with well-developed vulnerability management processes do not typically wait for a flaw to reach the catalog before patching it.
  • EPSS, the Exploit Prediction Scoring System, estimates the chance that a published flaw will be exploited in the next 30 days. It is updated daily, and its publisher advises combining it with CVSS and KEV.

When a vulnerability cannot be fixed right away

Some flaws cannot be fixed without downtime, help from the vendor or a business exception. They still need a decision, and you make it.

NIST's patch management guide gives reasons a fix may have to wait: no patch exists yet, the vendor no longer supports the software, or the change needs a scheduled outage or testing first. Field laptops that go months without a connection are one example. See how to keep offline field laptops patched.

The same guide calls patching "one of several ways" to respond. The others it names:

  • Isolate the vulnerable system, for example with firewalls and network segmentation.
  • Remove the vulnerable software, or retire the device that runs it.
  • Transfer the risk, for example through cyber insurance.
  • Accept the risk as it is. Whatever stays open goes on your residual risk list, and we document each exception.

How often to run vulnerability scans, rule by rule

What each rule and framework asks for in 2026.

  • FTC Safeguards RuleThis Federal Trade Commission rule covers non-bank financial businesses, accounting and tax firms included. Without effective continuous monitoring, they need vulnerability assessments at least every six months and after material changes to their operations or business arrangements, plus a yearly penetration test (16 CFR 314.4(d)(2)). Firms with customer information on fewer than 5,000 consumers are exempt from this testing requirement.
  • CIS ControlsThe Center for Internet Security (CIS) asks organizations at its second and third levels (Implementation Groups 2 and 3) to scan internet-facing systems monthly or more often. Internal systems need scans quarterly or more often, both with and without sign-in credentials.
  • NERC CIP-010CIP-010 is part of the Critical Infrastructure Protection (CIP) standards of the North American Electric Reliability Corporation (NERC). It asks utilities to run a paper or active vulnerability assessment on medium and high impact grid systems at least every 15 calendar months, and to document the results with a dated action plan. That duty is the utility's. Our NERC CIP IT-Scoped Governance Program covers your IT systems and how they are governed.
  • HIPAA Security RuleThe Security Rule under the Health Insurance Portability and Accountability Act (HIPAA) requires an "accurate and thorough assessment of the potential risks and vulnerabilities" to electronic patient data, and measures that reduce them (45 CFR 164.308(a)(1)(ii)(A) and (B)). The Department of Health and Human Services (HHS) proposed adding scans at least every six months in January 2025. As of November 2026, that is still a proposal.
  • NIST CSF 2.0NIST's Cybersecurity Framework (CSF) 2.0 lists as a core outcome that vulnerabilities in assets are "identified, validated, and recorded" (ID.RA-01). It also expects exceptions to be recorded and tracked (ID.RA-07).

What we do each cycle, What you authorize and decide

CyberBlip

  • Run the vulnerability scans each cycle
  • Put the findings in order of priority
  • Guide each fix
  • Confirm that fixes are closed
  • Document exceptions and the risk that remains

You

  • Authorize the scans
  • Approve the maintenance windows for fixes
  • Accept or reject the risk that remains

The limits of a vulnerability scan

A scan checks for flaws that are already publicly known, and attackers do not always wait for a fix. Mandiant's M-Trends 2026 also puts the mean time to exploit at an estimated minus 7 days, which means exploitation now routinely starts before a patch is even released.

New flaws come to light between cycles. Our separate Threat Intelligence and Security Advisory service gives early warning about new threats that affect the tools you use.

Questions about vulnerability management services

Do you fix the vulnerabilities, or only report them?

We guide the fixes and confirm they worked. Your team applies them, or our Security-First Endpoint Management and Secure Configuration and Hardening Management services do where you have them.

What is the difference between a vulnerability scan and a penetration test?

A vulnerability scan is a repeating check for known flaws. A penetration test is an approved break-in test, run as a project with our testing partner. See how penetration tests and scans work together.

How is vulnerability management different from patch management?

Patch management keeps software updated. Vulnerability management is the wider cycle: finding flaws, ranking them, choosing a response and checking the result. Some findings are insecure settings rather than missing updates, and some flaws have no patch yet.

Is a vulnerability scan the same as a risk assessment?

No. A cyber risk assessment is a project that reviews your security risks and control gaps, then ranks what to fix first. Vulnerability management is recurring and technical: it scans for known flaws every month or quarter and tracks the fixes.

Will vulnerability scanning cover our FTC Safeguards Rule or HIPAA requirements?

Only part of them. Scans support the vulnerability assessments the FTC Safeguards Rule asks for and the risk analysis HIPAA requires, but both rules ask for more, such as a written risk assessment, encryption and training under the FTC rule. Our Safeguards Rule program and HIPAA Security Rule program support the rest, and legal questions belong with your attorney.

Can these reports help with an audit or a cyber insurance application?

They can support one. Each cycle's records show what was found, what was fixed and what risk you chose to accept, but the auditor or insurer decides what it accepts as evidence. For insurance questionnaires, see cyber insurance readiness.

Sources

Show all 16 sourcesHide sources
  1. Glossary: vulnerability management (from NISTIR 8011 Vol. 1) NIST
  2. SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology NIST, 2022-04
  3. M-Trends 2026: Data, Insights, and Strategies From the Frontlines Mandiant, Google Cloud, 2026-03-23
  4. CISA Catalog of Known Exploited Vulnerabilities (data feed, version 2026.11.17) CISA, 2026-11-17
  5. 2026 Data Breach Investigations Report Verizon, 2026
  6. CVSS v4.0 Specification Document FIRST
  7. Exploit Prediction Scoring System (EPSS) FIRST
  8. 16 CFR 314.4, Elements (FTC Safeguards Rule) eCFR, 2026-11-13
  9. 16 CFR 314.6, Exceptions (FTC Safeguards Rule) eCFR, 2026-11-13
  10. CIS Controls Assessment Specification for Controls v8, Safeguard 7.5 (internal scans) CIS, 2025
  11. CIS Controls Assessment Specification for Controls v8, Safeguard 7.6 (internet-facing scans) CIS, 2025
  12. CIP-010-4, Cyber Security, Configuration Change Management and Vulnerability Assessments NERC, 2021-03-18
  13. 45 CFR 164.308, Administrative safeguards (HIPAA Security Rule) eCFR, 2026-11-13
  14. HIPAA Security Rule Notice of Proposed Rulemaking Fact Sheet HHS, 2024-12-27
  15. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 Federal Register, 2025-01-06
  16. The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 NIST, 2024-02-26

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt