Open-Source Cybersecurity Tools: Penetration Testing & Red Team

← Back to Open-Source Cybersecurity Tools Hub | Full Open Source Catalog | Main Atlas

This category contains 337 documented tools. It focuses on capabilities used for security control validation through offensive simulation and exploitation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Category Evaluation Checklist

• Coverage depth against your highest-priority threats and compliance obligations.
• Operational overhead for deployment, tuning, and long-term maintenance.
• Signal quality versus analyst workload and false-positive pressure.
• Integration fit with SIEM, ticketing, identity, cloud, and engineering workflows.
• Governance readiness including auditability, ownership clarity, and change control.

Jump by Name

# | 0 | 2 | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | R | S | T | U | V | W | X | Z

Letter

This letter section contains 20 tools.

"Hacking"

• Website: https://github.com/carpedm20/awesome-hacking
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Malware Analysis, Awesome Forensics

What it does: "Hacking" is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Forensics > Related Awesome Lists.

Back to Name Jump

AppMon

• Website: https://github.com/dpnishant/appmon
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: AppMon is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Monitor and analyze mobile apps on Android and iOS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

AppUse

• Website: https://appuse.org
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: AppUse is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open-source Android security testing platform.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

BlackArch

• Website: https://blackarch.org
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools, Awesome CTF

What it does: BlackArch is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Arch Linux-based distribution for penetration testers and security researchers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Operating Systems.

Back to Name Jump

BuiltWith

• Website: https://builtwith.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: BuiltWith is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Identify technologies, frameworks, and services used by websites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Information Gathering > Passive Information Gathering.

Back to Name Jump

Burp Suite Mobile Assistant

• Website: https://portswigger.net/burp/documentation/desktop/tools/mobile-assistant
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Burp Suite Mobile Assistant is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Integrated mobile assistant for Burp Suite.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

Dradis

• Website: https://dradisframework.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Dradis is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open-source collaboration and reporting tool for information security teams.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing.

Back to Name Jump

Drozer

• Website: https://github.com/mwrlabs/drozer
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Drozer is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Android security assessment framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

Frida

• Website: https://frida.re
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Frida is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Dynamic instrumentation toolkit for developers, reverse engineers, and security researchers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

HTTrack

• Website: https://www.httrack.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: HTTrack is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Website mirroring tool for offline analysis.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Information Gathering > Passive Information Gathering.

Back to Name Jump

Magisk

• Website: https://github.com/topjohnwu/Magisk
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Magisk is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Rooting solution with systemless root for Android.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

MobSF

• Website: https://github.com/MobSF/Mobile-Security-Framework-MobSF
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools, Awesome Forensics

What it does: MobSF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: An automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis and security assessment framework capable of performing static and dynamic analysis.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Mobile Penetration Testing.

Back to Name Jump

Netcraft

• Website: https://sitereport.netcraft.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Netcraft is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Checking the technology and infrastructure of any site.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Information Gathering > Passive Information Gathering.

Back to Name Jump

Netdiscover

• Website: https://github.com/alexxy/netdiscover
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Netdiscover is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Active and passive ARP reconnaissance tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Information Gathering > Active Information Gathering.

Back to Name Jump

Pentoo

• Website: https://www.pentoo.ch
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Pentoo is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Live CD and installable Linux distribution based on Gentoo optimized for penetration testing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Linux Distributions.

Back to Name Jump

Sqlmap

• Website: https://sqlmap.org
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: Sqlmap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated SQL injection and database takeover tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing.

Back to Name Jump

WHOIS

• Website: https://www.iana.org/whois
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cyber Security Tools

What it does: WHOIS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Query domain registration and ownership information.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Penetration Testing > Information Gathering > Passive Information Gathering.

Back to Name Jump

.NET Programming

• Website: https://github.com/quozd/awesome-dotnet
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: .NET Programming is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Software framework for Microsoft Windows platform development.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

@h3xstream

• Website: https://twitter.com/h3xstream/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: @h3xstream is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Security Researcher, interested in web security, crypto, pentest, static analysis but most of all, samy is my hero.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Twitter Users.

Back to Name Jump

@HackwithGitHub

• Website: https://twitter.com/HackwithGithub
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: @HackwithGitHub is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Initiative to showcase open source hacking tools for hackers and pentesters.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Twitter Users.

Back to Name Jump

Letter 0

This letter section contains 1 tools.

0e85dc6eaf

• Website: https://github.com/0e85dc6eaf/CTF-Writeups
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: 0e85dc6eaf is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Write-ups for CTF challenges by 0e85dc6eaf.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

Letter 2

This letter section contains 1 tools.

2600: The Hacker Quarterly

• Website: https://www.2600.com/Magazine/DigitalEditions
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: 2600: The Hacker Quarterly is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: American publication about technology and computer "underground" culture.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Periodicals.

Back to Name Jump

Letter A

This letter section contains 22 tools.

Active Directory and Privilege Escalation (ADAPE)

• Website: https://github.com/hausec/ADAPE-Script
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Active Directory and Privilege Escalation (ADAPE) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Umbrella script that automates numerous useful PowerShell modules to discover security misconfigurations and attempt privilege escalation against Active Directory.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

Advanced Penetration Testing by Wil Allsopp, 2017

• Website: https://www.amazon.com/Advanced-Penetration-Testing-Hacking-Networks/dp/1119367689/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Advanced Penetration Testing by Wil Allsopp, 2017 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Advanced Penetration Testing for Highly-Secured Environments by Lee Allen, 2012

• Website: http://www.packtpub.com/networking-and-servers/advanced-penetration-testing-highly-secured-environments-ultimate-security-gu
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Advanced Penetration Testing for Highly-Secured Environments by Lee Allen, 2012 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Advanced Persistent Threat Hacking: The Art and Science of Hacking Any Organization by Tyler Wrightson, 2014

• Website: http://www.amazon.com/Advanced-Persistent-Threat-Hacking-Organization/dp/0071828362
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Advanced Persistent Threat Hacking: The Art and Science of Hacking Any Organization by Tyler Wrightson, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Alexa Top 1 Million Security - Hacking the Big Ones

• Website: https://slashcrypto.org/data/itsecx2018.pdf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Alexa Top 1 Million Security - Hacking the Big Ones is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Miscellaneous.

Back to Name Jump

Android Exploits

• Website: https://github.com/sundaysec/Android-Exploits
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Android Exploits is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Guide on Android Exploitation and Hacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Android Tamer

• Website: https://androidtamer.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: Android Tamer is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Distribution built for Android security professionals that includes tools required for Android security testing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

Arch Linux Penetration Tester

• Website: https://hub.docker.com/r/noncetonic/archlinux-pentest-lxde
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Arch Linux Penetration Tester is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: System > Tools > Docker Images for Penetration Testing & Security.

Back to Name Jump

ArchStrike

• Website: https://archstrike.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ArchStrike is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Arch GNU/Linux repository for security professionals and enthusiasts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

ARIZONA CYBER WARFARE RANGE

• Website: http://azcwr.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ARIZONA CYBER WARFARE RANGE is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: 24x7 live fire exercises for beginners through real world operations; capability for upward progression into the real world of cyber warfare.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Security Education Courses.

Back to Name Jump

Armitage

• Website: http://fastandeasyhacking.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Armitage is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Java-based GUI front-end for the Metasploit Framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Multi-paradigm Frameworks.

Back to Name Jump

Astra

• Website: https://github.com/flipkart-incubator/astra
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Astra is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated Security Testing For REST API's by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Penetration Testing.

Back to Name Jump

AT Commands

• Website: https://atcommands.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: AT Commands is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Use AT commands over an Android device's USB port to rewrite device firmware, bypass security mechanisms, exfiltrate sensitive information, perform screen unlocks, and inject touch events.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Physical Access Tools.

Back to Name Jump

Atomic Red Team

• Website: https://atomicredteam.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cybersecurity Blue Team

What it does: Atomic Red Team is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Library of simple, automatable tests to execute for testing security controls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Cybersecurity Blue Team > Preparedness training and wargaming.

Back to Name Jump

AttifyOS

• Website: https://github.com/adi0x90/attifyos
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: AttifyOS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: GNU/Linux distribution focused on tools useful during Internet of Things (IoT) security assessments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

autochrome

• Website: https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2017/march/autochrome/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: autochrome is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Chrome browser profile preconfigured with appropriate settings needed for web application testing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

Awesome Pentest

• Website: https://github.com/enaqx/awesome-pentest
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Forensics

