
Penetration testing tools fall into a few types: discovery and port scanners, vulnerability scanners, web application proxies, exploitation frameworks, and credential and Active Directory testing tools, plus reporting tools and automated testing platforms. Many of the best known, including Nmap, ZAP and the Metasploit Framework, are free and open source. At NetSys the testing is AI-driven: AI-assisted tools do most of the testing work, and an engineer verifies every finding before it reaches your report.
This guide explains what each type of tool does, which are open source, why a tool on its own is not a penetration test, what AI changes, and what to ask any provider. To see a test on your own business, start with our free external penetration test; for software you build or run, see web application penetration testing.
What are the main types of penetration testing tools?
Most testers draw on the same categories of tools. The names below are well-known, documented examples of each type, not a list of what we run. Licensing is as each project or vendor describes it, checked October 2026.
| Type | What it does | Common examples | Open source or commercial |
|---|---|---|---|
| Discovery and port scanning | Finds the hosts, open ports and services an attacker could reach | Nmap | Free and open source |
| Vulnerability scanners | Compare what they find with known vulnerabilities and misconfigurations | Nessus, OpenVAS | Nessus is commercial, with a free trial; OpenVAS is open source, the scanner in the OpenVAS Community Edition developed by Greenbone |
| Web application proxies | Sit between a browser and an application so the tester can watch and change each request | Burp Suite, ZAP | Burp Suite has a free Community Edition and a paid Professional edition; ZAP is free and open source |
| Exploitation frameworks | Run known exploits against confirmed weaknesses to show what an attacker could actually reach | Metasploit | The Metasploit Framework is open source; Metasploit Pro is commercial |
| Password and credential testing | Check whether passwords can be guessed or cracked | Hashcat, John the Ripper | Both open source; John the Ripper also has commercial Pro editions |
| Active Directory attack paths | Map how an attacker could move from one account to control of the domain | BloodHound | The Community Edition is free and open source |
| Testing distributions | Bundle many of these tools in one operating system | Kali Linux | Open source |
| Reporting and collaboration | Collect findings and evidence from the other tools into one report and track remediation | Dradis | The Community Edition is open source; Dradis Professional is commercial |
| Automated and autonomous testing platforms | Run attack chains with little hands-on work, often on a schedule | NodeZero | Commercial, from Horizon3.ai |
Which tools are used for network and web application testing?
A network penetration test leans on discovery scanners such as Nmap, a vulnerability scanner such as Nessus or OpenVAS, an exploitation framework such as Metasploit, and, inside a Windows domain, credential tools and BloodHound to map paths to domain control. A web application test centers on an intercepting proxy, Burp Suite or ZAP, used against the application's logins, roles, inputs and APIs, and on a method such as the OWASP Web Security Testing Guide. The open source tools are enough to learn on and to run many tests; commercial editions add features such as the automated scanning in Burp Suite Professional.
Why is a tool not the same as a penetration test?
A scanner reports what might be wrong. A penetration test shows what an attacker could actually do with it, by confirming each weakness and chaining weaknesses together. NIST's technical guide to security testing, SP 800-115, files vulnerability scanning under identifying targets and weaknesses, and penetration testing under validating them. That is why a scanner export with a vendor's logo on it is not a penetration test, however many findings it lists.
The output should prove each finding: what was tested, what worked, the evidence and the fix. A list of possible problems, most of them never confirmed, leaves your team to do the testing themselves. Our vulnerability assessment vs penetration testing guide covers when a scan is enough, and our red team vs penetration testing comparison covers the step beyond a penetration test.
How do the main vulnerability scanning tools compare?
Vulnerability scanning is not a penetration test, but a scanner is where most testing starts and the tool most small businesses will actually run between tests. The matrix compares five widely used vulnerability scanning tools on the five things that decide whether a scan produces work you can act on. Every cell reflects the vendor's own product or documentation page as read on November 7, 2026; where a page does not state something, the cell says so rather than guessing.
| Tool | Scan coverage (as the vendor states it) | Validation and false-positive handling | Reporting | Licensing model | Human review needed |
|---|---|---|---|---|---|
| Tenable Nessus | Network and host vulnerability assessment; Professional adds web application scans for five FQDNs and external attack surface scans. Tenable lists 319,000+ plugins and 117,000+ CVEs covered, with 100+ new plugins a week | Tenable claims the industry's lowest false positive rate (a vendor claim; findings still need checking against your environment). Essentials gets plugin updates on a 30-day delay | Configurable reports in Professional and Expert; not included in Essentials | Essentials: free for non-commercial use, up to 5 IPs. Professional: subscription, listed from $4,790 for one year. Expert: from $6,790 for one year. Prices checked on November 7, 2026 | Yes. A scanner result is a lead until an engineer confirms the version, exposure and business impact |
| OpenVAS (Greenbone) | Unauthenticated and authenticated testing, internet and industrial protocols, vulnerability tests from a daily-updated feed. The Enterprise Feed adds enterprise software and network gear coverage and CIS Benchmark compliance checks | Not stated on the pages checked. Authenticated scans see installed software directly, which removes much of the version guessing behind false positives | Reports through the Greenbone web interface and exports; detail depends on the edition | Community Edition and Community Feed are free. The Enterprise Feed comes with Greenbone's paid products from OPENVAS BASIC up, which Greenbone points small businesses toward | Yes. The Community Feed is described as basic coverage to get started, so a person must judge what it does not see |
| Qualys VMDR | Asset discovery, virtual scanners, cloud agents, passive sensors, container sensors, cloud and mobile inventory, CIS benchmark evaluation and PCI ASV assessments | Prioritization through TruRisk and the Qualys Detection Score, with MITRE ATT&CK mapping. False-positive handling is not stated on the page checked | Automated vulnerability and compliance reports, dashboards, an executive summary view, and routing of findings to ServiceNow and Jira | Subscription, priced by segment (small business, mid-sized, enterprise); 30-day free trial. A free Community Edition exists for the security community | Yes. A risk score tells you what the vendor thinks matters; someone who knows which server runs payroll decides what actually gets fixed first |
| Rapid7 InsightVM | Scan Engines for network scanning, the Insight Agent for endpoints, dynamic and static asset groups | Draws on exploit knowledge from Metasploit; the documentation includes an investigate false positives procedure | Built-in report templates and SQL query exports, including a Top Remediation report | Sold through Rapid7's Exposure Command packages; contract details through your account team | Yes. Exploit knowledge improves the ranking; confirming exploitability on your systems is still a person's job |
| Microsoft Defender Vulnerability Management | Built-in and agentless assessment of Windows, macOS, Linux, Android, iOS and network devices; software, certificate, browser extension, hardware and firmware inventories; security baselines (CIS and STIG) | Risk-based prioritization using Microsoft threat intelligence, breach likelihood predictions and correlation with EDR insights. False-positive handling is not stated on the pages checked | Dashboard, recommendations, remediation tracking and exception records in the Microsoft Defender portal; APIs for automation | Core capabilities included in Defender for Endpoint Plan 2; premium capabilities through the Defender Vulnerability Management add-on; a standalone offering for any EDR. Not available to Defender for Business customers as of the page checked | Yes. Recommendations arrive ranked, but exceptions, change windows and the decision to block an application are human calls |
Reading the matrix: no tool fills the validation column on its own. Scanners find candidates and rank them; a person confirms them. That is why the NetSys vulnerability management service pairs weekly scanning with an engineer who reviews, prioritizes and verifies the fixes, and why a penetration test exists as a separate, deeper check. Whichever scanner you run, four practices make the output useful: scan with credentials so the tool sees installed software, scan everything on the inventory rather than a sample, fix by exposure and business impact rather than by raw score, and rescan after each fix so the register shrinks on evidence. Findings and retests belong in one tracker; our penetration testing report template includes an Excel findings and retest tracker that works for scan results too.
How does AI change a penetration test?
AI-driven testing tools can work through more of an environment in the same time: mapping what is exposed, trying attack paths, reading code and keeping track of every lead. They can also be wrong, reporting a flaw that is not there or missing the context that makes a finding serious. So the question to ask about AI in a penetration test is not whether it is used, but who checks its work.
At NetSys, testing is AI-driven: AI-assisted tools do most of the testing, and an engineer verifies every finding before it goes in your report. Nothing reaches the report unconfirmed. For source code tests, the AI-driven analysis runs inside our isolated sandbox, and your code is never sent to an outside service.
What should you ask a provider about their tools?
- Which parts of the test are automated? Scanning, exploitation, code review and reporting can each be done by a tool, a person or both.
- If AI is involved, who verifies each finding? Ask whether anything reaches the report unverified.
- Where does our data go? Ask whether source code, scan output or credentials are sent to an outside AI service, and on what terms.
- What is in scope, and who authorized it? The scope and the authorization should be agreed in writing before testing starts.
- What does a finding look like? Each one should come with evidence, reproduction steps and the specific fix.
- Is a retest included? A retest after you fix is how you know the fixes hold.
How NetSys penetration tests work
We run two tiers. The free external test is remote, limited to the information available to us and an external scope we agree with you, and you keep the findings either way. The Tier 2 web application test runs from your source code in an isolated sandbox under NDA and is quoted per application, with a retest after you patch. In both, testing is AI-driven and an engineer verifies every finding. We don't sell penetration testing as a subscription: each test is scoped on its own.
Frequently asked questions
What are the best penetration testing tools?
There is no single best tool, because each type answers a different question: Nmap for what is exposed, a web proxy such as Burp Suite for how an application behaves, Metasploit for whether a weakness can be exploited. The tester's method and the verification of each finding matter more than the brand names in the report.
What are the best vulnerability scanning tools for a small business?
The one that gets run, with credentials, on every device, and read by someone who acts on it. Nessus Professional, Greenbone's OpenVAS products, Qualys VMDR, Rapid7 InsightVM and Microsoft Defender Vulnerability Management all cover the common ground; the matrix above compares their coverage, validation, reporting and licensing as the vendors state them. A business already licensed for Defender for Endpoint Plan 2 has core vulnerability management included and should start there. None of them is a penetration test.
Is AI penetration testing reliable?
It can be, if every finding is verified. AI tools cover ground quickly but can report flaws that are not real or miss why a finding matters. At NetSys an engineer verifies every finding before it is reported, so the report contains confirmed results only.
Is automated penetration testing the same as a vulnerability scan?
No. A vulnerability scan lists weaknesses that might exist. Automated penetration testing goes further and tries to confirm and exploit them, the way an attacker would. Either way, ask who reviews the output: an unverified automated finding is still only a lead.
Do you offer penetration testing as a subscription?
No. Each NetSys test is scoped on its own, starting with the free external test. Tier 2 application tests are quoted per application after a short technical call.
Which penetration testing tools are open source?
Of the tools above, Nmap, OpenVAS, ZAP, the Metasploit Framework, Hashcat, John the Ripper, BloodHound Community Edition, Kali Linux and Dradis Community Edition are open source. Nessus, Metasploit Pro, Dradis Professional and NodeZero are commercial, and Burp Suite comes as a free Community Edition and a paid Professional edition.
What is included in a NetSys penetration test?
The free Tier 1 test is a remote external test, limited to the information available to us and the external scope we agree with you, and it ends with a prioritized fix list in plain English that you keep. The Tier 2 test takes your source code under NDA into an isolated sandbox for static review, dynamic testing of the running application and its APIs, and dependency, secret and configuration scanning; findings come with severity, reproduction steps and the fix, and we retest after you patch. Internal network work is scoped separately as an internal security assessment.
How does a penetration test start?
With scope and authorization in writing. For the free external test, we agree the domains and public-facing systems you authorize us to test. For a Tier 2 test, a short technical call sets the scope, then you provide the code under a signed NDA as a repository grant or an archive. Whoever you hire, agree before testing starts who the contact is on your side if something urgent turns up.
What affects the cost of a penetration test?
The assets you authorize, the access you provide, the testing methods, the exclusions, the depth of the report and whether a retest is included. Our free external test costs nothing within its agreed scope, and Tier 2 is quoted per codebase. Our penetration testing cost guide explains what drives a quote.
Who handles fixes and questions after the report?
Fixes stay with your team or your IT provider, guided by the specific fix written into each finding. The report states what was in scope and what was not tested, so nobody reads more into it than the test supports. For Tier 2, we retest once you have patched, which is how you know the fixes hold.
Sources and further reading
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment: vulnerability scanning (section 4.3) and penetration testing (section 5.2).
- OWASP Web Security Testing Guide, a widely used method for testing web applications.
- Vulnerability scanner pages behind the comparison matrix: Tenable Nessus and Nessus Essentials, OpenVAS and the Greenbone feed comparison, Qualys VMDR and Qualys Community Edition, Rapid7 InsightVM documentation and product page, and Microsoft Learn's Defender Vulnerability Management overview and plan comparison. Coverage, licensing and prices as each vendor states them, checked on November 7, 2026.
- Tool sites: Nmap, Nessus, OpenVAS, Burp Suite, ZAP, Metasploit, Hashcat, John the Ripper, BloodHound, Kali Linux, Dradis Community Edition and NodeZero: licensing and editions as each describes them, checked October 10, 2026.
Related reading
Also on this topic: Penetration Test Checklist: Authorize Scope, Review Findings and Retest
Discuss ai services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.


