<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Varaxon Technologies</title>
    <description>The latest articles on DEV Community by Varaxon Technologies (varaxontech).</description>
    <link>https://dev.to/varaxontech</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F14766%2Ffb56f4fc-c636-4c2f-9c30-ca726deec5f3.png</url>
      <title>DEV Community: Varaxon Technologies</title>
      <link>https://dev.to/varaxontech</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/varaxontech"/>
    <language>en</language>
    <item>
      <title>N-central vulnerabilities (Able2Shell): what MSPs should do now</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Sat, 14 Nov 2026 23:10:04 +0000</pubDate>
      <link>https://dev.to/varaxontech/n-central-vulnerabilities-able2shell-what-msps-should-do-now-2pmm</link>
      <guid>https://dev.to/varaxontech/n-central-vulnerabilities-able2shell-what-msps-should-do-now-2pmm</guid>
      <description>&lt;p&gt;&lt;em&gt;This article first appeared on &lt;a href="https://varaxontech.com/guides/n-central-able2shell-vulnerabilities" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;, where it is kept up to date.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The short version&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;On 8 to 9 November 2026 a researcher published working exploit code for flaws in &lt;strong&gt;N-able N-central&lt;/strong&gt;. N-able took hosted N-central offline on 9 November and shipped &lt;strong&gt;2026.4 Hotfix 2 (build 2026.4.1.26)&lt;/strong&gt; on 10 November with seven CVE fixes.&lt;/li&gt;
&lt;li&gt;More exploit code followed. N-able says the newer chains need the &lt;strong&gt;Legacy API&lt;/strong&gt;, a setting that is &lt;strong&gt;off by default&lt;/strong&gt;. Make sure it is off, upgrade to HF2, then &lt;strong&gt;upgrade every Agent and Probe&lt;/strong&gt;. A further hotfix, HF3, was still in validation on 14 November.&lt;/li&gt;
&lt;li&gt;N-able published &lt;strong&gt;indicators of compromise&lt;/strong&gt; on 13 November for servers that had the Legacy API turned on. Check your logs and firewall for them before you call the incident closed.&lt;/li&gt;
&lt;li&gt;This is N-central's &lt;strong&gt;fourth serious incident of 2026&lt;/strong&gt;: three earlier N-central CVEs are on CISA's Known Exploited Vulnerabilities list, each with a 3-day federal deadline.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you run N-central, the past week has been rough. Exploit code for what the researcher says are dozens of flaws went public with no warning to the vendor, the hosted service went dark, a hotfix arrived, and more exploit code landed the day after. Advice changed several times along the way.&lt;/p&gt;

&lt;p&gt;This page cuts it down to what N-able itself has said, what you should check on your own servers, and how to show your clients you are clear. Every fact below comes from N-able's &lt;a href="https://uptime.n-able.com/" rel="noopener noreferrer"&gt;status page&lt;/a&gt; and &lt;a href="https://status.n-able.com/2026/11/10/n-central-2026-4-hf2-release-notes/" rel="noopener noreferrer"&gt;HF2 release notes&lt;/a&gt;, CISA's KEV catalog and FIRST's EPSS scores, all read on 14 November 2026. We will update it when N-able releases HF3.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened, day by day
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;The Able2Shell timeline, from N-able's status page and release notes&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date (UTC)&lt;/th&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;8 to 9 Nov&lt;/td&gt;
&lt;td&gt;An independent researcher publishes proof-of-concept exploit code for N-central, under the name Able2Shell. N-able calls the disclosure non-responsible and says it was not reported through its channels.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9 Nov&lt;/td&gt;
&lt;td&gt;N-able takes hosted N-central (all regions) offline as a precaution and tells on-premises customers to keep their servers offline until they can upgrade. It reports scanning activity tied to the published code.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10 Nov&lt;/td&gt;
&lt;td&gt;N-central 2026.4 HF2 (build 2026.4.1.26) ships with seven CVEs. Hosted servers are upgraded and brought back. N-able says a follow-up hotfix will come.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;12 Nov&lt;/td&gt;
&lt;td&gt;After further disclosures, N-able restricts features: on-premises customers must make sure the Legacy API is disabled, and the Intune integration is switched off as a precaution. N-able says it has seen no signs of compromise.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;13 Nov&lt;/td&gt;
&lt;td&gt;N-able publishes indicators of compromise that apply only to servers where the Legacy API was not disabled.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;14 Nov&lt;/td&gt;
&lt;td&gt;HF3 is still in validation. N-able says it will not be available on 14 November and promises an update on the morning of 15 November (US Eastern).&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Still moving:&lt;/strong&gt; N-able's own guidance has changed from day to day. Before you act, read the newest entry on the &lt;a href="https://uptime.n-able.com/" rel="noopener noreferrer"&gt;N-able status page&lt;/a&gt;. Where this page and N-able disagree, N-able wins.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The CVEs fixed in HF2
&lt;/h2&gt;

&lt;p&gt;N-able's HF2 release notes list seven CVEs. The researcher's write-up claims many more issues than that. N-able has not said how many of them it reproduced, and it has promised a further hotfix, so treat HF2 as the floor, not the finish line.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;CVEs fixed in N-central 2026.4 HF2 (build 2026.4.1.26), as N-able describes them&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;CVE&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125883" rel="noopener noreferrer"&gt;CVE-2026-125883&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Multiple XML external entity (XXE) flaws&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125878" rel="noopener noreferrer"&gt;CVE-2026-125878&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Multiple OGNL injection flaws&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125879" rel="noopener noreferrer"&gt;CVE-2026-125879&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Local privilege escalation to root through a syslog-ng config the nable user can write&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125880" rel="noopener noreferrer"&gt;CVE-2026-125880&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Stored cross-site scripting through MMS3 patch metadata, run in an admin's session&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125881" rel="noopener noreferrer"&gt;CVE-2026-125881&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Server-side request forgery through service import schema validation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-125882" rel="noopener noreferrer"&gt;CVE-2026-125882&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Remote code execution through path traversal in file repository uploads&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-91000" rel="noopener noreferrer"&gt;CVE-2026-91000&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Insecure IPC channels that allow local privilege escalation&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None of the seven is on CISA's Known Exploited Vulnerabilities (KEV) catalog as of its 13 November update, and their EPSS scores were all under 1% on 14 November. Do not read that as "low risk". EPSS is a model that needs time to catch up with new CVEs, the exploit code is public, and N-able itself reports scanning against it. On a tool that can run commands on every endpoint you manage, public exploit code is enough reason to act today.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do now, in order
&lt;/h2&gt;

&lt;h3&gt;
  
  
  If you run N-central on-premises
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Make sure the Legacy API is off.&lt;/strong&gt; It is disabled by default, but check: if anyone turned it on, follow N-able's article &lt;a href="https://me.n-able.com/s/article/How-to-Disable-Legacy-API-settings-on-On-premise-N-central-servers" rel="noopener noreferrer"&gt;How to disable Legacy API settings on on-premises N-central servers&lt;/a&gt;. N-able ties the newer exploit chains and its published indicators to this setting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upgrade the server to 2026.4 HF2, build 2026.4.1.26.&lt;/strong&gt; N-able supports the upgrade from 2025.4 onward; older servers need its legacy upgrade path first. Until the upgrade is done, N-able's advice was to keep the server offline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upgrade every Agent and Probe, Agents first.&lt;/strong&gt; HF2 changes how Agents and Probes talk. An upgraded Probe cannot talk to Agents that are not yet on 2026.4.1.26, so features such as the offline patch cache stop until both sides match. Upgrading Agents first avoids the gap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cut internet exposure to the minimum.&lt;/strong&gt; The management interface should not be open to the whole internet. If your Agents and Probes need to reach the server from outside, scope what is reachable as tightly as your setup allows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check for the indicators of compromise&lt;/strong&gt; listed below, especially if the Legacy API was ever on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch for HF3&lt;/strong&gt; and apply it when N-able releases it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  If you use hosted N-central
&lt;/h3&gt;

&lt;p&gt;N-able upgrades hosted servers and has applied the temporary restrictions for you. Your job is the Agents and Probes: N-able says every customer, hosted or not, must upgrade them. Expect built-in remote control to stay off for now; N-able lists it as temporarily disabled in HF2, while Take Control keeps working.&lt;/p&gt;

&lt;h2&gt;
  
  
  N-able's indicators of compromise
&lt;/h2&gt;

&lt;p&gt;On 13 November N-able published these indicators, which it says apply only to servers that had the Legacy API enabled. They are written in the usual "defanged" form so nobody clicks them by accident. Search your firewall, proxy and DNS logs from 8 November onward.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Downloads from &lt;code&gt;hxxp://157.20.241[.]16:8080/&lt;/code&gt; (paths seen: &lt;code&gt;jup.sh&lt;/code&gt;, &lt;code&gt;xvgz&lt;/code&gt;, &lt;code&gt;xmrig.tgz&lt;/code&gt;, &lt;code&gt;ob/cronhit&lt;/code&gt;, &lt;code&gt;ob/fcheck&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Outbound traffic to &lt;code&gt;157.20.241[.]16&lt;/code&gt; on port 8080 or ports 19202 to 19418&lt;/li&gt;
&lt;li&gt;Outbound traffic to &lt;code&gt;139.99.69[.]109:10128&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Outbound traffic to &lt;code&gt;79.76.51[.]56:39100&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One of the file names, xmrig, is a well-known cryptocurrency miner. A miner on your RMM server is bad news on its own, but the bigger worry is the access it implies: whoever could install it could also push scripts to every managed machine. If you find a hit, treat it as a full incident: keep the logs and a snapshot, rotate every N-central admin, technician and integration credential, and review recent scripts, scheduled tasks and remote sessions sent to client endpoints.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fourth N-central emergency of 2026
&lt;/h2&gt;

&lt;p&gt;Able2Shell did not come out of nowhere. CISA has added three N-central CVEs to its KEV catalog this year, which means it had evidence of each one being used in real attacks. Each came with a 3-day fix deadline for US federal agencies.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;N-central CVEs on CISA's KEV catalog in 2026 (CISA feed, catalog version 2026.11.13; EPSS from FIRST on 14 November 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;CVE&lt;/th&gt;
&lt;th&gt;CISA's description&lt;/th&gt;
&lt;th&gt;Added to KEV&lt;/th&gt;
&lt;th&gt;Federal deadline&lt;/th&gt;
&lt;th&gt;EPSS today&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-18577" rel="noopener noreferrer"&gt;CVE-2026-18577&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Authentication bypass and account takeover; the result of an incomplete patch for CVE-2026-18556&lt;/td&gt;
&lt;td&gt;3 Aug 2026&lt;/td&gt;
&lt;td&gt;6 Aug 2026&lt;/td&gt;
&lt;td&gt;14.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-18556" rel="noopener noreferrer"&gt;CVE-2026-18556&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Authentication bypass using an alternate path or channel&lt;/td&gt;
&lt;td&gt;4 Aug 2026&lt;/td&gt;
&lt;td&gt;7 Aug 2026&lt;/td&gt;
&lt;td&gt;43.9%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-86218" rel="noopener noreferrer"&gt;CVE-2026-86218&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Static code injection allowing remote code execution before sign-in&lt;/td&gt;
&lt;td&gt;8 Sep 2026&lt;/td&gt;
&lt;td&gt;11 Sep 2026&lt;/td&gt;
&lt;td&gt;15.4%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Those EPSS scores sit in the top 4% of all scored CVEs. For an MSP, the pattern matters more than any single CVE: your RMM is the single place an attacker can reach every client at once, and attackers know it. Treat the RMM server itself as the most important asset you scan, not as plumbing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to show clients you are clear
&lt;/h2&gt;