What it does: Awesome Pentest is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A collection of awesome penetration testing resources, tools and other shiny things.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Other Awesome Lists > Other Security Awesome Lists.

Back to Name Jump

AWS PENETRATION TESTING PART 1. S3 BUCKETS

• Website: https://www.virtuesecurity.com/aws-penetration-testing-part-1-s3-buckets/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: AWS PENETRATION TESTING PART 1. S3 BUCKETS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > AWS.

Back to Name Jump

AWS PENETRATION TESTING PART 2. S3, IAM, EC2

• Website: https://www.virtuesecurity.com/aws-penetration-testing-part-2-s3-iam-ec2/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: AWS PENETRATION TESTING PART 2. S3, IAM, EC2 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > AWS.

Back to Name Jump

AWS Tool Arsenal

• Website: https://github.com/toniblyx/my-arsenal-of-aws-security-tools
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: AWS Tool Arsenal is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: List of tools for testing and securing AWS environments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

aws_pwn

• Website: https://github.com/dagrz/aws_pwn
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: aws_pwn is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A collection of AWS penetration testing junk by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Penetration Testing.

Back to Name Jump

Axiom

• Website: https://github.com/pry0cc/axiom
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security

What it does: Axiom is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Axiom is a dynamic infrastructure framework to efficiently work with multi-cloud environments, build and deploy repeatable infrastructure focussed on offensive and defensive security.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Red Team Infrastructure Deployment.

Back to Name Jump

Letter B

This letter section contains 19 tools.

BalCCon

• Website: https://www.balccon.org
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: BalCCon is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Balkan Computer Congress, annually held in Novi Sad, Serbia.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Europe.

Back to Name Jump

Bamboofox

• Website: https://bamboofox.github.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Bamboofox is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Chinese resources to learn CTF.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wikis.

Back to Name Jump

bandit

• Website: https://pypi.python.org/pypi/bandit/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: bandit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Security oriented static analyser for Python code.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

Beelogger

• Website: https://github.com/4w4k3/BeeLogger
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Beelogger is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool for generating keylooger.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

Bella

• Website: https://github.com/kdaoudieh/Bella
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Bella is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Pure Python post-exploitation data mining and remote administration tool for macOS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > macOS Utilities.

Back to Name Jump

Best Linux Penetration Testing Distributions @ CyberPunk

• Website: https://www.cyberpunk.rs/category/pentest-linux-distros
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security

What it does: Best Linux Penetration Testing Distributions @ CyberPunk is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Description of main penetration testing distributions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Operating Systems > Online resources.

Back to Name Jump

Best Linux Penetration Testing Distributions @ CyberPunk

• Website: https://n0where.net/best-linux-penetration-testing-distributions/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Best Linux Penetration Testing Distributions @ CyberPunk is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Description of main penetration testing distributions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: OS > Online resources.

Back to Name Jump

Black Hat Python: Python Programming for Hackers and Pentesters by Justin Seitz, 2014

• Website: http://www.amazon.com/Black-Hat-Python-Programming-Pentesters/dp/1593275900
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Black Hat Python: Python Programming for Hackers and Pentesters by Justin Seitz, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

BlackArch

• Website: https://www.blackarch.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: BlackArch is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Arch GNU/Linux-based distribution for penetration testers and security researchers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

Bless

• Website: https://github.com/bwrsandman/Bless
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Bless is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: High quality, full featured, cross-platform graphical hex editor written in Gtk#.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

Bloodhound

• Website: https://github.com/adaptivethreat/Bloodhound/wiki
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Bloodhound is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Graphical Active Directory trust relationship explorer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Blue Team

• Website: https://github.com/fabacab/awesome-cybersecurity-blueteam
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Blue Team is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Awesome resources, tools, and other shiny things for cybersecurity blue teams.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Boston Key Party CTF

• Website: http://bostonkeyparty.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Boston Key Party CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Browser Exploitation Framework (BeEF)

• Website: https://github.com/beefproject/beef
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: Browser Exploitation Framework (BeEF) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Command and control server for delivering exploits to commandeered Web browsers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

BruteForce Wallet

• Website: https://github.com/glv2/bruteforce-wallet
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: BruteForce Wallet is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Find the password of an encrypted wallet file (i.e. wallet.dat).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

BTFM: Blue Team Field Manual by Alan J White & Ben Clark, 2017

• Website: https://www.amazon.de/Blue-Team-Field-Manual-BTFM/dp/154101636X
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: BTFM: Blue Team Field Manual by Alan J White & Ben Clark, 2017 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Bug Hunter's Diary by Tobias Klein, 2011

• Website: https://nostarch.com/bughunter
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Bug Hunter's Diary by Tobias Klein, 2011 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Burp Suite

• Website: https://portswigger.net/burp/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools, Awesome CTF, Awesome Web Security

What it does: Burp Suite is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Burp Suite is an integrated platform for performing security testing of web applications by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Intercepting Web proxies.

Back to Name Jump

Buscador

• Website: https://inteltechniques.com/buscador/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Buscador is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: GNU/Linux virtual machine that is pre-configured for online investigators.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

Letter C

This letter section contains 32 tools.

C/C++ Programming

• Website: https://github.com/fffaraz/awesome-cpp
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: C/C++ Programming is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: One of the main language for open source security tools.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

CACTUSTORCH

• Website: https://github.com/mdsecactivebreach/CACTUSTORCH
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: CACTUSTORCH is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Payload Generation for Adversary Simulations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Tools.

Back to Name Jump

Captf

• Website: http://captf.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Captf is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Dumped CTF challenges and materials by psifertex.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

Catphish

• Website: https://github.com/ring0lab/catphish
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Catphish is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool for phishing and corporate espionage written in Ruby.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

CCC

• Website: https://events.ccc.de/congress/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: CCC is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Annual meeting of the international hacker scene in Germany.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Europe.

Back to Name Jump

CeWL

• Website: https://digi.ninja/projects/cewl.php
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: CeWL is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Generates custom wordlists by spidering a target's website and collecting unique words.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

CHCon

• Website: https://chcon.nz
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: CHCon is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Christchurch Hacker Con, Only South Island of New Zealand hacker con.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Zealandia.

Back to Name Jump

checksec.sh

• Website: https://www.trapkit.de/tools/checksec.html
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: checksec.sh is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Shell script designed to test what standard Linux OS and PaX security features are being used.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > GNU/Linux Utilities.

Back to Name Jump

ChipWhisperer

• Website: http://chipwhisperer.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ChipWhisperer is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Complete open-source toolchain for side-channel power analysis and glitching attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Side-channel Tools.

Back to Name Jump

Ciphey

• Website: https://github.com/ciphey/ciphey
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: Ciphey is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated decryption tool using artificial intelligence and natural language processing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > CTF Tools.

Back to Name Jump

Client XSS Introduction

• Website: https://domgo.at/cxss/intro
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Client XSS Introduction is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Comprehensive introduction to client-side cross-site scripting (XSS) attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Online Penetration Testing Resources.

Back to Name Jump

Cloakify

• Website: https://github.com/TryCatchHCF/Cloakify
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Cloakify is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Textual steganography toolkit that converts any filetype into lists of everyday strings.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Steganography Tools.

Back to Name Jump

Cloud Container Attack Tool (CCAT)

• Website: https://rhinosecuritylabs.com/aws/cloud-container-attack-tool/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Cloud Container Attack Tool (CCAT) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool for testing security of container environments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Cloud Platform Attack Tools.

Back to Name Jump

CloudHunter

• Website: https://github.com/belane/CloudHunter
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: CloudHunter is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Looks for AWS, Azure and Google cloud storage buckets and lists permissions for vulnerable buckets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Cloud Platform Attack Tools.

Back to Name Jump

Cloudsplaining

• Website: https://cloudsplaining.readthedocs.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Cloudsplaining is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Identifies violations of least privilege in AWS IAM policies and generates a pretty HTML report with a triage worksheet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Cloud Platform Attack Tools.

Back to Name Jump

Codegate CTF

• Website: http://ctf.codegate.org/html/Main.html?lang=eng
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Codegate CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Commando VM

• Website: https://github.com/fireeye/commando-vm
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Commando VM is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated installation of over 140 Windows software packages for penetration testing and red teaming.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Commix

• Website: https://github.com/commixproject/commix
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF, Awesome Web Security

What it does: Commix is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated all-in-one operating system command injection and exploitation tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web injection tools.

Back to Name Jump

Covenant

• Website: https://github.com/cobbr/Covenant
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Covenant is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: ASP.NET Core application that serves as a collaborative command and control platform for red teamers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

