<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CyberSpec</title>
    <description>The latest articles on DEV Community by CyberSpec (@cyberspec).</description>
    <link>https://dev.to/cyberspec</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257225%2F6d085f24-4767-403d-9d80-01481d0d62ae.png</url>
      <title>DEV Community: CyberSpec</title>
      <link>https://dev.to/cyberspec</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cyberspec"/>
    <language>en</language>
    <item>
      <title>Why my vulnerability scanner says "likely fail" but never "pass"</title>
      <dc:creator>CyberSpec</dc:creator>
      <pubDate>Sat, 21 Nov 2026 11:27:10 +0000</pubDate>
      <link>https://dev.to/cyberspec/why-my-vulnerability-scanner-says-likely-fail-but-never-pass-36oi</link>
      <guid>https://dev.to/cyberspec/why-my-vulnerability-scanner-says-likely-fail-but-never-pass-36oi</guid>
      <description>&lt;p&gt;I build a small external vulnerability scanner aimed at UK firms preparing for &lt;strong&gt;Cyber Essentials&lt;/strong&gt; (CE), the government-backed baseline certification. The most important design decision in the product was one word I refused to ship: &lt;strong&gt;"pass"&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;Cyber Essentials has five technical controls. When I mapped them against what a scanner sitting &lt;em&gt;outside&lt;/em&gt; your network can actually observe, I got this:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Control&lt;/th&gt;
&lt;th&gt;Visible from outside?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Firewalls / internet gateways&lt;/td&gt;
&lt;td&gt;Mostly: which services are reachable at all&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Secure configuration&lt;/td&gt;
&lt;td&gt;Mostly: exposed admin panels, unnecessary services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security update management&lt;/td&gt;
&lt;td&gt;Mostly: known-vulnerable and end-of-life versions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;User access control&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Malware protection&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Three out of five, roughly. The temptation is to show a green tick on the three you can see. That would be wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a scan can fail you but never pass you
&lt;/h2&gt;

&lt;p&gt;An external scan can find a &lt;strong&gt;reason to fail&lt;/strong&gt;. Under the NCSC's CE Plus test spec, a reachable service with a vulnerability scoring CVSS 7.0 or higher fails the external test outright. If my scanner sees one, that's a real, evidence-backed "this will likely fail".&lt;/p&gt;

&lt;p&gt;But "no issues found" is not "pass". Plenty of things that matter are invisible from outside:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;default passwords that were never changed&lt;/li&gt;
&lt;li&gt;whether logins lock out after repeated failures&lt;/li&gt;
&lt;li&gt;patching on internal machines&lt;/li&gt;
&lt;li&gt;whether that exposed admin panel has MFA in front of it&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the readiness states in the product are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;likely fail&lt;/strong&gt;: evidence of a fail condition&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;review&lt;/strong&gt;: an exposure a human has to justify (e.g. a reachable admin interface needs a documented business need plus MFA or an IP allow list; the scan can see the panel, never the documentation)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;no issues found&lt;/strong&gt;: we looked and found nothing, which is narrower than "fine"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;no scan yet&lt;/strong&gt;: different from "no issues found", and worth keeping separate&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The two controls a scan can't see at all are &lt;strong&gt;customer-attested&lt;/strong&gt;: the user records a statement, versioned against the scheme version, and the UI never pretends it measured anything.&lt;/p&gt;

&lt;p&gt;Simplified, the patching rule looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="nc"&gt;Status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"likely_fail"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"review"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"no_issues_found"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"no_scan_yet"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;updateManagementStatus&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;findings&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Finding&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;hasScan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;boolean&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Status&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;hasScan&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"no_scan_yet"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;failing&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;findings&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;open&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;checkType&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s2"&gt;"eol"&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cve&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cvss&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mf"&gt;7.0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;failing&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="s2"&gt;"likely_fail"&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"no_issues_found"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Note what's missing: there is no branch that returns &lt;code&gt;"pass"&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A rule people mix up
&lt;/h2&gt;

&lt;p&gt;"CVSS 7+ with a fix available for more than 14 days" is often quoted as &lt;em&gt;the&lt;/em&gt; CE patching rule. In the CE Plus test spec, that specific check is sub-test 2.1, the authenticated scan of &lt;strong&gt;sampled devices&lt;/strong&gt;, not the external scan. If you're building tooling against a compliance scheme, read the primary documents (NCSC publishes them as PDFs) and not vendor blog summaries. I got one claim wrong from general knowledge before checking them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway for anyone building compliance tooling
&lt;/h2&gt;

&lt;p&gt;Your product's vocabulary is a promise. A customer who sees "pass" will act on it, and then fail an audit. Listing what you &lt;em&gt;couldn't&lt;/em&gt; check honestly is a feature, not an apology for a missing one.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I'm the founder of &lt;a href="https://cyberspec.pro" rel="noopener noreferrer"&gt;CyberSpec&lt;/a&gt;, the scanner described here. It's a readiness tool, not a certification body, and isn't affiliated with IASME or NCSC. Happy to answer questions in the comments.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>showdev</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