&lt;p&gt;Clients will ask. "We patched" is a claim; a before-and-after scan is evidence. A short routine that works with whatever scanner you already use:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Scan the N-central server from outside.&lt;/strong&gt; An &lt;a href="https://varaxontech.com/guides/internal-vs-external-vulnerability-scans" rel="noopener noreferrer"&gt;external scan&lt;/a&gt; shows what the internet can actually reach. Note every open port and web path before you change anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run an authenticated scan inside&lt;/strong&gt; and look for the HF2 CVEs by ID. If your scanner has no check for them yet, record the build number you installed (2026.4.1.26) instead. Responders have noted that a hotfix does not always change the version string a scanner sees, so confirm the build using N-able's upgrade documentation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record the Legacy API setting&lt;/strong&gt; (screenshot or config export) and the date you confirmed it was off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rescan after the upgrade&lt;/strong&gt; and after HF3. The difference between the two scans is your &lt;a href="https://varaxontech.com/guides/proof-of-fix-since-the-last-scan" rel="noopener noreferrer"&gt;proof of fix&lt;/a&gt;: what was exposed, what changed, and when.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write it up in plain words&lt;/strong&gt; for each client: did this affect you, what did we do, and is anything still open. Our guide to &lt;a href="https://varaxontech.com/guides/explain-vulnerability-findings-to-non-technical-clients" rel="noopener noreferrer"&gt;explaining findings to non-technical clients&lt;/a&gt; has wording that works.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Varaxon Scan Hub does the bookkeeping part of this: it reads your scan exports, flags anything on CISA's KEV list, compares each rescan with the last one and turns the result into a client-ready report. It does not replace N-able's hotfix or your own judgement on the incident. If you want to see how the comparison looks with your own files, the &lt;a href="https://varaxontech.com/guides/compare-two-vulnerability-scans" rel="noopener noreferrer"&gt;compare two scans&lt;/a&gt; guide walks through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is Able2Shell?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Able2Shell is the name a security researcher gave to a set of N-able N-central flaws and exploit chains published on 8 to 9 November 2026, without warning the vendor first. Further releases followed (named 4EverAble2Shell and Agent2Shell), and N-able answered them with the restrictions it announced on 12 November.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which N-central version fixes Able2Shell?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;N-central 2026.4 Hotfix 2, build 2026.4.1.26, released on 10 November 2026, fixes seven CVEs. N-able says a further hotfix (HF3) is coming, and was still validating it on 14 November. Install HF2 now and HF3 when it ships.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is hosted N-central affected?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;N-able took hosted N-central offline on 9 November, upgraded it to HF2 and brought it back on 10 November. It has applied its later restrictions to hosted servers itself. Hosted customers still have to upgrade their own Agents and Probes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the N-central Legacy API and should it be on?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It is an older API setting that N-able ships turned off. N-able says the newer exploit chains and the indicators of compromise it published apply only to servers where it was turned on. Unless you have a hard dependency on it, keep it off.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are the Able2Shell CVEs on CISA's KEV list?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not as of CISA's 13 November 2026 update. Three earlier 2026 N-central CVEs are: CVE-2026-18577, CVE-2026-18556 and CVE-2026-86218. You can check any CVE against KEV and EPSS with our free &lt;a href="https://varaxontech.com/cve-checker" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://varaxontech.com/guides/n-central-able2shell-vulnerabilities" rel="noopener noreferrer"&gt;https://varaxontech.com/guides/n-central-able2shell-vulnerabilities&lt;/a&gt;. Varaxon Scan Hub turns vulnerability scan exports into evidence-led client reports, ranked by CISA KEV and EPSS.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>sysadmin</category>
      <category>infosec</category>
    </item>
    <item>
      <title>Patch Tuesday November 2026: 1,093 fixes, 1 exploited. What to patch first</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Sat, 14 Nov 2026 23:09:23 +0000</pubDate>
      <link>https://dev.to/varaxontech/patch-tuesday-november-2026-1093-fixes-1-exploited-what-to-patch-first-16kj</link>
      <guid>https://dev.to/varaxontech/patch-tuesday-november-2026-1093-fixes-1-exploited-what-to-patch-first-16kj</guid>
      <description>&lt;p&gt;&lt;em&gt;This article first appeared on &lt;a href="https://varaxontech.com/guides/patch-tuesday-november-2026-what-to-patch-first" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;, where it is kept up to date.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The short version&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Microsoft released fixes for &lt;strong&gt;1,093 of its own CVEs on 10 November 2026&lt;/strong&gt;, after a record &lt;strong&gt;1,408 in October&lt;/strong&gt;. Over the last four Patch Tuesdays that is &lt;strong&gt;3,875 CVEs&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Only &lt;strong&gt;6 of those 3,875 (0.15%)&lt;/strong&gt; are on CISA's Known Exploited Vulnerabilities (KEV) list. &lt;strong&gt;None of the 6 was rated Critical&lt;/strong&gt; by Microsoft. November's one exploited bug, in Outlook, is rated &lt;strong&gt;Moderate&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;If you patched only what Microsoft calls Critical, you would have fixed &lt;strong&gt;297 CVEs and missed all 6&lt;/strong&gt; that attackers actually used.&lt;/li&gt;
&lt;li&gt;A better order: &lt;strong&gt;KEV first&lt;/strong&gt;, then &lt;strong&gt;internet-facing systems&lt;/strong&gt;, then &lt;strong&gt;high EPSS&lt;/strong&gt;, then severity. EPSS put the Outlook bug &lt;strong&gt;7th of 1,093&lt;/strong&gt; this month, while its severity label put it near the bottom.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Patch Tuesday used to be a list you could read over coffee. In August 2026 Microsoft released 402 of its own CVEs on Patch Tuesday. In September it was 972, in October 1,408, and on 10 November 1,093. Nobody reads a thousand advisories a month, and nobody patches a thousand things in order of severity either.&lt;/p&gt;

&lt;p&gt;So we counted. This page takes Microsoft's own monthly security update data for the last four Patch Tuesdays, checks every CVE against CISA's KEV catalog and FIRST's EPSS scores, and asks one question: which signals would have pointed you at the bugs attackers actually used? The method is at the end, and you are welcome to reuse the numbers with a link back.&lt;/p&gt;