cppcheck

• Website: http://cppcheck.sourceforge.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: cppcheck is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Extensible C/C++ static analyzer focused on finding bugs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

CSAW CTF

• Website: https://ctf.isis.poly.edu/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: CSAW CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

csp evaluator

• Website: https://csper.io/evaluator
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: csp evaluator is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A tool for evaluating content-security-policies by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > XSS - Cross-Site Scripting.

Back to Name Jump

cSploit

• Website: https://github.com/cSploit/android
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: cSploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Advanced IT security professional toolkit on Android featuring an integrated Metasploit daemon and MITM capabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Android Utilities.

Back to Name Jump

CTF archives (shell-storm)

• Website: http://shell-storm.org/repo/CTF/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking, Awesome CTF

What it does: CTF archives (shell-storm) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

CTF Field Guide

• Website: https://trailofbits.github.io/ctf/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF, Awesome Web Security

What it does: CTF Field Guide is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Everything you need to win your next CTF competition.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > CTF Tools.

Back to Name Jump

CTF Resources

• Website: http://ctfs.github.io/resources/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: CTF Resources is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Start Guide maintained by community.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Tutorials.

Back to Name Jump

CTF write-ups (community)

• Website: https://github.com/ctfs/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: CTF write-ups (community) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF challenges + write-ups archive maintained by the community.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

ctf-tools

• Website: https://github.com/zardus/ctf-tools
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: ctf-tools is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Collection of setup scripts to install various security research tools easily and quickly deployable to new machines.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > CTF Tools.

Back to Name Jump

CTFTime Scrapper

• Website: https://github.com/abdilahrf/CTFWriteupScrapper
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: CTFTime Scrapper is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Scraps all writeup from CTF Time and organize which to read first.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

CTFTime.org

• Website: https://ctftime.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: CTFTime.org is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Directory of upcoming and archive of past Capture The Flag (CTF) competitions with links to challenge writeups.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events.

Back to Name Jump

ctftool

• Website: https://github.com/taviso/ctftool
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: ctftool is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Interactive Collaborative Translation Framework (CTF) exploration tool capable of launching cross-session edit session attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

cwe_checker

• Website: https://github.com/fkie-cad/cwe_checker
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: cwe_checker is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Suite of tools built atop the Binary Analysis Platform (BAP) to heuristically detect CWEs in compiled binaries and firmware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

Letter D

This letter section contains 13 tools.

DAws

• Website: https://github.com/dotcppfile/DAws
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DAws is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Advanced Web shell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

DeathStar

• Website: https://github.com/byt3bl33d3r/DeathStar
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DeathStar is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Python script that uses Empire's RESTful API to automate gaining Domain Admin rights in Active Directory environments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

DEF CON

• Website: https://www.defcon.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DEF CON is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Annual hacker convention in Las Vegas.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > North America.

Back to Name Jump

DEF CON

• Website: https://legitbs.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: DEF CON is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

DET

• Website: https://github.com/sensepost/DET
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DET is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Proof of concept to perform data exfiltration using either single or multiple channel(s) at the same time.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Exfiltration Tools.

Back to Name Jump

Docker Metasploit

• Website: https://hub.docker.com/r/phocean/msf/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Docker Metasploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: System > Tools > Docker Images for Penetration Testing & Security.

Back to Name Jump

DomainPasswordSpray

• Website: https://github.com/dafthack/DomainPasswordSpray
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DomainPasswordSpray is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool written in PowerShell to perform a password spray attack against users of a domain.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools > Password Spraying Tools.

Back to Name Jump

dos-over-tor

• Website: https://github.com/skizap/dos-over-tor
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: dos-over-tor is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Proof of concept denial of service over Tor stress test tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Anonymity Tools > Tor Tools.

Back to Name Jump

DotDotPwn

• Website: https://dotdotpwn.blogspot.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: DotDotPwn is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Directory traversal fuzzer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web path discovery and bruteforcing tools.

Back to Name Jump

Dradis

• Website: https://dradis.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Dradis is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open-source reporting and collaboration tool for IT security professionals.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

dtd-finder

• Website: https://github.com/GoSecure/dtd-finder
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: dtd-finder is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: List DTDs and generate XXE payloads using those local DTDs by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > XXE.

Back to Name Jump

duplicut

• Website: https://github.com/nil0x42/duplicut
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: duplicut is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Quickly remove duplicates, without changing the order, and without getting OOM on huge wordlists.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

DVCS Ripper

• Website: https://github.com/kost/dvcs-ripper
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF, Awesome Web Security

What it does: DVCS Ripper is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Rip web accessible (distributed) version control systems: SVN/GIT/HG... by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web-accessible source code ripping tools.

Back to Name Jump

Letter E

This letter section contains 8 tools.

echoCTF.RED

• Website: https://github.com/echoCTF/echoCTF.RED
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: echoCTF.RED is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Develop, deploy and maintain your own CTF infrastructure.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

echoCTF.RED

• Website: https://echoctf.red/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: echoCTF.RED is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Online CTF with a variety of targets to attack.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

Effective Software Testing, 2021

• Website: https://www.manning.com/books/effective-software-testing
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Effective Software Testing, 2021 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Empire

• Website: https://www.powershellempire.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Empire is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Pure PowerShell post-exploitation agent.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Endgame

• Website: https://endgame.readthedocs.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Endgame is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: AWS Pentesting tool that lets you use one-liner commands to backdoor an AWS account's resources with a rogue AWS account.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Cloud Platform Attack Tools.

Back to Name Jump

Evilginx2

• Website: https://github.com/kgretzky/evilginx2
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Evilginx2 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Standalone Machine-in-the-Middle (MitM) reverse proxy attack framework for setting up phishing pages capable of defeating most forms of 2FA security schemes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

EvilOSX

• Website: https://github.com/Marten4n6/EvilOSX
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: EvilOSX is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Modular RAT that uses numerous evasion and exfiltration techniques out-of-the-box.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > macOS Utilities.

Back to Name Jump

ExifTool

• Website: https://www.sno.phy.queensu.ca/~phil/exiftool/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ExifTool is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Platform-independent Perl library plus a command-line application for reading, writing and editing meta information in a wide variety of files.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > File Format Analysis Tools.

Back to Name Jump

Letter F

This letter section contains 7 tools.

Faraday

• Website: https://github.com/infobyte/faraday
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Faraday is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Multiuser integrated pentesting environment for red teams performing cooperative penetration tests, security audits, and risk assessments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Multi-paradigm Frameworks.

Back to Name Jump

FiercePhish

• Website: https://github.com/Raikia/FiercePhish
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: FiercePhish is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Full-fledged phishing framework to manage all phishing engagements.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

FindBugs

• Website: http://findbugs.sourceforge.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: FindBugs is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Free software static analyzer to look for bugs in Java code.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

FLAWS

• Website: http://flaws.cloud/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: FLAWS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Amazon AWS CTF challenge - Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Practices > AWS.

Back to Name Jump

Frhed

• Website: http://frhed.sourceforge.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Frhed is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Binary file editor for Windows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

FSec

• Website: http://fsec.foi.hr
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: FSec is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: FSec - Croatian Information Security Gathering in Varaždin, Croatia.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Europe.

Back to Name Jump

FuzzDB

• Website: https://github.com/fuzzdb-project/fuzzdb
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: FuzzDB is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Dictionary of attack patterns and primitives for black-box application fault injection and resource discovery.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

Letter G

This letter section contains 11 tools.

Gauntlt

• Website: http://gauntlt.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cybersecurity Blue Team

What it does: Gauntlt is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Pentest applications during routine continuous integration build pipelines.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Cybersecurity Blue Team > DevSecOps.

Back to Name Jump

GCPBucketBrute

• Website: https://github.com/RhinoSecurityLabs/GCPBucketBrute
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: GCPBucketBrute is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Script to enumerate Google Storage buckets, determine what access you have to them, and determine if they can be privilege escalated.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Cloud Platform Attack Tools.

Back to Name Jump

Ghost in the Shellcode

• Website: http://ghostintheshellcode.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Ghost in the Shellcode is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Ghost in the Wires by Kevin D. Mitnick & William L. Simon, 2011

• Website: http://www.hachettebookgroup.com/titles/kevin-mitnick/ghost-in-the-wires/9780316134477/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Ghost in the Wires by Kevin D. Mitnick & William L. Simon, 2011 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Books.

Back to Name Jump

git-dumper

