Join our Newsletter — 33% off our NHI Course
Home› Guides› Open Source Penetration Testing Tools Landscape Guide: Choosing…
Guide Offensive Security & Testing

Open Source Penetration Testing Tools Landscape Guide: Choosing Tools for Authorised Assessments

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 12 min read
On this page

Open source testing tools are powerful, free and widely available, which is exactly why organisations need to govern who uses them, where and under what authority. This guide is for defenders and authorised testers only, and it contains no usage walkthroughs. It maps the main categories of open source and free penetration testing tools, the licences they ship under, and the legal and organisational controls that should surround their use. It also explains what defenders see when these tools are used against them, so blue teams can use the same landscape to plan detections. It is written for security managers, internal testing teams, procurement and legal reviewers, and SOC leads.

Key takeaways

  • Authorisation, not the tool, makes testing lawful. In the UK, the Computer Misuse Act 1990 makes unauthorised access an offence regardless of tooling, and section 3A also covers making, supplying or obtaining tools for use in offences.
  • "Open source" covers very different licences. Metasploit Framework is BSD 3-clause, Ghidra and BloodHound Community Edition are Apache 2.0, Atomic Red Team is MIT, and Nmap uses its own Nmap Public Source License with restrictions on embedding in proprietary products.
  • Free is not the same as open source. Burp Suite Community Edition is free to download but is a separate product from the paid Professional edition; check licence terms before building it into services.
  • Tool use needs a governance wrapper. An approved tool list, controlled testing hosts, written scope, rules of engagement and data handling rules turn ad hoc tool use into an auditable programme.
  • Defenders should know the landscape too. Most of these tools have recognisable network and host signatures, and emulation libraries mapped to ATT&CK let blue teams test detections safely.

What the tools do: the landscape by category

No single tool covers an assessment. Testing methodologies such as NIST SP 800-115 (Technical Guide to Information Security Testing and Assessment) and the OWASP Web Security Testing Guide (stable version 4.2) describe phases from planning and discovery through to reporting; tools map onto those phases. The table summarises categories with representative open source or free projects. Licences are given only where confirmed from the project's own source.

CategoryPurpose in an authorised assessmentRepresentative projectsLicence (confirmed)
Network discovery and port scanningIdentify live hosts and exposed services within scopeNmapNmap Public Source License, based on GPLv2 with additional terms
Packet capture and protocol analysisInspect traffic, verify encryption, troubleshoot findingsWiresharkFree and open source (check the source repository for exact terms)
Web application proxies and scannersIntercept and test web and API trafficZAP; Burp Suite Community Edition (free, not open source)ZAP is free and open source; Burp Community is a free edition of a commercial product
Exploitation frameworksValidate that a vulnerability is exploitable, in scope and with approvalMetasploit FrameworkBSD 3-clause; third-party components carry their own licences
Identity and attack path analysisMap privilege relationships in Active Directory and Entra IDBloodHound Community EditionApache 2.0
Adversary emulation and detection testingRun small, ATT&CK-mapped tests to validate detectionsAtomic Red TeamMIT
Reverse engineeringAnalyse binaries and malware samplesGhidra (NSA Research Directorate)Apache 2.0
Testing distributionsPackaged, signed toolsets on a known baseKali Linux (Debian-based, an OffSec community project, several hundred tools)Open source distribution; each packaged tool keeps its own licence
Vulnerability scanning, password auditing, wireless and social engineering simulationBroader assessment needsMany community projectsVaries; verify per project before approval

Deeper guides on individual tools: Nmap for Defenders Guide, Burp Suite for Authorised Web Testing Guide, Kali Linux for Authorised Testing Guide, Ghidra for Malware Analysis Guide and BloodHound and Active Directory Attack Path Guide.

Licence considerations that matter in practice

  • Using versus redistributing: Most licences place few limits on internal use. Obligations bite when you redistribute, embed the tool in a product or offer it as part of a commercial service. Nmap's licence states an aim of prohibiting redistribution within proprietary hardware and software products and offers a separate OEM licence for that case.
  • Permissive versus copyleft: BSD, MIT and Apache 2.0 allow reuse with attribution; GPL-family licences require source to be shared when you distribute derivative works. Managed service providers building tooling on top of these projects need legal review.
  • Bundled components: Frameworks and distributions bundle many third-party components, each with its own licence. The Metasploit Framework licence file says so explicitly.
  • Free editions of commercial tools: Free community editions usually carry an end-user licence, not an open source licence, and feature limits. Burp Suite Professional adds a scanner, full Intruder, Burp Collaborator and saved projects over Community.

