What a Vulnerability Assessment Finds

Somewhere on your network there is probably a device nobody has updated in a while: an old server, a firewall, a remote access box someone set up years ago. A vulnerability assessment is how you find those weak spots and rank them before someone else finds them for you. Verizon’s 2025 Data Breach Investigations Report found that exploiting a known weakness was the way in for 20% of breaches, a 34% jump on the year before.

A vulnerability assessment is a planned scan and review of your network, computers, cloud accounts and websites. It lists the known weaknesses an attacker could use and ranks them by how urgently each needs fixing. It finds problems; it does not break in, and it does not touch your data. For a business of 10 to 200 people, it often looks at your systems from both outside and inside your network and ends with a written report.

What Is a Vulnerability Assessment?

A vulnerability assessment is a check of your systems against the long, public list of known security flaws, followed by a report that says which ones you have and which to fix first. Think of it as a building inspection for your IT. The inspector walks through, notes every loose railing and faulty outlet, and hands you a list ranked by danger.

It is not a verdict on your IT team or your current provider. Every network collects weaknesses over time, because new flaws in common software are published all the time. The assessment can’t predict which cybersecurity threats will come your way. It shows which known weaknesses those threats could use, and where you stand today.

What Gets Scanned in an Assessment?

A good assessment covers every place an attacker could get a foothold, not just the server closet. That usually includes:

  • Firewalls, routers and VPN or remote access devices
  • Servers, whether in your office or hosted
  • Desktop computers and laptops, including the ones that travel
  • Wi-Fi networks and access points
  • Cloud services and Microsoft 365
  • Your public website and any web applications customers log into

Microsoft 365 and other cloud services are worth a settings review as well as a network scan. A scanner pointed at your office may not show whether multi-factor authentication is turned on for every account, or whether an old employee’s mailbox is still active. Looking at the configuration itself is the usual way to check.

The scan also turns up systems you forgot you had.

  • Example: a server that ran an old accounting package was replaced three years ago, but nobody unplugged it. It still sits on the network, still answers requests, and has not received a security update since the day it was retired.

Outside Scan vs. Inside Scan: What Is the Difference?

An outside scan shows what a stranger on the internet can see; an inside scan shows what someone could reach once they are past your front door. You need both, because they answer different questions.

The outside, or external, scan looks at your public internet addresses and anything exposed to the internet: open ports on your firewall, your VPN and remote access tools, your website. Guidance from the Cybersecurity and Infrastructure Security Agency (CISA), the federal agency for cyber defense, says an external scope should include all of an organization’s public IP addresses and internet-facing applications. This is the view a potential attacker gets before they have any access at all.

The inside, or internal, scan runs from within your network. It looks at servers, computers, printers and anything else connected, and asks what an intruder could reach if they got in, for instance through a laptop infected by a phishing email. Many serious problems only show up from the inside.

Internal scans come in two kinds. An unauthenticated scan looks from the outside of each machine, like checking which doors are locked. An authenticated, or signed-in, scan logs into each system with credentials you provide, so it can see missing patches, outdated software and weak settings. Testing guidance from the National Institute of Standards and Technology (NIST) notes that signed-in scans see more, and the Center for Internet Security (CIS) recommends running both kinds.

Neither scan replaces the other. A tight firewall does not help much if one click on a bad link puts an attacker inside a flat network full of unpatched machines.

If your organization counts as critical infrastructure or is a government body, CISA offers free weekly scanning of internet-facing systems through its Cyber Hygiene service. Most private companies are not eligible, so the outside scan usually comes from your IT provider or a security firm.

What Network Vulnerabilities Does an Assessment Usually Find?