• Website: https://github.com/arthaud/git-dumper
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: git-dumper is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool to dump a git repository from a website.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web-accessible source code ripping tools.

Back to Name Jump

GitPhish

• Website: https://github.com/praetorian-inc/GitPhish
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: GitPhish is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: GitHub Device Code phishing security assessment tool with dynamic device-code generation and automated landing page deployment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

GitTools

• Website: https://github.com/internetwache/GitTools
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: GitTools is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automatically find and download Web-accessible .git repositories.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web-accessible source code ripping tools.

Back to Name Jump

gobuster

• Website: https://github.com/OJ/gobuster
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: gobuster is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Lean multipurpose brute force search/fuzzing tool for Web (and DNS) reconnaissance.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

GoCrack

• Website: https://github.com/fireeye/gocrack
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: GoCrack is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Management Web frontend for distributed password cracking sessions using hashcat (or other supported tools) written in Go.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

grayhatwarfare

• Website: https://buckets.grayhatwarfare.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: grayhatwarfare is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Public buckets by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Penetration Testing.

Back to Name Jump

GTFOBins

• Website: https://gtfobins.github.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: GTFOBins is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Curated list of Unix binaries that can be used to bypass local security restrictions in misconfigured systems.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

Letter H

This letter section contains 20 tools.

Hachoir

• Website: https://hachoir.readthedocs.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hachoir is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Python library to view and edit a binary stream as tree of fields and tools for metadata extraction.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > File Format Analysis Tools.

Back to Name Jump

Hack This Site!

• Website: https://www.hackthissite.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking, Awesome CTF

What it does: Hack This Site! is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: a free, safe and legal training ground for hackers to test and expand their hacking skills.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

hack.lu CTF

• Website: http://hack.lu/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: hack.lu CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Hacker101

• Website: https://www.hacker101.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF, Awesome Web Security

What it does: Hacker101 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF from HackerOne.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Digests.

Back to Name Jump

Hacking home routers from the Internet

• Website: https://medium.com/@radekk/hackers-can-get-access-to-your-home-router-1ddadd12a7a7
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Hacking home routers from the Internet is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > DNS Rebinding.

Back to Name Jump

Hacking with a Heads Up Display

• Website: https://segment.com/blog/hacking-with-a-heads-up-display/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Hacking with a Heads Up Display is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Miscellaneous.

Back to Name Jump

Hacking with JSP Shells

• Website: https://blog.netspi.com/hacking-with-jsp-shells/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Hacking with JSP Shells is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > Web Shell.

Back to Name Jump

HackTheArch

• Website: https://github.com/mcpa-stlouis/hack-the-arch
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: HackTheArch is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF scoring platform.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

HackTheBox

• Website: https://academy.hackthebox.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: HackTheBox is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: While not directly related to threat detection, the website features training modules on general security and offensive topics that can be beneficial for junior SOC analysts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Trainings.

Back to Name Jump

HackThisSite

• Website: https://github.com/HackThisSite/CTF-Writeups
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: HackThisSite is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF write-ups repo maintained by HackThisSite team.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

Hackxor

• Website: http://hackxor.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Hackxor is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Realistic web application hacking game - Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Practices > Application.

Back to Name Jump

Hashcat

• Website: http://hashcat.net/hashcat/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hashcat is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The more fast hash cracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

hate_crack

• Website: https://github.com/trustedsec/hate_crack
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: hate_crack is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool for automating cracking methodologies through Hashcat.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

Hex Fiend

• Website: http://ridiculousfish.com/hexfiend/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hex Fiend is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Fast, open source, hex editor for macOS with support for viewing binary diffs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

hexedit

• Website: https://github.com/pixel/hexedit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: hexedit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Simple, fast, console-based hex editor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

HexEdit.js

• Website: https://hexed.it
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: HexEdit.js is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Browser-based hex editing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

Hexinator

• Website: https://hexinator.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hexinator is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: World's finest (proprietary, commercial) Hex Editor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

Hexway Hive

• Website: https://hexway.io/hive/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hexway Hive is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Commercial collaboration, data aggregation, and reporting framework for red teams with a limited free self-hostable option.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

How to Get Started in CTF

• Website: https://www.endgame.com/blog/how-get-started-ctf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: How to Get Started in CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Short guideline for CTF beginners by Endgame.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Tutorials.

Back to Name Jump

Hwacha

• Website: https://github.com/n00py/Hwacha
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Hwacha is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Post-exploitation tool to quickly execute payloads via SSH on one or more Linux systems simultaneously.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > GNU/Linux Utilities.

Back to Name Jump

Letter I

This letter section contains 9 tools.

I2P

• Website: https://geti2p.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: I2P is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome OSINT > ↑ Privacy and Encryption Tools.

Back to Name Jump

InfoSec § Hacking challenges

• Website: https://github.com/AnarchoTechNYC/meta/wiki/InfoSec#hacking-challenges
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: InfoSec § Hacking challenges is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Comprehensive directory of CTFs, wargames, hacking challenge websites, pentest practice lab exercises, and more.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Infosecurity Europe

• Website: http://www.infosecurityeurope.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Infosecurity Europe is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Europe's number one information security event, held in London, UK.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Europe.

Back to Name Jump

Insomni’hack

• Website: https://insomnihack.ch/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Insomni’hack is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Intelligent, Automated Red Team Emulation

• Website: https://dl.acm.org/citation.cfm?id=2991111
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection, Awesome Fuzzing

What it does: Intelligent, Automated Red Team Emulation is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Fuzzing > Papers > ACM Conference on Computer and Communications Security (ACM CCS).

Back to Name Jump

Intigriti

• Website: https://www.intigriti.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Intigriti is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Europe's #1 ethical hacking and bug bounty program.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Wargame > Bug bounty - Earn Some Money.

Back to Name Jump

Inveigh

• Website: https://github.com/Kevin-Robertson/Inveigh
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Inveigh is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Windows PowerShell ADIDNS/LLMNR/mDNS/NBNS spoofer/machine-in-the-middle tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Iodine

• Website: https://code.kryo.se/iodine/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Iodine is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tunnel IPv4 data through a DNS server; useful for exfiltration from networks where Internet access is firewalled, but DNS queries are allowed.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Exfiltration Tools.

Back to Name Jump

ISIS Lab

• Website: https://github.com/isislab/Project-Ideas/wiki
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: ISIS Lab is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF Wiki by Isis lab.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wikis.

Back to Name Jump

Letter J

This letter section contains 5 tools.

JavaScript Programming

• Website: https://github.com/sorrycc/awesome-javascript
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: JavaScript Programming is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: In-browser development and scripting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

John the Ripper

• Website: http://www.openwall.com/john/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: John the Ripper is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A fast password cracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

JShell

• Website: https://github.com/s0md3v/JShell
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: JShell is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Get a JavaScript shell with XSS by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > XSS - Cross-Site Scripting.

Back to Name Jump

Juice Shop CTF

• Website: https://github.com/bkimminich/juice-shop-ctf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Juice Shop CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Scripts and tools for hosting a CTF on easily.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

JWT Cracker

• Website: https://github.com/lmammino/jwt-cracker
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: JWT Cracker is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Simple HS256 JSON Web Token (JWT) token brute force cracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

Letter K

This letter section contains 2 tools.

Kali Linux Tools

• Website: http://tools.kali.org/tools-listing
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Kali Linux Tools is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: List of tools present in Kali Linux.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

kalitorify

• Website: https://github.com/brainfuckSec/kalitorify
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: kalitorify is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Transparent proxy through Tor for Kali Linux OS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Anonymity Tools > Tor Tools.

Back to Name Jump

Letter L

This letter section contains 5 tools.

Lair

• Website: https://github.com/lair-framework/lair/wiki
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Lair is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Reactive attack collaboration framework and web application built with meteor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

LaZagne

• Website: https://github.com/AlessandroZ/LaZagne
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: LaZagne is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Credentials recovery project.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

liffy

• Website: https://github.com/hvqzao/liffy
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: liffy is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: LFI exploitation tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web file inclusion tools.

Back to Name Jump

list of Windows API and their potential use in offensive security

• Website: https://malapi.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome SOC

What it does: list of Windows API and their potential use in offensive security is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: To go further > Must read.

Back to Name Jump

LOLBAS (Living Off The Land Binaries and Scripts)

• Website: https://lolbas-project.github.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: LOLBAS (Living Off The Land Binaries and Scripts) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Documents binaries, scripts, and libraries that can be used for "Living Off The Land" techniques, i.e., binaries that can be used by an attacker to perform actions beyond their original purpose.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