Defender use cases

  • Validating detections: Run ATT&CK-mapped emulation tests in a controlled scope and confirm that the SIEM and EDR alert. See the Purple Teaming Guide and Detection Engineering Guide.
  • Knowing your own exposure: Authorised discovery scans of your own ranges show what an attacker's reconnaissance would find. See the Attack Surface Management Guide.
  • Attack path reduction: Identity graph analysis shows which accounts and group memberships give the shortest paths to domain admin, so they can be removed before an attacker finds them.
  • Incident response and malware analysis: Packet analysers and reverse engineering tools support triage of suspicious traffic and samples in an isolated lab.
  • Verifying fixes: Retesting a remediated finding with the same tool class the tester used gives evidence for closure. See the Vulnerability Scanning Guide.

Deployment and safe use

Legal and authorisation requirements

  • Computer Misuse Act 1990 (UK): Section 1 covers unauthorised access. Section 3A makes it an offence to make, adapt or supply an article (which includes a program) intending it to be used in an offence, to supply it believing it is likely to be so used, or to obtain it with that intent; the maximum on indictment is two years' imprisonment. Written authorisation from someone entitled to give it is what separates a test from an offence.
  • Equivalents elsewhere: Most jurisdictions have comparable laws, such as the US Computer Fraud and Abuse Act and national laws transposing the Council of Europe Budapest Convention. Testing across borders or against cloud providers' infrastructure needs legal review and adherence to the provider's own testing policy.
  • Third-party assets: You cannot authorise testing of systems you do not own or control. SaaS, hosting and managed service assets need the provider's permission or must stay out of scope.

Scope and rules of engagement

The UK NCSC describes penetration testing as assurance of your vulnerability management rather than the main way to find vulnerabilities, and recommends that scoping involves risk owners, technical owners and the testing team. Its scoping outputs include technical boundaries, test types, timeframe, scenarios, tester requirements, compliance needs and reporting format, and it notes that scope changes are generally the risk owner's decision. HMG organisations are advised to use CHECK scheme testers. Use the Penetration Test Scoping Checklist and the Red Team Rules of Engagement Template to record:

  • Targets: In-scope IP ranges, hostnames, applications, accounts and cloud subscriptions, and explicit exclusions.
  • Techniques: Which tool categories are approved (for example, discovery and web proxying but no exploitation of production databases).
  • Timing and contacts: Testing windows, a named technical point of contact, and a stop procedure.
  • Source identification: Tester source IP addresses and accounts, shared with the SOC so alerts can be attributed.

Organisational governance of tool use

ControlWhat good looks likeFramework reference
Approved tool listEach tool reviewed for licence, provenance and signing, with an owner and a review dateCIS Controls v8.1 Control 2 (software inventory); NIST SP 800-53 CM-7
Controlled testing hostsDedicated, hardened testing machines or VMs, not general workstations; EDR exclusions scoped to those hosts onlyNIST SP 800-53 AC-6, CM-7
Authorisation recordsSigned scope and rules of engagement stored with each engagementNIST SP 800-53 CA-8; CIS Control 18
Acceptable usePolicy forbidding use of testing tools outside an authorised engagement, acknowledged by testersNIST SP 800-53 PL-4
Evidence and data handlingCaptured credentials, hashes and data encrypted, minimised and deleted at engagement closeISO/IEC 27001:2022 Annex A 8.10 (information deletion)
Detection of unauthorised useSOC alerts on testing tool signatures from hosts that are not registered testing hostsNIST SP 800-53 SI-4; CSF 2.0 DE.CM-09

Safe lab and data handling

  • Isolate practice: Learning and tool evaluation belong in an isolated lab, never on production or third-party networks. See the Building a Cybersecurity Home Lab Guide.
  • Verify provenance: Download from official project sources, verify signatures or checksums, and pin versions. Kali signs every package, which is one reason teams standardise on a distribution.
  • Handle findings as sensitive data: Credentials and tokens discovered during testing are live secrets. Report them through a secure channel, rotate them, and do not store them in reports in clear text. See the Secrets Management Guide.
  • Treat testing accounts as privileged non-human identities: Accounts created for testers or tools should be time-bound, individually attributable and removed at the end of the engagement. See the Service Account Security Guide.

