Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Vulnerability scanning is the automated process of checking systems, networks, and applications for known security weaknesses, such as missing patches, misconfigurations, and outdated software.

What Is Vulnerability Scanning?
Vulnerability scanning is the use of automated tools to identify known security weaknesses in computers, networks, applications, and cloud services. A scanner probes its targets, works out what software and versions they run and how they are configured, and compares the results against databases of known vulnerabilities. The output is a report listing each issue, its severity, and usually a recommended fix.
Scanning is one of the most cost-effective security activities available. It does not find every problem, but it catches the common, well-known weaknesses that attackers search for automatically across the internet every day.
A typical scan moves through several stages:
| Scan type | What it covers |
|---|---|
| External | Internet-facing systems, as an outside attacker would see them |
| Internal | Systems inside the network, as a compromised device or insider would see them |
| Authenticated | Logs in with credentials to check patches and configuration in depth |
| Unauthenticated | Tests only what is visible without credentials |
| Web application (DAST) | Running web applications and APIs, for issues such as injection and misconfiguration |
| Container and image | Container images and registries, for vulnerable packages |
| Cloud configuration | Cloud accounts, for risky settings such as public storage or excessive permissions |
Authenticated scans are far more accurate. An unauthenticated scan can only guess from what a service reveals, while an authenticated scan can read installed software versions and settings directly, finding many more issues with fewer false positives.
Widely used scanners include commercial products such as Tenable Nessus, Qualys, and Rapid7 InsightVM, and open-source options such as OpenVAS (Greenbone) and the template-based Nuclei. Web application scanners such as Burp Suite and OWASP ZAP focus on application-layer issues. Many cloud platforms also include native configuration and vulnerability scanning.
Frequency depends on risk and change. Many organisations run external scans at least monthly and internal scans monthly or weekly, with continuous scanning increasingly common for internet-facing assets. PCI DSS requires quarterly internal scans and quarterly external scans by an Approved Scanning Vendor, plus scans after significant changes. Critical new vulnerabilities, such as a widely exploited flaw in a VPN product, justify an immediate targeted scan.
Scanners are powerful but have clear limits:
Scanning and penetration testing are complementary. Scanning is automated, broad, and frequent; penetration testing is manual, deep, and periodic. A penetration tester uses scanner output as a starting point, then verifies findings, chains weaknesses together, and demonstrates real impact. Most organisations need both: continuous scanning to catch new issues quickly, and regular penetration tests to find what automation misses.
Scanning only reduces risk if findings are fixed. Results should feed a vulnerability management process with clear ownership, risk-based prioritisation, agreed remediation timescales, and rescanning to confirm fixes. Without that, scan reports simply pile up.
At Privia Security, our Continuous Vulnerability Scanning Services scan your internal and external assets regularly, validate findings, and help your teams focus on the issues that matter most.
Modern scanners are designed to be safe, using non-destructive checks by default, and most scans run on production systems without issue. However, fragile or legacy devices, particularly in operational technology environments, can be affected by intensive scanning. Agree scan windows, start with lighter policies, and exclude or carefully handle sensitive systems.
An unauthenticated scan only sees what a system exposes to the network, so it relies on guesses from service banners and responses. An authenticated scan logs in with credentials and inspects installed software, patches, and configuration directly. Authenticated scans find far more vulnerabilities with fewer false positives and are recommended for internal systems.
No. Scans are automated and broad, finding known vulnerabilities quickly and frequently. Penetration tests are manual and deep, validating findings, uncovering logic flaws, and showing how weaknesses can be chained into real attacks. Most security frameworks and regulators expect both, with scans run frequently and penetration tests performed at least annually.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.