Letter M

This letter section contains 16 tools.

MailSniper

• Website: https://github.com/dafthack/MailSniper
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: MailSniper is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Modular tool for searching through email in a Microsoft Exchange environment, gathering the Global Address List from Outlook Web Access (OWA) and Exchange Web Services (EWS), and more.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

mcafee-xpass

• Website: https://github.com/SujalMeghwal/mcafee-xpass
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: mcafee-xpass is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Decrypts encrypted administrator passwords from McAfee Sitelist.xml files using known XOR + 3DES logic. Useful for Red Team privilege escalation and forensic recovery.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

Mellivora

• Website: https://github.com/Nakiami/mellivora
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Mellivora is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A CTF engine written in PHP.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

Merlin

• Website: https://github.com/Ne0nd0g/merlin
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Merlin is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Cross-platform post-exploitation HTTP/2 Command and Control server and agent written in Golang.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

Metadata Anonymization Toolkit (MAT)

• Website: https://0xacab.org/jvoisin/mat2
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Metadata Anonymization Toolkit (MAT) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Metadata removal tool, supporting a wide range of commonly used file formats, written in Python3.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Anonymity Tools.

Back to Name Jump

Metasploit

• Website: https://www.metasploit.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: Metasploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Software for offensive security teams to help verify vulnerabilities and manage security assessments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Multi-paradigm Frameworks.

Back to Name Jump

Metasploit

• Website: http://www.metasploit.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Metasploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Penetration testing software.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Solve > Exploits.

Back to Name Jump

Metasploit: The Penetration Tester's Guide by David Kennedy et al., 2011

• Website: https://nostarch.com/metasploit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Metasploit: The Penetration Tester's Guide by David Kennedy et al., 2011 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Microcorruption

• Website: https://microcorruption.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Microcorruption is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Embedded security CTF.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

mimikatz

• Website: http://blog.gentilkiwi.com/mimikatz
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: mimikatz is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Credentials extraction tool for Windows operating system.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

MITRE's Adversarial Tactics, Techniques & Common Knowledge (ATT&CK)

• Website: https://attack.mitre.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: MITRE's Adversarial Tactics, Techniques & Common Knowledge (ATT&CK) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Curated knowledge base and model for cyber adversary behavior.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Online Penetration Testing Resources.

Back to Name Jump

Modlishka

• Website: https://github.com/drk1wi/Modlishka
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Modlishka is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Flexible and powerful reverse proxy with real-time two-factor authentication.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

MotherFucking-CTF

• Website: https://github.com/andreafioraldi/motherfucking-ctf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: MotherFucking-CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Badass lightweight plaform to host CTFs. No JS involved.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

Movies For Hacker

• Website: https://github.com/k4m4/movies-for-hackers
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Hacking

What it does: Movies For Hacker is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A curated list of movies every hacker & cyberpunk must watch.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Other Awesome Lists > Other Common Awesome Lists.

Back to Name Jump

MPT

• Website: https://github.com/ByteSnipers/mobile-pentest-toolkit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: MPT is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: MPT (Mobile Pentest Toolkit) is a must-have solutions for your android penetration testing workflow. It allows you to automate tasks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Android Utilities.

Back to Name Jump

Mzfr

• Website: https://github.com/mzfr/ctf-writeups/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Mzfr is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF competition write-ups by mzfr.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

Letter N

This letter section contains 5 tools.

NFS PENETRATION TESTING ACADEMY

• Website: https://pentestacademy.wordpress.com/2017/09/20/nfs/?t=1&cn=ZmxleGlibGVfcmVjc18y&refsrc=email&iid=b34422ce15164e99a193fea0ccc7a02f&uid=1959680352&nid=244+289476616
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: NFS PENETRATION TESTING ACADEMY is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > NFS.

Back to Name Jump

NightShade

• Website: https://github.com/UnrealAkama/NightShade
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: NightShade is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A simple security CTF framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

No Tech Hacking by Johnny Long & Jack Wiles, 2008

• Website: https://www.elsevier.com/books/no-tech-hacking/mitnick/978-1-59749-215-7
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: No Tech Hacking by Johnny Long & Jack Wiles, 2008 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Books.

Back to Name Jump

Node.js Programming by @sindresorhus

• Website: https://github.com/sindresorhus/awesome-nodejs
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Node.js Programming by @sindresorhus is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Curated list of delightful Node.js packages and resources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

NoSQLmap

• Website: https://github.com/codingo/NoSQLMap
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: NoSQLmap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated NoSQL database enumeration and web application exploitation tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web injection tools.

Back to Name Jump

Letter O

This letter section contains 13 tools.

Offensive Security Training

• Website: https://www.offensive-security.com/information-security-training/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Offensive Security Training is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Training from BackTrack/Kali developers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Security Education Courses.

Back to Name Jump

Offensive Web Testing Framework (OWTF)

• Website: https://www.owasp.org/index.php/OWASP_OWTF
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Offensive Web Testing Framework (OWTF) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Python-based framework for pentesting Web applications based on the OWASP Testing Guide.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

official Kali Linux

• Website: https://hub.docker.com/r/kalilinux/kali-last-release/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: official Kali Linux is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: System > Tools > Docker Images for Penetration Testing & Security.

Back to Name Jump

OnionScan

• Website: https://onionscan.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: OnionScan is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tool for investigating the Dark Web by finding operational security issues introduced by Tor hidden service operators.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Anonymity Tools > Tor Tools.

Back to Name Jump

Open redirect/SSRF payload generator

• Website: https://tools.intigriti.io/redirector/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Open redirect/SSRF payload generator is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open redirect/SSRF payload generator by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > Server-Side Request Forgery.

Back to Name Jump

Open Security Training

• Website: http://opensecuritytraining.info/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Open Security Training is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Training material for computer security classes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Security Education Courses.

Back to Name Jump

Open Web Application Security Project (OWASP)

• Website: https://www.owasp.org/index.php/Main_Page
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Open Web Application Security Project (OWASP) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Worldwide not-for-profit charitable organization focused on improving the security of especially Web-based and Application-layer software.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Online Penetration Testing Resources.

Back to Name Jump

OpenCTF

• Website: https://github.com/easyctf/openctf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: OpenCTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF in a box. Minimal setup required.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

OpenToAll

• Website: https://github.com/OpenToAllCTF/Tips
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: OpenToAll is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF tips by OTA CTF team members.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wikis.

Back to Name Jump

OWASP Juice Shop

• Website: https://github.com/bkimminich/juice-shop#docker-container--
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome Web Security

What it does: OWASP Juice Shop is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Probably the most modern and sophisticated insecure web application - Written by and the team.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Name Jump

OWASP WebGoat Project 7.1 docker image

• Website: https://hub.docker.com/r/webgoat/webgoat-7.1/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: OWASP WebGoat Project 7.1 docker image is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: docker pull webgoat/webgoat-7.1.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Name Jump

OWASP WebGoat Project 8.0 docker image

• Website: https://hub.docker.com/r/webgoat/webgoat-8.0/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: OWASP WebGoat Project 8.0 docker image is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: docker pull webgoat/webgoat-8.0.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Name Jump

OWASP Zed Attack Proxy (ZAP)

• Website: https://www.zaproxy.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: OWASP Zed Attack Proxy (ZAP) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Feature-rich, scriptable HTTP intercepting proxy and fuzzer for penetration testing web applications.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Intercepting Web proxies.

Back to Name Jump

Letter P

This letter section contains 41 tools.

Parrot

• Website: https://parrotlinux.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Parrot is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Distribution similar to Kali, with support for multiple hardware architectures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

Payload Generation using SharpShooter

• Website: https://www.mdsec.co.uk/2018/03/payload-generation-using-sharpshooter/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: Payload Generation using SharpShooter is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Resources.

Back to Name Jump

payloadbox/command-injection-payload-list

• Website: https://github.com/payloadbox/command-injection-payload-list
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: payloadbox/command-injection-payload-list is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > Command Injection.

Back to Name Jump

payloadbox/open-redirect-payload-list

• Website: https://github.com/payloadbox/open-redirect-payload-list
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: payloadbox/open-redirect-payload-list is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > Open Redirect.

Back to Name Jump

payloadbox/sql-injection-payload-list

• Website: https://github.com/payloadbox/sql-injection-payload-list
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: payloadbox/sql-injection-payload-list is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > SQL Injection.

Back to Name Jump

payloadbox/xss-payload-list