The network vulnerabilities an assessment turns up are usually ordinary: devices that missed updates, passwords that were never changed, and doors left open for convenience. Few are exotic. Common findings include:

  • Unpatched internet-facing devices. Firewalls, VPNs and remote access appliances with known flaws that have a fix available.
  • Default or weak passwords. Admin accounts on printers, cameras, switches or Wi-Fi gear still using the factory login.
  • Missing multi-factor authentication. Email, remote access or admin accounts protected by a password alone.
  • Remote desktop exposed to the internet. A port opened years ago so someone could work from home, never closed.
  • Systems too old to get updates. Operating systems and software the maker no longer supports.
  • Firewall rules nobody remembers adding. Exceptions made for a vendor or a one-time project that are still in place.

The edge devices at the top of that list deserve special attention. In Verizon’s 2025 report, edge devices and VPNs made up 22% of the targets when attackers exploited a weakness to get in, up from 3% the year before. Only 54% of those edge-device flaws were fully fixed, and the median time to fix them was 32 days. That gap between a fix being available and a fix being applied is exactly what an assessment exposes.

What Does a Vulnerability Assessment Report Look Like?

A vulnerability assessment report is a ranked to-do list with evidence attached. A useful one has these parts:

  • Executive summary. A page in plain English: how many findings, how serious, and the handful that matter most.
  • Scope. What was scanned, what was not, and when. If the cloud settings or a branch office were left out, the report should say so.
  • Findings list. Each weakness with where it is, the evidence, a severity rating and how to fix it.
  • Recommended order. Which fixes come first and why.
  • Retest plan. When the systems will be scanned again to ensure the fixes worked.

Severity is usually shown as Critical, High, Medium or Low, based on a standard score from 0 to 10. That score measures how serious the flaw is in general. It does not know that one server runs your payroll and another is a test machine in a closet. A good report adds that business context.

Here is what a few rows of the findings list might look like. This is an illustrative example, not a real client’s report.

Finding Where it is Severity What to do
VPN appliance missing a security update for a known exploited flaw Main office firewall, internet-facing Critical Apply the vendor’s update this week; rescan to confirm
Remote desktop open to the internet Accounting workstation High Close the port; move remote access behind the VPN with multi-factor sign-in
Factory admin password on network printer Second-floor printer Medium Change the password; restrict admin access
Old operating system no longer supported Retired file server High Unplug and decommission, or isolate until it can be retired

What Gets Fixed First?

Fix first what attackers are already using, on the systems they can reach, that your business depends on. The severity score comes after that, not before. A practical order:

  1. Known exploited flaws. CISA keeps a public catalog of vulnerabilities known to be exploited in the wild, and it advises organizations to use that catalog as one input when deciding what to fix first. If a finding is on that list, it goes to the top.
  2. Anything facing the internet. Firewalls, VPNs, remote access and websites can be reached by anyone, so a flaw there carries more risk than the same flaw deep inside.
  3. The systems you can’t run without. Your accounting system, file server, line-of-business software and email.
  4. Everything else, by severity score. Work down from Critical to Low.

This is why a “High” can outrank a “Critical.” A High-rated flaw on your internet-facing VPN may be a bigger risk than a Critical one on an isolated test machine with no outside access.

  • Example: a report shows a Critical flaw on an old lab computer that sits on its own network segment, and a High flaw on the firewall that also appears on CISA’s exploited list. The firewall gets fixed first, the same week. The lab computer goes on the list for the following month.

How Often Should a Business Your Size Repeat It?

Repeat the scanning on a schedule, not once: CIS recommends scanning internet-facing systems at least monthly and internal systems at least quarterly. A one-time vulnerability assessment is out of date as soon as the next batch of flaws is published.

Rule or standard What it asks for
CIS Critical Security Controls Outside scans monthly or more often; inside scans quarterly or more often, both signed-in and not; fixes applied monthly or more often
PCI DSS (if you take card payments) Internal and external scans at least once every three months, plus after any significant change
HIPAA (if you handle patient data) A risk analysis kept up to date as your systems change
Any business A fresh scan after big changes: a new firewall, a move to the cloud, an office build-out