A phased rollout for an internal testing capability

  1. Policy first: Publish an acceptable use and authorisation policy and nominate who can sign scopes.
  2. Approve a minimal toolset: Start with discovery, web proxy and emulation categories; add exploitation frameworks only once governance is proven.
  3. Build testing hosts: Dedicated, logged hosts registered with the SOC, with narrowly scoped EDR exclusions.
  4. Pilot in a lab, then a non-production scope: Confirm tools behave as expected and that the SOC can see and attribute them.
  5. Extend to production with signed scope: Include a stop procedure and rollback contacts for any service impact.
  6. Review annually: Re-check licences, retire unmaintained tools and update the approved list.

Detection and hardening value

Because these tools are freely available, attackers use them too. Defenders gain by knowing what they look like.

  • Discovery and scanning: Connection fan-out across many ports or hosts, visible in firewall, flow and IDS logs (ATT&CK T1046 Network Service Discovery, T1595 Active Scanning). See the Discovery and Reconnaissance Techniques Guide.
  • Web testing: High request rates, unusual parameter values and wordlist-style path requests in web server and WAF logs (T1595.003).
  • Identity graph collection: Bursts of LDAP and SAMR queries from one host (T1087.002, T1069.002), which directory sensors flag as reconnaissance.
  • Exploitation frameworks: Many default payloads and behaviours are signatured by EDR products; defenders should test that their EDR detects default behaviours rather than assume it. See the EDR Guide.

Useful measures: percentage of authorised test activity detected by the SOC; mean time to attribute an alert to a registered test; number of tool alerts from unregistered hosts (should be zero or investigated); proportion of approved tools reviewed in the last 12 months; and proportion of engagements with signed scope on file before start.

Alternatives

OptionStrengthsTrade-offsBest fit
Open source tools run by an internal teamNo licence cost, transparent code, large communityNeeds skilled staff, governance overhead, variable maintenanceOrganisations with a security engineering function
Commercial editions and platformsSupport, reporting, scheduled scanning, vendor accountabilityLicence cost; confirm capabilities with the vendorTeams needing repeatable scanning and audit evidence
External testing providerIndependence, accredited testers (for example CHECK for HMG)Cost per engagement, point-in-time viewRegulatory or contractual assurance. See the Penetration Testing Provider Buyer's Guide
Continuous automated testingFrequent coverage between manual testsComplements manual testing; needs tuningLarge estates. See the Continuous Automated Red Teaming (CART) Guide

Small organisations usually get more from an external provider plus a small set of defender-focused tools (discovery and emulation) than from building an internal offensive capability. Large organisations typically combine all four, with the internal team using open source tools under strict governance.

Common failure patterns

  • Testing on verbal approval: No signed scope means no evidence of authorisation if something breaks or is challenged legally.
  • Tools on everyday laptops: Testing tools installed on general workstations with broad EDR exclusions create a blind spot an attacker can reuse.
  • Unchecked downloads: Tools pulled from unofficial mirrors or forks without signature checks can carry malware.
  • Licence surprises: Embedding a tool in a commercial product or service without reading its licence, particularly Nmap's restrictions on proprietary use.
  • Loot left behind: Credentials and data collected during testing kept in shared drives or reports long after the engagement.

Practitioner checklist

  • Publish an authorisation and acceptable use policy for testing tools and name who can sign scopes.
  • Maintain an approved tool list with licence, source, owner and review date for each tool.
  • Run tools only from dedicated, registered testing hosts with narrowly scoped EDR exclusions.
  • Require signed scope and rules of engagement before any test, including tester source IPs shared with the SOC.
  • Get provider permission before testing any SaaS, hosting or third-party asset.
  • Verify signatures or checksums for every tool download and pin versions.
  • Encrypt, minimise and delete captured credentials and data at engagement close, and rotate exposed secrets.
  • Alert on testing tool signatures from unregistered hosts and measure detection of authorised tests.

Standards and references

Related NHI Mgmt Group resources: Penetration Testing Guide · Red Teaming Guide · Purple Teaming Guide · Building a Cybersecurity Home Lab Guide · Penetration Test Scoping Checklist

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.