• Website: https://github.com/payloadbox/xss-payload-list
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: payloadbox/xss-payload-list is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > XSS - Cross-Site Scripting.

Back to Name Jump

payloadbox/xxe-injection-payload-list

• Website: https://github.com/payloadbox/xxe-injection-payload-list
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: payloadbox/xxe-injection-payload-list is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > XXE - XML eXternal Entity.

Back to Name Jump

PayloadsAllTheThings

• Website: https://github.com/swisskyrepo/PayloadsAllTheThings
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Web Security

What it does: PayloadsAllTheThings is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A list of useful payloads and bypass for Web Application Security and Pentest/CTF.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Exploits & Payloads.

Back to Name Jump

PENETRATION TESTING AWS STORAGE: KICKING THE S3 BUCKET

• Website: https://rhinosecuritylabs.com/penetration-testing/penetration-testing-aws-storage/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: PENETRATION TESTING AWS STORAGE: KICKING THE S3 BUCKET is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by Dwight Hohnstein from .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > AWS.

Back to Name Jump

Penetration Testing Execution Standard (PTES)

• Website: http://www.pentest-standard.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Penetration Testing Execution Standard (PTES) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Documentation designed to provide a common language and scope for performing and reporting the results of a penetration test.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Online Penetration Testing Resources.

Back to Name Jump

Penetration Testing: A Hands-On Introduction to Hacking by Georgia Weidman, 2014

• Website: https://nostarch.com/pentesting
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Penetration Testing: A Hands-On Introduction to Hacking by Georgia Weidman, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Penetration Testing: Procedures & Methodologies by EC-Council, 2010

• Website: http://www.amazon.com/Penetration-Testing-Procedures-Methodologies-EC-Council/dp/1435483677
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Penetration Testing: Procedures & Methodologies by EC-Council, 2010 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Pentest Collaboration Framework (PCF)

• Website: https://gitlab.com/invuls/pentest-projects/pcf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Pentest Collaboration Framework (PCF) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open source, cross-platform, and portable toolkit for automating routine pentest processes with a team.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

Pentest reports

• Website: https://pentestreports.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Pentest reports is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Information hub with list of public penetration test reports, companies, tools and vulnerabilities all in one place.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Penetration Testing Report Templates.

Back to Name Jump

Pentest-Ground

• Website: https://pentest-ground.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Pentest-Ground is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Intentionally Vulnerable Systems.

Back to Name Jump

PENTEST-WIKI

• Website: https://github.com/nixawk/pentest-wiki
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: PENTEST-WIKI is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Free online security knowledge library for pentesters and researchers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Online Penetration Testing Resources.

Back to Name Jump

PentestBox

• Website: https://pentestbox.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: PentestBox is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open source pre-configured portable penetration testing environment for the Windows Operating System.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

PHD CTF

• Website: http://www.phdays.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: PHD CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

phishery

• Website: https://github.com/ryhanson/phishery
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: phishery is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: TLS/SSL enabled Basic Auth credential harvester.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

PhpSploit

• Website: https://github.com/nil0x42/phpsploit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking, Awesome Web Security

What it does: PhpSploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Full-featured C2 framework which silently persists on webserver via evil PHP oneliner. Built for stealth persistence, with many privilege-escalation & post-exploitation features.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

Phrack Magazine

• Website: http://www.phrack.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: Phrack Magazine is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: By far the longest running hacker zine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Periodicals.

Back to Name Jump

Pico CTF

• Website: https://picoctf.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Pico CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

PicoCTF

• Website: https://github.com/picoCTF/picoCTF
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: PicoCTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The platform used to run picoCTF. A great framework to host any CTF.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

PicoCTF

• Website: https://2019game.picoctf.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: PicoCTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: All year round ctf game. Questions from the yearly picoCTF competition.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

Pliad CTF

• Website: http://www.plaidctf.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Pliad CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Poisontap

• Website: https://samy.pl/poisontap/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Poisontap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Siphons cookies, exposes internal (LAN-side) router and installs web backdoor on locked computers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Physical Access Tools.

Back to Name Jump

Postenum

• Website: https://github.com/mbahadou/postenum
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Postenum is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Shell script used for enumerating possible privilege escalation opportunities on a local GNU/Linux system.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

PowerSploit

• Website: https://github.com/PowerShellMafia/PowerSploit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Threat Detection, Awesome Hacking

What it does: PowerSploit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A PowerShell Post-Exploitation Framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Tools.

Back to Name Jump

Professional Penetration Testing by Thomas Wilhelm, 2013

• Website: https://www.elsevier.com/books/professional-penetration-testing/wilhelm/978-1-59749-993-4
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Professional Penetration Testing by Thomas Wilhelm, 2013 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Progpilot

• Website: https://github.com/designsecurity/progpilot
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Progpilot is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Static security analysis tool for PHP code.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

prompt(1) to win

• Website: http://prompt.ml/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking, Awesome Web Security

What it does: prompt(1) to win is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Complex 16-Level XSS Challenge held in summer 2014 (+4 Hidden Levels) - Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Practices > XSS.

Back to Name Jump

Proxmark3

• Website: https://proxmark3.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Proxmark3 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: RFID/NFC cloning, replay, and spoofing toolkit often used for analyzing and attacking proximity cards/readers, wireless keys/keyfobs, and more.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Physical Access Tools.

Back to Name Jump

PTF

• Website: https://github.com/trustedsec/ptf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Penetration Testing

What it does: PTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Distro organized around the Penetration Testing Execution Standard (PTES), providing a curated collection of utilities that omits less frequently used utilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Operating System Distributions.

Back to Name Jump

Public Pentesting Reports

• Website: https://github.com/juliocesarfort/public-pentesting-reports
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Public Pentesting Reports is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Curated list of public penetration test reports released by several consulting firms and academic security groups.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Penetration Testing Report Templates.

Back to Name Jump

Pupy

• Website: https://github.com/n1nj4sec/pupy
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Pupy is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Cross-platform (Windows, Linux, macOS, Android) remote administration and post-exploitation tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Multi-paradigm Frameworks.

Back to Name Jump

pwnat

• Website: https://github.com/samyk/pwnat
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: pwnat is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Punches holes in firewalls and NATs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Exfiltration Tools.

Back to Name Jump

pwntools writeups

• Website: https://github.com/Gallopsled/pwntools-write-ups
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: pwntools writeups is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A collection of CTF write-ups all using pwntools.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

PyChallFactory

• Website: https://github.com/pdautry/py_chall_factory
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: PyChallFactory is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Small framework to create/manage/package jeopardy CTF challenges.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

Python Programming by @svaksha

• Website: https://github.com/svaksha/pythonidae
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Python Programming by @svaksha is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: General Python programming.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Python Programming by @vinta

• Website: https://github.com/vinta/awesome-python
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Python Programming by @vinta is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: General Python programming.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Python tools for penetration testers

• Website: https://github.com/dloss/python-pentest-tools
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Python tools for penetration testers is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Lots of pentesting tools are written in Python.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Letter R

This letter section contains 28 tools.

Rar Crack

• Website: http://rarcrack.sourceforge.net
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Rar Crack is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: RAR bruteforce cracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hash Cracking Tools.

Back to Name Jump

Rawsec's CyberSecurity Inventory

• Website: https://inventory.raw.pm/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: Rawsec's CyberSecurity Inventory is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: An open-source inventory of tools, resources, CTF platforms and Operating Systems about CyberSecurity. ().

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Reconmap

• Website: https://reconmap.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Reconmap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open-source collaboration platform for InfoSec professionals that streamlines the pentest process.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

recursebuster

• Website: https://github.com/c-sto/recursebuster
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: recursebuster is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Content discovery tool to perform directory and file bruteforcing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web path discovery and bruteforcing tools.

Back to Name Jump

Red Team Tales 0x01: From MSSQL to RCE

• Website: https://www.tarlogic.com/en/blog/red-team-tales-0x01/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: Red Team Tales 0x01: From MSSQL to RCE is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tricks > SQL Injection.

Back to Name Jump

Red Teaming

• Website: https://github.com/yeyintminthuhtut/Awesome-Red-Teaming
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Red Teaming is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: List of Awesome Red Teaming Resources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Red Teaming/Adversary Simulation Toolkit

• Website: https://github.com/infosecn1nja/Red-Teaming-Toolkit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: Red Teaming/Adversary Simulation Toolkit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A collection of open source and commercial tools that aid in red team operations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Resources.

Back to Name Jump

Red-Team Infrastructure Wiki

