{"id":1152,"date":"2026-11-15T10:40:00","date_gmt":"2026-11-15T10:40:00","guid":{"rendered":"https:\/\/flyaiaa.com\/blog\/?p=1152"},"modified":"2026-11-16T23:40:00","modified_gmt":"2026-11-16T23:40:00","slug":"dashboard-green-risk-isnt-vulnerabilityops-diagnosis","status":"publish","type":"post","link":"https:\/\/flyaiaa.com\/blog\/dashboard-green-risk-isnt-vulnerabilityops-diagnosis\/","title":{"rendered":"Green Dashboard, Same Risk: A VulnerabilityOps Diagnosis"},"content":{"rendered":"<p>Picture a flight academy&#8217;s operations manager, call him the one who always arrives before the first lesson, looking at a report that makes him smile. Open security findings have dropped by a third in two months. The chart is green. His small IT contractor is pleased. Yet something nags at him, the way a slightly odd engine note nags at a pilot who cannot yet say why. This post follows that nag through four symptoms to their causes and fixes. The academy and its people are invented for illustration; the pattern is real and well documented.<\/p>\n<p>The diagnostic ideas are borrowed from <a href=\"https:\/\/www.xopsschool.com\/vulnerabilityops\/\">a VulnerabilityOps reference in the Ops Atlas<\/a>, a page that treats vulnerability handling as an ongoing flow with owners, deadlines and confirmed closure.<\/p>\n<h2>Symptom one: fewer findings, same systems<\/h2>\n<p>The first thing our manager checks is whether the number of systems being scanned changed. It did not appear to, but the scanner&#8217;s login failures were not in the report he received. This is the best-known false win in the field. When a scanner loses the credentials it needs to look inside a machine, it sees less, and fewer findings are reported. The Atlas notes specific scanner checks that exist to reveal this, such as one plugin in a widely used scanner that reports when a login failed and another that checks for package inventory on Linux. If those appear in your results, the green is imaginary.<\/p>\n<p><strong>Cause:<\/strong> a password rotation that was never passed on to the scanner.<\/p>\n<p><strong>Fix:<\/strong> treat scan credentials as managed secrets, and report credentialed coverage over a seven-day window next to the finding count. In the Atlas example, 80 of 1,900 hosts dropped out of coverage after a key rotation, leaving the figure at 95.8 percent.<\/p>\n<h2>Symptom two: items marked done that reappear<\/h2>\n<p>Next, he notices several flaws that were closed in March showing up again in June. The contractor says new scans found them. The truth is more mundane. The tracker marked each one resolved when a technician applied a change, but no one confirmed it worked. A few changes were reverted when a server was rebuilt from an old image.<\/p>\n<p><strong>Cause:<\/strong> closure defined by ticket status.<\/p>\n<p><strong>Fix:<\/strong> require proof. The Atlas accepts a fresh scan that logs in, a passing configuration test, a rebuilt image carrying a different digest, or a dispute accepted on review. Track how many closed items recur within ninety days; a high count is a bright warning light.<\/p>\n<h2>Symptom three: old items never seem to age<\/h2>\n<p>The manager asks the contractor for the age of the oldest open item. It is oddly young. Digging further, he finds that each weekly rescan creates a new record rather than updating the old one, so the first-seen date resets and any deadline restarts. A weakness that has been open for half a year looks brand new.<\/p>\n<p><strong>Cause:<\/strong> a record key that does not combine the asset, the flaw and the affected component.<\/p>\n<p><strong>Fix:<\/strong> deduplicate on all three, preserving the first-seen date. Our post on <a href=\"https:\/\/flyaiaa.com\/blog\/mastering-tech-selections-your-blueprint-for-choosing-software-wisely\/\">picking technology with a clear head<\/a> argues for asking such questions of any tool before you buy it.<\/p>\n<h2>Symptom four: a healthy age chart over a growing pile<\/h2>\n<p>Finally the contractor proudly shows that the age of the older items has fallen from thirty weeks to twelve. Our manager counts the open items and sees that the list grows by around twenty-five every week. New arrivals are diluting the older ones in the average.<\/p>\n<p><strong>Cause:<\/strong> a metric chosen in isolation.<\/p>\n<p><strong>Fix:<\/strong> for each tier, report new arrivals over verified closures. A figure above one means the pile is growing no matter what the age chart says. The Atlas worked example has a lower tier at about 1.15, which tells you at a glance why it will outlast its sixty-day deadline.<\/p>\n<h2>A bonus symptom: alerts that go nowhere<\/h2>\n<p>While tracing the first four, the manager spots a fifth problem. Urgent notices are sent to a shared mailbox that two former employees used to read. Nobody reads it now. The Atlas recalls a major breach in which the warning was published, yet the follow-up scan seven days on skipped the exposed portal and the notification reached people who had moved on. Routing fails quietly, which is why it deserves a regular check.<\/p>\n<p><strong>Cause:<\/strong> an ownership list that nobody maintains.<\/p>\n<p><strong>Fix:<\/strong> every month, sample a handful of owners and confirm each is a current person or team who has acknowledged receiving the work. Put a due date next to each acknowledgement so silence becomes visible.<\/p>\n<h2>What the contractor got right<\/h2>\n<p>It is tempting to cast the contractor as a villain, and that would be unfair. He ran the scans on schedule, produced a tidy chart and responded to every message. The tooling nudged him towards counting what it saw, and nobody had told him what the academy needed to know. This matters because the cure is a clearer brief, not a change of supplier. Write down which numbers you want, how they are calculated and what evidence backs them, and most contractors will happily provide them.<\/p>\n<p>It also helps to agree on language. When the contractor says a finding is closed, the academy should hear that someone confirmed it, using one of the agreed proofs. When he says a system is covered, that should mean a successful credentialed scan within the last week. Shared definitions remove most of the arguments before they begin.<\/p>\n<h2>The conversation that follows<\/h2>\n<p>Our manager does not shout. He asks for four things in writing: a coverage figure with failed logins listed, evidence of closure for ten sampled items, the key used to identify duplicates, and the arrivals-to-closures ratio for each tier. The contractor takes a week. The results are humbling but useful, and the green dashboard turns amber, which is the first honest picture the academy has had.<\/p>\n<p>If you have read our account of <a href=\"https:\/\/flyaiaa.com\/blog\/booking-mistakes-first-time-charter-travelers-should-avoid\/\">common booking mistakes first-time charter travellers make<\/a>, you will recognise the shape: a small unnoticed gap early on becomes an expensive surprise later.<\/p>\n<h2>Why this keeps happening<\/h2>\n<p>Dashboards reward a falling line. Most tools make it easy to count what they find and hard to count what they miss. The Atlas lists these false-progress patterns among its anti-patterns, along with a few others: policy that is nothing but chase the highest severity numbers, a belief that patching everything is possible, and a findings database that anyone can browse, when it is really a list of weak spots. It also warns against letting the team that owns a system approve its own statement that a flaw does not apply.<\/p>\n<h2>A short repair plan<\/h2>\n<ol>\n<li>Report scan coverage and credential failures alongside findings, every week.<\/li>\n<li>Define closure by evidence and sample ten closed items each month.<\/li>\n<li>Check the deduplication key and restore first-seen dates.<\/li>\n<li>Replace age charts with an arrivals-to-closures ratio per tier.<\/li>\n<li>Guard the findings list and the scanner logins as sensitive material.<\/li>\n<\/ol>\n<p>For another warning pattern in the same family, read our note on <a href=\"https:\/\/flyaiaa.com\/blog\/common-charter-safety-mistakes-travelers-should-avoid\/\">safety slip-ups charter passengers should watch for<\/a>. The principle repeats: check the thing itself, not the paperwork about the thing.<\/p>\n<h2>Closing the loop<\/h2>\n<p>Six weeks later the academy&#8217;s report looks less pretty and far more useful. Coverage is up, closed items come with proof, and the age of old findings is honest. The manager still arrives before the first lesson. The nag is gone, replaced by a one-page summary he can read in two minutes and trust.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A story-led diagnosis of a common VulnerabilityOps failure: findings fall, dashboards turn green, and nothing has actually been fixed.<\/p>\n","protected":false},"author":6,"featured_media":1153,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[634],"tags":[],"class_list":["post-1152","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-flight-training-tech"],"_links":{"self":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1152","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/comments?post=1152"}],"version-history":[{"count":1,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1152\/revisions"}],"predecessor-version":[{"id":1253,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1152\/revisions\/1253"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media\/1153"}],"wp:attachment":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media?parent=1152"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/categories?post=1152"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/tags?post=1152"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}