&lt;h2&gt;
  
  
  November 2026 Patch Tuesday in numbers
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;Microsoft-assigned CVEs released on 10 November 2026 (Microsoft update data; KEV catalog 2026.11.13; EPSS 14 November 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Measure&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;CVEs Microsoft released on 10 November&lt;/td&gt;
&lt;td&gt;1,093&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rated Critical by Microsoft&lt;/td&gt;
&lt;td&gt;63 (5.8%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remote code execution in the title&lt;/td&gt;
&lt;td&gt;296&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Exploited before the fix (Microsoft's own flag)&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;On CISA's KEV list&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EPSS score of 1% or more&lt;/td&gt;
&lt;td&gt;99&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EPSS score of 10% or more&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Microsoft's monthly document also lists 548 more CVEs that other organisations issued for open-source parts Microsoft ships, such as the Chromium engine in Edge. Two of those are on KEV this month: the Chromium bug &lt;a href="https://varaxontech.com/cve/CVE-2026-125350" rel="noopener noreferrer"&gt;CVE-2026-125350&lt;/a&gt; and the OpenSSH bug &lt;a href="https://varaxontech.com/cve/CVE-2026-123158" rel="noopener noreferrer"&gt;CVE-2026-123158&lt;/a&gt;. They are not in our counts, but they belong on your list.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one that matters: the Outlook zero-day (CVE-2026-124194)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-124194" rel="noopener noreferrer"&gt;CVE-2026-124194&lt;/a&gt; is the only November bug Microsoft marked as exploited, and CISA added it to KEV on the same day with a federal deadline of 24 November. In Microsoft's description, an attacker sends a crafted file and persuades someone to open it in Outlook. Outlook then connects to a server the attacker controls without showing its usual external-content warning, and that leaks the user's NTLMv2 password hash, which can be used to sign in as them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Severity: Moderate, CVSS 6.5.&lt;/strong&gt; It needs the user to open the file, and Microsoft says the Preview Pane is not a way in. On paper that sounds minor.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In practice it is a credential theft bug that attackers were already using.&lt;/strong&gt; That is why it is the first thing to patch this month, ahead of every Critical on the list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What to do:&lt;/strong&gt; install the November Office and Outlook updates, then confirm on a sample of machines that the update is really there. If you can, also block outbound SMB (TCP 445) to the internet, which limits this whole class of hash-leak attacks.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Four months of Patch Tuesday: severity missed every exploited bug
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;Microsoft-assigned CVEs released on each Patch Tuesday, August to November 2026&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Patch Tuesday&lt;/th&gt;
&lt;th&gt;CVEs&lt;/th&gt;
&lt;th&gt;Rated Critical&lt;/th&gt;
&lt;th&gt;Now on KEV&lt;/th&gt;
&lt;th&gt;Of those, rated Critical&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;11 August&lt;/td&gt;
&lt;td&gt;402&lt;/td&gt;
&lt;td&gt;44&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8 September&lt;/td&gt;
&lt;td&gt;972&lt;/td&gt;
&lt;td&gt;113&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;13 October&lt;/td&gt;
&lt;td&gt;1,408&lt;/td&gt;
&lt;td&gt;77&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10 November&lt;/td&gt;
&lt;td&gt;1,093&lt;/td&gt;
&lt;td&gt;63&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;3,875&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;297&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;6&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All six exploited CVEs were rated Important or Moderate. Four were privilege-escalation or bypass bugs in Windows, the kind attackers chain after they already have a foothold, and one was the Outlook credential leak. The sixth is a useful warning:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;"Exploitation less likely" is a forecast, not a promise:&lt;/strong&gt; Microsoft released the SharePoint bug &lt;a href="https://varaxontech.com/cve/CVE-2026-65660" rel="noopener noreferrer"&gt;CVE-2026-65660&lt;/a&gt; on 11 August, rated Important and marked "exploitation less likely". CISA added it to KEV on 25 September, 45 days later, with a 3-day deadline. If your process only revisits a month when Microsoft flags exploitation on release day, that one slips through.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;em&gt;The six exploited CVEs from August to November 2026 (Microsoft update data, CISA KEV, EPSS on 14 November 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;CVE&lt;/th&gt;
&lt;th&gt;What&lt;/th&gt;
&lt;th&gt;Microsoft severity&lt;/th&gt;
&lt;th&gt;CVSS&lt;/th&gt;
&lt;th&gt;Added to KEV&lt;/th&gt;
&lt;th&gt;EPSS today&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-68820" rel="noopener noreferrer"&gt;CVE-2026-68820&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Windows Ancillary Function Driver for WinSock, elevation of privilege&lt;/td&gt;
&lt;td&gt;Important&lt;/td&gt;
&lt;td&gt;7.0&lt;/td&gt;
&lt;td&gt;11 Aug&lt;/td&gt;
&lt;td&gt;8.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-65660" rel="noopener noreferrer"&gt;CVE-2026-65660&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;SharePoint Server, remote code execution&lt;/td&gt;
&lt;td&gt;Important&lt;/td&gt;
&lt;td&gt;8.8&lt;/td&gt;
&lt;td&gt;25 Sep&lt;/td&gt;
&lt;td&gt;9.9%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-81963" rel="noopener noreferrer"&gt;CVE-2026-81963&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Windows Update Stack, elevation of privilege&lt;/td&gt;
&lt;td&gt;Important&lt;/td&gt;
&lt;td&gt;7.8&lt;/td&gt;
&lt;td&gt;8 Sep&lt;/td&gt;
&lt;td&gt;7.1%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-85880" rel="noopener noreferrer"&gt;CVE-2026-85880&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Windows ALPC, elevation of privilege&lt;/td&gt;
&lt;td&gt;Important&lt;/td&gt;
&lt;td&gt;7.8&lt;/td&gt;
&lt;td&gt;8 Sep&lt;/td&gt;
&lt;td&gt;0.4%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-96951" rel="noopener noreferrer"&gt;CVE-2026-96951&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Windows Shell, security feature bypass&lt;/td&gt;
&lt;td&gt;Important&lt;/td&gt;
&lt;td&gt;8.8&lt;/td&gt;
&lt;td&gt;13 Oct&lt;/td&gt;
&lt;td&gt;9.8%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://varaxontech.com/cve/CVE-2026-124194" rel="noopener noreferrer"&gt;CVE-2026-124194&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Outlook, spoofing (NTLMv2 hash leak)&lt;/td&gt;
&lt;td&gt;Moderate&lt;/td&gt;
&lt;td&gt;6.5&lt;/td&gt;
&lt;td&gt;10 Nov&lt;/td&gt;
&lt;td&gt;1.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What EPSS got right, and where it falls short
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://varaxontech.com/guides/what-is-epss" rel="noopener noreferrer"&gt;EPSS&lt;/a&gt; estimates the chance a CVE will be exploited in the next 30 days. It did better than severity here, with a catch.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;It ranks well.&lt;/strong&gt; On 14 November the Outlook zero-day had an EPSS score of 1.6%, which sounds tiny, but only six of November's 1,093 Microsoft CVEs scored higher. Sorted by EPSS, it is on the first screen. Sorted by severity, it is near the bottom.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Its numbers look small.&lt;/strong&gt; Not one of the 3,875 CVEs from these four months scores 10% or more today, not even the exploited ones. If your rule is "patch anything over 10%", you would patch none of them. Use EPSS to rank, not as a pass mark.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It lags.&lt;/strong&gt; EPSS learns from what it sees. Across all of 2026, 81% of the CVEs CISA added to KEV had no EPSS score or a score under 10% the day before they were listed (&lt;a href="https://varaxontech.com/guides/cisa-kev-statistics" rel="noopener noreferrer"&gt;CISA KEV statistics&lt;/a&gt;). KEV tells you what has happened; EPSS tells you what is likely. You want both.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A patch order that would have caught all six
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Anything on CISA's KEV list, now.&lt;/strong&gt; Check every month's KEV additions against your whole estate, not just the latest Patch Tuesday, so late listings like the SharePoint bug get caught. Our &lt;a href="https://varaxontech.com/exploited-now" rel="noopener noreferrer"&gt;Exploited now&lt;/a&gt; page lists the last 30 days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Internet-facing systems next.&lt;/strong&gt; A remote code execution bug on an exposed Exchange, SharePoint or RD Gateway server is a different emergency from the same bug on an internal desktop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Then sort the rest by EPSS&lt;/strong&gt;, highest first, and give the top 1 to 2% a short deadline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Then severity&lt;/strong&gt;, to break ties and to plan the routine monthly rollout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rescan and prove it.&lt;/strong&gt; A patch that was deployed is not the same as a patch that installed. Rescan, compare against the last scan, and close only what the scan shows is gone.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That is the order Varaxon Scan Hub uses when it builds a report from your scan export: KEV findings first, then EPSS, then severity, with each finding showing the evidence behind its place in the list. You can try the same ordering on a single CVE with the free &lt;a href="https://varaxontech.com/cve-checker" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt;, or read more about the approach in &lt;a href="https://varaxontech.com/guides/risk-based-vulnerability-management" rel="noopener noreferrer"&gt;risk-based vulnerability management&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we counted
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Source:&lt;/strong&gt; Microsoft's public monthly security update documents for August to November 2026 (the CVRF data behind the Security Update Guide), read on 14 November 2026.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What counts as a CVE here:&lt;/strong&gt; CVEs Microsoft itself assigned, first released on the Patch Tuesday date. CVEs Microsoft added later in the month, and CVEs other organisations assigned for third-party components, are left out. That is why our totals can differ slightly from other write-ups.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Critical:&lt;/strong&gt; the CVE has a Critical rating for at least one affected product in Microsoft's data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exploited:&lt;/strong&gt; on CISA's KEV catalog, version 2026.11.13. Microsoft's own "exploited" flag matched KEV for five of the six; the sixth (CVE-2026-65660) was listed by CISA later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;EPSS:&lt;/strong&gt; FIRST's EPSS API, scores dated 14 November 2026.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We will add December's numbers after the next Patch Tuesday on 8 December 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;When was Patch Tuesday in November 2026?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Tuesday 10 November 2026. Microsoft releases its monthly security updates on the second Tuesday of each month. The next one is 8 December 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How many vulnerabilities did Microsoft fix in November 2026?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1,093 CVEs that Microsoft itself assigned were released on 10 November 2026, 63 of them rated Critical. Microsoft's monthly document also lists 548 CVEs from other organisations for third-party components such as Chromium.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Was there a zero-day in the November 2026 Patch Tuesday?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes, one: CVE-2026-124194, an Outlook spoofing bug that leaks the user's NTLMv2 hash. Microsoft marked it as exploited and CISA added it to KEV on 10 November with a 24 November deadline for US federal agencies.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should I patch Critical vulnerabilities first?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not by default. From August to November 2026, none of the six Microsoft CVEs that attackers used was rated Critical. Patch anything on CISA's KEV list first, then internet-facing systems, then the highest EPSS scores, and use severity to plan the rest.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://varaxontech.com/guides/patch-tuesday-november-2026-what-to-patch-first" rel="noopener noreferrer"&gt;https://varaxontech.com/guides/patch-tuesday-november-2026-what-to-patch-first&lt;/a&gt;. Varaxon Scan Hub turns vulnerability scan exports into evidence-led client reports, ranked by CISA KEV and EPSS.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>microsoft</category>
      <category>sysadmin</category>
    </item>
    <item>
      <title>How to compare two vulnerability scans from the command line</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Mon, 09 Nov 2026 17:28:28 +0000</pubDate>
      <link>https://dev.to/varaxontech/how-to-compare-two-vulnerability-scans-from-the-command-line-580d</link>
      <guid>https://dev.to/varaxontech/how-to-compare-two-vulnerability-scans-from-the-command-line-580d</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted with AI assistance. Every command below was run on 9 November 2026 against a pair of sample Nessus CSV exports in the default column layout before publishing.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Last month's scan had 9 findings and this month's has 5. Does that mean 4 were fixed? Not necessarily. Here's how to compare two Nessus CSV exports line by line with &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;cut&lt;/code&gt;, &lt;code&gt;sort&lt;/code&gt;, &lt;code&gt;comm&lt;/code&gt; and &lt;code&gt;awk&lt;/code&gt;, then check whether the findings that went away were really fixed. Two optional steps use Python 3.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Turn each export into one line per finding
&lt;/h2&gt;

&lt;p&gt;A finding is the same finding in both scans when the host, the Nessus plugin ID and the port match. In a default Nessus CSV, Plugin ID is column 1, Risk is 4, Host is 5, Protocol is 6 and Port is 7. This skips plugins with a Risk of &lt;code&gt;None&lt;/code&gt; (informational):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -E &lt;span class="s1"&gt;'^"[0-9]+",'&lt;/span&gt; october.csv &lt;span class="o"&gt;|&lt;/span&gt; cut -d, -f1,4,5,6,7 &lt;span class="o"&gt;|&lt;/span&gt; tr -d &lt;span class="s1"&gt;'"'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; awk -F, &lt;span class="s1"&gt;'$2 != "None" {print $3","$1","$4"/"$5}'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; october.txt
grep -E &lt;span class="s1"&gt;'^"[0-9]+",'&lt;/span&gt; november.csv &lt;span class="o"&gt;|&lt;/span&gt; cut -d, -f1,4,5,6,7 &lt;span class="o"&gt;|&lt;/span&gt; tr -d &lt;span class="s1"&gt;'"'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; awk -F, &lt;span class="s1"&gt;'$2 != "None" {print $3","$1","$4"/"$5}'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; november.txt
wc -l october.txt november.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Nessus puts long descriptions and plugin output on several lines inside quotes. The &lt;code&gt;grep&lt;/code&gt; keeps only lines that start a new row with a quoted plugin ID, so those extra lines are dropped. &lt;code&gt;cut&lt;/code&gt; is safe because the first seven columns never contain commas. A line looks like &lt;code&gt;10.0.0.5,104743,tcp/443&lt;/code&gt;. Our October sample had 9 findings and November had 5.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Split them into fixed, new and still open
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -23 october.txt november.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; fixed.txt   &lt;span class="c"&gt;# gone (looks fixed)&lt;/span&gt;
&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -13 october.txt november.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; new.txt     &lt;span class="c"&gt;# new&lt;/span&gt;
&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -12 october.txt november.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; open.txt    &lt;span class="c"&gt;# still open&lt;/span&gt;
wc -l fixed.txt new.txt open.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Our sample gave 5 gone, 1 new (SSH Terrapin, CVE-2023-48795, on &lt;code&gt;10.0.0.12&lt;/code&gt;) and 4 still open. &lt;code&gt;LC_ALL=C&lt;/code&gt; keeps &lt;code&gt;sort&lt;/code&gt; and &lt;code&gt;comm&lt;/code&gt; in the same order.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Check for hosts that weren't scanned
&lt;/h2&gt;

&lt;p&gt;If a host was switched off or left out of the scan range, every finding on it disappears. That isn't a fix.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -E &lt;span class="s1"&gt;'^"[0-9]+",'&lt;/span&gt; october.csv &lt;span class="o"&gt;|&lt;/span&gt; cut -d, -f5 &lt;span class="o"&gt;|&lt;/span&gt; tr -d &lt;span class="s1"&gt;'"'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; october-hosts.txt
grep -E &lt;span class="s1"&gt;'^"[0-9]+",'&lt;/span&gt; november.csv &lt;span class="o"&gt;|&lt;/span&gt; cut -d, -f5 &lt;span class="o"&gt;|&lt;/span&gt; tr -d &lt;span class="s1"&gt;'"'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; november-hosts.txt
&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -23 october-hosts.txt november-hosts.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; gone-hosts.txt
awk -F, &lt;span class="s1"&gt;'NR==FNR {gone[$1]; next} !($1 in gone)'&lt;/span&gt; gone-hosts.txt fixed.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; fixed-scanned.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In our sample, &lt;code&gt;10.0.0.20&lt;/code&gt; dropped out, so its two findings (TLS 1.0 and a self-signed certificate) only looked fixed. That left 3 in &lt;code&gt;fixed-scanned.txt&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check that both scans logged in
&lt;/h2&gt;

&lt;p&gt;A credentialed scan logs in and checks installed packages. If the login fails next time, those local checks don't run and their findings vanish. Nessus records the result per host in plugin 19506 (Nessus Scan Information) as &lt;code&gt;Credentialed checks : yes&lt;/code&gt; or &lt;code&gt;no&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python3 -c &lt;span class="s1"&gt;'import csv,sys; [print(r["Host"], l.split(":", 1)[1].strip()) for r in csv.DictReader(open(sys.argv[1], newline="")) if r["Plugin ID"] == "19506" for l in r["Plugin Output"].splitlines() if l.startswith("Credentialed checks")]'&lt;/span&gt; november.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it on both files. In our sample, &lt;code&gt;10.0.0.12&lt;/code&gt; logged in during October but printed &lt;code&gt;no&lt;/code&gt; in November, so its OpenSSH package finding went missing because the login failed, not because OpenSSH was updated.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Put names on the results
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python3 -c &lt;span class="s1"&gt;'import csv,sys; keys = {tuple(l.strip().split(",")) for l in open(sys.argv[2])}; rows = {(r["Host"], r["Plugin ID"], r["Protocol"] + "/" + r["Port"]): r for r in csv.DictReader(open(sys.argv[1], newline=""))}; [print(rows[k]["Risk"], k[0], rows[k]["Name"], sep="\t") for k in sorted(keys) if k in rows]'&lt;/span&gt; october.csv fixed-scanned.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use the older export for fixed findings and the newer one (with &lt;code&gt;new.txt&lt;/code&gt;) for new findings. Setting aside the OpenSSH finding from step 4, two findings in our sample were really fixed: MS17-010 (EternalBlue) on &lt;code&gt;10.0.0.10&lt;/code&gt; and TLS 1.0 on &lt;code&gt;10.0.0.5&lt;/code&gt;. &lt;strong&gt;Five findings disappeared, but only two were fixed.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One more trap: Tenable sometimes retires a plugin and replaces it with a new one. The old ID then shows as fixed and the new ID as new, on the same host and port. If a fixed and a new finding share a host and port, read both before reporting either.&lt;/p&gt;

&lt;h2&gt;
  
  
  Putting it to use
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Compare scans from the same scanner with the same policy. Nessus and Qualys name and check issues differently, so their lists won't line up.&lt;/li&gt;
&lt;li&gt;Keep the dated lists with both exports. A list of what was fixed, and the scan that confirmed it, is useful evidence for audits and client reviews.&lt;/li&gt;
&lt;li&gt;Run steps 3 and 4 every time. They catch the two most common reasons a finding looks fixed when it isn't.&lt;/li&gt;
&lt;li&gt;If you changed the Nessus CSV columns, check &lt;code&gt;head -1 october.csv&lt;/code&gt; and change the numbers. The Python steps read columns by name.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;The original version of this guide lives on &lt;a href="https://varaxontech.com/guides/compare-two-vulnerability-scans?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=compare-scans-nov-2026" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;. To see which of the new and still-open findings are being exploited, see &lt;a href="https://varaxontech.com/guides/check-scan-results-against-cisa-kev?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=compare-scans-nov-2026" rel="noopener noreferrer"&gt;how to check your scan results against CISA KEV&lt;/a&gt;. We built Varaxon Scan Hub to do this comparison on every report, without counting a finding as fixed when the host wasn't rescanned or the login failed.&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
      <category>linux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Closing out the year with proof: a remediation checklist for security consultants and MSPs</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Sun, 08 Nov 2026 01:06:15 +0000</pubDate>
      <link>https://dev.to/varaxontech/closing-out-the-year-with-proof-a-remediation-checklist-for-security-consultants-and-msps-2fmk</link>
      <guid>https://dev.to/varaxontech/closing-out-the-year-with-proof-a-remediation-checklist-for-security-consultants-and-msps-2fmk</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted with AI assistance and checked by the Varaxon team. The offer at the end is ours: we built Varaxon Scan Hub.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;December is when clients ask the awkward question: "So, did we actually fix what you found this year?" Year-end audits, cyber insurance renewals and budget reviews all want the same thing, which is evidence that findings were closed, not just reported.&lt;/p&gt;

&lt;p&gt;Here's a short checklist for getting that evidence in order before the holidays, whatever scanner you run.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Pick one baseline scan per client
&lt;/h2&gt;

&lt;p&gt;Choose the scan everyone agreed on as the starting point, usually the first full scan of the year or the one attached to the last report. Every "fixed" claim later is measured against it. If you have several scanners on one client, keep one baseline per scanner. Comparing a Nessus scan to a Greenbone scan as if they were the same tool produces false "fixed" results.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Rescan with the same scope and credentials
&lt;/h2&gt;

&lt;p&gt;A finding that disappears because a host was left out of the rescan isn't fixed. Use the same targets, the same credentialed or uncredentialed setup and the same policy. Write down anything that changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Sort every finding into one of four buckets
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fixed:&lt;/strong&gt; present in the baseline, gone from a rescan with the same scope.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Still open:&lt;/strong&gt; present in both.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accepted:&lt;/strong&gt; the client chose not to fix it, with a name, a reason and a review date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not compared:&lt;/strong&gt; the host or check wasn't in the rescan, so you can't say either way.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last bucket matters most. A gap reported as "clean" is the fastest way to lose a client's trust.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Put exploited issues first
&lt;/h2&gt;

&lt;p&gt;Check the open list against CISA's Known Exploited Vulnerabilities catalog. Anything on it should be at the top of January's plan, with a due date, whatever its CVSS score.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Hand over one document
&lt;/h2&gt;

&lt;p&gt;Clients and auditors don't want five exports. They want one report: what was found, what was fixed and when, what's still open and who owns it, and what was accepted and why. Each line should trace back to the scan that proves it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Doing this without the spreadsheet work
&lt;/h2&gt;

&lt;p&gt;This is the work Varaxon Scan Hub does. You upload the exports from the scanners you already use, and it writes a plain-language report with your logo, ranks findings by real-world danger and shows what was closed since the last scan, with each line traced to its evidence. Fixes can go straight into ConnectWise PSA or HaloPSA as tickets.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Black Friday offer:&lt;/strong&gt; 40% off your first 3 months on any monthly plan with code &lt;strong&gt;BF40&lt;/strong&gt;. It's for new customers on monthly plans, and it runs until Wednesday, December 2, 2026 at 11:59 PM ET. Every account starts with a 14-day free trial of Core, no card needed, so you can try it on your last scan first.&lt;/p&gt;

&lt;p&gt;Details and the fine print: &lt;a href="https://varaxontech.com/black-friday" rel="noopener noreferrer"&gt;https://varaxontech.com/black-friday&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to check your scan results against CISA KEV from the command line</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Fri, 06 Nov 2026 13:32:50 +0000</pubDate>
      <link>https://dev.to/varaxontech/how-to-check-your-scan-results-against-cisa-kev-from-the-command-line-pbe</link>
      <guid>https://dev.to/varaxontech/how-to-check-your-scan-results-against-cisa-kev-from-the-command-line-pbe</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted with AI assistance. Every command below was run on 6 November 2026 (jq 1.7) against the live CISA KEV feed, FIRST's EPSS API and a sample Nessus CSV export before publishing.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A scan report can list hundreds of CVEs. CISA's Known Exploited Vulnerabilities (KEV) catalog tells you which of them attackers are actually using, and FIRST's EPSS score estimates how likely the rest are to be exploited soon. Here's how to check your own scan export against both with &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;sort&lt;/code&gt;, &lt;code&gt;comm&lt;/code&gt;, &lt;code&gt;curl&lt;/code&gt; and &lt;code&gt;jq&lt;/code&gt; (1.6 or later).&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Pull the CVE IDs out of your export
&lt;/h2&gt;

&lt;p&gt;This works on a Nessus CSV or &lt;code&gt;.nessus&lt;/code&gt; file, an OpenVAS/Greenbone XML report, a Qualys or Rapid7 CSV, or a JSON export. It doesn't parse the format. It just finds every string that looks like a CVE ID.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -ohE &lt;span class="s1"&gt;'CVE-[0-9]{4}-[0-9]{4,}'&lt;/span&gt; scan-export.csv &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; scan-cves.txt
wc -l &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; scan-cves.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To check several exports at once, list them all after &lt;code&gt;grep&lt;/code&gt; (or use &lt;code&gt;*.csv&lt;/code&gt;). &lt;code&gt;LC_ALL=C&lt;/code&gt; keeps every sort in the same order, which &lt;code&gt;comm&lt;/code&gt; needs in step 3.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Download the KEV catalog
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -o kev.json https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
jq -r &lt;span class="s1"&gt;'.catalogVersion, .count'&lt;/span&gt; kev.json
jq -r &lt;span class="s1"&gt;'.vulnerabilities[].cveID'&lt;/span&gt; kev.json &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; kev-cves.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On 6 November 2026 the catalog was version &lt;code&gt;2026.11.04&lt;/code&gt; with 1,768 entries. CISA adds entries several times a week, so grab a fresh copy each time.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Find the CVEs that are on KEV
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;comm -12&lt;/code&gt; prints only the lines found in both sorted lists: the CVEs in your scan that are known to be exploited.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -12 scan-cves.txt kev-cves.txt &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; on-kev.txt

&lt;span class="c"&gt;# CVE, vendor, product, date added, due date, ransomware use (tab-separated)&lt;/span&gt;
jq -r --rawfile ids on-kev.txt &lt;span class="s1"&gt;'($ids | split("\n") | map(select(length &amp;gt; 0))) as $l
  | .vulnerabilities[] | select(.cveID | IN($l[]))
  | [.cveID, .vendorProject, .product, .dateAdded, .dueDate, .knownRansomwareCampaignUse] | @tsv'&lt;/span&gt; kev.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Our sample export had 6 unique CVEs, and 3 were on KEV: CVE-2024-3400 (Palo Alto PAN-OS), CVE-2021-44228 (Log4j) and CVE-2023-4863 (Chromium WebP). The first two are marked &lt;code&gt;Known&lt;/code&gt; for ransomware use.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. See which hosts have them
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Every row that mentions a KEV CVE&lt;/span&gt;
grep -F -f on-kev.txt scan-export.csv

&lt;span class="c"&gt;# Just CVE and host, using Nessus's default CSV columns (CVE = 2, Host = 5)&lt;/span&gt;
grep -F -f on-kev.txt scan-export.csv &lt;span class="o"&gt;|&lt;/span&gt; cut -d, -f2,5 &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C sort -u
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you changed the columns, or your scanner uses a different layout, check the header row and adjust the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Rank everything by EPSS
&lt;/h2&gt;

&lt;p&gt;FIRST's EPSS API takes up to 100 CVEs per request and needs no key. This splits the list into groups of 100, so it works for a scan of any size:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;split -l 100 scan-cves.txt chunk_
&lt;span class="k"&gt;for&lt;/span&gt; f &lt;span class="k"&gt;in&lt;/span&gt; chunk_*&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
  curl -s &lt;span class="s2"&gt;"https://api.first.org/data/v1/epss?cve=$(paste -sd, "&lt;/span&gt;&lt;span class="nv"&gt;$f&lt;/span&gt;&lt;span class="s2"&gt;")&amp;amp;limit=100"&lt;/span&gt;
&lt;span class="k"&gt;done&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jq -rs &lt;span class="s1"&gt;'[.[].data[]] | sort_by(-(.epss | tonumber)) | .[] | [.cve, .epss, .percentile] | @tsv'&lt;/span&gt;

&lt;span class="c"&gt;# The CVEs that are not on KEV, to work through next&lt;/span&gt;
&lt;span class="nv"&gt;LC_ALL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;C comm -23 scan-cves.txt kev-cves.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In our sample, the three KEV entries all scored above 0.99. Of the rest, SSH Terrapin (CVE-2023-48795) scored 0.94, well above the two OpenSSL CVEs at 0.04 and 0.02. That puts it next in line, even though its CVSS score was the lowest of the three.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;KEV first, whatever the EPSS score.&lt;/strong&gt; A CVE on KEV is being exploited now, even if its EPSS score is low. EPSS estimates exploitation across the whole internet over the next 30 days, so a narrowly targeted appliance bug can score low and still be on KEV.&lt;/p&gt;

&lt;h2&gt;
  
  
  Putting it to use
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Treat KEV's &lt;code&gt;dueDate&lt;/code&gt; as your target for anything internet-facing. US federal agencies get anywhere from a few days to three weeks.&lt;/li&gt;
&lt;li&gt;Re-run steps 2 and 3 when CISA adds entries. A CVE you deferred last week can be on KEV today.&lt;/li&gt;
&lt;li&gt;Keep the TSV output with the scan. A dated list of exploited CVEs and the hosts that had them is useful evidence for audits and client reviews.&lt;/li&gt;
&lt;li&gt;Findings with no CVE (weak TLS settings, default credentials) won't show up here. Review those in the report itself.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If &lt;code&gt;comm&lt;/code&gt; complains a file isn't sorted, re-create both lists with &lt;code&gt;LC_ALL=C sort -u&lt;/code&gt;. If &lt;code&gt;jq&lt;/code&gt; says &lt;code&gt;IN&lt;/code&gt; or &lt;code&gt;--rawfile&lt;/code&gt; isn't defined, your jq is older than 1.6.&lt;/p&gt;




&lt;p&gt;The original version of this guide lives on &lt;a href="https://varaxontech.com/guides/check-scan-results-against-cisa-kev?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=scan-vs-kev-nov-2026" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;. To follow what CISA adds each month, see &lt;a href="https://varaxontech.com/guides/track-cisa-kev-and-epss-with-curl-and-jq?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=scan-vs-kev-nov-2026" rel="noopener noreferrer"&gt;how to track KEV additions with curl and jq&lt;/a&gt;. We built Varaxon Scan Hub to run these KEV and EPSS checks on every finding when you upload a scan export.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>bash</category>
      <category>devops</category>
    </item>
    <item>
      <title>Track CISA KEV additions and EPSS scores with curl and jq</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Mon, 02 Nov 2026 17:33:14 +0000</pubDate>
      <link>https://dev.to/varaxontech/track-cisa-kev-additions-and-epss-scores-with-curl-and-jq-3152</link>
      <guid>https://dev.to/varaxontech/track-cisa-kev-additions-and-epss-scores-with-curl-and-jq-3152</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted with AI assistance. Every command below was run against the live CISA KEV feed and FIRST's EPSS API on 2 November 2026 (jq 1.7) before publishing.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You don't need a platform to keep an eye on what attackers are exploiting. CISA's Known Exploited Vulnerabilities (KEV) catalog is one public JSON file, and FIRST's EPSS scores come from a free API with no key. With &lt;code&gt;curl&lt;/code&gt; and &lt;code&gt;jq&lt;/code&gt; (1.6 or later) you can list a month's new exploited CVEs, see how long US agencies were given to fix them, and add EPSS scores in a few commands.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Download the KEV catalog
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -o kev.json https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
jq -r &lt;span class="s1"&gt;'.catalogVersion, .count'&lt;/span&gt; kev.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On 2 November 2026 this printed &lt;code&gt;2026.10.30&lt;/code&gt; and &lt;code&gt;1766&lt;/code&gt;. Each entry has &lt;code&gt;cveID&lt;/code&gt;, &lt;code&gt;vendorProject&lt;/code&gt;, &lt;code&gt;product&lt;/code&gt;, &lt;code&gt;dateAdded&lt;/code&gt;, &lt;code&gt;dueDate&lt;/code&gt; and &lt;code&gt;knownRansomwareCampaignUse&lt;/code&gt;, which is all the commands below need.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. List one month's additions
&lt;/h2&gt;

&lt;p&gt;Dates are plain &lt;code&gt;YYYY-MM-DD&lt;/code&gt; strings, so a text comparison picks a month. Swap the two dates for the month you want.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# How many&lt;/span&gt;
jq &lt;span class="s1"&gt;'[.vulnerabilities[] | select(.dateAdded &amp;gt;= "2026-10-01" and .dateAdded &amp;lt; "2026-11-01")] | length'&lt;/span&gt; kev.json

&lt;span class="c"&gt;# Date added, CVE, vendor, product, due date (tab-separated)&lt;/span&gt;
jq -r &lt;span class="s1"&gt;'.vulnerabilities[] | select(.dateAdded &amp;gt;= "2026-10-01" and .dateAdded &amp;lt; "2026-11-01") | [.dateAdded, .cveID, .vendorProject, .product, .dueDate] | @tsv'&lt;/span&gt; kev.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For October 2026 the count is 36. The TSV output pastes straight into a spreadsheet.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. See how long agencies were given to fix them
&lt;/h2&gt;

&lt;p&gt;The gap between &lt;code&gt;dateAdded&lt;/code&gt; and &lt;code&gt;dueDate&lt;/code&gt; is the BOD 22-01 deadline for US federal agencies, and a useful benchmark for everyone else.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;jq -r &lt;span class="s1"&gt;'.vulnerabilities[] | select(.dateAdded &amp;gt;= "2026-10-01" and .dateAdded &amp;lt; "2026-11-01") | (.dueDate | strptime("%Y-%m-%d") | mktime) - (.dateAdded | strptime("%Y-%m-%d") | mktime) | . / 86400'&lt;/span&gt; kev.json &lt;span class="o"&gt;|&lt;/span&gt; sort -n &lt;span class="o"&gt;|&lt;/span&gt; uniq -c

&lt;span class="c"&gt;# Entries known to be used in ransomware, whole catalog&lt;/span&gt;
jq &lt;span class="s1"&gt;'[.vulnerabilities[] | select(.knownRansomwareCampaignUse == "Known")] | length'&lt;/span&gt; kev.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For October 2026: 29 entries with a 3-day window and 7 with 14 days. The ransomware count was 361 across the catalog. CISA updates that field after entries are added, so re-check it rather than trusting an old copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Add EPSS scores
&lt;/h2&gt;

&lt;p&gt;FIRST's API takes a comma-separated list of CVEs and returns up to 100 results by default, enough for any month of KEV additions.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;ids&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;jq -r &lt;span class="s1"&gt;'[.vulnerabilities[] | select(.dateAdded &amp;gt;= "2026-10-01" and .dateAdded &amp;lt; "2026-11-01") | .cveID] | join(",")'&lt;/span&gt; kev.json&lt;span class="o"&gt;)&lt;/span&gt;
curl -s -o epss.json &lt;span class="s2"&gt;"https://api.first.org/data/v1/epss?cve=$ids&amp;amp;limit=100"&lt;/span&gt;

&lt;span class="c"&gt;# Highest first: CVE, EPSS, percentile&lt;/span&gt;
jq -r &lt;span class="s1"&gt;'.data | sort_by(-(.epss | tonumber)) | .[] | [.cve, .epss, .percentile] | @tsv'&lt;/span&gt; epss.json

&lt;span class="c"&gt;# How many score under 10%&lt;/span&gt;
jq &lt;span class="s1"&gt;'[.data[] | select((.epss | tonumber) &amp;lt; 0.1)] | length'&lt;/span&gt; epss.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Scores change daily. On 2 November 2026, 35 of October's 36 additions had a score, and 16 of those were under 10%.&lt;/p&gt;

&lt;p&gt;That last number is the interesting one. A CVE on KEV is already being exploited, whatever its EPSS score. EPSS estimates the chance of exploitation in the next 30 days across the whole internet, so a low score on a KEV entry usually means a narrow target, like one vendor's appliance. Fix KEV entries first, then use EPSS to order everything else.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Check a single CVE
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;jq -r &lt;span class="s1"&gt;'.vulnerabilities[] | select(.cveID == "CVE-2024-3400") | [.dateAdded, .dueDate, .knownRansomwareCampaignUse] | @tsv'&lt;/span&gt; kev.json
curl -s &lt;span class="s2"&gt;"https://api.first.org/data/v1/epss?cve=CVE-2024-3400"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.data[0].epss'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Putting it to use
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Run steps 1 and 2 weekly (or from cron) and compare the new CVEs with your asset list or last scan.&lt;/li&gt;
&lt;li&gt;Treat &lt;code&gt;dueDate&lt;/code&gt; as your own target for anything internet-facing.&lt;/li&gt;
&lt;li&gt;Keep the TSV output. A dated list of what was exploited and when is good evidence for audits and client reviews.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If &lt;code&gt;jq&lt;/code&gt; complains that &lt;code&gt;strptime&lt;/code&gt; is not defined, your version is older than 1.5. Install a current one from your package manager.&lt;/p&gt;




&lt;p&gt;The original version of this guide, with these commands, lives on &lt;a href="https://varaxontech.com/guides/track-cisa-kev-and-epss-with-curl-and-jq?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=kev-jq-nov-2026" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;. We publish the monthly numbers too: here's the &lt;a href="https://varaxontech.com/guides/cisa-kev-report-october-2026?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=kev-jq-nov-2026" rel="noopener noreferrer"&gt;CISA KEV report for October 2026&lt;/a&gt;. If you'd rather not use a terminal, the free &lt;a href="https://varaxontech.com/cve-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=kev-jq-nov-2026" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt; shows KEV, EPSS and CVSS for any CVE.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>bash</category>
      <category>devops</category>
    </item>
    <item>
      <title>8 free security tools for IT teams: CVE, DMARC, SPF, DKIM and MX checks (no sign-up)</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Sun, 01 Nov 2026 01:57:37 +0000</pubDate>
      <link>https://dev.to/varaxontech/8-free-security-tools-for-it-teams-cve-dmarc-spf-dkim-and-mx-checks-no-sign-up-13bg</link>
      <guid>https://dev.to/varaxontech/8-free-security-tools-for-it-teams-cve-dmarc-spf-dkim-and-mx-checks-no-sign-up-13bg</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted with AI assistance. Every tool and link below was checked on the live site before publishing.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Most security checks don't need a paid product or a sales call. They need public data, read correctly, and an answer you can act on. Over the last few weeks we built eight free tools that do exactly that. None of them needs an account.&lt;/p&gt;

&lt;p&gt;Here is what each one is for, a 10-minute routine that uses them, and what changed in Varaxon Scan Hub this month.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vulnerability checks
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. &lt;a href="https://varaxontech.com/cve-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt;: is this CVE being exploited right now?&lt;/strong&gt;&lt;br&gt;
Paste a CVE ID and get three answers at once: whether it is on CISA's Known Exploited Vulnerabilities (KEV) catalog, its EPSS score (the chance of exploitation in the next 30 days) and its CVSS severity, with a plain-English verdict on how urgently to fix it. Use it when a new CVE hits the news, or when a scan report hands you 400 "Critical" findings and you need to know which ones attackers actually use.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. &lt;a href="https://scan.varaxontech.com/scan-summary/page?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;Free pre-flight check&lt;/a&gt;: will your scan export work?&lt;/strong&gt;&lt;br&gt;
Upload an export from your vulnerability scanner and see what Scan Hub can read from it before you spend anything. No account needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Email security checks
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;3. &lt;a href="https://varaxontech.com/email-check?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;Email security check&lt;/a&gt;: can someone send email pretending to be you?&lt;/strong&gt;&lt;br&gt;
One check covers SPF, DKIM, DMARC, lookalike domains and up to three suppliers, then grades the domain A to F and lists the exact DNS records that would raise the grade. It takes about 20 seconds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. &lt;a href="https://varaxontech.com/spf-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;SPF checker&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
Shows your SPF record and catches the usual mistakes, such as more than 10 DNS lookups or duplicate records. Each problem comes with the exact fix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. &lt;a href="https://varaxontech.com/dkim-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;DKIM checker&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
Finds the DKIM keys your domain publishes, checks their length, and explains how to switch signing on if it is missing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. &lt;a href="https://varaxontech.com/dmarc-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;DMARC checker&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
Shows your DMARC policy and, in plain words, whether email that fakes your domain is rejected, quarantined or delivered anyway.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. &lt;a href="https://varaxontech.com/dmarc-record-generator?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;DMARC record generator&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
Pick a policy and a reporting address, then copy a valid DMARC TXT record. It includes plain advice on moving safely from &lt;code&gt;p=none&lt;/code&gt; to &lt;code&gt;p=reject&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  DNS
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;8. &lt;a href="https://varaxontech.com/mx-lookup?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;MX lookup&lt;/a&gt;: who receives email for a domain?&lt;/strong&gt;&lt;br&gt;
Lists the mail servers for any domain, who hosts them, and whether SPF and DMARC are set up. It's handy before a migration, or when you're vetting a supplier's email.&lt;/p&gt;

&lt;p&gt;All eight are in one place at &lt;a href="https://varaxontech.com/free-tools?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;varaxontech.com/free-tools&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 10-minute routine for your own domain (or a client's)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Run the &lt;a href="https://varaxontech.com/email-check?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;email security check&lt;/a&gt; and note the grade.&lt;/li&gt;
&lt;li&gt;If SPF fails, open the &lt;a href="https://varaxontech.com/spf-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;SPF checker&lt;/a&gt; and fix the record it flags first. Lookup-limit errors silently break SPF for every message.&lt;/li&gt;
&lt;li&gt;If there is no DMARC record, build one with the &lt;a href="https://varaxontech.com/dmarc-record-generator?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;generator&lt;/a&gt; at &lt;code&gt;p=none&lt;/code&gt; with a reporting address, and calendar a move to &lt;code&gt;quarantine&lt;/code&gt; once the reports look clean.&lt;/li&gt;
&lt;li&gt;Take the three newest CVEs from your last scan or patch notes and run them through the &lt;a href="https://varaxontech.com/cve-checker?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt;. Anything on KEV moves to the top of this week's list.&lt;/li&gt;
&lt;li&gt;Rerun the email check after DNS has updated and keep the before and after grades. That's your evidence.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What's new in Scan Hub
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://varaxontech.com/?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;Varaxon Scan Hub&lt;/a&gt; turns the export from the vulnerability scanner you already use into a client-ready report, ranked by what attackers actually exploit (CISA KEV, VulnCheck KEV and EPSS) rather than severity alone. It's scanner-agnostic: it reads exports from network, host and web vulnerability scanners, and it can also connect to Microsoft Defender or ConnectSecure. Code decides the facts, and AI only writes the plain-English explanation from them.&lt;/p&gt;

&lt;p&gt;Recently added:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Proof of fix in every report:&lt;/strong&gt; a "Since the last scan" section showing what was fixed, what came back and what's new, system by system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix deadlines and signed risk acceptance:&lt;/strong&gt; due dates from each finding's priority (or the CISA KEV due date when that's sooner), a past-due list per client, and a one-time link for a client to sign off on a risk they choose to accept.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proof packs:&lt;/strong&gt; a white-label PDF of up to a year of fixes, open items and accepted risks, for audits, insurers and renewals.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tickets:&lt;/strong&gt; after you review a report, Scan Hub can push the fixes into ConnectWise PSA or HaloPSA as tickets.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The free tools above&lt;/strong&gt;, now with their own &lt;a href="https://varaxontech.com/free-tools?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;hub page&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The full rundown is in &lt;a href="https://varaxontech.com/guides/whats-new-in-scan-hub-october-2026?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;What's new in Scan Hub: October 2026&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it free for 14 days
&lt;/h2&gt;

&lt;p&gt;Every new account gets a &lt;strong&gt;14-day free trial of Core&lt;/strong&gt;: up to 10 reports, 3 team members and every feature. No credit card is needed, and there's no automatic charge when the trial ends. You pick a plan, or buy single reports, only if you want to.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://scan.varaxontech.com/signup?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;Start the free trial&lt;/a&gt; or &lt;a href="https://varaxontech.com/sample-reports?utm_source=devto&amp;amp;utm_medium=blog&amp;amp;utm_campaign=free-tools-nov-2026" rel="noopener noreferrer"&gt;look at sample reports&lt;/a&gt; first.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>email</category>
      <category>devops</category>
    </item>
    <item>
      <title>Is this CVE actually being exploited? Check KEV, EPSS and CVSS in under a minute</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Sat, 31 Oct 2026 21:58:44 +0000</pubDate>
      <link>https://dev.to/varaxontech/is-this-cve-actually-being-exploited-check-kev-epss-and-cvss-in-under-a-minute-1oan</link>
      <guid>https://dev.to/varaxontech/is-this-cve-actually-being-exploited-check-kev-epss-and-cvss-in-under-a-minute-1oan</guid>
      <description>&lt;p&gt;A new CVE lands in your feed, or a scan report comes back with 400 "Critical" findings. The question that actually decides what you do next is not "how bad could this be?" It is "is anyone using this right now?"&lt;/p&gt;

&lt;p&gt;You can answer that in under a minute with three free, public data sources. Here is how to check each one yourself, from the command line, and how to read the answers together.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. CISA KEV: is it being exploited right now?
&lt;/h2&gt;

&lt;p&gt;The US Cybersecurity and Infrastructure Security Agency keeps the &lt;strong&gt;Known Exploited Vulnerabilities (KEV)&lt;/strong&gt; catalog: CVEs with reliable evidence of active exploitation. It is short (1,766 entries as of 30 October 2026, out of hundreds of thousands of CVEs), so a match means something.&lt;/p&gt;

&lt;p&gt;CISA publishes the whole catalog as one JSON file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json -o kev.json

jq -r &lt;span class="s1"&gt;'.vulnerabilities[] | select(.cveID=="CVE-2021-44228") | "\(.cveID) on KEV since \(.dateAdded), ransomware use: \(.knownRansomwareCampaignUse)"'&lt;/span&gt; kev.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;CVE-2021-44228 on KEV since 2021-12-10, ransomware use: Known
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No output means the CVE is not on the list. That is not proof it is safe; it means nobody has confirmed exploitation to CISA's standard yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. EPSS: how likely is exploitation soon?
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;Exploit Prediction Scoring System&lt;/strong&gt;, published daily by FIRST, estimates the probability that a CVE is exploited in the next 30 days. It has a free API that needs no key:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s &lt;span class="s2"&gt;"https://api.first.org/data/v1/epss?cve=CVE-2021-44228"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.data[0] | "EPSS \(.epss)  percentile \(.percentile)  (\(.date))"'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;EPSS 0.999990000  percentile 1.000000000  (2026-10-31)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read it as a probability: 0.05 is 5%. Most CVEs score well under 1%, so anything in the top few percentiles deserves attention even if it isn't on KEV yet. Scores change daily, so check again rather than caching last month's number.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. CVSS: how bad would it be?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;CVSS&lt;/strong&gt; is the 0 to 10 severity score most scanners lead with. The NVD API returns it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s &lt;span class="s2"&gt;"https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-44228"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.vulnerabilities[0].cve.metrics.cvssMetricV31[0].cvssData.baseScore'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;10.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;CVSS tells you the damage if exploited. It does not tell you whether anyone will bother, which is why thousands of 9.8s sit untouched for years while a 7.5 on KEV gets used in ransomware campaigns.&lt;/p&gt;

&lt;h2&gt;
  
  
  Putting the three together
&lt;/h2&gt;

&lt;p&gt;A simple, defensible order for any list of findings:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;On KEV:&lt;/strong&gt; fix first. Someone is using it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High EPSS&lt;/strong&gt; (say, top 5% by percentile): fix next. Exploitation is likely soon.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Everything else, by CVSS:&lt;/strong&gt; schedule by severity and exposure.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That order also makes reports easier to defend. "We fixed these 6 first because CISA confirms they are being exploited" lands better with a client or manager than "we fixed the reds."&lt;/p&gt;

&lt;p&gt;A few gotchas worth knowing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Scanner exports often leave CVEs out.&lt;/strong&gt; Some checks only carry a vendor ID (an OpenVAS OID or a Nessus plugin ID), so a CVE-based lookup misses them unless you map the ID first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;KEV has a sibling list.&lt;/strong&gt; VulnCheck publishes its own KEV with more entries and faster additions; worth a look if CISA's list feels slow.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;EPSS is per CVE, not per host.&lt;/strong&gt; An internet-facing server and an isolated lab box get the same score. Exposure is still your call.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Skip the terminal
&lt;/h2&gt;

&lt;p&gt;If you'd rather paste a CVE into a box, we built a free &lt;a href="https://varaxontech.com/cve-checker" rel="noopener noreferrer"&gt;CVE checker&lt;/a&gt; that runs all three lookups at once and gives a plain-English answer on how urgently to fix it. No account, nothing stored. It sits alongside our other &lt;a href="https://varaxontech.com/free-tools" rel="noopener noreferrer"&gt;free tools&lt;/a&gt; (DMARC, SPF, DKIM and MX checks, and a DMARC record generator).&lt;/p&gt;

&lt;p&gt;For the longer background, see &lt;a href="https://varaxontech.com/guides/what-is-cisa-kev" rel="noopener noreferrer"&gt;What is CISA KEV?&lt;/a&gt; and &lt;a href="https://varaxontech.com/guides/what-is-epss" rel="noopener noreferrer"&gt;What is EPSS?&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Drafted with AI assistance. Every command above was run against the live APIs on 31 October 2026 before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>devops</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to test a vulnerability reporting tool in 14 days</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:38:42 +0000</pubDate>
      <link>https://dev.to/varaxontech/how-to-test-a-vulnerability-reporting-tool-in-14-days-16lp</link>
      <guid>https://dev.to/varaxontech/how-to-test-a-vulnerability-reporting-tool-in-14-days-16lp</guid>
      <description>&lt;p&gt;Most free trials end the same way. You sign up, click around with the sample data, get pulled into other work, and the trial expires before you have tested anything that matters.&lt;/p&gt;

&lt;p&gt;A vulnerability reporting tool is easy to judge if you test it on your own data, against a few clear questions. Here is a two-week plan that does that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use &lt;strong&gt;your own scan exports&lt;/strong&gt;, not the vendor's demo data. Bring at least one messy one.&lt;/li&gt;
&lt;li&gt;Check the ranking against &lt;strong&gt;real-world evidence&lt;/strong&gt;, not just severity scores.&lt;/li&gt;
&lt;li&gt;Send one report to a &lt;strong&gt;real reader&lt;/strong&gt; (a client or your manager) and watch what they ask.&lt;/li&gt;
&lt;li&gt;Test the &lt;strong&gt;second scan&lt;/strong&gt;, not just the first: proving fixes is where most of the value is.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you start: pick your test data
&lt;/h2&gt;

&lt;p&gt;Gather three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A typical export&lt;/strong&gt; from the scanner you run most.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A difficult export&lt;/strong&gt;: a large one, one from a second scanner, or one where you know the scanner left CVEs out.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Two scans of the same client&lt;/strong&gt;, about a month apart, from the same scanner. You will need these for the proof-of-fix test.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Remove anything you are not allowed to share with a third party, and read the tool's data retention terms first. How long does it keep your raw uploads?&lt;/p&gt;

&lt;h2&gt;
  
  
  Days 1 to 3: first report
&lt;/h2&gt;

&lt;p&gt;Upload the typical export and read the report as if you were the client.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Did it read everything?&lt;/strong&gt; Compare the host and finding counts with the scanner's own summary. A tool that silently drops rows is a tool you can't trust.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is the top of the list right?&lt;/strong&gt; The first ten findings should be the ones you would fix first. Check that anything on the CISA KEV list is near the top, whatever its CVSS score.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can you see why?&lt;/strong&gt; For each top finding, the report should show its evidence: KEV listing, exploit likelihood (EPSS), end-of-life status. "Critical" alone is not a reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is anything made up?&lt;/strong&gt; If the tool uses AI to write, check that every CVE, host name and count in the text matches the export. Facts should come from the data, not from the model.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Days 4 to 6: the hard export
&lt;/h2&gt;

&lt;p&gt;Now upload the difficult one. This is where tools separate.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does it handle a &lt;strong&gt;different scanner's&lt;/strong&gt; format without you converting anything?&lt;/li&gt;
&lt;li&gt;If the export is missing CVEs, does the tool &lt;strong&gt;map the scanner's own check IDs&lt;/strong&gt; back to CVEs, or does it just show less?&lt;/li&gt;
&lt;li&gt;Does a large file finish in a reasonable time, and does it tell you what it skipped and why?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Days 7 to 9: a real reader
&lt;/h2&gt;

&lt;p&gt;Send one report to the person who would really receive it, under your own branding if you are an MSP.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do they understand the &lt;strong&gt;first page&lt;/strong&gt; without your help?&lt;/li&gt;
&lt;li&gt;Do they ask "what should I do first?" If so, the report didn't answer it.&lt;/li&gt;
&lt;li&gt;Is the &lt;strong&gt;fix list&lt;/strong&gt; something your team can act on: specific steps, per system?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Days 10 to 12: the second scan
&lt;/h2&gt;

&lt;p&gt;Upload the later scan of the same client. This is the test most trials skip, and it matters most for monthly work.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does the report show what was &lt;strong&gt;fixed&lt;/strong&gt;, what &lt;strong&gt;came back&lt;/strong&gt; and what is &lt;strong&gt;new&lt;/strong&gt; since the last scan?&lt;/li&gt;
&lt;li&gt;Is it honest about gaps? If the second scan didn't log in, issues should show as &lt;strong&gt;not rechecked&lt;/strong&gt;, not fixed.&lt;/li&gt;
&lt;li&gt;Can findings become &lt;strong&gt;tickets&lt;/strong&gt; in your PSA, with due dates, without retyping?&lt;/li&gt;
&lt;li&gt;Can you record a finding the client &lt;strong&gt;won't fix&lt;/strong&gt;, with a reason and an end date?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Days 13 and 14: decide
&lt;/h2&gt;

&lt;p&gt;Answer four questions in writing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Did it save time compared with how you build reports today? Roughly how much per report?&lt;/li&gt;
&lt;li&gt;Would you send its report to a client or auditor without editing it?&lt;/li&gt;
&lt;li&gt;Did it get the priorities right on your own data?&lt;/li&gt;
&lt;li&gt;What does it cost at the number of reports you produce in a normal month?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If three of the four answers are yes, it is probably worth paying for. If not, you have lost nothing but two weeks, and you know exactly what to look for next time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try this plan on Scan Hub
&lt;/h2&gt;

&lt;p&gt;We built &lt;a href="https://varaxontech.com" rel="noopener noreferrer"&gt;Varaxon Scan Hub&lt;/a&gt; to pass this test. It is scanner-agnostic, ranks findings by CISA KEV, VulnCheck KEV and EPSS before severity, maps scanner check IDs to CVEs when an export leaves them out, and shows what was fixed since the last scan. Code decides the facts, and AI only writes the explanations from them. Raw uploads are deleted within 7 days.&lt;/p&gt;

&lt;p&gt;Every new account gets a &lt;strong&gt;14-day free trial of Core&lt;/strong&gt;: up to 10 reports and 3 team seats, with no card needed and no automatic charge at the end. Not ready to sign up? The free &lt;a href="https://varaxontech.com" rel="noopener noreferrer"&gt;pre-flight check&lt;/a&gt; needs no account at all. &lt;a href="https://scan.varaxontech.com/signup" rel="noopener noreferrer"&gt;Start a free trial&lt;/a&gt; or &lt;a href="https://varaxontech.com/sample-reports" rel="noopener noreferrer"&gt;see sample reports&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>vulnerabilitymanagement</category>
      <category>msp</category>
    </item>
    <item>
      <title>Turning vulnerability scan results into billable remediation work</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:38:01 +0000</pubDate>
      <link>https://dev.to/varaxontech/turning-vulnerability-scan-results-into-billable-remediation-work-3o25</link>
      <guid>https://dev.to/varaxontech/turning-vulnerability-scan-results-into-billable-remediation-work-3o25</guid>
      <description>&lt;p&gt;A vulnerability scan is one of the best sources of project work an MSP has. It is also one of the easiest to give away for free.&lt;/p&gt;

&lt;p&gt;The pattern is familiar. The scan finds 200 issues. Some are patches your managed service already covers. Others are an unsupported server, an old firewall, or a line-of-business app that needs a vendor upgrade. If you don't separate the two, your team quietly absorbs the second group, or it never gets done.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sort every finding into &lt;strong&gt;covered&lt;/strong&gt; (your contract already pays for it) or &lt;strong&gt;project&lt;/strong&gt; (it needs approval and a quote).&lt;/li&gt;
&lt;li&gt;Group project findings by &lt;strong&gt;fix&lt;/strong&gt;, not by finding: one upgrade can close forty rows.&lt;/li&gt;
&lt;li&gt;Lead the quote with evidence the client understands: "this is being exploited right now", not "CVSS 9.8".&lt;/li&gt;
&lt;li&gt;If the client says no, record it as an accepted risk, with an end date.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 1: Draw the line your contract already draws
&lt;/h2&gt;

&lt;p&gt;Read your agreement before you read the scan. Most managed service agreements cover routine patching of supported operating systems and common software on a schedule. They usually don't cover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replacing or upgrading &lt;strong&gt;end-of-life&lt;/strong&gt; systems and software, where no patch is coming.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Major version upgrades&lt;/strong&gt; of line-of-business apps, especially when the software vendor has to be involved.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configuration projects&lt;/strong&gt;: hardening, TLS changes, firewall rule clean-up, network segmentation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hardware&lt;/strong&gt; replacement, such as network devices with no firmware fix.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Whatever your contract says, write the line down once and apply it the same way every month. Clients accept a consistent rule much more easily than a case-by-case argument.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Group project findings by fix
&lt;/h2&gt;

&lt;p&gt;Clients don't buy findings. They buy fixes. A single end-of-life server can produce dozens of findings in a scan. Present it as one item:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;th&gt;Findings it closes&lt;/th&gt;
&lt;th&gt;Why now&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Replace Windows Server 2012 R2 host&lt;/td&gt;
&lt;td&gt;38&lt;/td&gt;
&lt;td&gt;Extended support ended October 2023&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Upgrade the VPN appliance firmware&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;2 are on the CISA KEV list&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Disable old TLS versions on the web server&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Fails common insurer questionnaires&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Three lines are something a client can decide on in one meeting. Two hundred rows are not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Rank by evidence, not by score
&lt;/h2&gt;

&lt;p&gt;A CVSS score says how bad a flaw &lt;em&gt;could&lt;/em&gt; be. It doesn't say whether anyone is using it. For the quote, lead with stronger evidence:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;On the CISA KEV list.&lt;/strong&gt; Attackers are exploiting it right now. This is the easiest conversation you will have.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High EPSS score.&lt;/strong&gt; A good chance it gets exploited in the next 30 days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;End of life.&lt;/strong&gt; No patch is ever coming, so the risk only grows.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;"Two of these are being actively exploited, and there will never be a patch for this server" will get a budget approved. "We found 14 criticals" usually won't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Get a decision, and record it
&lt;/h2&gt;

&lt;p&gt;Send the project items as a short proposal with a price and a due date for each. Then make sure every item ends in one of two places:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Approved&lt;/strong&gt;: it becomes a ticket with an owner and a due date, and the next scan proves it was done.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Declined&lt;/strong&gt;: it becomes an &lt;strong&gt;accepted risk&lt;/strong&gt;, with the client's reason, any compensating control and an end date. When the date comes, ask again.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The second outcome is just as important as the first. If a breach ever happens through a declined item, a signed acceptance shows the risk was explained and the client chose. Without it, the client may remember things differently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Show the work at the next review
&lt;/h2&gt;

&lt;p&gt;At the quarterly review, show three lists: what was fixed (proven by a rescan), what was accepted, and what is still open or past due. Billable work that was approved and done is the best proof that your managed service is worth renewing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Scan Hub helps
&lt;/h2&gt;

&lt;p&gt;We built &lt;a href="https://varaxontech.com" rel="noopener noreferrer"&gt;Varaxon Scan Hub&lt;/a&gt; to make this sorting quick. It is scanner-agnostic: upload an export from the scanner you already run, or connect Microsoft Defender or ConnectSecure. Each report ranks findings by CISA KEV, VulnCheck KEV and EPSS first, flags end-of-life software with the date support ended, and is white-label, so it goes to the client under your name.&lt;/p&gt;

&lt;p&gt;After you review a report, Scan Hub can push the fixes into ConnectWise PSA or HaloPSA as tickets, record accepted risks (or let the client sign them online), and prove fixes in the next report.&lt;/p&gt;

&lt;p&gt;Every new account gets a &lt;strong&gt;14-day free trial of Core&lt;/strong&gt;, with up to 10 reports and no card needed. &lt;a href="https://scan.varaxontech.com/signup" rel="noopener noreferrer"&gt;Start a free trial&lt;/a&gt; or &lt;a href="https://varaxontech.com/sample-reports" rel="noopener noreferrer"&gt;see sample reports&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>msp</category>
      <category>cybersecurity</category>
      <category>vulnerabilitymanagement</category>
      <category>security</category>
    </item>
    <item>
      <title>Fixed, accepted or ticketed: close the loop on every vulnerability finding</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:37:20 +0000</pubDate>
      <link>https://dev.to/varaxontech/fixed-accepted-or-ticketed-close-the-loop-on-every-vulnerability-finding-30e9</link>
      <guid>https://dev.to/varaxontech/fixed-accepted-or-ticketed-close-the-loop-on-every-vulnerability-finding-30e9</guid>
      <description>&lt;p&gt;Most vulnerability reports end the same way. The scan runs, the PDF goes out, and three months later the same findings are back in the next PDF. Nobody decided to ignore them. Nobody decided anything at all.&lt;/p&gt;

&lt;p&gt;The fix is not a better scanner. It is a rule: &lt;strong&gt;every finding has to end somewhere.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every finding should end in one of three places: &lt;strong&gt;fixed&lt;/strong&gt; and proven by a rescan, &lt;strong&gt;accepted&lt;/strong&gt; in writing, or &lt;strong&gt;ticketed&lt;/strong&gt; with an owner and a due date.&lt;/li&gt;
&lt;li&gt;Rank by real-world evidence first (is it being exploited, how likely is it to be), then by severity score.&lt;/li&gt;
&lt;li&gt;A fix only counts when a rescan that could actually see the issue no longer finds it.&lt;/li&gt;
&lt;li&gt;"Accepted" needs a reason, a compensating control if there is one, and an end date.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why findings get stuck
&lt;/h2&gt;

&lt;p&gt;A raw scan export gives you hundreds of rows, each with a severity score. It does not tell you who owns the fix, when it is due, or whether the client already said no last quarter. So the report becomes a list of problems, and the list becomes background noise.&lt;/p&gt;

&lt;p&gt;Findings get stuck in four predictable places:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Nobody owns them.&lt;/strong&gt; The report went to a contact, not to the person who patches.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No date.&lt;/strong&gt; "Critical" with no deadline is a mood, not a plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Silent refusals.&lt;/strong&gt; The client said "we can't take that server down" on a call, and that decision lives nowhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No proof.&lt;/strong&gt; The patch went in, but nobody checked the rescan, so the finding is still on the books, or worse, marked fixed when it isn't.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The three outcomes
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Fixed, and proven
&lt;/h3&gt;

&lt;p&gt;A finding is fixed when a rescan of the same system, by the same scanner, with the same access, no longer finds it. All three parts matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Same system.&lt;/strong&gt; If the host is missing from this scan, you know nothing about it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Same scanner.&lt;/strong&gt; Scanners name and detect issues differently, so comparing two different tools gives you false "fixes".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Same access.&lt;/strong&gt; If last month's scan logged in and this month's didn't, issues that need a login were never looked for. Mark them &lt;strong&gt;not rechecked&lt;/strong&gt;, not fixed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write the result down system by system: "OpenSSH fixed on three servers" is proof. "We did some patching" is not.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Accepted, in writing
&lt;/h3&gt;

&lt;p&gt;Sometimes the right answer is not to fix. A legacy system runs a line-of-business app, or the fix needs downtime the client won't approve. That is a valid decision, as long as it is recorded:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What&lt;/strong&gt; is being accepted, and on which systems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Why&lt;/strong&gt;, in the client's words.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compensating control&lt;/strong&gt;, if there is one (network isolation, extra monitoring).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Who&lt;/strong&gt; signed off, and &lt;strong&gt;when the acceptance ends&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An end date matters most. Acceptances that never expire turn into permanent blind spots. When one ends, the finding comes back for a new decision.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Ticketed, with a due date
&lt;/h3&gt;

&lt;p&gt;Everything else becomes work. Each ticket needs an owner and a due date based on how urgent the finding really is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Known exploited&lt;/strong&gt; (on the CISA KEV list): fix first. If KEV gives a due date, use it when it is sooner than your own.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Likely to be exploited&lt;/strong&gt; (a high EPSS score): next.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Severity alone&lt;/strong&gt;: after that, on your normal schedule.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Put the ticket where the work already happens, in your PSA or ticketing system, not in a separate spreadsheet. Then track what is past due, by how many days, and how many were fixed on time.&lt;/p&gt;

&lt;h2&gt;
  
  
  A monthly loop that works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Scan&lt;/strong&gt; with the same scanner and settings as last time. Use a credentialed scan if you can.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rank&lt;/strong&gt; by evidence: KEV, then exploit likelihood, then severity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decide&lt;/strong&gt; for each new finding: fix (ticket it) or accept (record it).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rescan&lt;/strong&gt; and compare. Close what is proven fixed. Flag what came back.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Report&lt;/strong&gt; the three lists to the client: fixed, accepted, in progress, with what is past due.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do this every month and the report stops being a list of problems. It becomes a record of decisions and work done, which is what clients, auditors and insurers actually want to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we built this into Scan Hub
&lt;/h2&gt;

&lt;p&gt;We built &lt;a href="https://varaxontech.com" rel="noopener noreferrer"&gt;Varaxon Scan Hub&lt;/a&gt; around this loop. It is scanner-agnostic: upload the export from the scanner you already run, or connect Microsoft Defender or ConnectSecure. Reports are evidence-led. Code ranks findings by CISA KEV, VulnCheck KEV and EPSS before severity, and AI only writes the explanations from those facts.&lt;/p&gt;

&lt;p&gt;From there, each finding can end in one of the three places: pushed as a ticket into ConnectWise PSA or HaloPSA with a due date, accepted with a reason and an end date (or signed online by the client), or proven fixed in the next report's &lt;strong&gt;Since the last scan&lt;/strong&gt; section. A proof pack rolls months of that into one PDF for audits and renewals.&lt;/p&gt;

&lt;p&gt;Every new account gets a &lt;strong&gt;14-day free trial of Core&lt;/strong&gt;, with up to 10 reports and no card needed. &lt;a href="https://scan.varaxontech.com/signup" rel="noopener noreferrer"&gt;Start a free trial&lt;/a&gt; or &lt;a href="https://varaxontech.com/sample-reports" rel="noopener noreferrer"&gt;see sample reports&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>vulnerabilitymanagement</category>
      <category>msp</category>
    </item>
    <item>
      <title>What's new in Varaxon Scan Hub: October 2026</title>
      <dc:creator>Brandon Sooknanan</dc:creator>
      <pubDate>Mon, 26 Oct 2026 21:50:11 +0000</pubDate>
      <link>https://dev.to/varaxontech/whats-new-in-varaxon-scan-hub-october-2026-1hnk</link>
      <guid>https://dev.to/varaxontech/whats-new-in-varaxon-scan-hub-october-2026-1hnk</guid>
      <description>&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;New:&lt;/strong&gt; a free email and domain check, graded A to F, for your own domain, your clients and their suppliers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reports&lt;/strong&gt; now prove what was fixed since the last scan, with deadlines and a past due list behind them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proof packs&lt;/strong&gt; turn months of that history into evidence for audits, insurers and renewals.&lt;/li&gt;
&lt;li&gt;Everything stays evidence-led: code decides the facts, and AI only writes from them.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;p&gt;This month we built the parts that come after the report: proving the work was done, tracking what is late, recording what the client chose not to fix, and handing all of it to whoever asks. We also added a free check that has nothing to do with scanners at all. Here is everything, with links to the full guides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Free email and domain check
&lt;/h2&gt;

&lt;p&gt;Can someone send email pretending to be you? The &lt;a href="https://varaxontech.com/email-check" rel="noopener noreferrer"&gt;free email check&lt;/a&gt; answers in about 20 seconds, with no account. It reads SPF, DKIM, DMARC, MTA-STS and the domain's registry record, looks at about 400 lookalike names, and checks up to three suppliers. It grades the domain A to F by fixed rules and lists only the DNS changes that raise the grade.&lt;/p&gt;

&lt;p&gt;Inside Scan Hub it runs for each client at no cost, as a white-label PDF with a fingerprint, and a recheck shows the grade before and after your fixes. &lt;a href="https://varaxontech.com/guides/free-email-security-check" rel="noopener noreferrer"&gt;Read the full guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Proof of fix in every report
&lt;/h2&gt;

&lt;p&gt;Each report now has a &lt;strong&gt;Since the last scan&lt;/strong&gt; section: what was fixed, what came back and what is new, system by system, most urgent first. If a rescan didn't log in, issues are marked not rechecked, never fixed. &lt;a href="https://varaxontech.com/guides/proof-of-fix-since-the-last-scan" rel="noopener noreferrer"&gt;Read the full guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix deadlines and signed risk acceptance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fix deadlines.&lt;/strong&gt; Every tracked finding has a due date from its priority band, or the CISA KEV due date when that is sooner. Each client has a past due list with days late and an on-time count. You can set deadlines for the whole organization or per client.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Risk acceptance.&lt;/strong&gt; When a client won't fix something, record why, any compensating control and an end date, or send their contact a one-time link to sign online. Accepted findings stay open but are not past due, and you are reminded before an acceptance ends.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Proof packs
&lt;/h2&gt;

&lt;p&gt;A white-label PDF of a client's last 30 to 365 days: what was fixed and proven by a rescan, what is open, past due or accepted, the tickets sent and the scans used. It can map that evidence to CIS Controls v8, NIST CSF 2.0 and the HIPAA Security Rule, and answer the questions cyber insurers commonly ask, without ever claiming a control is met. A fingerprint lets anyone confirm the facts weren't changed. &lt;a href="https://varaxontech.com/guides/proof-pack-vulnerability-evidence" rel="noopener noreferrer"&gt;Read the full guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  An In progress page
&lt;/h2&gt;

&lt;p&gt;After you upload a scan or click Build report, you no longer have to go back to the client's page to find it. &lt;strong&gt;In progress&lt;/strong&gt; in the sidebar lists every report, proof pack and email check being built across your team, with its current step and a progress bar, plus what finished in the last 24 hours. The sidebar shows a count while anything is building, and a one-line strip at the top of every page links to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  More evidence behind every ranking
&lt;/h2&gt;

&lt;p&gt;Scan Hub ranks findings by real-world evidence first, not by severity score alone. Each report now shows more of that evidence:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CISA KEV&lt;/strong&gt; decides the top band, and &lt;strong&gt;EPSS&lt;/strong&gt; exploit likelihood moves a finding up and orders findings within each band. See &lt;a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev" rel="noopener noreferrer"&gt;CVSS vs EPSS vs CISA KEV&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;VulnCheck KEV&lt;/strong&gt; listings are shown next to CISA's, so a CVE reported as exploited elsewhere is not missed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;End-of-life dates&lt;/strong&gt; for common software and operating systems, so the report says when no patch is coming and what to move to.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;What public threat data adds&lt;/strong&gt; section at the top of the report sums up what this evidence changed.&lt;/li&gt;
&lt;li&gt;For exports that leave CVEs out, Scan Hub now maps the scanner's own check IDs to CVEs. Our second &lt;a href="https://varaxontech.com/sample-reports" rel="noopener noreferrer"&gt;sample report&lt;/a&gt; went from no known-exploited matches to &lt;strong&gt;9&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Already in Scan Hub
&lt;/h2&gt;

&lt;p&gt;Scan Hub is scanner-agnostic: upload exports from the network, host and web vulnerability scanners you already run, or connect Microsoft Defender or ConnectSecure. After you review a report, it can push the fixes into ConnectWise PSA or HaloPSA as tickets. Reports are white-label, team members have their own roles with an activity log, and there is a free pre-flight check before you spend anything. Scan Hub is listed on &lt;a href="https://varaxontech.com/guides/scan-hub-on-connectwise-and-microsoft-marketplace" rel="noopener noreferrer"&gt;Microsoft Marketplace and the ConnectWise® Marketplace&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We built it for MSPs, and just as much for internal IT, compliance and security teams. Every new account gets a 14-day free trial of Core, with no card needed. &lt;a href="https://scan.varaxontech.com/signup" rel="noopener noreferrer"&gt;Create an account&lt;/a&gt; or &lt;a href="https://varaxontech.com/sample-reports" rel="noopener noreferrer"&gt;see sample reports&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do the new features cost extra?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Proof of fix, fix deadlines, risk acceptance, the In progress page and email checks are included. A proof pack is paid for like a report, from your monthly allowance or one credit. See &lt;a href="https://varaxontech.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does AI decide what is fixed or how urgent a finding is?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Code compares scans, ranks findings from public threat data and builds the facts. AI writes the plain-English report and the proof pack summary from those facts, and its output is checked against them.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://varaxontech.com/guides/whats-new-in-scan-hub-october-2026" rel="noopener noreferrer"&gt;varaxontech.com&lt;/a&gt;. Scan Hub is listed on Microsoft Marketplace and the ConnectWise® Marketplace, and it can push fixes into ConnectWise PSA or HaloPSA as tickets.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>msp</category>
      <category>vulnerabilities</category>
    </item>
  </channel>
</rss>