The PCI Security Standards Council sets 90 days as the maximum gap between scans and encourages businesses to scan more often than required. If you are under PCI DSS or HIPAA, your compliance and IT risk management work should already account for this schedule.

Cyber insurance is another reason to keep records. Requirements vary by carrier, so ask your insurance broker what evidence of scanning and patching your policy expects.

What Happens After the Report?

After the report, someone has to own the fixes, work through them in order and prove they are done. A report nobody acts on protects nothing.

The work usually goes like this:

  • Assign an owner. One person or one provider is responsible for the list, with dates.
  • Fix in priority order. Apply patches, change settings, close ports and retire old systems, starting with the top of the list. Some fixes take minutes; other solutions, such as replacing an unsupported server, take budget and planning. CIS recommends fixing detected software flaws monthly or more often.
  • Add a stopgap where a fix has to wait. If a system can’t be patched yet, perhaps because a vendor hasn’t released an update or a machine runs equipment that can’t go offline, limit who can reach it and set a date to revisit.
  • Rescan. Compare the follow-up scan results with the original report to confirm each fix worked and nothing new appeared.

Then the cycle starts again. Ongoing vulnerability management means scanning, fixing and checking on a regular rhythm, so the list stays short instead of growing back.

  • Example: an assessment finds 40 issues. The five most urgent are fixed in the first week, a stopgap goes in for one old machine that runs shop-floor equipment, and the rest are worked through over the next month. The rescan shows the open list down to a few low-severity items.

Frequently Asked Questions

What are the four stages of a vulnerability assessment?

The process is commonly described in four stages: identify, analyze, prioritize, and fix and verify. The analyze stage is the one people overlook: it is where false alarms get weeded out, so your team doesn’t spend a week chasing findings that turn out not to apply.

What is the Common Vulnerability Scoring System (CVSS)?

CVSS is the standard severity score behind most report ratings, maintained by FIRST, the body that publishes the standard. In its current version 4.0, scores of 9.0 to 10.0 are Critical, 7.0 to 8.9 High, 4.0 to 6.9 Medium and 0.1 to 3.9 Low. Many reports still use the older version, which runs on the same 0 to 10 range.

What are the main types of vulnerability?

A common grouping uses five types: network, host, application, wireless, and process or people. The last group, such as weak password habits or staff who have never had security training, is the one a scanner can’t fully measure, so a complete assessment also asks how your people and processes work.

How is a vulnerability assessment different from a penetration test?

Penetration tests go a step further: NIST describes them as testers trying to get around or defeat security features, often using real attacks on real systems. CREST, a security testing accreditation body, notes that an assessment relies mainly on automated scanning while a test adds manual work to exploit what it finds. The two complement each other, and most small businesses start with the assessment and fix what it finds before paying for one of those tests.

How ThrottleNet Can Help

ThrottleNet offers a free on-site assessment and security report: in our words, “a deep evaluation of risk exposure, system health, user experience, and IT processes.” You get a clear picture of where you stand, explained without the jargon.

What matters most is what happens next. If you choose to work with us, onboarding into managed or co-managed IT puts our dedicated cybersecurity team and 24/7 Security Operations Center on your systems, with proactive patching and monitoring so the findings get fixed and stay fixed. Our multi-tier help desk is the reason problems are solved faster: each request goes straight to the engineer level it needs.

We back that work with the $500,000 Cybersecurity Protection Program, which covers ransomware and data theft, business email compromise, regulatory fines and legal fees, downtime and recovery expenses, and cyber extortion payments. And in our own words: ThrottleNet customers have never paid a ransomware attack.

We have been helping St. Louis-area businesses since 1999, on month-to-month agreements. You stay because you want to.

Don’t wait for your next IT crisis. Call (314) 961-1027 or contact us today for a free consultation.

Russia's Hybrid War: What to Know About Hackers and Ukraine

16 Ways to Protect Your St. Louis Business From Cyberattacks

Free Download
15 Ways to Protect Your Business from Cyberattacks
Call Now (866) 826-5966