• Website: https://github.com/bluscreenofjeff/Red-Team-Infrastructure-Wiki
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: Red-Team Infrastructure Wiki is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Wiki to collect Red Team infrastructure hardening resources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Resources.

Back to Name Jump

Redcloud

• Website: https://github.com/khast3x/Redcloud
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security

What it does: Redcloud is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A automated Red Team Infrastructure deployement using Docker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Red Team Infrastructure Deployment.

Back to Name Jump

Reddit Security CTF

• Website: http://www.reddit.com/r/securityctf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Reddit Security CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Reddit CTF category.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Websites.

Back to Name Jump

RedELK

• Website: https://github.com/outflanknl/RedELK
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: RedELK is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Track and alarm about Blue Team activities while providing better usability in long term offensive operations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Collaboration Tools.

Back to Name Jump

redsnarf

• Website: https://github.com/nccgroup/redsnarf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: redsnarf is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Post-exploitation tool for retrieving password hashes and credentials from Windows workstations, servers, and domain controllers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

ReelPhish

• Website: https://github.com/fireeye/ReelPhish
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ReelPhish is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Real-time two-factor phishing tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

RegEx-DoS

• Website: https://github.com/jagracey/RegEx-DoS
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: RegEx-DoS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Analyzes source code for Regular Expressions susceptible to Denial of Service attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

Responder

• Website: https://github.com/SpiderLabs/Responder
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Responder is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Link-Local Multicast Name Resolution (LLMNR), NBT-NS, and mDNS poisoner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

RID_ENUM

• Website: https://github.com/trustedsec/ridenum
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: RID_ENUM is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Python script that can enumerate all users from a Windows Domain Controller and crack those user's passwords using brute-force.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Ringzer0Team

• Website: https://ringzer0team.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Ringzer0Team is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Ringzer0 Team Online CTF.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

Rookit Arsenal

• Website: https://amzn.com/144962636X
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: Rookit Arsenal is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: OS RE and rootkit development.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > General.

Back to Name Jump

Root-Me

• Website: https://www.root-me.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Root-Me is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Hacking and Information Security learning platform.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

RootTheBox

• Website: https://github.com/moloch--/RootTheBox
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: RootTheBox is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A Game of Hackers (CTF Scoreboard & Game Manager).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Create > Platforms.

Back to Name Jump

RsaCtfTool

• Website: https://github.com/Ganapati/RsaCtfTool
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: RsaCtfTool is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Decrypt data enciphered using weak RSA keys, and recover private keys from public keys using a variety of automated attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > CTF Tools.

Back to Name Jump

RTFM: Red Team Field Manual by Ben Clark, 2014

• Website: http://www.amazon.com/Rtfm-Red-Team-Field-Manual/dp/1494295504/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: RTFM: Red Team Field Manual by Ben Clark, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Rubeus

• Website: https://github.com/GhostPack/Rubeus
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Rubeus is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Toolset for raw Kerberos interaction and abuses.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Ruby Programming by @dreikanter

• Website: https://github.com/dreikanter/ruby-bookmarks
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Ruby Programming by @dreikanter is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The de-facto language for writing exploits.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Ruby Programming by @markets

• Website: https://github.com/markets/awesome-ruby
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Ruby Programming by @markets is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The de-facto language for writing exploits.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Ruby Programming by @Sdogruyol

• Website: https://github.com/Sdogruyol/awesome-ruby
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Ruby Programming by @Sdogruyol is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The de-facto language for writing exploits.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

RuCTFe

• Website: http://ructf.org/e/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: RuCTFe is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

Ruler

• Website: https://github.com/sensepost/ruler
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Ruler is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Abuses client-side Outlook features to gain a remote shell on a Microsoft Exchange server.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Letter S

This letter section contains 27 tools.

SababaSec

• Website: https://github.com/SababaSec/ctf-writeups
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: SababaSec is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A collection of CTF write-ups by the SababaSec team.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

SCOMDecrypt

• Website: https://github.com/nccgroup/SCOMDecrypt
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SCOMDecrypt is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Retrieve and decrypt RunAs credentials stored within Microsoft System Center Operations Manager (SCOM) databases.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

SecLists

• Website: https://github.com/danielmiessler/SecLists
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: SecLists is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Collection of multiple types of lists used during security assessments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

SECUINSIDE CTF

• Website: http://secuinside.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: SECUINSIDE CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump

SGX-Step

• Website: https://github.com/jovanbulck/sgx-step
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SGX-Step is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open-source framework to facilitate side-channel attack research on Intel x86 processors in general and Intel SGX (Software Guard Extensions) platforms in particular.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Side-channel Tools.

Back to Name Jump

SharpShooter

• Website: https://github.com/mdsecactivebreach/SharpShooter
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Threat Detection

What it does: SharpShooter is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Payload Generation Framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Threat Detection and Hunting > Threat Simulation Tools.

Back to Name Jump

SharPyShell

• Website: https://github.com/antonioCoco/SharPyShell
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SharPyShell is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Tiny and obfuscated ASP.NET webshell for C# web applications.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

Shell Scripting

• Website: https://github.com/alebcay/awesome-shell
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Shell Scripting is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Command line frameworks, toolkits, guides and gizmos.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Other Lists Online.

Back to Name Jump

Shellcode Examples

• Website: http://shell-storm.org/shellcode/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Shellcode Examples is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Shellcodes database.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Shellcoding Guides and Tutorials.

Back to Name Jump

shellpop

• Website: https://github.com/0x00-0x00/shellpop
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: shellpop is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Easily generate sophisticated reverse or bind shell commands to help you save time during penetration tests.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > CTF Tools.

Back to Name Jump

ShmooCon

• Website: http://shmoocon.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: ShmooCon is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Annual US East coast hacker convention.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > North America.

Back to Name Jump

Smoke Leet Everyday

• Website: https://github.com/smokeleeteveryday/CTF_WRITEUPS
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Smoke Leet Everyday is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: CTF write-ups repo maintained by SmokeLeetEveryday team.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Writeups Collections.

Back to Name Jump

sobelow

• Website: https://github.com/nccgroup/sobelow
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: sobelow is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Security-focused static analysis for the Phoenix Framework.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Static Analyzers.

Back to Name Jump

Social Engineer Toolkit (SET)

• Website: https://github.com/trustedsec/social-engineer-toolkit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Social Engineer Toolkit (SET) is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open source pentesting framework designed for social engineering featuring a number of custom attack vectors to make believable attacks quickly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

Social Engineering Framework

• Website: http://www.social-engineer.org/framework/general-discussion/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Social Engineering Framework is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Information resource for social engineers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Online Resources.

Back to Name Jump

Social Engineering in IT Security: Tools, Tactics, and Techniques by Sharon Conheady, 2014

• Website: https://www.mhprofessional.com/9780071818469-usa-social-engineering-in-it-security-tools-tactics-and-techniques-group
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Social Engineering in IT Security: Tools, Tactics, and Techniques by Sharon Conheady, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Books.

Back to Name Jump

SocialFish

• Website: https://github.com/UndeadSec/SocialFish
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SocialFish is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Social media phishing framework that can run on an Android phone or in a Docker container.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

SprayingToolkit

• Website: https://github.com/byt3bl33d3r/SprayingToolkit
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SprayingToolkit is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Scripts to make password spraying attacks against Lync/S4B, Outlook Web Access (OWA) and Office 365 (O365) a lot quicker, less painful and more efficient.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools > Password Spraying Tools.

Back to Name Jump

sqlmap

• Website: http://sqlmap.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Penetration Testing

What it does: sqlmap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: sqlmap is an open source penetration testing tool that automates the process of detecting and exploiting SQL injection flaws and taking over of database servers. It comes with a powerful detection engine, many niche features for the ultimate penetration tester and a broad range of switches lasting from database fingerprinting, over data fetching from the database, to accessing the underlying file system and executing commands on the operating system via out-of-band connections.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web injection tools.

Back to Name Jump

SSL & TLS Penetration Testing

• Website: https://www.aptive.co.uk/blog/tls-ssl-security-testing/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: SSL & TLS Penetration Testing is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Introduction > SSL/TLS.

Back to Name Jump

sslstrip

• Website: https://www.thoughtcrime.org/software/sslstrip/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: sslstrip is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Demonstration of the HTTPS stripping attacks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

sslstrip2

• Website: https://github.com/LeonardoNve/sslstrip2
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: sslstrip2 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: SSLStrip version to defeat HSTS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation.

Back to Name Jump

StegCracker

• Website: https://github.com/Paradoxis/StegCracker
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: StegCracker is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Steganography brute-force utility to uncover hidden data inside files.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Steganography Tools.

