<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Varaxon Blog]]></title><description><![CDATA[Practical guides for MSPs and security consultants on reading scan results, prioritizing fixes and writing vulnerability reports clients understand.]]></description><link>https://varaxontech.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6ad708bd1bcd36d206f5c5a4/3e21262f-7b32-485c-9543-5ef0e8f36321.png</url><title>Varaxon Blog</title><link>https://varaxontech.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 15:59:35 GMT</lastBuildDate><atom:link href="https://varaxontech.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[8 free security tools for IT teams: CVE, DMARC, SPF, DKIM and MX checks (no sign-up)]]></title><description><![CDATA[Eight free tools, no account: check if a CVE is exploited, test SPF, DKIM and DMARC, build a DMARC record, look up MX. Plus a 14-day Scan Hub trial.]]></description><link>https://varaxontech.hashnode.dev/free-security-tools-cve-dmarc-spf-dkim-mx</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/free-security-tools-cve-dmarc-spf-dkim-mx</guid><category><![CDATA[Security]]></category><category><![CDATA[cybersecurity]]></category><category><![CDATA[email]]></category><category><![CDATA[Devops]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Sun, 01 Nov 2026 12:05:29 GMT</pubDate><content:encoded><![CDATA[<p><em>Drafted with AI assistance. Every tool and link below was checked on the live site before publishing.</em></p>
<p>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.</p>
<p>Here is what each one is for, a 10-minute routine that uses them, and what changed in Varaxon Scan Hub this month.</p>
<h2>Vulnerability checks</h2>
<p><strong>1.</strong> <a href="https://varaxontech.com/cve-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>CVE checker</strong></a><strong>: is this CVE being exploited right now?</strong> 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.</p>
<p><strong>2.</strong> <a href="https://scan.varaxontech.com/scan-summary/page?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>Free pre-flight check</strong></a><strong>: will your scan export work?</strong> Upload an export from your vulnerability scanner and see what Scan Hub can read from it before you spend anything. No account needed.</p>
<h2>Email security checks</h2>
<p><strong>3.</strong> <a href="https://varaxontech.com/email-check?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>Email security check</strong></a><strong>: can someone send email pretending to be you?</strong> 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.</p>
<p><strong>4.</strong> <a href="https://varaxontech.com/spf-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>SPF checker</strong></a> 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.</p>
<p><strong>5.</strong> <a href="https://varaxontech.com/dkim-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>DKIM checker</strong></a> Finds the DKIM keys your domain publishes, checks their length, and explains how to switch signing on if it is missing.</p>
<p><strong>6.</strong> <a href="https://varaxontech.com/dmarc-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>DMARC checker</strong></a> Shows your DMARC policy and, in plain words, whether email that fakes your domain is rejected, quarantined or delivered anyway.</p>
<p><strong>7.</strong> <a href="https://varaxontech.com/dmarc-record-generator?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>DMARC record generator</strong></a> Pick a policy and a reporting address, then copy a valid DMARC TXT record. It includes plain advice on moving safely from <code>p=none</code> to <code>p=reject</code>.</p>
<h2>DNS</h2>
<p><strong>8.</strong> <a href="https://varaxontech.com/mx-lookup?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026"><strong>MX lookup</strong></a><strong>: who receives email for a domain?</strong> 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.</p>
<p>All eight are in one place at <a href="https://varaxontech.com/free-tools?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">varaxontech.com/free-tools</a>.</p>
<h2>A 10-minute routine for your own domain (or a client's)</h2>
<ol>
<li>Run the <a href="https://varaxontech.com/email-check?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">email security check</a> and note the grade.</li>
<li>If SPF fails, open the <a href="https://varaxontech.com/spf-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">SPF checker</a> and fix the record it flags first. Lookup-limit errors silently break SPF for every message.</li>
<li>If there is no DMARC record, build one with the <a href="https://varaxontech.com/dmarc-record-generator?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">generator</a> at <code>p=none</code> with a reporting address, and calendar a move to <code>quarantine</code> once the reports look clean.</li>
<li>Take the three newest CVEs from your last scan or patch notes and run them through the <a href="https://varaxontech.com/cve-checker?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">CVE checker</a>. Anything on KEV moves to the top of this week's list.</li>
<li>Rerun the email check after DNS has updated and keep the before and after grades. That's your evidence.</li>
</ol>
<h2>What's new in Scan Hub</h2>
<p><a href="https://varaxontech.com/?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">Varaxon Scan Hub</a> 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.</p>
<p>Recently added:</p>
<ul>
<li><strong>Proof of fix in every report:</strong> a "Since the last scan" section showing what was fixed, what came back and what's new, system by system.</li>
<li><strong>Fix deadlines and signed risk acceptance:</strong> 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.</li>
<li><strong>Proof packs:</strong> a white-label PDF of up to a year of fixes, open items and accepted risks, for audits, insurers and renewals.</li>
<li><strong>Tickets:</strong> after you review a report, Scan Hub can push the fixes into ConnectWise PSA or HaloPSA as tickets.</li>
<li><strong>The free tools above</strong>, now with their own <a href="https://varaxontech.com/free-tools?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">hub page</a>.</li>
</ul>
<p>The full rundown is in <a href="https://varaxontech.com/guides/whats-new-in-scan-hub-october-2026?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">What's new in Scan Hub: October 2026</a>.</p>
<h2>Try it free for 14 days</h2>
<p>Every new account gets a <strong>14-day free trial of Core</strong>: 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.</p>
<p><a href="https://scan.varaxontech.com/signup?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">Start the free trial</a> or <a href="https://varaxontech.com/sample-reports?utm_source=hashnode&amp;utm_medium=blog&amp;utm_campaign=free-tools-nov-2026">look at sample reports</a> first.</p>
]]></content:encoded></item><item><title><![CDATA[How to test a vulnerability reporting tool in 14 days]]></title><description><![CDATA[A practical 14-day plan for trialling a vulnerability reporting tool on your own scan data: what to upload, what to check, and what decides it.]]></description><link>https://varaxontech.hashnode.dev/test-a-vulnerability-reporting-tool-in-14-days</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/test-a-vulnerability-reporting-tool-in-14-days</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Wed, 28 Oct 2026 18:27:45 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ad708bd1bcd36d206f5c5a4/5cdb6c3e-e753-420f-9d95-f4886a042ff8.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>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.</p>
<p>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.</p>
<p><strong>Key takeaways</strong></p>
<ul>
<li>Use <strong>your own scan exports</strong>, not the vendor's demo data. Bring at least one messy one.</li>
<li>Check the ranking against <strong>real-world evidence</strong>, not just severity scores.</li>
<li>Send one report to a <strong>real reader</strong> (a client or your manager) and watch what they ask.</li>
<li>Test the <strong>second scan</strong>, not just the first: proving fixes is where most of the value is.</li>
</ul>
<h2>Before you start: pick your test data</h2>
<p>Gather three things:</p>
<ol>
<li><strong>A typical export</strong> from the scanner you run most.</li>
<li><strong>A difficult export</strong>: a large one, one from a second scanner, or one where you know the scanner left CVEs out.</li>
<li><strong>Two scans of the same client</strong>, about a month apart, from the same scanner. You will need these for the proof-of-fix test.</li>
</ol>
<p>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?</p>
<h2>Days 1 to 3: first report</h2>
<p>Upload the typical export and read the report as if you were the client.</p>
<ul>
<li><strong>Did it read everything?</strong> 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.</li>
<li><strong>Is the top of the list right?</strong> 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.</li>
<li><strong>Can you see why?</strong> 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.</li>
<li><strong>Is anything made up?</strong> 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.</li>
</ul>
<h2>Days 4 to 6: the hard export</h2>
<p>Now upload the difficult one. This is where tools separate.</p>
<ul>
<li>Does it handle a <strong>different scanner's</strong> format without you converting anything?</li>
<li>If the export is missing CVEs, does the tool <strong>map the scanner's own check IDs</strong> back to CVEs, or does it just show less?</li>
<li>Does a large file finish in a reasonable time, and does it tell you what it skipped and why?</li>
</ul>
<h2>Days 7 to 9: a real reader</h2>
<p>Send one report to the person who would really receive it, under your own branding if you are an MSP.</p>
<ul>
<li>Do they understand the <strong>first page</strong> without your help?</li>
<li>Do they ask "what should I do first?" If so, the report didn't answer it.</li>
<li>Is the <strong>fix list</strong> something your team can act on: specific steps, per system?</li>
</ul>
<h2>Days 10 to 12: the second scan</h2>
<p>Upload the later scan of the same client. This is the test most trials skip, and it matters most for monthly work.</p>
<ul>
<li>Does the report show what was <strong>fixed</strong>, what <strong>came back</strong> and what is <strong>new</strong> since the last scan?</li>
<li>Is it honest about gaps? If the second scan didn't log in, issues should show as <strong>not rechecked</strong>, not fixed.</li>
<li>Can findings become <strong>tickets</strong> in your PSA, with due dates, without retyping?</li>
<li>Can you record a finding the client <strong>won't fix</strong>, with a reason and an end date?</li>
</ul>
<h2>Days 13 and 14: decide</h2>
<p>Answer four questions in writing:</p>
<ol>
<li>Did it save time compared with how you build reports today? Roughly how much per report?</li>
<li>Would you send its report to a client or auditor without editing it?</li>
<li>Did it get the priorities right on your own data?</li>
<li>What does it cost at the number of reports you produce in a normal month?</li>
</ol>
<p>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.</p>
<h2>Try this plan on Scan Hub</h2>
<p>We built <a href="https://varaxontech.com">Varaxon Scan Hub</a> 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.</p>
<p>Every new account gets a <strong>14-day free trial of Core</strong>: 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 <a href="https://varaxontech.com">pre-flight check</a> needs no account at all. <a href="https://scan.varaxontech.com/signup">Start a free trial</a> or <a href="https://varaxontech.com/sample-reports">see sample reports</a>.</p>
]]></content:encoded></item><item><title><![CDATA[Fixed, accepted or ticketed: close the loop on every vulnerability finding]]></title><description><![CDATA[Every vulnerability finding should end in one of three places: fixed and proven by a rescan, accepted in writing, or ticketed with a due date.]]></description><link>https://varaxontech.hashnode.dev/close-the-loop-on-every-vulnerability-finding</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/close-the-loop-on-every-vulnerability-finding</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Wed, 28 Oct 2026 18:25:32 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ad708bd1bcd36d206f5c5a4/ffae36f9-fa2b-45ce-b1b6-cfdd7e023034.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>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.</p>
<p>The fix is not a better scanner. It is a rule: <strong>every finding has to end somewhere.</strong></p>
<p><strong>Key takeaways</strong></p>
<ul>
<li>Every finding should end in one of three places: <strong>fixed</strong> and proven by a rescan, <strong>accepted</strong> in writing, or <strong>ticketed</strong> with an owner and a due date.</li>
<li>Rank by real-world evidence first (is it being exploited, how likely is it to be), then by severity score.</li>
<li>A fix only counts when a rescan that could actually see the issue no longer finds it.</li>
<li>"Accepted" needs a reason, a compensating control if there is one, and an end date.</li>
</ul>
<h2>Why findings get stuck</h2>
<p>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.</p>
<p>Findings get stuck in four predictable places:</p>
<ol>
<li><strong>Nobody owns them.</strong> The report went to a contact, not to the person who patches.</li>
<li><strong>No date.</strong> "Critical" with no deadline is a mood, not a plan.</li>
<li><strong>Silent refusals.</strong> The client said "we can't take that server down" on a call, and that decision lives nowhere.</li>
<li><strong>No proof.</strong> 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.</li>
</ol>
<h2>The three outcomes</h2>
<h3>1. Fixed, and proven</h3>
<p>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:</p>
<ul>
<li><strong>Same system.</strong> If the host is missing from this scan, you know nothing about it.</li>
<li><strong>Same scanner.</strong> Scanners name and detect issues differently, so comparing two different tools gives you false "fixes".</li>
<li><strong>Same access.</strong> If last month's scan logged in and this month's didn't, issues that need a login were never looked for. Mark them <strong>not rechecked</strong>, not fixed.</li>
</ul>
<p>Write the result down system by system: "OpenSSH fixed on three servers" is proof. "We did some patching" is not.</p>
<h3>2. Accepted, in writing</h3>
<p>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:</p>
<ul>
<li><strong>What</strong> is being accepted, and on which systems.</li>
<li><strong>Why</strong>, in the client's words.</li>
<li><strong>Compensating control</strong>, if there is one (network isolation, extra monitoring).</li>
<li><strong>Who</strong> signed off, and <strong>when the acceptance ends</strong>.</li>
</ul>
<p>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.</p>
<h3>3. Ticketed, with a due date</h3>
<p>Everything else becomes work. Each ticket needs an owner and a due date based on how urgent the finding really is:</p>
<ul>
<li><strong>Known exploited</strong> (on the CISA KEV list): fix first. If KEV gives a due date, use it when it is sooner than your own.</li>
<li><strong>Likely to be exploited</strong> (a high EPSS score): next.</li>
<li><strong>Severity alone</strong>: after that, on your normal schedule.</li>
</ul>
<p>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.</p>
<h2>A monthly loop that works</h2>
<ol>
<li><strong>Scan</strong> with the same scanner and settings as last time. Use a credentialed scan if you can.</li>
<li><strong>Rank</strong> by evidence: KEV, then exploit likelihood, then severity.</li>
<li><strong>Decide</strong> for each new finding: fix (ticket it) or accept (record it).</li>
<li><strong>Rescan</strong> and compare. Close what is proven fixed. Flag what came back.</li>
<li><strong>Report</strong> the three lists to the client: fixed, accepted, in progress, with what is past due.</li>
</ol>
<p>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.</p>
<h2>How we built this into Scan Hub</h2>
<p>We built <a href="https://varaxontech.com">Varaxon Scan Hub</a> 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.</p>
<p>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 <strong>Since the last scan</strong> section. A proof pack rolls months of that into one PDF for audits and renewals.</p>
<p>Every new account gets a <strong>14-day free trial of Core</strong>, with up to 10 reports and no card needed. <a href="https://scan.varaxontech.com/signup">Start a free trial</a> or <a href="https://varaxontech.com/sample-reports">see sample reports</a>.</p>
]]></content:encoded></item><item><title><![CDATA[Turning vulnerability scan results into billable remediation work]]></title><description><![CDATA[A vulnerability scan finds work your contract may not cover. How MSPs can sort findings into covered and billable, and get the client to approve it.]]></description><link>https://varaxontech.hashnode.dev/billable-vulnerability-remediation</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/billable-vulnerability-remediation</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Wed, 28 Oct 2026 18:23:00 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ad708bd1bcd36d206f5c5a4/1392764e-eac4-4bfe-8082-d5294cf71d62.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>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.</p>
<p>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.</p>
<p><strong>Key takeaways</strong></p>
<ul>
<li>Sort every finding into <strong>covered</strong> (your contract already pays for it) or <strong>project</strong> (it needs approval and a quote).</li>
<li>Group project findings by <strong>fix</strong>, not by finding: one upgrade can close forty rows.</li>
<li>Lead the quote with evidence the client understands: "this is being exploited right now", not "CVSS 9.8".</li>
<li>If the client says no, record it as an accepted risk, with an end date.</li>
</ul>
<h2>Step 1: Draw the line your contract already draws</h2>
<p>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:</p>
<ul>
<li>Replacing or upgrading <strong>end-of-life</strong> systems and software, where no patch is coming.</li>
<li><strong>Major version upgrades</strong> of line-of-business apps, especially when the software vendor has to be involved.</li>
<li><strong>Configuration projects</strong>: hardening, TLS changes, firewall rule clean-up, network segmentation.</li>
<li><strong>Hardware</strong> replacement, such as network devices with no firmware fix.</li>
</ul>
<p>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.</p>
<h2>Step 2: Group project findings by fix</h2>
<p>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:</p>
<table>
<thead>
<tr>
<th>Fix</th>
<th>Findings it closes</th>
<th>Why now</th>
</tr>
</thead>
<tbody><tr>
<td>Replace Windows Server 2012 R2 host</td>
<td>38</td>
<td>Extended support ended October 2023</td>
</tr>
<tr>
<td>Upgrade the VPN appliance firmware</td>
<td>6</td>
<td>2 are on the CISA KEV list</td>
</tr>
<tr>
<td>Disable old TLS versions on the web server</td>
<td>4</td>
<td>Fails common insurer questionnaires</td>
</tr>
</tbody></table>
<p>Three lines are something a client can decide on in one meeting. Two hundred rows are not.</p>
<h2>Step 3: Rank by evidence, not by score</h2>
<p>A CVSS score says how bad a flaw <em>could</em> be. It doesn't say whether anyone is using it. For the quote, lead with stronger evidence:</p>
<ul>
<li><strong>On the CISA KEV list.</strong> Attackers are exploiting it right now. This is the easiest conversation you will have.</li>
<li><strong>High EPSS score.</strong> A good chance it gets exploited in the next 30 days.</li>
<li><strong>End of life.</strong> No patch is ever coming, so the risk only grows.</li>
</ul>
<p>"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.</p>
<h2>Step 4: Get a decision, and record it</h2>
<p>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:</p>
<ul>
<li><strong>Approved</strong>: it becomes a ticket with an owner and a due date, and the next scan proves it was done.</li>
<li><strong>Declined</strong>: it becomes an <strong>accepted risk</strong>, with the client's reason, any compensating control and an end date. When the date comes, ask again.</li>
</ul>
<p>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.</p>
<h2>Step 5: Show the work at the next review</h2>
<p>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.</p>
<h2>How Scan Hub helps</h2>
<p>We built <a href="https://varaxontech.com">Varaxon Scan Hub</a> 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.</p>
<p>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.</p>
<p>Every new account gets a <strong>14-day free trial of Core</strong>, with up to 10 reports and no card needed. <a href="https://scan.varaxontech.com/signup">Start a free trial</a> or <a href="https://varaxontech.com/sample-reports">see sample reports</a>.</p>
]]></content:encoded></item><item><title><![CDATA[What's new in Varaxon Scan Hub: October 2026]]></title><description><![CDATA[A free email and domain check, proof of fix, fix deadlines, signed risk acceptance, proof packs, an In progress page and more evidence behind every…]]></description><link>https://varaxontech.hashnode.dev/whats-new-in-scan-hub-october-2026</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/whats-new-in-scan-hub-october-2026</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:47 GMT</pubDate><enclosure url="https://varaxontech.com/covers/whats-new-in-scan-hub-october-2026.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Key takeaways</strong></p>
<ul>
<li><strong>New:</strong> a free email and domain check, graded A to F, for your own domain, your clients and their suppliers.</li>
<li><strong>Reports</strong> now prove what was fixed since the last scan, with deadlines and a past due list behind them.</li>
<li><strong>Proof packs</strong> turn months of that history into evidence for audits, insurers and renewals.</li>
<li>Everything stays evidence-led: code decides the facts, and AI only writes from them.</li>
</ul>
<h2>The short version</h2>
<p>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.</p>
<h2>Free email and domain check</h2>
<p>Can someone send email pretending to be you? The <a href="https://varaxontech.com/email-check">free email check</a> 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.</p>
<p>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. <a href="https://varaxontech.com/guides/free-email-security-check">Read the full guide</a>.</p>
<h2>Proof of fix in every report</h2>
<p>Each report now has a <strong>Since the last scan</strong> 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. <a href="https://varaxontech.com/guides/proof-of-fix-since-the-last-scan">Read the full guide</a>.</p>
<h2>Fix deadlines and signed risk acceptance</h2>
<ul>
<li><strong>Fix deadlines.</strong> 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.</li>
<li><strong>Risk acceptance.</strong> 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.</li>
</ul>
<h2>Proof packs</h2>
<p>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. <a href="https://varaxontech.com/guides/proof-pack-vulnerability-evidence">Read the full guide</a>.</p>
<h2>An In progress page</h2>
<p>After you upload a scan or click Build report, you no longer have to go back to the client's page to find it. <strong>In progress</strong> 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.</p>
<h2>More evidence behind every ranking</h2>
<p>Scan Hub ranks findings by real-world evidence first, not by severity score alone. Each report now shows more of that evidence:</p>
<ul>
<li><strong>CISA KEV</strong> decides the top band, and <strong>EPSS</strong> exploit likelihood moves a finding up and orders findings within each band. See <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev">CVSS vs EPSS vs CISA KEV</a>.</li>
<li><strong>VulnCheck KEV</strong> listings are shown next to CISA's, so a CVE reported as exploited elsewhere is not missed.</li>
<li><strong>End-of-life dates</strong> for common software and operating systems, so the report says when no patch is coming and what to move to.</li>
<li>A <strong>What public threat data adds</strong> section at the top of the report sums up what this evidence changed.</li>
<li>For exports that leave CVEs out, Scan Hub now maps the scanner's own check IDs to CVEs. Our second <a href="https://varaxontech.com/sample-reports">sample report</a> went from no known-exploited matches to <strong>9</strong>.</li>
</ul>
<h2>Already in Scan Hub</h2>
<p>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 <a href="https://varaxontech.com/guides/scan-hub-on-connectwise-and-microsoft-marketplace">Microsoft Marketplace and the ConnectWise® Marketplace</a>.</p>
<p>We built it for MSPs, and just as much for internal IT, compliance and security teams. Your first three reports are free, with no card needed. <a href="https://scan.varaxontech.com/signup">Create an account</a> or <a href="https://varaxontech.com/sample-reports">see sample reports</a>.</p>
<h2>Common questions</h2>
<p><strong>Do the new features cost extra?</strong></p>
<p>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 <a href="https://varaxontech.com/pricing">pricing</a>.</p>
<p><strong>Does AI decide what is fixed or how urgent a finding is?</strong></p>
<p>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.</p>
<hr />
<p><em>Originally published at <a href="https://varaxontech.com/guides/whats-new-in-scan-hub-october-2026">varaxontech.com</a>. Scan Hub is listed on Microsoft Marketplace and the ConnectWise® Marketplace, and it can push fixes into ConnectWise PSA or HaloPSA as tickets.</em></p>
]]></content:encoded></item><item><title><![CDATA[Proof pack: evidence of your vulnerability work for audits, insurers and renewals]]></title><description><![CDATA[Fix deadlines, signed risk acceptances and a proof pack PDF that maps your evidence to CIS, NIST CSF and HIPAA controls and answers common cyber insurance…]]></description><link>https://varaxontech.hashnode.dev/proof-pack-vulnerability-evidence</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/proof-pack-vulnerability-evidence</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[compliance ]]></category><category><![CDATA[MSP]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:46 GMT</pubDate><enclosure url="https://varaxontech.com/covers/proof-pack-vulnerability-evidence.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Key takeaways</strong></p>
<ul>
<li>Every tracked finding now has a <strong>fix deadline</strong>, and a <strong>past due</strong> list shows what is late and by how many days.</li>
<li>When a client won't fix something, they can <strong>accept the risk</strong> by signing online, with a reason and an end date.</li>
<li>A <strong>proof pack</strong> turns 30 to 365 days of that history into a white-label PDF: what was fixed and proven, what is open, what was accepted.</li>
<li>It maps the evidence to common control frameworks and insurance questions, and it never claims a control is met.</li>
</ul>
<h2>The question every report leaves open</h2>
<p>A vulnerability report says what is wrong today. Auditors, cyber insurers and clients at renewal ask something else: "Show me what you did about it." The answer is usually spread across old reports, tickets and email threads, and someone spends a day pulling it together.</p>
<p>We built the <strong>proof pack</strong> to answer that question from records Scan Hub already keeps. It has three parts that work together: fix deadlines, risk acceptance and the pack itself.</p>
<h2>1. Fix deadlines and the past due list</h2>
<p>Each finding Scan Hub tracks gets one due date: its priority band's deadline, counted from when it was first seen, or the CISA KEV due date when that comes sooner.</p>
<ul>
<li>Set deadlines once for your whole organization, and give a client its own when its contract says something different.</li>
<li>Each client's overview shows a <strong>Past due</strong> list with days late, and how many fixes landed on time in the last 90 days.</li>
<li><strong>Fix these first</strong> shows each finding's due date.</li>
<li>A fix counts as on time only when the rescan that proved it ran by the due date. Saying it was patched is not enough.</li>
</ul>
<p>Not sure what deadlines to use? See <a href="https://varaxontech.com/guides/vulnerability-remediation-sla">how to set remediation SLAs</a>.</p>
<h2>2. Risk acceptance with an online signature</h2>
<p>Some findings won't be fixed: a legacy system, a vendor that hasn't shipped a patch, a cost the client won't pay. That is the client's decision, and it should be written down. In Scan Hub an owner or admin records it with a reason, an optional compensating control and an end date no more than 12 months away. Then either:</p>
<ul>
<li><strong>Record an acceptance you already have</strong>, from an email or a meeting, or</li>
<li><strong>Ask the client's contact to sign online.</strong> They get a one-time link that lasts 14 days, read the exact wording, and sign by typing their name, or decline.</li>
</ul>
<p>The wording, the signature and the time are kept together. While an acceptance is in force, the finding stays open (it is never counted as fixed) but it is not past due. You get an email 14 days before it ends, so it is reviewed rather than forgotten. See <a href="https://blog.varaxontech.com/vulnerability-risk-acceptance">how to document risk acceptance</a> for what a good acceptance says.</p>
<h2>3. The proof pack</h2>
<p>Pick a client and a period (the last 30, 90, 180 or 365 days), add a cover note if you like, and Scan Hub builds a white-label PDF from the facts:</p>
<ul>
<li>What was <strong>fixed and proven by a rescan</strong>, on time or late against its deadline.</li>
<li>What is <strong>open</strong>, what is <strong>past due</strong> and what is <strong>accepted</strong>, with how each acceptance was signed.</li>
<li>The tickets sent to your PSA and the scans the pack is based on.</li>
</ul>
<p>Code gathers these facts and freezes them in a facts file. Its SHA-256 is the pack's <strong>fingerprint</strong>, printed in the PDF. You can download the PDF, a CSV of the lists and the facts file itself, so an auditor can recompute the fingerprint and confirm nothing was changed.</p>
<h2>Control map and insurance questions</h2>
<p>A pack can map its evidence to <strong>CIS Controls v8</strong>, <strong>NIST CSF 2.0</strong>, the <strong>HIPAA Security Rule</strong> and <strong>CMMC Level 2</strong>. You choose which. Each row prints the evidence the pack holds for that control, or says plainly that it holds none. No row ever says a control is met: that is the auditor's call, not ours.</p>
<p>You can also tick the questions cyber insurers commonly ask, such as how often you scan, how fast you fix and what is still open. Each answer is the evidence from the pack: scans run, fix deadlines and median days to fix, known-exploited issues, what is past due, accepted risks and tickets.</p>
<blockquote>
<p><strong>Evidence, not certification.</strong> A proof pack is evidence for your own audit, insurance and client work. It does not certify anything or state that a standard, regulation or insurance requirement is met.</p>
</blockquote>
<h2>Where AI fits, and where it doesn't</h2>
<p>AI writes one thing: a short cover summary. It works only from the pack's counts and dates, and every number it writes must point to one of those facts, or the summary is rejected. It is not allowed words like compliant, certified or audit-ready. It never receives the client's name, the reasons for an acceptance or who signed it. If its draft fails the checks twice, the pack uses fixed wording instead. The method page says when AI wrote the summary, and you can turn it off for any pack.</p>
<p>Everything else in the pack comes straight from your records. That is what we mean by evidence-led.</p>
<h2>How to start</h2>
<ol>
<li>Set your fix deadlines in Settings, and a client's own deadlines if they differ.</li>
<li>Keep scanning each client with the same settings, so fixes are proven by a rescan. <a href="https://varaxontech.com/guides/proof-of-fix-since-the-last-scan">Proof of fix</a> shows the changes in every report.</li>
<li>Record risk acceptances as they happen, not the week before the audit.</li>
<li>Make a proof pack for the period the auditor, insurer or client asks about.</li>
</ol>
<p>A proof pack is paid for like a report: from your plan's monthly allowance, then one credit. If a pack fails three times, the credit comes back. Your first three reports are free, with no card needed. <a href="https://scan.varaxontech.com/signup">Create an account</a> or <a href="https://varaxontech.com/pricing">see pricing</a>.</p>
<h2>Common questions</h2>
<p><strong>Does a proof pack make my client compliant?</strong></p>
<p>No. It is evidence of the work done, mapped to controls so an auditor can find it quickly. Whether a control is met is the auditor's or insurer's decision.</p>
<p><strong>What if the client won't sign a risk acceptance online?</strong></p>
<p>Record the acceptance you already have, from an email or meeting notes, and say where it came from. The pack shows how each acceptance was made.</p>
<p><strong>Can someone check the pack wasn't edited?</strong></p>
<p>Yes. Download the facts file and compute its SHA-256. It must match the fingerprint printed in the PDF.</p>
<hr />
<p><em>Originally published at <a href="https://varaxontech.com/guides/proof-pack-vulnerability-evidence">varaxontech.com</a>. Scan Hub is listed on Microsoft Marketplace and the ConnectWise® Marketplace, and it can push fixes into ConnectWise PSA or HaloPSA as tickets.</em></p>
]]></content:encoded></item><item><title><![CDATA[Proof of fix: show clients what you fixed since the last scan]]></title><description><![CDATA[Varaxon Scan Hub reports now list what was fixed, what came back and what is new since the last scan, system by system, so MSPs can prove monthly…]]></description><link>https://varaxontech.hashnode.dev/proof-of-fix-since-the-last-scan</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/proof-of-fix-since-the-last-scan</guid><category><![CDATA[MSP]]></category><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:44 GMT</pubDate><enclosure url="https://varaxontech.com/covers/scan-hub-proof-of-fix.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Every month you patch, rescan and send the client a report. And every month the report shows a long list of what is still wrong, while the work your team did is invisible.</p>
<p><strong>Proof of fix</strong> changes that. Varaxon Scan Hub reports now open with a <strong>Since the last scan</strong> section that names what your team fixed.</p>
<p><strong>Key takeaways</strong></p>
<ul>
<li>Each report compares this scan with the previous scan of the same systems from the same scanner.</li>
<li>It lists every issue that was <strong>fixed</strong>, <strong>came back</strong> or is <strong>new</strong>, with the systems it changed on, most urgent first.</li>
<li>If the rescan did not log in, issues are marked <strong>not rechecked</strong>, never fixed.</li>
<li>It is in the client's PDF and on the report page in the app, at no extra cost.</li>
</ul>
<h2>What the client sees</h2>
<p>At the top of the section are five numbers: fixed, new, reopened, still open and not rechecked. Still-open issues are also split by priority band.</p>
<p>Below that are the lists:</p>
<ul>
<li><strong>Fixed since the last scan.</strong> Each issue by name, with its priority band, a KEV tag if it is on the CISA Known Exploited Vulnerabilities list, and the systems it was fixed on.</li>
<li><strong>Back since the last scan.</strong> Issues that were fixed before and have returned.</li>
<li><strong>New since the last scan.</strong> Issues this scan found for the first time.</li>
</ul>
<p>So instead of "we did some patching", the client reads "Zerologon fixed on dc01, OpenSSH fixed on three servers". That is the conversation you want to have at renewal.</p>
<p>The numbers come straight from comparing the two scans. AI does not write or guess them.</p>
<h2>When it won't mark something fixed</h2>
<p>A wrong "fixed" is worse than no proof at all, so Scan Hub is careful:</p>
<ul>
<li><strong>The rescan didn't log in.</strong> If last month's scan logged in to a system and this month's didn't, issues that need a login to see were not looked for. They show as <strong>not rechecked</strong> and stay open until a logged-in scan checks again.</li>
<li><strong>A different scanner.</strong> Scanners name and check issues differently, so a Nessus scan is never compared with a Qualys scan. The comparison starts with the next scan from the same scanner.</li>
<li><strong>The scanner isn't named.</strong> An export that doesn't say which scanner made it is not compared, and nothing is marked fixed.</li>
<li><strong>A system is missing.</strong> If a system from last time isn't in this scan, its issues are not counted as fixed or still open. Some sources, such as Defender pulls and some CSV exports, list only systems that still have findings, so the report says so.</li>
</ul>
<p>In the app (not in the client's PDF), you also get a note when every issue on a system vanished at once. That is usually good news, but it is also what a scan that never reached the system looks like.</p>
<h2>How to use it each month</h2>
<ol>
<li>Scan the client with the same scanner and settings as last month. Use a logged-in (credentialed) scan if you can.</li>
<li>Upload the export, or let the Defender or ConnectSecure connection build the report.</li>
<li>Send the PDF. The fixed list is your proof of work. The new and reopened lists are next month's plan.</li>
</ol>
<p>Proof of fix works with Nessus, Qualys, Rapid7, Greenbone/OpenVAS, Nuclei, Microsoft Defender and the other scanners Scan Hub reads. Your first three reports are free, with no card needed. <a href="https://scan.varaxontech.com/signup">Try Scan Hub</a> or <a href="https://varaxontech.com/sample-reports">see sample reports</a>.</p>
<p>Scan Hub is listed on Microsoft Marketplace and the ConnectWise® Marketplace, and it can push fixes into ConnectWise PSA as tickets.</p>
]]></content:encoded></item><item><title><![CDATA[Can someone fake your email? A free SPF, DKIM and DMARC check, graded A to F]]></title><description><![CDATA[Check whether anyone can send email pretending to be your domain or your suppliers. Free, no account, graded A to F, with the exact DNS records that raise…]]></description><link>https://varaxontech.hashnode.dev/free-email-security-check</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/free-email-security-check</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[email]]></category><category><![CDATA[dns]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:43 GMT</pubDate><enclosure url="https://varaxontech.com/covers/free-email-security-check.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Key takeaways</strong></p>
<ul>
<li>The <a href="https://varaxontech.com/email-check">free email check</a> tells you in about 20 seconds whether anyone can send email pretending to be your domain.</li>
<li>It reads public records only, grades the domain A to F by fixed rules, and lists only the DNS changes that raise the grade.</li>
<li>It also checks up to three <strong>suppliers</strong> and about 400 <strong>lookalike</strong> names of your domain.</li>
<li>Inside Scan Hub the same check runs for each client, as a white-label PDF that shows the grade <strong>before and after</strong> your fixes.</li>
</ul>
<h2>Why this matters</h2>
<p>Fake invoices and "we've changed our bank details" emails work because many domains still let anyone send mail in their name. Nothing has to be hacked. The scammer just writes your address in the From line, and if your domain doesn't tell mail servers to refuse it, the email lands in the inbox looking real.</p>
<p>Three DNS records decide this: <strong>SPF</strong> (which servers may send for you), <strong>DKIM</strong> (a signature that proves a message really came from you) and <strong>DMARC</strong> (what receivers should do with mail that fails those checks). We built a free check that reads them and tells you, in plain words, whether fake email in your name is stopped.</p>
<h2>What the check looks at</h2>
<ul>
<li><strong>Fake email in your name.</strong> SPF and DMARC: whether mail servers are told to refuse, junk or deliver email that pretends to come from you.</li>
<li><strong>Signed email.</strong> DKIM keys under the names common mail services use, and whether they are long enough.</li>
<li><strong>Encrypted delivery.</strong> MTA-STS and TLS reporting, which make other servers insist on encryption when they send to you.</li>
<li><strong>Domain and DNS.</strong> Registration expiry, the registrar lock, DNSSEC and CAA, from the registry's public record.</li>
<li><strong>Lookalike domains.</strong> About 400 typo and look-alike names of your domain, and which of them are set up to send or receive email.</li>
<li><strong>Your suppliers.</strong> The same spoofing basics for up to three companies you pay, because fake invoices usually pretend to come from one of them.</li>
</ul>
<p>Every answer shows the record it came from, so you can check it yourself.</p>
<h2>How the grade works</h2>
<p>The grade follows fixed rules, so the same records always get the same grade:</p>
<table>
<thead>
<tr>
<th>Grade</th>
<th>What it means</th>
</tr>
</thead>
<tbody><tr>
<td>F</td>
<td>Fake email is not stopped, and SPF is missing or broken.</td>
</tr>
<tr>
<td>D</td>
<td>Fake email is not stopped: no DMARC record, a broken one, or p=none.</td>
</tr>
<tr>
<td>C</td>
<td>Fake email is only partly stopped (for example sent to junk), or something else must be fixed now.</td>
</tr>
<tr>
<td>B</td>
<td>Fake email is refused, with smaller items left to improve.</td>
</tr>
<tr>
<td>A</td>
<td>Fake email is refused and nothing is left to fix.</td>
</tr>
</tbody></table>
<p>Lookalike domains are listed but never change the grade, because they are other people's registrations, not your setup.</p>
<p>Under the grade is <strong>How to raise the grade</strong>: only the steps that change it, in order, each with the exact record to publish. Each item is labelled <strong>Needed for B</strong> (or whichever grade it unlocks) or <strong>Optional</strong>, so you know what to do first and what can wait.</p>
<h2>We ran it on our own domain first</h2>
<p>varaxontech.com got a <strong>D</strong>. Our DMARC record was set to p=none, which only asks for reports and stops nothing. We changed it to p=quarantine, so fakes go to junk, and turned on DKIM signing with our mail provider. The next check gave a <strong>C</strong>, and the before and after report showed exactly what changed.</p>
<p>The last step is p=reject, which tells servers to refuse fakes outright. We are waiting one to two weeks first, reading the DMARC reports to make sure none of our own real email fails the checks. That order (p=none with reports, then quarantine, then reject) is the safe way to roll DMARC out on any domain.</p>
<h2>For your clients: a white-label report with before and after</h2>
<p>If you look after other companies' IT, the same check runs inside <a href="https://scan.varaxontech.com/signup">Scan Hub</a> for each client, at no cost:</p>
<ul>
<li>A <strong>white-label PDF</strong> with your logo, the grade, the steps to raise it and the evidence behind every answer.</li>
<li>A <strong>fingerprint</strong> (SHA-256 of the check's facts) printed on the report, so anyone can confirm the facts were not changed.</li>
<li><strong>Since the last check.</strong> Run it again after the fixes and the report shows the grade, each finding and each supplier before and after. The client sees the work was done.</li>
<li>Supplier checks for the companies your client pays, which makes a good conversation about invoice fraud.</li>
</ul>
<p>It sits next to the client's vulnerability reports, so email security, scan results and <a href="https://varaxontech.com/guides/proof-of-fix-since-the-last-scan">proof of fix</a> are in one place.</p>
<h2>How it's checked, and what it can't see</h2>
<p>Only public records: DNS answers read through Google and Cloudflare DNS-over-HTTPS, the registry's public RDAP record, and your published MTA-STS policy file if there is one. We never connect to your mail servers or send any email. On the public page, results are held in memory for ten minutes and then discarded. Nothing is stored or linked to you.</p>
<ul>
<li>DKIM keys can only be looked for under common names. A key under another name is not visible from outside, so "not found" does not prove DKIM is off.</li>
<li>Lookalike names come from fixed typo and look-alike rules, so some lookalikes may not be in the list.</li>
<li>A DNS change can take up to the record's TTL to show everywhere, so recheck a little later if a fix doesn't appear straight away.</li>
</ul>
<blockquote>
<p><strong>A good grade is not a reason to skip the phone call.</strong> Whatever a supplier's grade, confirm any change of bank details by phone, on a number you already have.</p>
</blockquote>
<h2>Common questions</h2>
<p><strong>Is the email check really free?</strong></p>
<p>Yes. The public check at <a href="https://varaxontech.com/email-check">varaxontech.com/email-check</a> needs no account. Inside Scan Hub, email checks for your clients don't use a report or a credit.</p>
<p><strong>What DMARC policy should I use?</strong></p>
<p>End at p=reject. Start with p=none and a reporting address, read the reports for a week or two to find any real senders that fail, fix them, then move to p=quarantine and finally p=reject.</p>
<p><strong>Does the check send email or log in to anything?</strong></p>
<p>No. It only reads public DNS and registry records and the published MTA-STS policy file. It never connects to a mail server.</p>
<hr />
<p><em>Originally published at <a href="https://varaxontech.com/guides/free-email-security-check">varaxontech.com</a>. Scan Hub is listed on Microsoft Marketplace and the ConnectWise® Marketplace, and it can push fixes into ConnectWise PSA or HaloPSA as tickets.</em></p>
]]></content:encoded></item><item><title><![CDATA[Varaxon Scan Hub is now on the ConnectWise Marketplace and Microsoft Marketplace]]></title><description><![CDATA[Varaxon Scan Hub, evidence-led vulnerability reporting, is now listed on the ConnectWise Marketplace and Microsoft Marketplace. What it connects to and how…]]></description><link>https://varaxontech.hashnode.dev/scan-hub-on-connectwise-and-microsoft-marketplace</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/scan-hub-on-connectwise-and-microsoft-marketplace</guid><category><![CDATA[MSP]]></category><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[ConnectWise]]></category><category><![CDATA[Microsoft]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:41 GMT</pubDate><enclosure url="https://varaxontech.com/covers/scan-hub-on-connectwise-and-microsoft-marketplace.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Varaxon Scan Hub</strong> is now listed on the <strong><a href="https://marketplace.connectwise.com/varaxon-scan-hub">ConnectWise® Marketplace</a></strong> and <strong><a href="https://marketplace.microsoft.com/en-us/product/varaxontechnologies.varaxon-scan-hub?tab=Overview">Microsoft Marketplace</a></strong>.</p>
<p><strong>Key takeaways</strong></p>
<ul>
<li>Scan Hub connects to Microsoft Defender, and after you review a report it pushes the fixes into ConnectWise PSA or HaloPSA as tickets.</li>
<li>It is scanner-agnostic: it also reads exports from the network, host and web vulnerability scanners you already run.</li>
<li>Your first three reports are free, with no card needed.</li>
</ul>
<h2>What Varaxon Scan Hub does</h2>
<p>Varaxon Scan Hub turns vulnerability scan results into client-ready reports for MSPs, MSSPs and security consultants. Upload an export or connect a source. Scan Hub ranks every finding by real-world exploitation and writes a branded report in plain English: what was found, how serious it is and what to fix first.</p>
<p>Each finding is checked against the CISA Known Exploited Vulnerabilities catalog, EPSS exploit likelihood and vendor fixes. Findings are then grouped into the fewest actions that close the most risk. See <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev">how the ranking works</a> or <a href="https://varaxontech.com/sample-reports">browse sample reports</a>.</p>
<h2>Why the ConnectWise and Microsoft marketplaces</h2>
<p>Most MSPs spend their day in two places: Microsoft 365 and Defender for their clients' devices, and a PSA for their service desk. Scan Hub works with both, so we listed it where MSPs already look for tools.</p>
<ul>
<li><strong>Microsoft Defender.</strong> Connect a client's Defender Vulnerability Management, Defender for Endpoint Plan 2, Defender for Servers or Defender for Business (in Microsoft 365 Business Premium), and build a report without exporting anything.</li>
<li><strong>ConnectWise PSA.</strong> After you review a report, Scan Hub opens a ticket for each fix, so remediation lands in the queue your technicians already work from. HaloPSA works the same way.</li>
<li><strong>ConnectSecure.</strong> Connect ConnectSecure with an API key and report on one company or several.</li>
</ul>
<h2>Where to find the listings</h2>
<ul>
<li><strong>ConnectWise Marketplace:</strong> <a href="https://marketplace.connectwise.com/varaxon-scan-hub">Varaxon Scan Hub on the ConnectWise Marketplace</a></li>
<li><strong>Microsoft Marketplace:</strong> <a href="https://marketplace.microsoft.com/en-us/product/varaxontechnologies.varaxon-scan-hub?tab=Overview">Varaxon Scan Hub on Microsoft Marketplace</a>. Use the Contact me button and we reply by email.</li>
</ul>
<p>Plans are bought at scan.varaxontech.com, not through either marketplace.</p>
<h2>It still works with the scanner you already run</h2>
<p>The marketplaces are a new way to find Scan Hub, not a new requirement. You can still upload a CSV, XML or JSON export from the network, host and web vulnerability scanners you already run. There are guides for <a href="https://varaxontech.com/nessus-vulnerability-reports">Nessus reports</a> and <a href="https://varaxontech.com/openvas-vulnerability-reports">OpenVAS reports</a>.</p>
<h2>How to get started</h2>
<ol>
<li>Run the <a href="https://scan.varaxontech.com/scan-summary/page">free pre-flight check</a> on one of your exports. It needs no account and shows what Scan Hub can read.</li>
<li><a href="https://scan.varaxontech.com/signup">Create an account</a>. Your first three reports are free.</li>
<li>Connect Defender, ConnectSecure or your PSA when you're ready, or keep uploading exports.</li>
</ol>
<h2>Common questions</h2>
<p><strong>Is Varaxon Scan Hub on the ConnectWise Marketplace?</strong>
Yes. It is listed as a security reporting integration that creates ConnectWise PSA tickets from reviewed reports.</p>
<p><strong>Is Varaxon Scan Hub on Microsoft Marketplace?</strong>
Yes, as a SaaS app. Use the Contact me button on the listing and we reply by email.</p>
<p><strong>Does Scan Hub work with Microsoft Defender for Business?</strong>
Yes, along with Defender for Endpoint Plan 2, Defender Vulnerability Management and Defender for Servers.</p>
<p><strong>Do I need ConnectWise or Microsoft to use Scan Hub?</strong>
No. You can upload exports from your vulnerability scanner without connecting anything.</p>
<p><strong>How much does it cost?</strong>
Your first three reports are free with no card needed. After that, plans start at $49 a month, or you can pay $9 per report. See <a href="https://varaxontech.com/pricing">pricing</a>.</p>
<hr />
<p><em>Originally published at <a href="https://varaxontech.com/guides/scan-hub-on-connectwise-and-microsoft-marketplace">varaxontech.com</a>. ConnectWise is a registered trademark of ConnectWise, LLC. Microsoft is a trademark of the Microsoft group of companies. A marketplace listing is not an endorsement by either company.</em></p>
]]></content:encoded></item><item><title><![CDATA[A Critical CVE Just Dropped. What MSPs Should Do in the First 48 Hours]]></title><description><![CDATA[A calm, repeatable routine for finding exposure, fixing what matters and telling clients]]></description><link>https://varaxontech.hashnode.dev/first-48-hours-after-a-critical-cve</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/first-48-hours-after-a-critical-cve</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[incident response]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:40 GMT</pubDate><enclosure url="https://varaxontech.com/covers/first-48-hours-after-a-critical-cve.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It happens a few times a year. A vulnerability in a VPN appliance, a firewall, a file-transfer tool or a widely used library gets announced, it's rated critical, and within hours there are reports of attacks. Clients start emailing. Your team wants to know where to start.</p>
<p>The MSPs that handle these well aren't faster typists. They follow the same short routine every time.</p>
<h2>Hour 0 to 4: confirm what you're dealing with</h2>
<p>Before touching anything, answer four questions from reliable sources (the vendor advisory, the CVE record, and CISA if it has commented):</p>
<ol>
<li><strong>What exactly is affected?</strong> Product, versions and configurations. Many critical flaws only apply when a specific feature is turned on.</li>
<li><strong>Is it being exploited?</strong> Check whether it's on CISA's Known Exploited Vulnerabilities catalog, and look at its EPSS score, which estimates how likely exploitation is in the next 30 days.</li>
<li><strong>Is it reachable from the internet?</strong> An internet-facing VPN portal and an internal-only admin console are very different emergencies.</li>
<li><strong>Is there a fix or a workaround?</strong> A patched version, a configuration change, or a vendor mitigation to apply until the patch is out.</li>
</ol>
<p>Write the answers down in a short internal note. It becomes the basis for everything you tell clients.</p>
<h2>Hour 4 to 12: find out who's exposed</h2>
<p>This is where good asset data pays off. Work from what you already have:</p>
<ul>
<li><strong>Your RMM and asset inventory:</strong> search for the product and version across every client</li>
<li><strong>Your latest scan exports:</strong> filter by the product name, CPE or affected port</li>
<li><strong>A targeted rescan:</strong> many scanners publish a check for a high-profile CVE quickly; run it against the likely systems rather than waiting for the monthly scan</li>
<li><strong>External exposure:</strong> check which clients have the affected service open to the internet</li>
</ul>
<p>The output you want is a simple list: client, system, version, internet-facing or not, and whether a fix is available.</p>
<h2>Hour 12 to 24: fix in order of exposure</h2>
<p>Not every affected system needs the same urgency. A sensible order:</p>
<ol>
<li>Internet-facing systems where exploitation has been confirmed</li>
<li>Other internet-facing systems</li>
<li>Internal systems that hold sensitive data or admin access</li>
<li>Everything else, inside the normal patch cycle</li>
</ol>
<p>Where a patch isn't available yet, apply the vendor's mitigation, restrict access to the affected service, or take it offline briefly if the client agrees. For edge devices that were exposed before you patched, check the vendor's guidance on signs of compromise, because patching alone doesn't remove an attacker who is already in.</p>
<h2>Hour 24 to 48: confirm and tell clients</h2>
<p>Patching isn't finished until you've checked it worked. Rescan the affected systems, or verify the version directly, and note the result.</p>
<p>Then send each affected client a short update. Clients who weren't affected appreciate a note too:</p>
<blockquote>
<p>"Yesterday a critical vulnerability was announced in [product]. We checked all of your systems. Two were affected; both were updated last night and we've confirmed the fix. No action is needed from you."</p>
</blockquote>
<p>Three sentences, no jargon, and a clear answer to the only question they have: are we OK?</p>
<h2>Afterwards: keep the lessons</h2>
<p>Once things are quiet, spend twenty minutes on what slowed you down. Usually it's one of three things: an asset that wasn't in the inventory, a client whose scans hadn't run recently, or a device nobody had admin access to. Fix that gap and the next one goes faster.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports, with known exploited vulnerabilities at the top. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=critical-cve-48h&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=critical-cve-48h&amp;utm_content=inline">CVSS vs EPSS vs CISA KEV</a> · <a href="https://varaxontech.com/guides/vulnerability-remediation-sla?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=critical-cve-48h&amp;utm_content=inline">Vulnerability remediation SLAs</a></em></p>
]]></content:encoded></item><item><title><![CDATA[End-of-Life Software in Vulnerability Reports: What to Do When There's No Patch Coming]]></title><description><![CDATA[How to find unsupported systems, explain them to clients and plan their way out]]></description><link>https://varaxontech.hashnode.dev/end-of-life-software-in-vulnerability-reports</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/end-of-life-software-in-vulnerability-reports</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 27 Oct 2026 03:36:13 GMT</pubDate><enclosure url="https://varaxontech.com/covers/end-of-life-software-in-vulnerability-reports.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most findings in a vulnerability report have a fix: install the update, change the setting, restart the service. End-of-life software is different. When a vendor stops supporting a product, new vulnerabilities in it are still discovered, but nobody ships a patch. The finding will be on every report from now on until the system is upgraded, replaced or removed.</p>
<p>That makes end-of-life (EOL) software one of the most important things a report can point out, and one of the easiest to bury in a long list.</p>
<h2>Why EOL deserves its own section</h2>
<p>A missing patch is a task. An unsupported system is a decision. Treating it like one more finding causes three problems:</p>
<ul>
<li><strong>It looks fixable when it isn't.</strong> A ticket that says "patch Windows Server 2012 R2" can't be closed, because there is nothing left to install.</li>
<li><strong>The real risk is understated.</strong> The scanner can only flag vulnerabilities that are already known. On an unsupported product, every new one found from now on stays open for good.</li>
<li><strong>The fix needs budget.</strong> Replacing a server or a line-of-business application is a project, and the client has to approve it. They can only do that if the report says so plainly.</li>
</ul>
<h2>How to spot it in a scan</h2>
<p>Most scanners report unsupported software directly, with findings named along the lines of "Unsupported Version Detection" or "End of Life", often at critical severity. Look for them across:</p>
<ul>
<li><strong>Operating systems:</strong> Windows 10 (mainstream support ended October 14, 2025, with paid Extended Security Updates available for a limited time), Windows Server 2012 and 2012 R2 (ended October 2023), and older Linux releases past their vendor's support window</li>
<li><strong>Server software:</strong> old versions of SQL Server, Exchange, PHP, Apache, OpenSSL and Java runtimes</li>
<li><strong>Network gear:</strong> firewalls, VPN appliances and switches whose firmware line the vendor no longer updates</li>
<li><strong>Applications:</strong> older browsers, PDF readers, and line-of-business software tied to an old runtime</li>
</ul>
<p>Credentialed scans find far more of this than network-only scans, because the installed version is read directly instead of guessed from a banner.</p>
<h2>Explaining it to a client</h2>
<p>Keep it concrete and short:</p>
<blockquote>
<p>"The accounting server runs a version of Windows that Microsoft stopped fixing in 2023. New security problems are still being found in it, and none of them will ever be patched. We recommend moving it to a supported version this quarter."</p>
</blockquote>
<p>Then give them the options, not just the problem:</p>
<table>
<thead>
<tr>
<th>Option</th>
<th>When it fits</th>
<th>What it costs</th>
</tr>
</thead>
<tbody><tr>
<td>Upgrade in place</td>
<td>The application supports a newer OS or version</td>
<td>Licence plus a maintenance window</td>
</tr>
<tr>
<td>Replace</td>
<td>Hardware is old too, or the vendor offers a newer product</td>
<td>Budget and a project plan</td>
</tr>
<tr>
<td>Pay for extended support</td>
<td>A vendor offers it (for example Microsoft ESU) and a short bridge is needed</td>
<td>A yearly fee that usually rises each year</td>
</tr>
<tr>
<td>Isolate and accept</td>
<td>The system can't change yet, such as lab or medical equipment</td>
<td>Network changes plus a documented, dated risk acceptance</td>
</tr>
<tr>
<td>Retire</td>
<td>Nobody actually needs it anymore</td>
<td>Usually the cheapest option of all</td>
</tr>
</tbody></table>
<h2>Track it as a roadmap, not a ticket</h2>
<p>EOL items move on budget cycles, not patch cycles. A short table at the end of each report works well: system, product and version, support end date, chosen option, owner and target date. Add products whose support ends within the next twelve months too, so the client can budget before the date arrives rather than after.</p>
<p>Then report progress the same way each time. "Unsupported systems: 7 last quarter, 4 now, 2 scheduled for replacement in January" is a line a client can follow, and it shows the work moving even when individual findings don't.</p>
<h2>Don't let isolation become permanent</h2>
<p>Isolating an unsupported system is a reasonable bridge. It is not a plan. Give every isolated EOL system a review date, check that the network rules are still in place at each scan, and raise it again if anything changes, such as the system becoming reachable from the internet or one of its vulnerabilities appearing on CISA's Known Exploited Vulnerabilities list.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports with prioritized actions. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=end-of-life&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/credentialed-vs-non-credentialed-scans?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=end-of-life&amp;utm_content=inline">Credentialed vs non-credentialed scans</a> · <a href="https://varaxontech.com/guides/vulnerability-assessment-report-template?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=end-of-life&amp;utm_content=inline">Vulnerability assessment report template</a></em></p>
]]></content:encoded></item><item><title><![CDATA[Your First Vulnerability Scan for a New Client: A Baseline That Sets the Tone]]></title><description><![CDATA[How to scope it, run it and present it so the second meeting is easier than the first]]></description><link>https://varaxontech.hashnode.dev/first-vulnerability-scan-for-a-new-client</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/first-vulnerability-scan-for-a-new-client</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Thu, 22 Oct 2026 00:49:22 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/7f58dd12-a64f-4f04-81ad-380d89cb97c9.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The first scan for a new client is different from every scan after it. There's no previous report to compare against, the asset list is probably incomplete, and the results will almost certainly look worse than anyone expected. Handled well, it becomes the baseline every future report is measured against. Handled badly, it becomes the scary PDF that made the client nervous in week one.</p>
<h2>Before the scan: agree on scope in writing</h2>
<p>A one-page scope note avoids most first-scan surprises. It should cover:</p>
<ul>
<li><strong>What's in:</strong> public IP ranges and hostnames for the external scan; subnets, sites and cloud networks for the internal one</li>
<li><strong>What's out:</strong> anything fragile or owned by someone else, such as medical devices, industrial controls or a landlord's network</li>
<li><strong>When:</strong> a scan window, and who to call if something misbehaves</li>
<li><strong>Credentials:</strong> which accounts the scanner will use, and who created them</li>
<li><strong>Permission:</strong> written sign-off from someone authorized to approve scanning, especially for anything hosted by a third party</li>
</ul>
<p>The sign-off isn't just formality. Scanning systems you aren't authorized to test can breach a hosting contract, and occasionally the law.</p>
<h2>Get credentials working before scan day</h2>
<p>A failed login silently turns a credentialed scan into a network-only scan, and the results look misleadingly clean. Test the scan account on a couple of Windows and Linux hosts first. On scan day, check the scanner's own authentication results before you trust a single number.</p>
<h2>Expect a big number, and say so first</h2>
<p>A first credentialed scan of a network nobody has scanned before routinely produces hundreds or thousands of findings. That doesn't mean the previous IT provider did a terrible job. It usually means nobody was looking.</p>
<p>Tell the client before they see the report:</p>
<blockquote>
<p>"First scans always look worse than later ones, because they include everything that's built up over the years. Most of it comes down to a small number of fixes."</p>
</blockquote>
<p>Setting that expectation turns a shock into a plan.</p>
<h2>Present a baseline, not a verdict</h2>
<p>The first report should do four things:</p>
<ol>
<li><strong>Show what was covered.</strong> Which hosts were scanned, which had working credentials, and anything that couldn't be reached.</li>
<li><strong>Group findings into actions.</strong> Hundreds of findings usually collapse into ten or twenty actions: update a browser everywhere, patch a server, replace an end-of-life machine.</li>
<li><strong>Pick a first wave.</strong> Known exploited vulnerabilities and anything exposed to the internet go first. Agree a short list the client can approve in one meeting.</li>
<li><strong>Record the starting point.</strong> Total findings by severity, number of known exploited issues and number of hosts covered. Those are the numbers future reports compare against.</li>
</ol>
<h2>Fill the gaps the scan reveals</h2>
<p>First scans almost always uncover something about the environment itself:</p>
<ul>
<li>Devices nobody had on the asset list</li>
<li>Systems the scanner couldn't log in to</li>
<li>End-of-life operating systems that can't be patched</li>
<li>Network segments that weren't in scope because nobody knew they existed</li>
</ul>
<p>Put these in the report as findings in their own right. An unknown device is a risk, and a host that couldn't be assessed is a gap, not a pass.</p>
<h2>Plan the second scan now</h2>
<p>The second scan is where the client sees progress. Book it before you leave the first meeting, usually 30 days later, after the first wave of fixes. When the next report shows known exploited issues going from twelve to two, the value of the work explains itself.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports that show coverage and gaps up front. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=first-client-scan&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/credentialed-vs-non-credentialed-scans?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=first-client-scan&amp;utm_content=inline">Credentialed vs non-credentialed scans</a> · <a href="https://varaxontech.com/guides/msp-vulnerability-management-reporting?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=first-client-scan&amp;utm_content=inline">Vulnerability management for MSPs</a></em></p>
]]></content:encoded></item><item><title><![CDATA[Internal vs External Vulnerability Scans: What Each One Tells You]]></title><description><![CDATA[Internal vs external vulnerability scans: what each one finds, the questions it answers, and why every client report should say which view it covers.]]></description><link>https://varaxontech.hashnode.dev/internal-vs-external-vulnerability-scans</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/internal-vs-external-vulnerability-scans</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[networking]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Thu, 22 Oct 2026 00:49:19 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/0efa406d-f4ff-431f-91ae-41b94947418e.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>"We scanned your network" can mean two very different things. An external scan looks at the client from the internet, the way any stranger can. An internal scan looks from inside the office or the cloud network, the way an attacker would after getting a foothold. They find different problems, they answer different questions, and mixing them up in a report leads to bad decisions.</p>
<h2>External scans: the front door</h2>
<p>An external scan runs from outside the client's network against their public IP addresses and hostnames: the firewall, VPN gateway, email server, websites and any cloud services they expose.</p>
<p>It answers: <strong>what can anyone on the internet reach, and is any of it vulnerable?</strong></p>
<p>Typical findings:</p>
<ul>
<li>Remote access services (RDP, SSH, VPN portals) exposed to the internet</li>
<li>Outdated firmware on firewalls and VPN appliances</li>
<li>Weak TLS settings or expired certificates</li>
<li>Admin interfaces that should never be public</li>
<li>Forgotten test servers and old DNS records still pointing at live systems</li>
</ul>
<p>External findings are usually few in number and high in consequence. Edge devices such as VPN appliances and firewalls show up on the CISA Known Exploited Vulnerabilities list again and again, because they are the easiest way in.</p>
<h2>Internal scans: everything behind it</h2>
<p>An internal scan runs from a machine or agent inside the network and looks at workstations, servers, printers, switches and everything else that isn't public.</p>
<p>It answers: <strong>if someone gets in, how far can they go?</strong></p>
<p>Typical findings:</p>
<ul>
<li>Missing operating system and application patches</li>
<li>Outdated browsers, PDF readers and office software</li>
<li>Old protocols still enabled (SMBv1, unsigned SMB, legacy TLS)</li>
<li>Default credentials on printers, cameras and network gear</li>
<li>End-of-life systems nobody has replaced</li>
</ul>
<p>Internal scans produce far more findings, especially when they're credentialed. That is normal: there is much more to look at.</p>
<h2>Side by side</h2>
<table>
<thead>
<tr>
<th></th>
<th>External</th>
<th>Internal</th>
</tr>
</thead>
<tbody><tr>
<td>Runs from</td>
<td>The internet</td>
<td>Inside the network</td>
</tr>
<tr>
<td>Targets</td>
<td>Public IPs, hostnames, web apps</td>
<td>Workstations, servers, network devices</td>
</tr>
<tr>
<td>Main question</td>
<td>What can a stranger reach?</td>
<td>How far could an intruder get?</td>
</tr>
<tr>
<td>Finding volume</td>
<td>Low</td>
<td>High</td>
</tr>
<tr>
<td>Typical priority</td>
<td>Fix fast; often exposed and exploited</td>
<td>Fix by risk; prioritize known exploited issues</td>
</tr>
<tr>
<td>Common requirement</td>
<td>PCI DSS quarterly external scans (by an ASV)</td>
<td>PCI DSS quarterly internal scans, cyber insurance questionnaires</td>
</tr>
</tbody></table>
<h2>Why you usually need both</h2>
<p>An external scan alone tells you the doors are locked but nothing about what's inside. Phishing, a stolen password or a compromised vendor gets an attacker past the edge without touching any of those doors, and then the internal findings decide how bad the day gets.</p>
<p>An internal scan alone misses the most exposed systems entirely, and those are the ones that get hit by automated attacks within days of a new vulnerability being announced.</p>
<p>A sensible baseline for most small and mid-sized clients is an external scan at least monthly and after any firewall or DNS change, and a credentialed internal scan monthly.</p>
<h2>Report them separately</h2>
<p>The most common reporting mistake is merging both scans into one long list. Three critical internal findings on workstations and one critical finding on the VPN gateway are not the same kind of problem, and a merged table makes them look identical.</p>
<p>Better:</p>
<ul>
<li><strong>Separate sections</strong> for external and internal results, each with its own scope statement (which IPs, which subnets, credentialed or not)</li>
<li><strong>External first</strong>, because those findings are reachable by anyone</li>
<li><strong>A clear note when one is missing</strong>: "This report covers the internal network only. No external scan was performed this month."</li>
</ul>
<p>That last line is easy to skip and important to keep. A client who reads "no critical findings" on an internal-only report may reasonably assume their internet-facing systems were checked too.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports with a scope statement up front. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=internal-vs-external&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/how-often-to-run-vulnerability-scans?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=internal-vs-external&amp;utm_content=inline">How often to run vulnerability scans</a> · <a href="https://varaxontech.com/guides/vulnerability-scan-vs-penetration-test?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=internal-vs-external&amp;utm_content=inline">Vulnerability scan vs penetration test</a></em></p>
]]></content:encoded></item><item><title><![CDATA[Risk Acceptance: How to Document a Vulnerability Your Client Won't Fix]]></title><description><![CDATA[How to document a vulnerability your client won't fix: when risk acceptance is the right call, what to write down, who signs it, and when to review it.]]></description><link>https://varaxontech.hashnode.dev/vulnerability-risk-acceptance</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/vulnerability-risk-acceptance</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[compliance ]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Thu, 22 Oct 2026 00:49:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/b6e1d326-6d1d-4e8c-88e2-be3c02f14058.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Sooner or later a client says no. The finance system only runs on an old version of Windows. The vendor won't support the patch. The fix means a weekend of downtime they can't afford this quarter.</p>
<p>That is a legitimate business decision. The problem is what happens next: the finding stays on every report, someone marks it "ignore" in the scanner, and a year later nobody remembers who decided, or why. If that system is ever the way in, "we knew about it" is a hard conversation to have without paperwork.</p>
<p>Risk acceptance is the paperwork. Done well, it takes ten minutes and protects both you and the client.</p>
<h2>When acceptance is the right call</h2>
<p>Acceptance fits when fixing the finding costs more than the risk it removes, and the client understands that trade. Common cases:</p>
<ul>
<li>Legacy systems that a business application depends on</li>
<li>Medical, industrial or lab equipment that the manufacturer must patch</li>
<li>Fixes that need budget or downtime the client has deferred</li>
<li>Findings on systems scheduled for retirement soon</li>
</ul>
<p>It is not the right call when nobody has looked at the finding yet, or when the real reason is that the ticket got lost. That is a backlog, not a decision.</p>
<h2>What a risk acceptance record should include</h2>
<p>Keep it short enough that people actually fill it in:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>What to write</th>
</tr>
</thead>
<tbody><tr>
<td>Finding and systems</td>
<td>The vulnerability, its CVE where there is one, and the exact hosts</td>
</tr>
<tr>
<td>Why it can't be fixed now</td>
<td>One or two sentences in plain language</td>
</tr>
<tr>
<td>What could happen</td>
<td>The realistic consequence, for example "someone on the internal network could take control of the finance server"</td>
</tr>
<tr>
<td>Compensating controls</td>
<td>What reduces the risk in the meantime (see below)</td>
</tr>
<tr>
<td>Decision owner</td>
<td>A named person at the client with authority to accept business risk</td>
</tr>
<tr>
<td>Accepted on / expires on</td>
<td>Dates. Every acceptance should expire</td>
</tr>
<tr>
<td>Review trigger</td>
<td>What reopens it early, such as the finding appearing on the CISA KEV list</td>
</tr>
</tbody></table>
<p>The decision owner matters most. Your technician can recommend, but only the client can accept risk to their business. An owner, practice manager or IT lead signing their name is what makes it a decision instead of a shrug.</p>
<h2>Compensating controls</h2>
<p>Acceptance rarely means "do nothing". It usually means "do something cheaper than the fix":</p>
<ul>
<li>Move the system to its own network segment and limit who can reach it</li>
<li>Block the vulnerable service at the firewall, or allow it only from specific hosts</li>
<li>Turn off the affected feature if the business doesn't use it</li>
<li>Add monitoring or alerting on that host</li>
<li>Restrict which accounts can log in to it</li>
</ul>
<p>Write down which ones are in place. They also give you something to check at the next review.</p>
<h2>Set an expiry, and reopen early when the risk changes</h2>
<p>Six or twelve months is a sensible default. When it expires, ask the same question again: can it be fixed now? Often the answer has changed: a vendor released an update, the budget came through, or the system was finally retired.</p>
<p>Some changes should reopen the decision before the date:</p>
<ul>
<li>The CVE is added to CISA's Known Exploited Vulnerabilities catalog</li>
<li>Its EPSS score jumps, meaning exploitation has become much more likely</li>
<li>The system becomes reachable from the internet</li>
<li>A compensating control is removed</li>
</ul>
<h2>How accepted risks should appear in reports</h2>
<p>Accepted findings should stay visible, just in their own place. A separate "Accepted risks" section, with the owner and expiry date next to each one, keeps the main action list focused on work that will happen, while making it clear nothing has been hidden.</p>
<p>In the summary, one line is enough: "Three findings are accepted risks with compensating controls; the next review is due in March." That sentence tells the client you're tracking it, and it reminds them a decision is theirs to revisit.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports with prioritized actions. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=risk-acceptance&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/vulnerability-remediation-sla?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=risk-acceptance&amp;utm_content=inline">Vulnerability remediation SLAs</a> · <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=risk-acceptance&amp;utm_content=inline">CVSS vs EPSS vs CISA KEV</a></em></p>
]]></content:encoded></item><item><title><![CDATA[False Positives in Vulnerability Scans: How to Verify Them Without Hiding Real Risk]]></title><description><![CDATA[Verify vulnerability scan false positives without hiding real risk: why scanners get it wrong, how to check each finding, and how to record it in reports.]]></description><link>https://varaxontech.hashnode.dev/false-positives-in-vulnerability-scans</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/false-positives-in-vulnerability-scans</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[MSP]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Thu, 22 Oct 2026 00:49:15 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/1201e917-50e9-48a1-9e43-a3fb3daac8b2.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Every scan has a few findings that make you squint. The web server is flagged for an Apache flaw, but the box runs nginx. A Windows patch shows as missing on a machine you updated yesterday. A client forwards the report and asks, "Is this real?"</p>
<p>Some of those findings really are false positives. Some are not, and calling them false positives is how real risk quietly leaves the report. The goal is not to make the list shorter. It is to make every finding on it true.</p>
<h2>Why scanners get it wrong</h2>
<p>Most false positives come from a handful of causes:</p>
<ul>
<li><strong>Version guessing.</strong> Without a login, a scanner reads a service banner and infers the software version. Backported patches (common on Red Hat, Debian and Ubuntu) fix the flaw without changing the version string, so the banner still looks vulnerable.</li>
<li><strong>Leftover files.</strong> An uninstalled program can leave an old DLL or executable behind. A credentialed scan sees the file and reports the old version.</li>
<li><strong>Pending reboots.</strong> The update is installed but not active until the machine restarts. The scanner is right that the old code is still running.</li>
<li><strong>Shared IPs and load balancers.</strong> Two different systems answer on the same address across scans, and findings get attached to the wrong one.</li>
<li><strong>Generic checks.</strong> Some checks test for a behaviour rather than a product, and match systems that behave similarly but are not affected.</li>
</ul>
<p>Notice that two of those (leftover files, pending reboots) are not really false positives. The scanner found something true; it just wasn't what you expected.</p>
<h2>A four-step check</h2>
<p>Run each disputed finding through the same steps, so two technicians reach the same answer.</p>
<ol>
<li><strong>Read the evidence, not the title.</strong> Scanners include the output that triggered the finding: a version string, a file path, a registry key, a response header. Most disputes are settled here.</li>
<li><strong>Confirm on the host.</strong> Check the installed package version, the file on disk or the running service directly. For Linux distributions, look up the vendor's security advisory for that CVE, which tells you which package version contains the fix.</li>
<li><strong>Check the scan type.</strong> If the finding came from a network-only check, a credentialed rescan of that host is often the fastest way to settle it.</li>
<li><strong>Decide one of three outcomes:</strong> confirmed (keep it), false positive (with proof), or true but different (for example, "patched, reboot pending"). The third outcome deserves its own action, not a dismissal.</li>
</ol>
<h2>Record the proof</h2>
<p>A false positive without evidence is just an opinion, and it will come back on the next scan. For each one, keep a short record:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>Example</th>
</tr>
</thead>
<tbody><tr>
<td>Finding</td>
<td>Apache HTTP Server before 2.4.58 (CVE-2023-45802)</td>
</tr>
<tr>
<td>Host</td>
<td>web01 (10.0.4.12)</td>
</tr>
<tr>
<td>Reason</td>
<td>Host runs nginx 1.24; Apache not installed. Banner came from an old reverse-proxy rule.</td>
</tr>
<tr>
<td>Evidence</td>
<td><code>dpkg -l</code> output, screenshot of server headers</td>
</tr>
<tr>
<td>Checked by / date</td>
<td>J. Ortiz, 2026-10-14</td>
</tr>
<tr>
<td>Review again</td>
<td>Next quarterly scan</td>
</tr>
</tbody></table>
<p>That record does three jobs. It saves the next technician from repeating the check, it lets you suppress the finding in future scans with a reason attached, and it gives you something to show an auditor or a client who asks.</p>
<h2>How to show false positives in a client report</h2>
<p>Leaving them out entirely makes the report look tidier, but it also makes it impossible to check. A better pattern:</p>
<ul>
<li>Keep the main findings and actions limited to confirmed items.</li>
<li>Add a short appendix listing findings excluded as false positives, each with a one-line reason.</li>
<li>Mention the count in the summary: "Four findings were reviewed and excluded as false positives; details are in Appendix C."</li>
</ul>
<p>Clients rarely read the appendix. They notice that it exists, and that is what builds trust.</p>
<h2>Watch the trend</h2>
<p>If one check produces false positives on every scan, fix the cause rather than re-verifying it each month. That usually means turning on credentialed scanning for that host group, cleaning up the leftover files, or adjusting the scan policy. A false positive you suppress with a documented reason is fine. A whole class of them you dismiss by habit is how a real finding slips through.</p>
<hr />
<p><em>Varaxon Scan Hub reads exports from the scanners you already use and turns them into clear, client-ready reports that keep the scanner's evidence next to every finding. Your first 3 reports are free, no credit card needed: <a href="https://varaxontech.com/?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=false-positives&amp;utm_content=cta-end">varaxontech.com</a>.</em></p>
<p><em>Related: <a href="https://varaxontech.com/guides/credentialed-vs-non-credentialed-scans?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=false-positives&amp;utm_content=inline">Credentialed vs non-credentialed scans</a> · <a href="https://varaxontech.com/guides/how-to-read-a-nessus-scan-report?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=false-positives&amp;utm_content=inline">How to read a Nessus scan report</a></em></p>
]]></content:encoded></item><item><title><![CDATA[How to turn a vulnerability scan export into a client-ready report]]></title><description><![CDATA[Which file to export from Nessus, Greenbone / OpenVAS, Qualys, Rapid7 and Nuclei, how to check it, and how to turn it into a prioritized report a client…]]></description><link>https://varaxontech.hashnode.dev/turn-scan-export-into-client-report</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/turn-scan-export-into-client-report</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:07:12 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/66ca52a6-2cb8-4f05-bd8b-bee49c3082b3.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The short version:</strong></p>
<ul>
<li>Export the scanner's complete machine-readable format (XML, JSON or full CSV), never its PDF.</li>
<li>Check scope, scan date and credential status before you write a word.</li>
<li>Group findings into remediation actions and rank them by known exploitation first.</li>
<li>Lead the report with decisions; move the raw detail to an appendix.</li>
</ul>
<h2>Step 1: export the right file</h2>
<p>Every scanner offers a polished PDF and a raw data export. The PDF is designed to be read, so it summarizes; fields such as CVE lists, plugin output or detection details are often trimmed. The raw export keeps everything, which is what you need to build a report you can defend.</p>
<p><em>The export to use per scanner</em></p>
<table>
<thead>
<tr>
<th>Scanner</th>
<th>Export to use</th>
<th>Avoid for reporting</th>
</tr>
</thead>
<tbody><tr>
<td>Tenable Nessus</td>
<td><code>.nessus</code> file (XML)</td>
<td>Executive summary PDF or HTML</td>
</tr>
<tr>
<td>Greenbone / OpenVAS</td>
<td>Report downloaded in the XML format, with the filter checked</td>
<td>Classic PDF format (<a href="https://varaxontech.com/guides/openvas-report-missing-cves?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">why</a>)</td>
</tr>
<tr>
<td>Qualys VMDR</td>
<td>Scan results as XML or CSV, or a VMDR CVE / QID data list</td>
<td>PCI and web application reports</td>
</tr>
<tr>
<td>Rapid7 Nexpose / InsightVM</td>
<td>XML Export (version 1.0 or 2.0) report</td>
<td>Document-style PDF reports</td>
</tr>
<tr>
<td>Nuclei</td>
<td>JSON or JSON Lines output</td>
<td>Plain terminal output</td>
</tr>
<tr>
<td>Anything else</td>
<td>The fullest CSV or JSON export the tool offers</td>
<td>Screenshots and PDFs</td>
</tr>
</tbody></table>
<p>Microsoft Defender Vulnerability Management and ConnectSecure have no export file to upload. Connect them to Varaxon Scan Hub directly instead, which keeps the complete record including software inventory. Defender needs Microsoft Defender for Endpoint Plan 2, Defender Vulnerability Management or Defender for Servers.</p>
<h2>Step 2: check what the scan could see</h2>
<p>Before reading findings, confirm the scan's boundary. A report built on a partial scan should say so on the first page.</p>
<ul>
<li><strong>Scope.</strong> Compare the hosts in the export with the client's asset list. A missing server is a gap, not a pass.</li>
<li><strong>Date and feed age.</strong> Record when the scan ran and how current the scanner's checks were.</li>
<li><strong>Credentials.</strong> Note which hosts were scanned with working credentials. A failed login quietly drops a host to a network-only view; see <a href="https://varaxontech.com/guides/credentialed-vs-non-credentialed-scans?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">credentialed vs non-credentialed scans</a>.</li>
<li><strong>Filters.</strong> Some exports apply filters at download time, such as Greenbone's Quality of Detection threshold. Make sure nothing was hidden by accident.</li>
</ul>
<h2>Step 3: group findings into actions</h2>
<p>Clients do not fix findings; they perform actions. Forty Windows findings across twenty laptops usually collapse into one action: apply the current cumulative update. Group by the remediation, then list the affected hosts under it. This turns a 600-row export into a list of 15 or 20 things to do, which is a list a client can actually schedule.</p>
<blockquote>
<p><strong>Keep the evidence attached</strong> When you group, keep each action linked to the scanner evidence behind it: the detected version, the plugin or check output, the CVE list. That is what lets a technician verify the fix and lets you answer the client's "how do you know?"</p>
</blockquote>
<h2>Step 4: put the actions in order</h2>
<p>Rank actions by the strongest evidence of real-world risk first. A defensible order:</p>
<ol>
<li>Anything in the CISA Known Exploited Vulnerabilities (KEV) catalog, with known ransomware use at the very top.</li>
<li>Critical findings (CVSS 9.0 or above) without a KEV match, especially on internet-facing systems.</li>
<li>Other findings with a CVE and meaningful severity, ordered by severity and EPSS.</li>
<li>Findings without a CVE that still matter, such as end-of-life software or weak remote access configuration.</li>
<li>Low and informational items, as context.</li>
</ol>
<p>The reasoning behind this order is in <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">CVSS vs EPSS vs CISA KEV</a>. Varaxon Scan Hub applies exactly these six bands with deterministic code, so two reports from the same export always agree.</p>
<h2>Step 5: write for the person who decides</h2>
<p>The first page is for the business owner or IT manager. Say what was scanned, the three to five actions that matter most, what they protect against and roughly what each involves. Leave raw counts of Highs and Mediums off this page: they alarm without informing.</p>
<p>After the summary come the scope and method, the full prioritized action list with owners and target dates, and a technical appendix with per-host detail. The <a href="https://varaxontech.com/guides/vulnerability-assessment-report-template?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">report template guide</a> lists every section and what goes in it.</p>
<h2>Step 6: hand over the work, then track it</h2>
<p>A report is only useful if the actions become tickets someone closes. Agree target dates with the client (the <a href="https://varaxontech.com/guides/vulnerability-remediation-sla?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">remediation SLA guide</a> has a starting matrix), create the tickets, and compare the next scan against this one so the client sees what was fixed and what is still open.</p>
<p>Varaxon Scan Hub covers steps 2 to 6 from the uploaded export: it checks coverage, groups and ranks the actions, writes the report, creates reviewed HaloPSA or ConnectWise PSA tickets and tracks each client between scans. <a href="https://varaxontech.com/sample-reports?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">See the sample reports</a>, or try it on your own export with the free pre-flight check.</p>
<h2>Common questions</h2>
<p><strong>Should I send the scanner's own PDF report to a client?</strong></p>
<p>It is better as an appendix than as the report. Scanner PDFs are organized by finding and host, not by the actions the client needs to take, and some omit fields the raw export contains.</p>
<p><strong>How long should a vulnerability report for a small business be?</strong></p>
<p>Keep the decision part to one or two pages: a summary and the prioritized action list. The technical appendix can be as long as the scan requires, because only technicians read it.</p>
<hr />
<p><em>This guide first appeared on <a href="https://varaxontech.com/guides/turn-scan-export-into-client-report">varaxontech.com</a>.</em></p>
<p>I'm building <a href="https://varaxontech.com?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=turn-scan-export-into-client-report">Varaxon Scan Hub</a>. It turns exports from Nessus, Greenbone/OpenVAS, Qualys, Rapid7, Nuclei, Burp, Defender and other network, host and web scanners into clear, client-ready reports, and can open HaloPSA or ConnectWise tickets after you review them. Your first three reports are free, and a free pre-flight check shows what it can read from your export first.</p>
<p>— Brandon Sooknanan<br />Founder, Varaxon Technologies</p>
]]></content:encoded></item><item><title><![CDATA[Why your OpenVAS PDF report is missing CVEs (and how to fix it)]]></title><description><![CDATA[Greenbone / OpenVAS PDF reports often drop CVE details or whole results. Here is why it happens, how QoD filters hide findings, and which export to use…]]></description><link>https://varaxontech.hashnode.dev/openvas-report-missing-cves</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/openvas-report-missing-cves</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><category><![CDATA[#openvas]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:07:11 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/7d8e9859-f4ca-4820-9890-7f462056b72f.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The short version:</strong></p>
<ul>
<li>The classic Greenbone PDF format summarizes results and can leave out CVE details that XML and CSV include.</li>
<li>The report filter, especially Quality of Detection (QoD), decides which results appear at all.</li>
<li>Export the XML report for anything you will hand to a client or process with a tool.</li>
<li>Many Greenbone checks have no CVE at all; that is Unknown, not clean.</li>
</ul>
<h2>The symptom</h2>
<p>You run a scan in Greenbone Community Edition or a Greenbone appliance, download the PDF, and the report shows hosts and result summaries but few or no CVE identifiers. Sometimes the totals at the top count critical results that never appear in the tables below. Both problems come up repeatedly on the Greenbone community forum, and both have ordinary causes.</p>
<h2>Cause 1: the PDF format leaves details out</h2>
<p>Greenbone generates reports through report formats. The long-standing PDF format is built for a human-readable summary and is not where Greenbone puts its maintenance effort; forum maintainers have confirmed that it can omit CVE details the other formats include. The XML, CSV and TXT formats carry the full reference list for each result.</p>
<blockquote>
<p><strong>Fix</strong> Download the report as <strong>XML</strong>. It is Greenbone's native format and holds every field: the NVT OID, severity, QoD, references (CVE, CERT-Bund, DFN-CERT), detection details and the solution. Use the PDF only as a quick visual check.</p>
</blockquote>
<h2>Cause 2: the report filter hides results</h2>
<p>Every Greenbone report is generated through a results filter. The default filter typically includes <code>min_qod=70</code>, which hides results whose Quality of Detection is below 70 percent. QoD expresses how reliable the detection method is: a remote banner check scores lower than an authenticated package check. Filters can also apply severity thresholds, a row limit (<code>rows=</code>) or hide overridden results.</p>
<ul>
<li>Open the report in the web interface and look at the filter string before downloading.</li>
<li>Lower or remove <code>min_qod</code> if you need the complete picture, then label low-QoD results as lower-confidence in your report.</li>
<li>Remove the row limit so large reports are not truncated.</li>
<li>Check whether overrides or false-positive markings changed severities.</li>
</ul>
<h2>Cause 3: the check has no CVE</h2>
<p>Many Greenbone NVTs test for things that never received a CVE: deprecated TLS versions, weak SSH algorithms, default credentials, end-of-life operating systems, exposed services. Those results are real findings with an OID and a severity but an empty CVE list. A report that counts only CVE-backed findings will under-report them.</p>
<p>Varaxon Scan Hub reports CVE-based assessment for those findings as <strong>Unknown</strong> rather than zero, and can optionally map Greenbone OIDs to CVEs on the server where a reliable mapping exists. Either way the gap stays visible.</p>
<h2>A checklist before you send a Greenbone report</h2>
<ol>
<li>Confirm the scan used credentials for the hosts where you expect local checks.</li>
<li>Check the filter: QoD threshold, severity threshold, row limit, overrides.</li>
<li>Download the XML report.</li>
<li>Compare the result count in the XML with the count shown in the web interface.</li>
<li>State in the report which results have no CVE and how they were prioritized.</li>
</ol>
<p>Upload the XML to Varaxon Scan Hub to get a prioritized, client-ready report from it. The <a href="https://varaxontech.com/openvas-vulnerability-reports?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=openvas-report-missing-cves">Greenbone / OpenVAS page</a> and its sample report show the result.</p>
<h2>Common questions</h2>
<p><strong>What does QoD mean in OpenVAS?</strong></p>
<p>QoD, Quality of Detection, is a percentage expressing how reliable a detection method is. Authenticated package checks score high; remote banner checks score lower. Report filters often hide results below a QoD of 70.</p>
<p><strong>Which OpenVAS report format includes CVEs?</strong></p>
<p>The XML report format includes every result with its full reference list, including CVEs. CSV and TXT also include CVE references. The classic PDF format can omit them.</p>
<hr />
<p><em>This guide first appeared on <a href="https://varaxontech.com/guides/openvas-report-missing-cves">varaxontech.com</a>.</em></p>
<p>I'm building <a href="https://varaxontech.com?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=openvas-report-missing-cves">Varaxon Scan Hub</a>. It turns exports from Nessus, Greenbone/OpenVAS, Qualys, Rapid7, Nuclei, Burp, Defender and other network, host and web scanners into clear, client-ready reports, and can open HaloPSA or ConnectWise tickets after you review them. Your first three reports are free, and a free pre-flight check shows what it can read from your export first.</p>
<p>— Brandon Sooknanan<br />Founder, Varaxon Technologies</p>
]]></content:encoded></item><item><title><![CDATA[Vulnerability remediation timelines: how to set SLAs for clients]]></title><description><![CDATA[How fast should Critical, High and Medium vulnerabilities be fixed? Common remediation timelines, what frameworks require, and a starting SLA matrix MSPs…]]></description><link>https://varaxontech.hashnode.dev/vulnerability-remediation-sla</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/vulnerability-remediation-sla</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:07:11 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/31bd9feb-1bb5-4205-80bc-c15dc53996fd.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The short version:</strong></p>
<ul>
<li>There is no universal deadline; the client's policy, contract or framework sets it.</li>
<li>Base SLAs on exploitation and exposure, not severity alone.</li>
<li>A common starting point: known exploited and internet-facing within days, Critical 14 days, High 30, Medium 90.</li>
<li>Track the age of open findings so missed SLAs are visible before the next review.</li>
</ul>
<h2>Why remediation SLAs matter</h2>
<p>A scan without a deadline produces a report that ages on a shelf. Remediation service level agreements turn findings into commitments: who fixes what, by when. For an MSP they also define the scope of the service and protect both sides when something is exploited later.</p>
<h2>Common timelines</h2>
<p>Organizations set their own numbers, but published policies cluster around similar values. US federal agencies must fix vulnerabilities in the CISA KEV catalog by the due date CISA sets (Binding Operational Directive 22-01), commonly two to three weeks for newly added entries. Many security teams aim for 7 to 14 days on Critical, about 30 days on High, 60 to 90 days on Medium and the next maintenance cycle for Low.</p>
<p><em>A starting SLA matrix to adapt per client</em></p>
<table>
<thead>
<tr>
<th>Priority</th>
<th>Internet-facing or critical system</th>
<th>Internal system</th>
</tr>
</thead>
<tbody><tr>
<td>Known exploited (CISA KEV), especially with ransomware use</td>
<td>72 hours</td>
<td>14 days</td>
</tr>
<tr>
<td>Critical (CVSS 9.0 or above)</td>
<td>7 days</td>
<td>14 to 30 days</td>
</tr>
<tr>
<td>High (CVSS 7.0 to 8.9)</td>
<td>14 days</td>
<td>30 days</td>
</tr>
<tr>
<td>Medium (CVSS 4.0 to 6.9)</td>
<td>30 days</td>
<td>90 days</td>
</tr>
<tr>
<td>Low and informational</td>
<td>Next maintenance cycle</td>
<td>Next maintenance cycle</td>
</tr>
</tbody></table>
<blockquote>
<p>These are a starting point for a conversation, not a standard. Agree them with each client in writing, and check any contractual or regulatory requirement first.</p>
</blockquote>
<h2>What frameworks say</h2>
<ul>
<li><strong>PCI DSS v4:</strong> critical security patches must be installed within one month of release (requirement 6.3.3), and internal scans must show high-risk and critical vulnerabilities resolved.</li>
<li><strong>CISA BOD 22-01:</strong> mandatory for US federal civilian agencies; widely used by everyone else as a benchmark for known exploited vulnerabilities.</li>
<li><strong>CIS Controls v8:</strong> Control 7 calls for a documented remediation process and risk-based remediation on a monthly or more frequent basis.</li>
<li><strong>HIPAA, SOC 2, ISO 27001:</strong> require a risk-based process and evidence that it is followed, rather than fixed day counts.</li>
</ul>
<h2>Handling exceptions</h2>
<p>Some findings cannot be fixed in time: a legacy system the vendor no longer supports, a line-of-business application that breaks on the new version. Treat these as risk acceptances, not silent misses. Record the finding, the reason, any compensating control (isolation, restricted access, monitoring), who accepted the risk and a review date.</p>
<h2>Tracking SLAs between scans</h2>
<p>An SLA is only real if someone can see it being missed. Compare each scan with the previous one per client: what is new, what was fixed and how long each open finding has been open. Bring overdue items to the next client review with a reason.</p>
<p>Varaxon Scan Hub keeps reports per client and tracks the age of open findings between scans, so overdue known exploited vulnerabilities stand out. Remediation actions become HaloPSA or ConnectWise PSA tickets once you review and approve them. The <a href="https://varaxontech.com/guides/cvss-vs-epss-vs-cisa-kev?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=vulnerability-remediation-sla">priority bands</a> map directly onto the matrix above.</p>
<h2>Common questions</h2>
<p><strong>What is a reasonable SLA for critical vulnerabilities?</strong></p>
<p>Between 7 and 30 days is common, shortened to days when the vulnerability is in the CISA KEV catalog or the system is reachable from the internet.</p>
<p><strong>Who should own remediation, the MSP or the client?</strong></p>
<p>Whoever controls the system. MSPs usually own patching on managed endpoints and servers, while line-of-business applications and vendor-managed systems need a named client or vendor owner in the report.</p>
<hr />
<p><em>This guide first appeared on <a href="https://varaxontech.com/guides/vulnerability-remediation-sla">varaxontech.com</a>.</em></p>
<p>I'm building <a href="https://varaxontech.com?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=vulnerability-remediation-sla">Varaxon Scan Hub</a>. It turns exports from Nessus, Greenbone/OpenVAS, Qualys, Rapid7, Nuclei, Burp, Defender and other network, host and web scanners into clear, client-ready reports, and can open HaloPSA or ConnectWise tickets after you review them. Your first three reports are free, and a free pre-flight check shows what it can read from your export first.</p>
<p>— Brandon Sooknanan<br />Founder, Varaxon Technologies</p>
]]></content:encoded></item><item><title><![CDATA[Vulnerability scan vs penetration test: what's the difference?]]></title><description><![CDATA[A vulnerability scan finds known weaknesses automatically; a penetration test proves what an attacker could do with them. When clients need each, and how…]]></description><link>https://varaxontech.hashnode.dev/vulnerability-scan-vs-penetration-test</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/vulnerability-scan-vs-penetration-test</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:07:11 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/9197ee98-af03-460b-a742-0670efba9c91.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The short version:</strong></p>
<ul>
<li>A scan is automated, broad and frequent; a penetration test is manual, deep and periodic.</li>
<li>Scans answer "what known weaknesses exist?"; tests answer "what could an attacker actually achieve?"</li>
<li>Most clients need regular scanning all year and a penetration test annually or after major change.</li>
</ul>
<h2>Two different questions</h2>
<p>A <strong>vulnerability scan</strong> uses an automated tool such as Nessus, Greenbone / OpenVAS, Qualys or Rapid7 to check systems against a database of known vulnerabilities and misconfigurations. It is broad, repeatable and cheap enough to run every month.</p>
<p>A <strong>penetration test</strong> is a time-boxed engagement in which a skilled tester tries to break in, chaining weaknesses together the way a real attacker would, and documents what they reached. It is deep, creative and expensive enough that most organizations do it once a year or after a major change.</p>
<h2>Side by side</h2>
<p><em>Vulnerability scan compared with a penetration test</em></p>
<table>
<thead>
<tr>
<th></th>
<th>Vulnerability scan</th>
<th>Penetration test</th>
</tr>
</thead>
<tbody><tr>
<td>Performed by</td>
<td>Automated tool, configured by a technician</td>
<td>Skilled human tester</td>
</tr>
<tr>
<td>Typical frequency</td>
<td>Monthly or more</td>
<td>Annually or after major change</td>
</tr>
<tr>
<td>Coverage</td>
<td>Every host in scope</td>
<td>Chosen targets and attack paths</td>
</tr>
<tr>
<td>Finds</td>
<td>Known vulnerabilities and misconfigurations</td>
<td>Exploitable paths, business logic flaws, chained weaknesses</td>
</tr>
<tr>
<td>Proves exploitation</td>
<td>No</td>
<td>Yes, within the agreed rules of engagement</td>
</tr>
<tr>
<td>Output</td>
<td>List of findings to remediate</td>
<td>Narrative of what was achieved, with findings</td>
</tr>
</tbody></table>
<h2>Which does a client need?</h2>
<ul>
<li><strong>Ongoing hygiene:</strong> regular vulnerability scanning with remediation tracking. This is the core of a managed security service.</li>
<li><strong>Compliance:</strong> PCI DSS requires both quarterly scans and an annual penetration test; many other frameworks and customers ask for a penetration test periodically.</li>
<li><strong>Before a big change or after an incident:</strong> a penetration test of the affected environment.</li>
<li><strong>Cyber insurance:</strong> applications commonly ask about scanning and patching; some ask about penetration testing for larger policies.</li>
</ul>
<blockquote>
<p>A penetration test on an environment that is not scanned and patched regularly mostly finds the missing patches a scan would have found. Do the scanning first; the test is then worth more.</p>
</blockquote>
<h2>Explaining it to a client</h2>
<p>An analogy that works: a vulnerability scan is checking every door and window in the building to see which are unlocked. A penetration test is hiring someone to try to get to the safe. You want the first done every month and the second once a year.</p>
<p>Varaxon Scan Hub is a reporting tool for the first: it turns the scanner's export into a prioritized, plain-language remediation report. It does not perform penetration tests or claim an environment is secure. See <a href="https://varaxontech.com/guides/vulnerability-assessment-report-template?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=vulnerability-scan-vs-penetration-test">what a vulnerability assessment report should include</a>.</p>
<h2>Common questions</h2>
<p><strong>Can a vulnerability scan replace a penetration test for PCI DSS?</strong></p>
<p>No. PCI DSS v4 requires both: vulnerability scans at least every three months (requirement 11.3) and penetration testing at least once every twelve months and after significant changes (requirement 11.4).</p>
<p><strong>Is a vulnerability assessment the same as a vulnerability scan?</strong></p>
<p>The terms are often used interchangeably. Strictly, the scan is the automated check, and the assessment includes reviewing the results, prioritizing them and recommending fixes, which is what the report delivers.</p>
<hr />
<p><em>This guide first appeared on <a href="https://varaxontech.com/guides/vulnerability-scan-vs-penetration-test">varaxontech.com</a>.</em></p>
<p>I'm building <a href="https://varaxontech.com?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=vulnerability-scan-vs-penetration-test">Varaxon Scan Hub</a>. It turns exports from Nessus, Greenbone/OpenVAS, Qualys, Rapid7, Nuclei, Burp, Defender and other network, host and web scanners into clear, client-ready reports, and can open HaloPSA or ConnectWise tickets after you review them. Your first three reports are free, and a free pre-flight check shows what it can read from your export first.</p>
<p>— Brandon Sooknanan<br />Founder, Varaxon Technologies</p>
]]></content:encoded></item><item><title><![CDATA[How often should you run vulnerability scans? PCI DSS, HIPAA, CIS and insurance]]></title><description><![CDATA[Quarterly is the compliance floor, monthly is the practical baseline. What PCI DSS, HIPAA, CIS Controls and cyber insurers expect, and how to set a scan…]]></description><link>https://varaxontech.hashnode.dev/how-often-to-run-vulnerability-scans</link><guid isPermaLink="true">https://varaxontech.hashnode.dev/how-often-to-run-vulnerability-scans</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[Security]]></category><category><![CDATA[Vulnerability management]]></category><category><![CDATA[MSP]]></category><category><![CDATA[sysadmin]]></category><dc:creator><![CDATA[Brandon Sooknanan]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:07:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/gql/6ad708bd1bcd36d206f5c5a4/70b5c8b2-68df-4cb6-876d-6320d6745e86.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The short version:</strong></p>
<ul>
<li>PCI DSS requires internal and external scans at least every three months and after significant changes.</li>
<li>HIPAA does not set a frequency today, but regular scanning supports the required risk analysis.</li>
<li>Monthly authenticated scanning is a sensible baseline for most small and mid-sized clients.</li>
<li>Scan internet-facing systems more often than internal ones.</li>
</ul>
<h2>The short answer</h2>
<p>At least quarterly to meet most compliance requirements, monthly as a practical baseline, and continuously or weekly for internet-facing systems where you can. Then scan again after any significant change, such as a new firewall, a new server or a major upgrade.</p>
<h2>PCI DSS</h2>
<ul>
<li><strong>Internal scans</strong> at least once every three months and after significant change (requirement 11.3.1), performed with authentication (11.3.1.2), with high-risk and critical vulnerabilities resolved and rescanned.</li>
<li><strong>External scans</strong> at least once every three months by a PCI SSC Approved Scanning Vendor (ASV), with a passing result (11.3.2), plus scans after significant change.</li>
</ul>
<p>ASV scans are a specific service with their own attestation; a general vulnerability report is not a substitute for one.</p>
<h2>HIPAA</h2>
<p>The HIPAA Security Rule requires covered entities and business associates to perform an accurate and thorough risk analysis and to implement reasonable safeguards, but it does not name a scan frequency. Regular vulnerability scanning is the standard way to support that risk analysis with evidence. Proposed updates to the Security Rule published in early 2025 would add explicit vulnerability scanning and penetration testing requirements; check the status of that rulemaking for your clients.</p>
<h2>CIS Controls and other frameworks</h2>
<ul>
<li><strong>CIS Controls v8, Control 7:</strong> automated authenticated and unauthenticated scans of internal assets at least quarterly (7.5), externally exposed assets at least monthly (7.6), and risk-based remediation at least monthly (7.7).</li>
<li><strong>SOC 2 and ISO 27001:</strong> no fixed interval, but auditors expect a defined cadence that you can show was followed.</li>
<li><strong>Cyber Essentials (UK):</strong> focuses on patching within 14 days for high and critical updates rather than a scan schedule.</li>
</ul>
<h2>Cyber insurance</h2>
<p>Underwriting questionnaires increasingly ask whether you scan regularly, whether internet-facing systems are covered and how quickly critical vulnerabilities are patched. Requirements vary by insurer and policy, so read the client's application. The most useful evidence is a dated history of reports showing findings being fixed.</p>
<h2>Setting a cadence per client</h2>
<p><em>A practical starting cadence</em></p>
<table>
<thead>
<tr>
<th>Client profile</th>
<th>Internal (credentialed)</th>
<th>External</th>
</tr>
</thead>
<tbody><tr>
<td>Small office, no regulated data</td>
<td>Monthly</td>
<td>Monthly</td>
</tr>
<tr>
<td>Takes card payments</td>
<td>Monthly, plus quarterly evidence</td>
<td>Quarterly ASV, plus monthly own scans</td>
</tr>
<tr>
<td>Healthcare or other regulated data</td>
<td>Monthly</td>
<td>Weekly to monthly</td>
</tr>
<tr>
<td>Public-facing applications or many remote users</td>
<td>Monthly</td>
<td>Weekly or continuous</td>
</tr>
</tbody></table>
<p>A higher cadence is only useful if the reports get read. Match scan frequency to how often the client can act, and use <a href="https://varaxontech.com/guides/vulnerability-remediation-sla?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=how-often-to-run-vulnerability-scans">remediation SLAs</a> to keep the two in step. Varaxon Scan Hub keeps every report per client, so a monthly cadence builds the dated evidence trail auditors and insurers ask for.</p>
<h2>Common questions</h2>
<p><strong>Is an annual vulnerability scan enough?</strong></p>
<p>Rarely. New vulnerabilities are published every day and many are exploited within weeks. Annual scanning leaves most of the year unmeasured and does not meet PCI DSS or CIS Controls expectations.</p>
<p><strong>Should I rescan after patching?</strong></p>
<p>Yes. A rescan confirms the fix worked and gives you evidence that the finding was resolved, which PCI DSS explicitly requires for high-risk and critical internal findings.</p>
<hr />
<p><em>This guide first appeared on <a href="https://varaxontech.com/guides/how-often-to-run-vulnerability-scans">varaxontech.com</a>.</em></p>
<p>I'm building <a href="https://varaxontech.com?utm_source=hashnode-blog&amp;utm_medium=referral&amp;utm_campaign=how-often-to-run-vulnerability-scans">Varaxon Scan Hub</a>. It turns exports from Nessus, Greenbone/OpenVAS, Qualys, Rapid7, Nuclei, Burp, Defender and other network, host and web scanners into clear, client-ready reports, and can open HaloPSA or ConnectWise tickets after you review them. Your first three reports are free, and a free pre-flight check shows what it can read from your export first.</p>
<p>— Brandon Sooknanan<br />Founder, Varaxon Technologies</p>
]]></content:encoded></item></channel></rss>