Back to Name Jump

StegOnline

• Website: https://stegonline.georgeom.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: StegOnline is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Web-based, enhanced, and open-source port of StegSolve.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Steganography Tools.

Back to Name Jump

Stratus Red Team

• Website: https://stratus-red-team.cloud/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Cybersecurity Blue Team

What it does: Stratus Red Team is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Emulate offensive attack techniques in a granular and self-contained manner against a cloud environment; think "Atomic Red Team™ for the cloud.".

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Cybersecurity Blue Team > Preparedness training and wargaming.

Back to Name Jump

SummerCon

• Website: https://www.summercon.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: SummerCon is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: One of the oldest hacker conventions in America, held during Summer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > North America.

Back to Name Jump

Sysinternals Suite

• Website: https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Sysinternals Suite is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The Sysinternals Troubleshooting Utilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

Letter T

This letter section contains 9 tools.

T&VS Pentesting Report Template

• Website: https://www.testandverification.com/wp-content/uploads/template-penetration-testing-report-v03.pdf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: T&VS Pentesting Report Template is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Pentest report template provided by Test and Verification Services, Ltd.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Penetration Testing Report Templates.

Back to Name Jump

Tails OS

• Website: https://tails.boum.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Penetration Testing, Awesome OSINT, Awesome Cyber Security Tools

What it does: Tails OS is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Live operating system that you can start on almost any computer from a USB stick or a DVD.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Operating Systems > Privacy & Security.

Back to Name Jump

The Art of Exploitation by Jon Erickson, 2008

• Website: https://nostarch.com/hacking2.htm
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: The Art of Exploitation by Jon Erickson, 2008 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

The Art of Intrusion by Kevin D. Mitnick & William L. Simon, 2005

• Website: http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764569597.html
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: The Art of Intrusion by Kevin D. Mitnick & William L. Simon, 2005 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Books.

Back to Name Jump

The Basics of Hacking and Penetration Testing by Patrick Engebretson, 2013

• Website: https://www.elsevier.com/books/the-basics-of-hacking-and-penetration-testing/engebretson/978-1-59749-655-1
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: The Basics of Hacking and Penetration Testing by Patrick Engebretson, 2013 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Thunderclap

• Website: https://thunderclap.io/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Thunderclap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Open source I/O security research platform for auditing physical DMA-enabled hardware peripheral ports.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Physical Access Tools.

Back to Name Jump

tplmap

• Website: https://github.com/epinna/tplmap
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: tplmap is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Code and Server-Side Template Injection Detection and Exploitation Tool by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web injection tools.

Back to Name Jump

TrevorC2

• Website: https://github.com/trustedsec/trevorc2
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: TrevorC2 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Client/server tool for masking command and control and data exfiltration through a normally browsable website, not typical HTTP POST requests.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Exfiltration Tools.

Back to Name Jump

Troopers

• Website: https://www.troopers.de
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Troopers is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Annual international IT Security event with workshops held in Heidelberg, Germany.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Conferences and Events > Europe.

Back to Name Jump

Letter U

This letter section contains 4 tools.

Unauthorised Access: Physical Penetration Testing For IT Security Teams by Wil Allsopp, 2010

• Website: http://www.amazon.com/Unauthorised-Access-Physical-Penetration-Security-ebook/dp/B005DIAPKE
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Unauthorised Access: Physical Penetration Testing For IT Security Teams by Wil Allsopp, 2010 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

unix-privesc-check

• Website: https://github.com/pentestmonkey/unix-privesc-check
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: unix-privesc-check is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Shell script to check for simple privilege escalation vectors on UNIX systems.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Privilege Escalation Tools.

Back to Name Jump

Unmasking the Social Engineer: The Human Element of Security by Christopher Hadnagy, 2014

• Website: http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118608577.html
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Unmasking the Social Engineer: The Human Element of Security by Christopher Hadnagy, 2014 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Books.

Back to Name Jump

USB Rubber Ducky

• Website: http://usbrubberducky.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: USB Rubber Ducky is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Customizable keystroke injection attack platform masquerading as a USB thumbdrive.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Physical Access Tools.

Back to Name Jump

Letter V

This letter section contains 4 tools.

V0lt

• Website: https://github.com/P1kachu/v0lt
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: V0lt is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Security CTF Toolkit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Solve > Exploits.

Back to Name Jump

Veles

• Website: https://codisec.com/veles/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Veles is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Binary data visualization and analysis tool.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > File Format Analysis Tools.

Back to Name Jump

Viblo CTF

• Website: https://ctf.viblo.asia
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: Viblo CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Various amazing CTF challenges, in many different categories. Has both Practice mode and Contest mode.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

Violent Python by TJ O'Connor, 2012

• Website: https://www.elsevier.com/books/violent-python/unknown/978-1-59749-957-6
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Violent Python by TJ O'Connor, 2012 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Books.

Back to Name Jump

Letter W

This letter section contains 10 tools.

W3Challs

• Website: https://w3challs.com
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome CTF

What it does: W3Challs is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: A penetration testing training platform, which offers various computer challenges, in various categories.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Resources > Wargames.

Back to Name Jump

WEB APPLICATION PENETRATION TESTING NOTES

• Website: https://techvomit.net/web-application-penetration-testing-notes/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: WEB APPLICATION PENETRATION TESTING NOTES is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Written by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Miscellaneous.

Back to Name Jump

Web Application Security Assessment Report Template

• Website: http://lucideus.com/pdf/stw.pdf
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Web Application Security Assessment Report Template is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Sample Web application security assessment reporting template provided by Lucideus.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Online Resources > Penetration Testing Report Templates.

Back to Name Jump

WeChall

• Website: http://www.wechall.net/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: WeChall is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > General.

Back to Name Jump

weevely3

• Website: https://github.com/epinna/weevely3
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: weevely3 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Weaponized PHP-based web shell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Web Exploitation > Web shells and C2 frameworks.

Back to Name Jump

What Every Browser Knows About You

• Website: http://webkay.robinlinus.com/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: What Every Browser Knows About You is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Comprehensive detection page to test your own Web browser's configuration for privacy and identity leaks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Anonymity Tools.

Back to Name Jump

wifiphisher

• Website: https://github.com/sophron/wifiphisher
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: wifiphisher is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Automated phishing attacks against WiFi networks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Social Engineering > Social Engineering Tools.

Back to Name Jump

Windows Credentials Editor

• Website: https://www.ampliasecurity.com/research/windows-credentials-editor/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: Windows Credentials Editor is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Inspect logon sessions and add, change, list, and delete associated credentials, including Kerberos tickets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

WinPwn

• Website: https://github.com/SecureThisShit/WinPwn
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: WinPwn is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Internal penetration test script to perform local and domain reconnaissance, privilege escalation and exploitation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Windows Utilities.

Back to Name Jump

wxHexEditor

• Website: http://www.wxhexeditor.org/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Penetration Testing

What it does: wxHexEditor is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Free GUI hex editor for GNU/Linux, macOS, and Windows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Penetration Testing > Hex Editors.

Back to Name Jump

Letter X

This letter section contains 3 tools.

XSRFProbe

• Website: https://github.com/0xInfection/XSRFProbe
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: XSRFProbe is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The Prime CSRF Audit & Exploitation Toolkit by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > Cross Site Request Forgery.

Back to Name Jump

xssor2

• Website: https://github.com/evilcos/xssor2
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: xssor2 is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: XSS'OR - Hack with JavaScript by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > XSS - Cross-Site Scripting.

Back to Name Jump

XSStrike

• Website: https://github.com/s0md3v/XSStrike
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Web Security

What it does: XSStrike is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: XSStrike is a program which can fuzz and bruteforce parameters for XSS. It can also detect and bypass WAFs by .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Web Security > Tools > Offensive > XSS - Cross-Site Scripting.

Back to Name Jump

Letter Z

This letter section contains 2 tools.

ZAP

• Website: https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Security, Awesome Hacking

What it does: ZAP is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: The Zed Attack Proxy (ZAP) is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Security > Web > Scanning / Pentesting.

Back to Name Jump

ZeroDays CTF

• Website: https://zerodays.ie/
• Model: Open Source
• Category: Penetration Testing & Red Team
• Source Lists: Awesome Hacking

What it does: ZeroDays CTF is used in penetration testing & red team programs to support security control validation through offensive simulation and exploitation. Source summaries describe it as: Source list entry describing this security tool and its use case.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: CTF > Competition.

Back to Name Jump