Cybersecurity Tools Atlas

Open-Source Cybersecurity Tools Catalog

This full reference catalog is generated from community-maintained cybersecurity lists and normalized into a single taxonomy. Use it for deep research, broad market scanning, and long-form side-by-side comparison when you need maximum coverage in one place.

Read This Page Effectively

If you prefer faster navigation, start with the Open-Source Cybersecurity Tools Hub, which breaks content into category-specific pages.

Use these evaluation criteria when comparing tools:

  • 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.

Category Index

AI / LLM Security

This category contains 1 documented tools. It focuses on capabilities used for model red teaming, prompt injection defense, and AI governance controls. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

shellfirm

  • Website: https://github.com/kaplanelad/shellfirm
  • Model: Open Source
  • Category: AI / LLM Security
  • Source Lists: Awesome Security

What it does: shellfirm is used in ai / llm security programs to support model red teaming, prompt injection defense, and AI governance controls. Source summaries describe it as: It is a handy utility to help avoid running dangerous commands with an extra approval step. You will immediately get a small prompt challenge that will double verify your action when risky patterns are detected.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Terminal.

Back to Category Index

Application Security

This category contains 8 documented tools. It focuses on capabilities used for secure SDLC controls, code scanning, and dependency risk management. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

AppSec

  • Website: https://github.com/paragonie/awesome-appsec
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: AppSec is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. 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 > Online Resources > Other Lists Online.

Back to Category Index

CakeFuzzer

  • Website: https://github.com/Zigrin-Security/CakeFuzzer
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: CakeFuzzer is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: The ultimate web application security testing tool for CakePHP-based web applications. CakeFuzzer employs a predefined set of attacks that are randomly modified before execution. Leveraging its deep understanding of the Cake PHP framework, Cake Fuzzer launches attacks on all potential application entry points.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Insider CLI

  • Website: https://github.com/insidersec/insider
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: Insider CLI is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: A open source Static Application Security Testing tool (SAST) written in GoLang for Java (Maven and Android), Kotlin (Android), Swift (iOS), .NET Full Framework, C# and Javascript (Node.js).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

Node.js Secure Coding: Defending Against Command Injection Vulnerabilities

  • Website: https://www.nodejs-security.com
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: Node.js Secure Coding: Defending Against Command Injection Vulnerabilities is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: Learn secure coding conventions in Node.js by executing command injection attacks on real-world npm packages and analyzing vulnerable 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 Security > EBooks.

Back to Category Index

Node.js Secure Coding: Prevention and Exploitation of Path Traversal Vulnerabilities

  • Website: https://www.nodejs-security.com/book/path-traversal
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: Node.js Secure Coding: Prevention and Exploitation of Path Traversal Vulnerabilities is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: Master secure coding in Node.js with real-world vulnerable dependencies and experience firsthand secure coding techniques against Path Traversal vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

OWASP

  • Website: http://www.owasp.org
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: OWASP is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: The Open Web Application Security Project (OWASP) is a 501(c)(3) worldwide not-for-profit charitable organization focused on improving the security of 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 Security > Web > Organization.

Back to Category Index

Portswigger

  • Website: https://portswigger.net
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: Portswigger is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: PortSwigger offers tools for web application security, testing & scanning. Choose from a wide range of security tools & identify the very latest vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Organization.

Back to Category Index

Scanmycode CE (Community Edition)

  • Website: https://github.com/marcinguy/scanmycode-ce
  • Model: Open Source
  • Category: Application Security
  • Source Lists: Awesome Security

What it does: Scanmycode CE (Community Edition) is used in application security programs to support secure SDLC controls, code scanning, and dependency risk management. Source summaries describe it as: Code Scanning/SAST/Static Analysis/Linting using many tools/Scanners with One Report. Currently supports: PHP, Java, Scala, Python, Ruby, Javascript, GO, Secret Scanning, Dependency Confusion, Trojan Source, Open Source and Proprietary Checks (total ca. 1000 checks).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Blue Team

This category contains 46 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

AllStar

  • Website: https://github.com/ossf/allstar
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: AllStar is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: GitHub App installed on organizations or repositories to set and enforce security policies.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Policy enforcement.

Back to Category Index

blackbox

  • Website: https://github.com/StackExchange/blackbox
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: blackbox is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Safely store secrets in Git/Mercurial/Subversion by encrypting them "at rest" using GnuPG.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Bubblewrap

  • Website: https://github.com/containers/bubblewrap
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Bubblewrap is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Sandboxing tool for use by unprivileged Linux users capable of restricting access to parts of the operating system or user data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Host-based tools > Sandboxes.

Back to Category Index

CanaryTokens

  • Website: https://github.com/thinkst/canarytokens
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Honeypots

What it does: CanaryTokens is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Self-hostable honeytoken generator and reporting dashboard; demo version available at .

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Honeypots.

Back to Category Index

chkrootkit

  • Website: http://chkrootkit.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: chkrootkit is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Locally checks for signs of a rootkit on GNU/Linux 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 Cybersecurity Blue Team > Host-based tools.

Back to Category Index

CodeQL

  • Website: https://securitylab.github.com/tools/codeql
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: CodeQL is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Discover vulnerabilities across a codebase by performing queries against code as though it were data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Conftest

  • Website: https://conftest.dev/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Conftest is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Utility to help you write tests against structured configuration data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Policy enforcement.

Back to Category Index

Crossfeed

  • Website: https://docs.crossfeed.cyber.dhs.gov/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Crossfeed is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Continuously enumerates and monitors an organization’s public-facing attack surface in order to discover assets and flag potential security flaws.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring.

Back to Category Index

Dangerzone

  • Website: https://dangerzone.rocks/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Dangerzone is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Host-based tools > Sandboxes.

Back to Category Index

DeepBlueCLI

  • Website: https://github.com/sans-blue-team/DeepBlueCLI
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: DeepBlueCLI is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A PowerShell Module for Hunt Teaming via Windows Event Logs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

DynamoRIO

  • Website: https://dynamorio.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: DynamoRIO is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Runtime code manipulation system that supports code transformations on any part of a program, while it executes, implemented as a process-level virtual machine.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Application or Binary Hardening.

Back to Category Index

DynInst

  • Website: https://dyninst.org/dyninst
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: DynInst is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Tools for binary instrumentation, analysis, and modification, useful for binary patching.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Application or Binary Hardening.

Back to Category Index

Egalito

  • Website: https://egalito.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Egalito is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Binary recompiler and instrumentation framework that can fully disassemble, transform, and regenerate ordinary Linux binaries designed for binary hardening and security research.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Application or Binary Hardening.

Back to Category Index

Endlessh

  • Website: https://github.com/skeeto/endlessh
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Honeypots

What it does: Endlessh is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: SSH tarpit that slowly sends an endless banner. ().

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Honeypots > Tarpits.

Back to Category Index

Fail2ban

  • Website: https://www.fail2ban.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Fail2ban is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Intrusion prevention software framework that protects computer servers from brute-force 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 Cybersecurity Blue Team > Host-based tools.

Back to Category Index

Git Secrets

  • Website: https://github.com/awslabs/git-secrets
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Git Secrets is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Prevents you from committing passwords and other sensitive information to a git repository.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

git-crypt

  • Website: https://www.agwa.name/projects/git-crypt/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: git-crypt is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Transparent file encryption in git; files which you choose to protect are encrypted when committed, and decrypted when checked out.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

GlobaLeaks

  • Website: https://www.globaleaks.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: GlobaLeaks is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Free, open source software enabling anyone to easily set up and maintain a secure whistleblowing 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: Awesome Cybersecurity Blue Team > Communications security (COMSEC).

Back to Category Index

GPG Sync

  • Website: https://github.com/firstlookmedia/gpgsync
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: GPG Sync is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Centralize and automate OpenPGP public key distribution, revocation, and updates amongst all members of an organization or 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 Cybersecurity Blue Team > Communications security (COMSEC).

Back to Category Index

HardenTools

  • Website: https://github.com/securitywithoutborders/hardentools
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: HardenTools is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Utility that disables a number of risky Windows 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 Cybersecurity Blue Team > Windows-based defenses.

Back to Category Index

Headscale

  • Website: https://github.com/juanfont/headscale
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Headscale is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Open source, self-hosted implementation of the Tailscale control 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 Cybersecurity Blue Team > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

helm-secrets

  • Website: https://github.com/jkroepke/helm-secrets
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: helm-secrets is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Helm plugin that helps manage secrets with Git workflow and stores them anywhere, backed by SOPS.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Icinga

  • Website: https://icinga.com/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Icinga is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Modular redesign of Nagios with pluggable user interfaces and an expanded set of data connectors, collectors, and reporting 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 Cybersecurity Blue Team > Security monitoring > Service and performance monitoring.

Back to Category Index

LaBrea

  • Website: http://labrea.sourceforge.net/labrea-info.html
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Honeypots

What it does: LaBrea is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Program that answers ARP requests for unused IP space, creating the appearance of fake machines that answer further requests very slowly in order to slow down scanners, worms, etcetera.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Honeypots > Tarpits.

Back to Category Index

Locust

  • Website: https://locust.io/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Locust is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Open source load testing tool in which you can define user behaviour with Python code and swarm your system with millions of simultaneous users.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Service and performance monitoring.

Back to Category Index

Logging Made Easy (LME)

  • Website: https://www.cisa.gov/resources-tools/services/logging-made-easy
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Logging Made Easy (LME) is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Free and open logging and protective monitoring solution serving.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

MITMEngine

  • Website: https://github.com/cloudflare/mitmengine
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: MITMEngine is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Golang library for server-side detection of TLS interception 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 Cybersecurity Blue Team > Transport-layer defenses.

Back to Category Index

Nebula

  • Website: https://github.com/slackhq/nebula
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Nebula is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Completely open source and self-hosted, scalable overlay networking tool with a focus on performance, simplicity, and security, inspired by tinc.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

NotRuler

  • Website: https://github.com/sensepost/notruler
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: NotRuler is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Detect both client-side rules and VBScript enabled forms used by the attack tool when attempting to compromise 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 Cybersecurity Blue Team > Windows-based defenses.

Back to Category Index

OnionBalance

  • Website: https://onionbalance.readthedocs.io/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OnionBalance is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Provides load-balancing while also making Onion services more resilient and reliable by eliminating single points-of-failure.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tor Onion service defenses.

Back to Category Index

Open Source HIDS SECurity (OSSEC)

  • Website: https://www.ossec.net/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Open Source HIDS SECurity (OSSEC) is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Fully open source and free, feature-rich, Host-based Instrusion Detection System (HIDS).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Host-based tools.

Back to Category Index

osquery

  • Website: https://github.com/facebook/osquery
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: osquery is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Operating system instrumentation framework for macOS, Windows, and Linux, exposing the OS as a high-performance relational database that can be queried with a SQL-like syntax.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Service and performance monitoring.

Back to Category Index

PlumHound

  • Website: https://github.com/PlumHound/PlumHound
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: PlumHound is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: More effectively use BloodHoundAD in continual security life-cycles by utilizing its pathfinding engine to identify Active Directory security vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses > Active Directory.

Back to Category Index

PSHunt

  • Website: https://github.com/Infocyte/PSHunt
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: PSHunt is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: PowerShell module designed to scan remote endpoints for indicators of compromise or survey them for more comprehensive information related to state of those 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 Cybersecurity Blue Team > Security monitoring > Threat hunting.

Back to Category Index

Sandboxie

  • Website: https://www.sandboxie.com/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Cyber Security Tools

What it does: Sandboxie is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Free and open source general purpose Windows application sandboxing utility.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses.

Back to Category Index

Santa

  • Website: https://github.com/google/santa
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Santa is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Keep track of binaries that are naughty or nice in an allow/deny-listing system 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 Cybersecurity Blue Team > macOS-based defenses.

Back to Category Index

SecureDrop

  • Website: https://securedrop.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: SecureDrop is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Open source whistleblower submission system that media organizations and NGOs can install to securely accept documents from anonymous sources.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Communications security (COMSEC).

Back to Category Index

Shufflecake

  • Website: https://shufflecake.net/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Shufflecake is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Plausible deniability for multiple hidden filesystems on 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 Cybersecurity Blue Team > Host-based tools.

Back to Category Index

SonarQube

  • Website: https://sonarqube.org
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: SonarQube is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Continuous inspection tool that provides detailed reports during automated testing and alerts on newly introduced security vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Starbase

  • Website: https://github.com/JupiterOne/starbase
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Starbase is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Collects assets and relationships from services and systems into an intuitive graph view to offer graph-based security analysis for everyone.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring.

Back to Category Index

Sticky Keys Slayer

  • Website: https://github.com/linuz/Sticky-Keys-Slayer
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Sticky Keys Slayer is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Establishes a Windows RDP session from a list of hostnames and scans for accessibility tools backdoors, alerting if one is discovered.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses.

Back to Category Index

Stronghold

  • Website: https://github.com/alichtman/stronghold
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Stronghold is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Easily configure macOS security settings from the terminal.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > macOS-based defenses.

Back to Category Index

USB Keystroke Injection Protection

  • Website: https://github.com/google/ukip
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: USB Keystroke Injection Protection is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Daemon for blocking USB keystroke injection devices on Linux 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 Cybersecurity Blue Team > Host-based tools.

Back to Category Index

Valgrind

  • Website: https://www.valgrind.org/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Valgrind is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Instrumentation framework for building dynamic analysis 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 Cybersecurity Blue Team > DevSecOps > Application or Binary Hardening.

Back to Category Index

Vanguards

  • Website: https://github.com/mikeperry-tor/vanguards
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Vanguards is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Version 3 Onion service guard discovery attack mitigation script (intended for eventual inclusion in Tor core).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tor Onion service defenses.

Back to Category Index

Zabbix

  • Website: https://www.zabbix.com/
  • Model: Open Source
  • Category: Blue Team
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Zabbix is used in blue team programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Mature, enterprise-level platform to monitor large-scale IT 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 Cybersecurity Blue Team > Security monitoring > Service and performance monitoring.

Back to Category Index

CTF & Training

This category contains 83 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Parrot Security OS

  • Website: https://www.parrotsec.org
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome Cyber Security Tools, Awesome CTF

What it does: Parrot Security OS is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Security-oriented Linux distribution designed for security experts and 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: Resources > Operating Systems.

Back to Category Index

AperiSolve

  • Website: https://aperisolve.fr/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: AperiSolve is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Aperi'Solve is a platform which performs layer analysis on image (open-source).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

BackBox

  • Website: https://backbox.org/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: BackBox is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Based on Ubuntu.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Backdoor

  • Website: https://backdoor.sdslabs.co/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Backdoor is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Security Platform by SDSLabs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Bettercap

  • Website: https://github.com/bettercap/bettercap
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Bettercap is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Framework to perform MITM (Man in the Middle) 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: Solve > Attacks.

Back to Category Index

bi0s Wiki

  • Website: https://teambi0s.gitlab.io/bi0s-wiki/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: bi0s Wiki is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Wiki from team bi0s.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

BinUtils

  • Website: http://www.gnu.org/software/binutils/binutils.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: BinUtils is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Collection of binary 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: Solve > Reversing.

Back to Category Index

Boomerang

  • Website: https://github.com/BoomerangDecompiler/boomerang
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Boomerang is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Decompile x86/SPARC/PowerPC/ST-20 binaries to C.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Convert

  • Website: http://www.imagemagick.org/script/convert.php
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Convert is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Convert images b/w formats and apply filters.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

CryptoHack

  • Website: https://cryptohack.org/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: CryptoHack is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Fun cryptography 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: Resources > Wargames.

Back to Category Index

CSWSH

  • Website: http://cow.cat/cswsh.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: CSWSH is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Cross-Site WebSocket Hijacking Tester.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Services.

Back to Category Index

ctf_import

  • Website: https://github.com/docileninja/ctf_import
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: ctf_import is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: run basic functions from stripped binaries cross 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: Solve > Reversing.

Back to Category Index

CTFd

  • Website: https://github.com/isislab/CTFd
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: CTFd is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Platform to host jeopardy style CTFs from ISISLab, NYU Tandon.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

CyberChef

  • Website: https://gchq.github.io/CyberChef
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: CyberChef is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Web app for analysing and decoding data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Crypto.

Back to Category Index

Damn Vulnerable Web Application

  • Website: http://www.dvwa.co.uk/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Damn Vulnerable Web Application is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: PHP/MySQL web application that is damn vulnerable.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

demovfuscator

  • Website: https://github.com/kirschju/demovfuscator
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: demovfuscator is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A work-in-progress deobfuscator for movfuscated binaries.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

DLLInjector

  • Website: https://github.com/OpenSecurityResearch/dllinjector
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: DLLInjector is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Inject dlls in processes.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Exif

  • Website: http://manpages.ubuntu.com/manpages/trusty/man1/exif.1.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Exif is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Shows EXIF information in JPEG 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: Solve > Steganography.

Back to Category Index

Exiftool

  • Website: https://linux.die.net/man/1/exiftool
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Exiftool is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Read and write meta information in 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: Solve > Steganography.

Back to Category Index

Exiv2

  • Website: http://www.exiv2.org/manpage.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Exiv2 is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Image metadata manipulation 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: Solve > Steganography.

Back to Category Index

FeatherDuster

  • Website: https://github.com/nccgroup/featherduster
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: FeatherDuster is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: An automated, modular cryptanalysis 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: Solve > Crypto.

Back to Category Index

Fedora Security Lab

  • Website: https://labs.fedoraproject.org/security/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Fedora Security Lab is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Based on Fedora.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Frida

  • Website: https://github.com/frida/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Frida is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Dynamic Code Injection.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

GDB

  • Website: https://www.gnu.org/software/gdb/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: GDB is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The GNU project debugger.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Gracker

  • Website: https://github.com/Samuirai/gracker
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Gracker is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Binary challenges having a slow learning curve, and write-ups for each level.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Hackbar

  • Website: https://addons.mozilla.org/en-US/firefox/addon/hackbartool/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Hackbar is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Firefox addon for easy web 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: Solve > Web.

Back to Category Index

Hash Extender

  • Website: https://github.com/iagox86/hash_extender
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Hash Extender is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A utility tool for performing hash length extension 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: Solve > Crypto.

Back to Category Index

Hone Your Ninja Skills

  • Website: https://honeyourskills.ninja/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Hone Your Ninja Skills is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Web challenges starting from basic ones.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Hydra

  • Website: https://tools.kali.org/password-attacks/hydra
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Hydra is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A parallelized login cracker which supports numerous protocols 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: Solve > Bruteforcers.

Back to Category Index

Image Steganography

  • Website: https://sourceforge.net/projects/image-steg/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Image Steganography is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Embeds text and files in images with optional encryption. Easy-to-use UI.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Image Steganography Online

  • Website: https://incoherency.co.uk/image-steganography
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Image Steganography Online is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: This is a client-side Javascript tool to steganographically hide images inside the lower "bits" of other images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

ImageMagick

  • Website: http://www.imagemagick.org/script/index.php
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: ImageMagick is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Tool for manipulating images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

IO

  • Website: http://io.netgarage.org/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: IO is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Wargame for binary 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: Resources > Wargames.

Back to Category Index

John The Jumbo

  • Website: https://github.com/magnumripper/JohnTheRipper
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: John The Jumbo is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Community enhanced version of John the Ripper.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Bruteforcers.

Back to Category Index

LazyKali

  • Website: https://github.com/jlevitsk/lazykali
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: LazyKali is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A 2016 refresh of LazyKali which simplifies install of tools and configuration.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Starter Packs.

Back to Category Index

libformatstr

  • Website: https://github.com/hellman/libformatstr
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: libformatstr is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Simplify format string 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: Solve > Exploits.

Back to Category Index

Metasploit JavaScript Obfuscator

  • Website: https://github.com/rapid7/metasploit-framework/wiki/How-to-obfuscate-JavaScript-in-Metasploit
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Metasploit JavaScript Obfuscator is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Create > Web.

Back to Category Index

Nozzlr

  • Website: https://github.com/intrd/nozzlr
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Nozzlr is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Nozzlr is a bruteforce framework, trully modular and script-friendly.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Bruteforcers.

Back to Category Index

one_gadget

  • Website: https://github.com/david942j/one_gadget
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: one_gadget is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A tool to find the one gadget execve('/bin/sh', NULL, NULL) call.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Outguess

  • Website: https://www.freebsd.org/cgi/man.cgi?query=outguess+&apropos=0&sektion=0&manpath=FreeBSD+Ports+5.1-RELEASE&format=html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Outguess is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Universal steganographic 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: Solve > Steganography.

Back to Category Index

Over The Wire

  • Website: http://overthewire.org/wargames/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Over The Wire is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Wargame maintained by OvertheWire 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 > Wargames.

Back to Category Index

Patator

  • Website: https://github.com/lanjelot/patator
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Patator is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Patator is a multi-purpose brute-forcer, with a modular design.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Bruteforcers.

Back to Category Index

PentesterLab

  • Website: https://pentesterlab.com/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: PentesterLab is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Variety of VM and online challenges (paid).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Pentoo

  • Website: http://www.pentoo.ch/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Pentoo is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Based on Gentoo.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Pin

  • Website: https://software.intel.com/en-us/articles/pin-a-dynamic-binary-instrumentation-tool
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Pin is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A dynamic binary instrumentaion tool by Intel.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

PinCTF

  • Website: https://github.com/ChrisTheCoolHut/PinCTF
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: PinCTF is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A tool which uses intel pin for Side Channel 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: Solve > Reversing.

Back to Category Index

PkCrack

  • Website: https://www.unix-ag.uni-kl.de/~conrad/krypto/pkcrack.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: PkCrack is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A tool for Breaking PkZip-encryption.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Crypto.

Back to Category Index

Pngtools

  • Website: https://packages.debian.org/sid/pngtools
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Pngtools is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: For various analysis related to PNGs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

PWN Challenge

  • Website: http://pwn.eonew.cn/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: PWN Challenge is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Binary Exploitation Wargame.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Pwnable.tw

  • Website: https://pwnable.tw/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Pwnable.tw is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Binary wargame.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Pwnable.xyz

  • Website: https://pwnable.xyz/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Pwnable.xyz is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Binary Exploitation Wargame.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Qira

  • Website: https://github.com/BinaryAnalysisPlatform/qira
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Qira is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: QEMU Interactive Runtime Analyser.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

QuipQuip

  • Website: https://quipqiup.com
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: QuipQuip is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: An online tool for breaking substitution ciphers or vigenere ciphers (without key).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Crypto.

Back to Category Index

Request Bin

  • Website: https://requestbin.com/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Request Bin is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Lets you inspect http requests to a particular url.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Services.

Back to Category Index

Revelo

  • Website: http://www.kahusecurity.com/posts/revelo_javascript_deobfuscator.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Revelo is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Analyze obfuscated Javascript 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: Solve > Reversing.

Back to Category Index

Reversin.kr

  • Website: http://reversing.kr/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Reversin.kr is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Reversing challenge.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

ROP Gadget

  • Website: https://github.com/JonathanSalwan/ROPgadget
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: ROP Gadget is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Framework for ROP 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: Solve > Exploits.

Back to Category Index

ROP Wargames

  • Website: https://github.com/xelenonz/game
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: ROP Wargames is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: ROP Wargames.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

RSATool

  • Website: https://github.com/ius/rsatool
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: RSATool is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Generate private key with knowledge of p and q.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Crypto.

Back to Category Index

SANS HHC

  • Website: https://holidayhackchallenge.com/past-challenges/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: SANS HHC is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Challenges with a holiday theme.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Scorebot

  • Website: https://github.com/legitbs/scorebot
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Scorebot is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Platform for CTFs by Legitbs (Defcon).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

SecGen

  • Website: https://github.com/cliffe/SecGen
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: SecGen is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Security Scenario Generator. Creates randomly vulnerable virtual 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: Create > Platforms.

Back to Category Index

SmartDeblur

  • Website: https://github.com/Y-Vladimir/SmartDeblur
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: SmartDeblur is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Used to deblur and fix defocused images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Steganabara

  • Website: https://www.openhub.net/p/steganabara
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Steganabara is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Tool for stegano analysis written in Java.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

SteganographyOnline

  • Website: https://stylesuxx.github.io/steganography/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: SteganographyOnline is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Online steganography encoder and decoder.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Stegbreak

  • Website: https://linux.die.net/man/1/stegbreak
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Stegbreak is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Launches brute-force dictionary attacks on JPG image.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

stegextract

  • Website: https://github.com/evyatarmeged/stegextract
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: stegextract is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Detect hidden files and text in images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Steghide

  • Website: http://steghide.sourceforge.net/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Steghide is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Hide data in various kind of images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

StegOnline

  • Website: https://georgeom.net/StegOnline/upload
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: StegOnline is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Conduct a wide range of image steganography operations, such as concealing/revealing files hidden within bits (open-source).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Stegsolve

  • Website: http://www.caesum.com/handbook/Stegsolve.jar
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Stegsolve is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Apply various steganography techniques to images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Steganography.

Back to Category Index

Triton

  • Website: https://github.com/JonathanSalwan/Triton/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Triton is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Dynamic Binary Analysis (DBA) 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: Solve > Reversing.

Back to Category Index

Turbo Intruder

  • Website: https://portswigger.net/research/turbo-intruder-embracing-the-billion-request-attack
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Turbo Intruder is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Burp Suite extension for sending large numbers of HTTP 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: Solve > Bruteforcers.

Back to Category Index

Uglify

  • Website: https://github.com/mishoo/UglifyJS
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Uglify is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Create > Web.

Back to Category Index

Uncompyle

  • Website: https://github.com/gstarnberger/uncompyle
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Uncompyle is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Decompile Python 2.7 binaries (.pyc).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

URIX OS

  • Website: http://urix.us/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: URIX OS is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Based on openSUSE.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Wifislax

  • Website: http://www.wifislax.com/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Wifislax is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Based on Slackware.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

WinDbg

  • Website: http://www.windbg.org/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: WinDbg is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Windows debugger distributed by Microsoft.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Xocopy

  • Website: http://reverse.lostrealm.com/tools/xocopy.html
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Xocopy is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Program that can copy executables with execute, but no read permission.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

XSSer

  • Website: http://xsser.sourceforge.net/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: XSSer is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Automated XSS testor.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Web.

Back to Category Index

Xxxswf

  • Website: https://bitbucket.org/Alexander_Hanel/xxxswf
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Xxxswf is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A Python script for analyzing Flash 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: Solve > Reversing.

Back to Category Index

Yersinia

  • Website: https://github.com/tomac/yersinia
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Yersinia is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Attack various protocols on layer 2.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Attacks.

Back to Category Index

Z3

  • Website: https://github.com/Z3Prover/z3
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF

What it does: Z3 is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A theorem prover from Microsoft Research.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Zsteg

  • Website: https://github.com/zed-0xff/zsteg/
  • Model: Open Source
  • Category: CTF & Training
  • Source Lists: Awesome CTF, Awesome Forensics

What it does: Zsteg is used in ctf & training programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A steganographic coder for WAV 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 Forensics > Tools > Steganography.

Back to Category Index

Cloud Security

This category contains 50 documented tools. It focuses on capabilities used for multi-cloud posture monitoring, workload protection, and misconfiguration control. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Aaia

  • Website: https://github.com/rams3sh/Aaia
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Aaia is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Helps in visualizing AWS IAM and Organizations in a graph format with help of Neo4j.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

Afterglow Cloud

  • Website: https://github.com/ayrus/afterglow-cloud
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Honeypots

What it does: Afterglow Cloud is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Contents > Data Tools.

Back to Category Index

attack_range

  • Website: https://github.com/splunk/attack_range
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Threat Detection

What it does: attack_range is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: A tool that allows you to create vulnerable instrumented local or cloud environments to simulate attacks against and collect the data into Splunk.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

AWS Security Fundamentals

  • Website: https://aws.amazon.com/fr/training/digital/aws-security-fundamentals/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: AWS Security Fundamentals is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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 > Nice to read.

Back to Category Index

aws-vault

  • Website: https://github.com/99designs/aws-vault
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: aws-vault is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Store AWS credentials in the OSX Keychain or an encrypted file.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Azure AD Internals suite

  • Website: https://aadinternals.com/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: Azure AD Internals suite is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

Azure Security

  • Website: https://www.manning.com/books/azure-security-2
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: Azure Security is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: A practical guide to the native security services of Microsoft Azure.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

BlueTeam Lab

  • Website: https://github.com/op7ic/BlueTeam.Lab
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Threat Detection, Awesome Forensics

What it does: BlueTeam Lab is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Blue Team detection lab created with Terraform and Ansible in Azure.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Labs.

Back to Category Index

chamber

  • Website: https://github.com/segmentio/chamber
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: chamber is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Store secrets using AWS KMS and SSM Parameter Store.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Checkov

  • Website: https://www.checkov.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Checkov is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Static analysis for Terraform (infrastructure as code) to help detect CIS policy violations and prevent cloud security misconfiguration.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Cloud Access Security Broker

  • Website: https://www.gartner.com/en/information-technology/glossary/cloud-access-security-brokers-casbs
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: Cloud Access Security Broker is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: , if company's IT environment uses a lot of external services like SaaS/IaaS:.

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

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

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Cloud Active Defense

  • Website: https://github.com/SAP/cloud-active-defense?tab=readme-ov-file
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Honeypots

What it does: Cloud Active Defense is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Cloud active defense lets you deploy decoys right into your cloud applications, putting adversaries into a dilemma: to hack or not to hack?.

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

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

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

Back to Category Index

confidant

  • Website: https://github.com/lyft/confidant
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: confidant is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Stores secrets in AWS DynamoDB, encrypted at rest and integrates with IAM.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Consul

  • Website: https://consul.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Consul is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Solution to connect and configure applications across dynamic, distributed infrastructure and, with Consul Connect, enabling secure service-to-service communication with automatic TLS encryption and identity-based authorization.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Service meshes.

Back to Category Index

Cortex

  • Website: https://cortexmetrics.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Cortex is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Provides horizontally scalable, highly available, multi-tenant, long term storage for Prometheus.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Distributed monitoring.

Back to Category Index

credstash

  • Website: https://github.com/fugue/credstash
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: credstash is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Store secrets using AWS KMS and DynamoDB.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

CrowdStrike Reporting Tool for Azure

  • Website: https://github.com/CrowdStrike/CRT
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: CrowdStrike Reporting Tool for Azure is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

GCP Security Analytics

  • Website: https://github.com/GoogleCloudPlatform/security-analytics
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Threat Detection

What it does: GCP Security Analytics is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Community Security Analytics provides a set of community-driven audit & threat queries for Google 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 Threat Detection and Hunting > Detection Rules.

Back to Category Index

Gluu Server

  • Website: https://gluu.org/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Gluu Server is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Central authentication and authorization for Web and mobile applications with a Free and Open Source Software cloud-native community distribution.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Identity and AuthN/AuthZ.

Back to Category Index

gVisor

  • Website: https://github.com/google/gvisor
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: gVisor is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Application kernel, written in Go, that implements a substantial portion of the Linux system surface to provide an isolation boundary between the application and the host kernel.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

Infection Monkey

  • Website: https://github.com/guardicore/monkey
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security, Awesome Threat Detection

What it does: Infection Monkey is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: An open source Breach and Attack Simulation (BAS) tool that assesses the resiliency of private and public cloud environments to post-breach attacks and lateral movement.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Istio

  • Website: https://istio.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Istio is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Service meshes.

Back to Category Index

Jaeger

  • Website: https://www.jaegertracing.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Jaeger is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Distributed tracing platform backend used for monitoring and troubleshooting microservices-based distributed 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 Cybersecurity Blue Team > Cloud platform security > Distributed monitoring.

Back to Category Index

k-rail

  • Website: https://github.com/cruise-automation/k-rail
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: k-rail is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Workload policy enforcement tool for Kubernetes.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Kata Containers

  • Website: https://katacontainers.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Kata Containers is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Secure container runtime with lightweight virtual machines that feel and perform like containers, but provide stronger workload isolation using hardware virtualization technology as a second layer of defense.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

kube-hunter

  • Website: https://kube-hunter.aquasec.com/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: kube-hunter is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Open-source tool that runs a set of tests ("hunters") for security issues in Kubernetes clusters from either outside ("attacker's view") or inside a cluster.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

kubernetes-event-exporter

  • Website: https://github.com/opsgenie/kubernetes-event-exporter
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: kubernetes-event-exporter is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Allows exporting the often missed Kubernetes events to various outputs so that they can be used for observability or alerting purposes.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

KubeSec

  • Website: https://kubesec.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: KubeSec is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Static analyzer of Kubernetes manifests that can be run locally, as a Kuberenetes admission controller, or as its own cloud service.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Kyverno

  • Website: https://kyverno.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Kyverno is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Policy engine designed for Kubernetes.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Linkerd

  • Website: https://linkerd.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Linkerd is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Ultra light Kubernetes-specific service mesh that adds observability, reliability, and security to Kubernetes applications without requiring any modification of the application itself.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

M365/Azure compromise asssessment SOP

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/sop_M365_compromise_assessment.md
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: M365/Azure compromise asssessment SOP is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Managed Kubernetes Inspection Tool (MKIT)

  • Website: https://github.com/darkbitio/mkit
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Managed Kubernetes Inspection Tool (MKIT) is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Query and validate several common security-related configuration settings of managed Kubernetes cluster objects and the workloads/resources running inside the cluster.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Microsoft Azure Sentinel

  • Website: https://azure.microsoft.com/en-us/products/microsoft-sentinel/#overview
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: Microsoft Azure Sentinel is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

Open Policy Agent (OPA)

  • Website: https://www.openpolicyagent.org/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Open Policy Agent (OPA) is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Unified toolset and framework for policy across the cloud native stack.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Policy enforcement.

Back to Category Index

OpenTelemetry

  • Website: https://opentelemetry.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OpenTelemetry is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Observability framework for cloud-native software, comprising a collection of tools, APIs, and SDKs for exporting application performance metrics to a tracing backend (formerly maintained by the OpenTracing and OpenCensus projects).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Distributed monitoring.

Back to Category Index

Polaris

  • Website: https://polaris.docs.fairwinds.com/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Polaris is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Validates Kubernetes best practices by running tests against code commits, a Kubernetes admission request, or live resources already running in a cluster.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Principal Mapper (PMapper)

  • Website: https://github.com/nccgroup/PMapper
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Principal Mapper (PMapper) is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Quickly evaluate IAM permissions in AWS via script and library capable of identifying risks in the configuration of AWS Identity and Access Management (IAM) for an AWS account or an AWS organization.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

Prometheus

  • Website: https://prometheus.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Prometheus is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Open-source systems monitoring and alerting toolkit originally built at SoundCloud.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Distributed monitoring.

Back to Category Index

Prowler

  • Website: https://github.com/toniblyx/prowler
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Prowler is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Tool based on AWS-CLI commands for Amazon Web Services account security assessment and hardening.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

Regula

  • Website: https://regula.dev/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Regula is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Checks infrastructure as code templates (Terraform, CloudFormation, K8s manifests) for AWS, Azure, Google Cloud, and Kubernetes security and compliance using Open Policy Agent/Rego.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Policy enforcement.

Back to Category Index

Scout Suite

  • Website: https://github.com/nccgroup/ScoutSuite
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome SOC

What it does: Scout Suite is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Open source multi-cloud security-auditing tool, which enables security posture assessment of cloud 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Sealed Secrets

  • Website: https://github.com/bitnami-labs/sealed-secrets
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Sealed Secrets is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Kubernetes controller and tool for one-way encrypted Secrets.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security > Kubernetes.

Back to Category Index

Selefra

  • Website: https://github.com/selefra/selefra
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security

What it does: Selefra is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: An open-source policy-as-code software that provides analytics for multi-cloud and SaaS.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > DevOps.

Back to Category Index

Sentinel Attack

  • Website: https://github.com/BlueTeamLabs/sentinel-attack
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Threat Detection

What it does: Sentinel Attack is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: A repository of Azure Sentinel alerts and hunting queries leveraging sysmon and the MITRE ATT&CK 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 > Tools.

Back to Category Index

Sops

  • Website: https://github.com/mozilla/sops
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: Sops is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Editor of encrypted files that supports YAML, JSON, ENV, INI and binary formats and encrypts with AWS KMS, GCP KMS, Azure Key Vault, and PGP.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

terrascan

  • Website: https://runterrascan.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: terrascan is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Static code analyzer for Infrastructure as Code tools that helps detect compliance and security violations to mitigate risk before provisioning cloud native 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 Cybersecurity Blue Team > DevSecOps.

Back to Category Index

Thor Cloud lite

  • Website: https://www.nextron-systems.com/2023/10/30/introducing-thor-cloud-lite-seamless-on-demand-security-scanning-made-easy/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: Thor Cloud lite is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Threat Matrix for Azure Storage services

  • Website: https://microsoft.github.io/Threat-matrix-for-storage-services/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome SOC

What it does: Threat Matrix for Azure Storage services is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Varna

  • Website: https://github.com/endgameinc/varna
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Threat Detection

What it does: Varna is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: A quick & cheap AWS CloudTrail Monitoring with Event Query Language (EQL).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Zipkin

  • Website: https://zipkin.io/
  • Model: Open Source
  • Category: Cloud Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Zipkin is used in cloud security programs to support multi-cloud posture monitoring, workload protection, and misconfiguration control. Source summaries describe it as: Distributed tracing system backend that helps gather timing data needed to troubleshoot latency problems in service 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 Cybersecurity Blue Team > Cloud platform security > Distributed monitoring.

Back to Category Index

Container & Kubernetes Security

This category contains 7 documented tools. It focuses on capabilities used for image integrity checks, cluster policy enforcement, and runtime threat detection. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Bane

  • Website: https://github.com/genuinetools/bane
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Bane is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Custom and better AppArmor profile generator for Docker containers.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Bunkerized-nginx

  • Website: https://github.com/bunkerity/bunkerized-nginx
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Bunkerized-nginx is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Docker image of an NginX configuration and scripts implementing many defensive techniques for Web sites.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security configurations.

Back to Category Index

Clair

  • Website: https://github.com/coreos/clair
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Clair is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Static analysis tool to probe for vulnerabilities introduced via application container (e.g., Docker) images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

DShield docker

  • Website: https://github.com/xme/dshield-docker
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Honeypots

What it does: DShield docker is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Docker container running cowrie with DShield output enabled.

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

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

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

Back to Category Index

Oriana

  • Website: https://github.com/mvelazc0/Oriana
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Threat Detection

What it does: Oriana is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Lateral movement and threat hunting tool for Windows environments built on Django comes Docker ready.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Snyk

  • Website: https://snyk.io/
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Snyk is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Finds and fixes vulnerabilities and license violations in open source dependencies and container images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Teleport

  • Website: https://goteleport.com/
  • Model: Open Source
  • Category: Container & Kubernetes Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Teleport is used in container & kubernetes security programs to support image integrity checks, cluster policy enforcement, and runtime threat detection. Source summaries describe it as: Allows engineers and security professionals to unify access for SSH servers, Kubernetes clusters, web applications, and databases across all 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 Cybersecurity Blue Team > Communications security (COMSEC).

Back to Category Index

Deception & Honeypots

This category contains 251 documented tools. It focuses on capabilities used for early attacker interaction detection and high-confidence alerting. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Acapulco

  • Website: https://github.com/hgascon/acapulco
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Acapulco is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Automated Attack Community Graph Construction.

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

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

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

Back to Category Index

ADBHoney

  • Website: https://github.com/huuck/ADBHoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ADBHoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction honeypot that simulates an Android device running Android Debug Bridge (ADB) server 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: Contents > Honeypots.

Back to Category Index

Afterglow

  • Website: http://afterglow.sourceforge.net/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Afterglow is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Data Tools.

Back to Category Index

AMTHoneypot

  • Website: https://github.com/packetflare/amthoneypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: AMTHoneypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot for Intel's AMT Firmware Vulnerability CVE-2017-5689.

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

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

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

Back to Category Index

Amun

  • Website: http://amunhoney.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Amun is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Vulnerability emulation honeypot.

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

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

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

Back to Category Index

Antivmdetect

  • Website: https://github.com/nsmfoo/antivmdetection
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Antivmdetect is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Script to create templates to use with VirtualBox to make VM detection harder.

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

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

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

Back to Category Index

arctic-swallow

  • Website: https://github.com/ajackal/arctic-swallow
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: arctic-swallow is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction honeypot.

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

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

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

Back to Category Index

Artemnesia VoIP

  • Website: http://artemisa.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Artemnesia VoIP is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Artillery

  • Website: https://github.com/BinaryDefense/artillery
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Artillery is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Combination honeypot, filesystem monitor, and alerting system designed to protect Linux and Windows operating 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 Cybersecurity Blue Team > Host-based tools.

Back to Category Index

Artillery

  • Website: https://github.com/trustedsec/artillery/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Artillery is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Open-source blue team tool designed to protect Linux and Windows operating systems through multiple methods.

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

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

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

Back to Category Index

Bait and Switch

  • Website: http://baitnswitch.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Bait and Switch is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Redirects all hostile traffic to a honeypot that is partially mirroring your production 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: Contents > Honeypots.

Back to Category Index

basic-auth-pot (bap)

  • Website: https://github.com/bjeborn/basic-auth-pot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: basic-auth-pot (bap) is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: HTTP Basic Authentication honeypot.

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

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

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

Back to Category Index

beelzebub

  • Website: https://github.com/mariocandela/beelzebub
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: beelzebub is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A secure honeypot framework, extremely easy to configure by yaml 🚀.

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

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

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

Back to Category Index

Bifrozt

  • Website: https://github.com/Ziemeck/bifrozt-ansible
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Bifrozt is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Automatic deploy bifrozt with ansible.

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

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

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

Back to Category Index

Blacknet

  • Website: https://github.com/morian/blacknet
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Blacknet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Multi-head SSH honeypot 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: Contents > Honeypots.

Back to Category Index

Bluepot

  • Website: https://github.com/andrewmichaelsmith/bluepot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Bluepot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

bwpot

  • Website: https://github.com/graneed/bwpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: bwpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Breakable Web applications honeyPot.

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

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

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

Back to Category Index

canarytokendetector

  • Website: https://github.com/referefref/canarytokendetector
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: canarytokendetector is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Tool for detection and nullification of Thinkst CanaryTokens.

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

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

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

Back to Category Index

Capture BAT

  • Website: https://www.honeynet.org/node/315
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Capture BAT is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Capture-HPC

  • Website: https://projects.honeynet.org/capture-hpc
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Capture-HPC is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: High interaction client honeypot (also called honeyclient).

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

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

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

Back to Category Index

Capture-HPC-Linux

  • Website: https://redmine.honeynet.org/projects/linux-capture-hpc/wiki
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Capture-HPC-Linux is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Capture-HPC-NG

  • Website: https://github.com/CERT-Polska/HSN-Capture-HPC-NG
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Capture-HPC-NG is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

CC2ASN

  • Website: http://www.cc2asn.com/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: CC2ASN is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple lookup service for AS-numbers and prefixes belonging to any given country in the world.

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

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

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

Back to Category Index

ciscoasa_honeypot

  • Website: https://github.com/cymmetria/ciscoasa_honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ciscoasa_honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A low interaction honeypot for the Cisco ASA component capable of detecting CVE-2018-0101, a DoS and remote code execution vulnerability.

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

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

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

Back to Category Index

Conpot

  • Website: https://github.com/mushorg/conpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Conpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: ICS/SCADA honeypot.

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

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

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

Back to Category Index

Cowrie

  • Website: https://github.com/micheloosterhof/cowrie
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis

What it does: Cowrie is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SSH honeypot, based.

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

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

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

Back to Category Index

Cowrie

  • Website: https://github.com/cowrie/cowrie
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Cowrie is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Cowrie SSH Honeypot (based on kippo).

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

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

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

Back to Category Index

cowrie2neo

  • Website: https://github.com/xlfe/cowrie2neo
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: cowrie2neo is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Parse cowrie honeypot logs into a neo4j 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: Contents > Honeypots.

Back to Category Index

Damn Simple Honeypot (DSHP)

  • Website: https://github.com/naorlivne/dshp
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Damn Simple Honeypot (DSHP) is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot framework with pluggable handlers.

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

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

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

Back to Category Index

DAVIX

  • Website: https://www.secviz.org/node/89
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: DAVIX is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: The DAVIX Live CD.

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

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

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

Back to Category Index

dcept

  • Website: https://github.com/secureworks/dcept
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: dcept is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Tool for deploying and detecting use of Active Directory honeytokens.

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

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

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

Back to Category Index

ddospot

  • Website: https://github.com/aelth/ddospot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ddospot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: NTP, DNS, SSDP, Chargen and generic UDP-based amplification DDoS honeypot.

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

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

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

Back to Category Index

Deception Toolkit

  • Website: http://www.all.net/dtk/dtk.html
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Deception Toolkit is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Deception-as-Detection

  • Website: https://github.com/0x4D31/deception-as-detection
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Threat Detection

What it does: Deception-as-Detection is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Deception based detection techniques mapped to the MITRE’s ATT&CK 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 > Resources.

Back to Category Index

Delilah

  • Website: https://github.com/SecurityTW/delilah
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Delilah is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Elasticsearch Honeypot written in Python (originally from Novetta).

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

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

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

Back to Category Index

dhp

  • Website: https://github.com/ciscocsirt/dhp
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: dhp is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple Docker Honeypot server emulating small snippets of the Docker HTTP API.

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

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

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

Back to Category Index

dicompot

  • Website: https://github.com/nsmfoo/dicompot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: dicompot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: DICOM Honeypot.

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

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

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

Back to Category Index

Dionaea

  • Website: https://github.com/DinoTools/dionaea
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Dionaea is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot designed to trap malware.

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

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

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

Back to Category Index

DionaeaFR

  • Website: https://github.com/rubenespadas/DionaeaFR
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: DionaeaFR is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Front Web to Dionaea low-interaction honeypot.

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

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

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

Back to Category Index

django-admin-honeypot

  • Website: https://github.com/dmpayton/django-admin-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: django-admin-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Fake Django admin login screen to notify admins of attempted unauthorized access.

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

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

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

Back to Category Index

Django-kippo

  • Website: https://github.com/jedie/django-kippo
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Django-kippo is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Django App for kippo SSH Honeypot.

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

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

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

Back to Category Index

dnsMole

  • Website: https://code.google.com/archive/p/dns-mole/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: dnsMole is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Analyses DNS traffic and potentionaly detect botnet command and control server activity, along with infected hosts.

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

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

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

Back to Category Index

Docker honeynet

  • Website: https://github.com/sreinhardt/Docker-Honeynet
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Docker honeynet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Several Honeynet tools set up for Docker containers.

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

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

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

Back to Category Index

Dockerized Thug

  • Website: https://hub.docker.com/r/honeynet/thug/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Dockerized Thug is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Dockerized to analyze malicious web content.

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

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

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

Back to Category Index

Dockerpot

  • Website: https://github.com/mrschyte/dockerpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Dockerpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Docker based honeypot.

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

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

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

Back to Category Index

DolosHoneypot

  • Website: https://github.com/Marist-Innovation-Lab/DolosHoneypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: DolosHoneypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SDN (software defined networking) honeypot.

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

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

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

Back to Category Index

Droidbox

  • Website: https://code.google.com/archive/p/droidbox/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Droidbox is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

drupo

  • Website: https://github.com/d1str0/drupot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: drupo is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Drupal Honeypot.

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

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

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

Back to Category Index

DShield Web Honeypot Project

  • Website: https://sites.google.com/site/webhoneypotsite/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: DShield Web Honeypot Project is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Elastic honey

  • Website: https://github.com/jordan-wright/elastichoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Elastic honey is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple Elasticsearch Honeypot.

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

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

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

Back to Category Index

ElasticPot

  • Website: https://gitlab.com/bontchev/elasticpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ElasticPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: An Elasticsearch Honeypot.

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

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

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

Back to Category Index

Ensnare

  • Website: https://github.com/ahoernecke/ensnare
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Ensnare is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Easy to deploy Ruby honeypot.

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

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

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

Back to Category Index

EoHoneypotBundle

  • Website: https://github.com/eymengunay/EoHoneypotBundle
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: EoHoneypotBundle is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot type for Symfony2 forms.

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

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

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

Back to Category Index

ESPot

  • Website: https://github.com/mycert/ESPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ESPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Elasticsearch honeypot written in NodeJS, to capture every attempts to exploit CVE-2014-3120.

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

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

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

Back to Category Index

Express honeypot

  • Website: https://github.com/christophe77/express-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Express honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: RFI & LFI honeypot using nodeJS and express.

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

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

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

Back to Category Index

fapro

  • Website: https://github.com/fofapro/fapro
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: fapro is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Fake Protocol 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: Contents > Honeypots.

Back to Category Index

galah

  • Website: https://github.com/0x4D31/galah
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: galah is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: an LLM-powered web honeypot using the OpenAI API.

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

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

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

Back to Category Index

GasPot

  • Website: https://github.com/sjhilt/GasPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: GasPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Veeder Root Gaurdian AST, common in the oil and gas industry.

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

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

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

Back to Category Index

GenAIPot

  • Website: https://github.com/ls1911/GenAIPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: GenAIPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: The first A.I based open source honeypot. supports POP3 and SMTP protocols and generates content using A.I based on user description.

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

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

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

Back to Category Index

Ghost-usb

  • Website: https://github.com/honeynet/ghost-usb-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Ghost-usb is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot for malware that propagates via USB storage devices.

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

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

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

Back to Category Index

Glastopf

  • Website: https://github.com/mushorg/glastopf
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Glastopf is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Web application honeypot.

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

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

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

Back to Category Index

Glastopf Analytics

  • Website: https://github.com/katkad/Glastopf-Analytics
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Glastopf Analytics is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Easy honeypot statistics.

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

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

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

Back to Category Index

glutton

  • Website: https://github.com/mushorg/glutton
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: glutton is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: All eating honeypot.

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

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

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

Back to Category Index

go-emulators

  • Website: https://github.com/kingtuna/go-emulators
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: go-emulators is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot Golang emulators.

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

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

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

Back to Category Index

go-HoneyPot

  • Website: https://github.com/Mojachieee/go-HoneyPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: go-HoneyPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot server 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: Contents > Honeypots.

Back to Category Index

go-sshoney

  • Website: https://github.com/ashmckenzie/go-sshoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: go-sshoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SSH Honeypot.

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

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

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

Back to Category Index

go0r

  • Website: https://github.com/fzerorubigd/go0r
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: go0r is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple ssh honeypot 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: Contents > Honeypots.

Back to Category Index

gohoney

  • Website: https://github.com/PaulMaddox/gohoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: gohoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SSH honeypot 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: Contents > Honeypots.

Back to Category Index

Google Hack Honeypot

  • Website: http://ghh.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Google Hack Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Designed to provide reconnaissance against attackers that use search engines as a hacking tool against your 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: Contents > Honeypots.

Back to Category Index

gridpot

  • Website: https://github.com/sk4ld/gridpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: gridpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Open source tools for realistic-behaving electric grid honeynets.

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

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

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

Back to Category Index

Helix

  • Website: https://github.com/Zeerg/helix-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Helix is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: K8s API Honeypot with Active Defense 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: Contents > Honeypots.

Back to Category Index

HellPot

  • Website: https://github.com/yunginnanet/HellPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HellPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot that tries to crash the bots and clients that visit it's location.

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

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

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

Back to Category Index

Heralding

  • Website: https://github.com/johnnykv/heralding
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Heralding is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Credentials catching honeypot.

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

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

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

Back to Category Index

Hexgolems - Pint Debugger Backend

  • Website: https://github.com/hexgolems/pint
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Hexgolems - Pint Debugger Backend is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Debugger backend and LUA wrapper for PIN.

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

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

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

Back to Category Index

Hexgolems - Schem Debugger Frontend

  • Website: https://github.com/hexgolems/schem
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Hexgolems - Schem Debugger Frontend is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Debugger frontend.

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

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

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

Back to Category Index

HIHAT

  • Website: http://hihat.sourceforge.net/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HIHAT is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Transform arbitrary PHP applications into web-based high-interaction Honeypots.

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

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

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

Back to Category Index

hived

  • Website: https://github.com/sahilm/hived
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: hived is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Golang-based honeypot.

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

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

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

Back to Category Index

Honeeepi

  • Website: https://redmine.honeynet.org/projects/honeeepi/wiki
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeeepi is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot sensor on a Raspberry Pi based on a customized Raspbian 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: Contents > Honeypots.

Back to Category Index

honey_ports

  • Website: https://github.com/run41/honey_ports
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honey_ports is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Very simple but effective docker deployed honeypot to detect port scanning in your environment.

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

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

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

Back to Category Index

honeyalarmg2

  • Website: https://github.com/schmalle/honeyalarmg2
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyalarmg2 is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simplified UI for showing honeypot alarms.

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

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

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

Back to Category Index

Honeybits

  • Website: https://github.com/0x4D31/honeybits
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeybits is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple tool designed to enhance the effectiveness of your traps by spreading breadcrumbs and honeytokens across your production servers and workstations to lure the attacker toward your honeypots.

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

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

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

Back to Category Index

HoneyBOT

  • Website: http://www.atomicsoftwaresolutions.com/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyBOT is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

HoneyBrid

  • Website: http://honeybrid.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyBrid is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

HoneyC

  • Website: https://projects.honeynet.org/honeyc
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyC is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Honeycomb

  • Website: http://www.icir.org/christian/honeycomb/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeycomb is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Automated signature creation using honeypots.

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

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

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

Back to Category Index

Honeycomb

  • Website: http://www.honeyd.org/tools.php
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeycomb is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeyd Tools.

Back to Category Index

honeycomb_plugins

  • Website: https://github.com/Cymmetria/honeycomb_plugins
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeycomb_plugins is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Plugin repository for Honeycomb, the honeypot framework by Cymmetria.

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

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

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

Back to Category Index

Honeyd

  • Website: http://www.honeyd.org/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis

What it does: Honeyd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Create a virtual honeynet.

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

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

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

Back to Category Index

Honeyd

  • Website: https://github.com/provos/honeyd
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: See .

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

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

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

Back to Category Index

Honeyd-Viz

  • Website: https://bruteforcelab.com/honeyd-viz
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyd-Viz is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeyd Tools.

Back to Category Index

Honeyd2MySQL

  • Website: https://bruteforcelab.com/honeyd2mysql
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyd2MySQL is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeyd Tools.

Back to Category Index

honeydet

  • Website: https://github.com/referefref/honeydet
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeydet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Signature based honeypot detector tool 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: Contents > Honeypots.

Back to Category Index

HoneyDrive

  • Website: https://bruteforce.gr/honeydrive/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Malware Analysis

What it does: HoneyDrive is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot bundle Linux distro.

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

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

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

Back to Category Index

HoneyDrive

  • Website: https://bruteforcelab.com/honeydrive
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyDrive is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Honeydsum.pl

  • Website: https://github.com/DataSoft/Honeyd/blob/master/scripts/misc/honeydsum-v0.3/honeydsum.pl
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeydsum.pl is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeyd Tools.

Back to Category Index

honeyfs

  • Website: https://github.com/referefref/honeyfs
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyfs is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Tool to create artificial file systems for medium/high interaction honeypots.

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

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

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

Back to Category Index

Honeygrove

  • Website: https://github.com/UHH-ISS/honeygrove
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeygrove is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Multi-purpose modular honeypot based on Twisted.

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

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

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

Back to Category Index

honeyhttpd

  • Website: https://github.com/bocajspear1/honeyhttpd
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyhttpd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python-based web server honeypot builder.

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

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

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

Back to Category Index

honeyku

  • Website: https://github.com/0x4D31/honeyku
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyku is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Heroku-based web honeypot that can be used to create and monitor fake HTTP endpoints (i.e. honeytokens).

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

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

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

Back to Category Index

honeymail

  • Website: https://github.com/sec51/honeymail
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeymail is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SMTP honeypot 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: Contents > Honeypots.

Back to Category Index

HoneyMalt

  • Website: https://github.com/SneakersInc/HoneyMalt
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyMalt is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Maltego tranforms for mapping Honeypot 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: Contents > Data Tools.

Back to Category Index

HoneyMap

  • Website: https://github.com/fw42/honeymap
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyMap is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Real-time websocket stream of GPS events on a fancy SVG world map.

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

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

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

Back to Category Index

Honeymole

  • Website: https://web.archive.org/web/20100326040550/http://www.honeynet.org.pt:80/index.php/HoneyMole
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeymole is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Deploy multiple sensors that redirect traffic to a centralized collection of honeypots.

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

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

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

Back to Category Index

honeyntp

  • Website: https://github.com/fygrave/honeyntp
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyntp is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: NTP logger/honeypot.

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

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

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

Back to Category Index

Honeyperl

  • Website: https://sourceforge.net/projects/honeyperl/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyperl is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot software based in Perl with plugins developed for many functions like : wingates, telnet, squid, smtp, etc.

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

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

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

Back to Category Index

Honeyport

  • Website: https://github.com/securitygeneration/Honeyport
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyport is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple honeyport written in Bash and 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: Contents > Honeypots.

Back to Category Index

honeypot

  • Website: https://github.com/jadb/honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: The Project Honey Pot un-official PHP SDK.

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

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

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

Back to Category Index

Honeypot (Dionaea and kippo) setup script

  • Website: https://github.com/andrewmichaelsmith/honeypot-setup-script/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeypot (Dionaea and kippo) setup script is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Guides.

Back to Category Index

Honeypot-32764

  • Website: https://github.com/knalli/honeypot-for-tcp-32764
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeypot-32764 is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot for router backdoor (TCP 32764).

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

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

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

Back to Category Index

honeypot-camera

  • Website: https://github.com/alexbredo/honeypot-camera
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypot-camera is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Observation camera honeypot.

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

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

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

Back to Category Index

honeypot-ftp

  • Website: https://github.com/alexbredo/honeypot-ftp
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypot-ftp is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: FTP Honeypot.

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

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

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

Back to Category Index

honeypot.go

  • Website: https://github.com/mdp/honeypot.go
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypot.go is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SSH Honeypot 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: Contents > Honeypots.

Back to Category Index

honeypotDisplay

  • Website: https://github.com/Joss-Steward/honeypotDisplay
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypotDisplay is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Flask website which displays data gathered from an SSH Honeypot.

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

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

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

Back to Category Index

honeypotpi

  • Website: https://github.com/free5ty1e/honeypotpi
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypotpi is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Script for turning a Raspberry Pi into a HoneyPot Pi.

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

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

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

Back to Category Index

honeypots

  • Website: https://github.com/qeeqbox/honeypots
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeypots is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: 25 different honeypots in a single pypi package! (dns, ftp, httpproxy, http, https, imap, mysql, pop3, postgres, redis, smb, smtp, socks5, ssh, telnet, vnc, mssql, elastic, ldap, ntp, memcache, snmp, oracle, sip and irc).

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

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

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

Back to Category Index

HoneyPress

  • Website: https://github.com/kungfuguapo/HoneyPress
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyPress is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python based WordPress honeypot 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: Contents > Honeypots.

Back to Category Index

Honeyprint

  • Website: https://github.com/glaslos/honeyprint
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyprint is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Printer honeypot.

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

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

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

Back to Category Index

Honeysnap

  • Website: https://projects.honeynet.org/honeysnap/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeysnap is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

honeyssh

  • Website: https://github.com/ppacher/honeyssh
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyssh is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Credential dumping SSH honeypot with statistics.

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

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

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

Back to Category Index

HoneyStats

  • Website: https://sourceforge.net/projects/honeystats/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyStats is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Statistical view of the recorded activity on a Honeynet.

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

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

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

Back to Category Index

HoneyThing

  • Website: https://github.com/omererdem/honeything
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyThing is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: TR-069 Honeypot.

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

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

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

Back to Category Index

honeyup

  • Website: https://github.com/LogoiLab/honeyup
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: honeyup is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: An uploader honeypot designed to look like poor website 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: Contents > Honeypots.

Back to Category Index

Honeyview

  • Website: http://honeyview.sourceforge.net/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeyview is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeyd Tools.

Back to Category Index

Honeywall

  • Website: https://projects.honeynet.org/honeywall/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Honeywall is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

HoneyWeb

  • Website: https://code.google.com/archive/p/gsoc-honeyweb/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyWeb is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Web interface created to manage and remotely share Honeyclients 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: Contents > Honeypots.

Back to Category Index

HoneyWRT

  • Website: https://github.com/CanadianJeff/honeywrt
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HoneyWRT is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction Python honeypot designed to mimic services or ports that might get targeted by attackers.

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

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

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

Back to Category Index

HonnyPotter

  • Website: https://github.com/MartinIngesen/HonnyPotter
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HonnyPotter is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: WordPress login honeypot for collection and analysis of failed login attempts.

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

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

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

Back to Category Index

Hontel

  • Website: https://github.com/stamparm/hontel
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Hontel is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Telnet Honeypot.

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

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

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

Back to Category Index

hornet

  • Website: https://github.com/czardoz/hornet
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: hornet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Medium interaction SSH honeypot that supports multiple virtual hosts.

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

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

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

Back to Category Index

HpfeedsHoneyGraph

  • Website: https://github.com/yuchincheng/HpfeedsHoneyGraph
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HpfeedsHoneyGraph is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Visualization app to visualize hpfeeds logs.

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

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

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

Back to Category Index

HPfriends

  • Website: http://hpfriends.honeycloud.net/#/home
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: HPfriends is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot data-sharing 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: Contents > Honeypots.

Back to Category Index

hpfriends - real-time social data-sharing

  • Website: https://heipei.io/sigint-hpfriends/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: hpfriends - real-time social data-sharing is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Presentation about HPFriends feed 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: Contents > Honeypots.

Back to Category Index

imap-honey

  • Website: https://github.com/yvesago/imap-honey
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: imap-honey is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: IMAP honeypot 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: Contents > Honeypots.

Back to Category Index

IMHoneypot

  • Website: https://github.com/mushorg/imhoneypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: IMHoneypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

IPP Honey

  • Website: https://gitlab.com/bontchev/ipphoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: IPP Honey is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A honeypot for the Internet Printing Protocol.

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

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

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

Back to Category Index

ipv6-attack-detector

  • Website: https://github.com/mzweilin/ipv6-attack-detector/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ipv6-attack-detector is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Google Summer of Code 2012 project, supported by The Honeynet Project organization.

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

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

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

Back to Category Index

Kako

  • Website: https://github.com/darkarnium/kako
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kako is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypots for a number of well known and deployed embedded device vulnerabilities.

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

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

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

Back to Category Index

Kippo stats

  • Website: https://github.com/mfontani/kippo-stats
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kippo stats is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Mojolicious app to display statistics for your kippo SSH honeypot.

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

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

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

Back to Category Index

Kippo-Graph

  • Website: https://bruteforcelab.com/kippo-graph
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kippo-Graph is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Full featured script to visualize statistics from a Kippo SSH honeypot.

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

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

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

Back to Category Index

Kippo-Malware

  • Website: https://bruteforcelab.com/kippo-malware
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kippo-Malware is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python script that will download all malicious files stored as URLs in a Kippo SSH honeypot 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: Contents > Honeypots.

Back to Category Index

Kippo2ElasticSearch

  • Website: https://bruteforcelab.com/kippo2elasticsearch
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kippo2ElasticSearch is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python script to transfer data from a Kippo SSH honeypot MySQL database to an ElasticSearch instance (server or cluster).

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

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

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

Back to Category Index

kippo_detect

  • Website: https://github.com/andrew-morris/kippo_detect
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: kippo_detect is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Offensive component that detects the presence of the kippo honeypot.

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

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

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

Back to Category Index

Kippo_JunOS

  • Website: https://github.com/gregcmartin/Kippo_JunOS
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kippo_JunOS is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Kippo configured to be a backdoored netscreen.

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

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

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

Back to Category Index

Kojoney2

  • Website: https://github.com/madirish/kojoney2
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Kojoney2 is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction SSH honeypot written in Python and based on Kojoney by Jose Antonio Coret.

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

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

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

Back to Category Index

Kushtaka

  • Website: https://kushtaka.org
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Kushtaka is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Sustainable all-in-one honeypot and honeytoken orchestrator for under-resourced 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 Cybersecurity Blue Team > Honeypots.

Back to Category Index

Laravel Application Honeypot

  • Website: https://github.com/msurguy/Honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Laravel Application Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple spam prevention package for Laravel 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: Contents > Honeypots.

Back to Category Index

Log4Pot

  • Website: https://github.com/thomaspatzke/Log4Pot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Log4Pot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A honeypot for the Log4Shell vulnerability (CVE-2021-44228).

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

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

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

Back to Category Index

Longitudinal Analysis of SSH Cowrie Honeypot Logs

  • Website: https://github.com/deroux/longitudinal-analysis-cowrie
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Longitudinal Analysis of SSH Cowrie Honeypot Logs is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python based command line tool to analyze cowrie logs over 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: Contents > Honeypots.

Back to Category Index

Lophiid

  • Website: https://github.com/mrheinen/lophiid/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Lophiid is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Distributed web application honeypot to interact with large scale exploitation attempts.

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

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

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

Back to Category Index

Lyrebird

  • Website: https://hub.docker.com/r/lyrebird/honeypot-base/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Lyrebird is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modern high-interaction honeypot 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: Contents > Honeypots.

Back to Category Index

Mail::SMTP::Honeypot

  • Website: https://metacpan.org/pod/release/MIKER/Mail-SMTP-Honeypot-0.11/Honeypot.pm
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Mail::SMTP::Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Perl module that appears to provide the functionality of a standard SMTP 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: Contents > Honeypots.

Back to Category Index

Mailoney

  • Website: https://github.com/phin3has/mailoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Mailoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SMTP honeypot 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: Contents > Honeypots.

Back to Category Index

Malbait

  • Website: https://github.com/batchmcnulty/Malbait
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Malbait is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple TCP/UDP honeypot implemented in Perl.

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

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

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

Back to Category Index

Manuka

  • Website: https://github.com/spaceraccoon/manuka
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Manuka is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Open-sources intelligence (OSINT) honeypot that monitors reconnaissance attempts by threat actors and generates actionable intelligence for Blue 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 Cybersecurity Blue Team > Honeypots.

Back to Category Index

Manuka

  • Website: https://github.com/andrewmichaelsmith/manuka
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Manuka is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Docker based honeypot (Dionaea and Kippo).

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

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

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

Back to Category Index

medpot

  • Website: https://github.com/schmalle/medpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: medpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: HL7 / FHIR honeypot.

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

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

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

Back to Category Index

MICROS honeypot

  • Website: https://github.com/Cymmetria/micros_honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MICROS honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction honeypot to detect CVE-2018-2636 in the Oracle Hospitality Simphony component of Oracle Hospitality Applications (MICROS).

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

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

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

Back to Category Index

miniprint

  • Website: https://github.com/sa7mon/miniprint
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: miniprint is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A medium interaction printer honeypot.

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

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

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

Back to Category Index

MockSSH

  • Website: https://github.com/ncouture/MockSSH
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MockSSH is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Mock an SSH server and define all commands it supports (Python, Twisted).

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

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

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

Back to Category Index

modpot

  • Website: https://github.com/referefref/modpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: modpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modpot is a modular web application honeypot framework and management application written in Golang and making use of gin 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: Contents > Honeypots.

Back to Category Index

MongoDB-HoneyProxy

  • Website: https://github.com/Plazmaz/MongoDB-HoneyProxy
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MongoDB-HoneyProxy is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: MongoDB honeypot proxy.

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

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

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

Back to Category Index

MonkeySpider

  • Website: http://monkeyspider.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MonkeySpider is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

MTPot

  • Website: https://github.com/Cymmetria/MTPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MTPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Open Source Telnet Honeypot, focused on Mirai malware.

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

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

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

Back to Category Index

mysql-honeypotd

  • Website: https://github.com/sjinks/mysql-honeypotd
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: mysql-honeypotd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction MySQL honeypot written in C.

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

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

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

Back to Category Index

MysqlPot

  • Website: https://github.com/schmalle/MysqlPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: MysqlPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: MySQL honeypot, still very early stage.

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

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

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

Back to Category Index

node-ftp-honeypot

  • Website: https://github.com/christophe77/node-ftp-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: node-ftp-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: FTP server honeypot in JS.

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

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

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

Back to Category Index

Nodepot

  • Website: https://github.com/schmalle/Nodepot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Nodepot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: NodeJS web application honeypot.

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

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

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

Back to Category Index

NoSQLpot

  • Website: https://github.com/torque59/nosqlpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: NoSQLpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot framework built on a NoSQL-style 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: Contents > Honeypots.

Back to Category Index

NOVA

  • Website: https://github.com/DataSoft/Nova
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: NOVA is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Uses honeypots as detectors, looks like a complete 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: Contents > Honeypots.

Back to Category Index

OpenCanary

  • Website: https://github.com/thinkst/opencanary
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: OpenCanary is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modular and decentralised honeypot daemon that runs several canary versions of services that alerts when a service is (ab)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: Contents > Honeypots.

Back to Category Index

owa-honeypot

  • Website: https://github.com/joda32/owa-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: owa-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A basic flask based Outlook Web Honey pot.

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

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

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

Back to Category Index

PasitheaHoneypot

  • Website: https://github.com/Marist-Innovation-Lab/PasitheaHoneypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: PasitheaHoneypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: RestAPI honeypot.

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

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

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

Back to Category Index

PayloadsAllTheThings - Web Cache Deception

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Web%20Cache%20Deception
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - Web Cache Deception is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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 Cache Poisoning.

Back to Category Index

peepdf

  • Website: https://github.com/jesparza/peepdf
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots, Awesome Cyber Security Tools

What it does: peepdf is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Powerful Python tool to analyze PDF documents.

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

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

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

Back to Category Index

pghoney

  • Website: https://github.com/betheroot/pghoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: pghoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low-interaction Postgres Honeypot.

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

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

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

Back to Category Index

PHARM

  • Website: http://www.nepenthespharm.com/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: PHARM is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Manage, report, and analyze your distributed Nepenthes instances.

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

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

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

Back to Category Index

PhoneyC

  • Website: https://github.com/honeynet/phoneyc
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: PhoneyC is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python honeyclient (later replaced by Thug).

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

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

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

Back to Category Index

phpmyadmin_honeypot

  • Website: https://github.com/gfoss/phpmyadmin_honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: phpmyadmin_honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple and effective phpMyAdmin honeypot.

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

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

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

Back to Category Index

portlurker

  • Website: https://github.com/bartnv/portlurker
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: portlurker is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Port listener in Rust with protocol guessing and safe string display.

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

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

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

Back to Category Index

potd

  • Website: https://github.com/lnslbrty/potd
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: potd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Highly scalable low- to medium-interaction SSH/TCP honeypot designed for OpenWrt/IoT devices leveraging several Linux kernel features, such as namespaces, seccomp and thread 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: Contents > Honeypots.

Back to Category Index

Pwnypot

  • Website: https://github.com/shjalayeri/pwnypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Pwnypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: High Interaction Client Honeypot.

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

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

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

Back to Category Index

pyrdp

  • Website: https://github.com/gosecure/pyrdp
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: pyrdp is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: RDP man-in-the-middle and library for Python 3 with the ability to watch connections live or after the fact.

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

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

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

Back to Category Index

Python-Honeypot

  • Website: https://github.com/OWASP/Python-Honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Python-Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: OWASP Honeypot, Automated Deception 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: Contents > Honeypots.

Back to Category Index

Quechua

  • Website: https://bitbucket.org/zaccone/quechua
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Quechua is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

rdppot

  • Website: https://github.com/kryptoslogic/rdppot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: rdppot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: RDP honeypot.

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

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

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

Back to Category Index

RDPy

  • Website: https://github.com/citronneur/rdpy
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: RDPy is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Microsoft Remote Desktop Protocol (RDP) honeypot implemented 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: Contents > Honeypots.

Back to Category Index

RedisHoneyPot

  • Website: https://github.com/cypwnpwnsocute/RedisHoneyPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: RedisHoneyPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: High Interaction Honeypot Solution for Redis protocol.

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

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

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

Back to Category Index

Rumal

  • Website: https://github.com/thugs-rumal/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Rumal is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Thug's Rumāl: a Thug's dress and weapon.

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

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

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

Back to Category Index

SCADA honeynet

  • Website: http://scadahoneynet.sourceforge.net
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: SCADA honeynet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Building Honeypots for Industrial 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: Contents > Honeypots.

Back to Category Index

scada-honeynet

  • Website: http://www.digitalbond.com/blog/2007/07/24/scada-honeynet-article-in-infragard-publication/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: scada-honeynet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Mimics many of the services from a popular PLC and better helps SCADA researchers understand potential risks of exposed control system devices.

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

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

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

Back to Category Index

SentryPeer

  • Website: https://github.com/SentryPeer/SentryPeer
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: SentryPeer is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Protect your SIP Servers from bad actors.

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

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

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

Back to Category Index

Servletpot

  • Website: https://github.com/schmalle/servletpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Servletpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Web application Honeypot.

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

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

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

Back to Category Index

Shadow Daemon

  • Website: https://shadowd.zecure.org/overview/introduction/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Shadow Daemon is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modular Web Application Firewall / High-Interaction Honeypot for PHP, Perl, and Python apps.

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

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

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

Back to Category Index

Shelia

  • Website: https://www.cs.vu.nl/~herbertb/misc/shelia/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Shelia is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Client-side honeypot for attack detection.

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

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

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

Back to Category Index

Shiva

  • Website: https://github.com/shiva-spampot/shiva
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Shiva is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Spam Honeypot with Intelligent Virtual Analyzer.

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

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

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

Back to Category Index

Shiva The Spam Honeypot Tips And Tricks For Getting It Up And Running

  • Website: https://www.pentestpartners.com/security-blog/shiva-the-spam-honeypot-tips-and-tricks-for-getting-it-up-and-running/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Shiva The Spam Honeypot Tips And Tricks For Getting It Up And Running is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

shockpot

  • Website: https://github.com/threatstream/shockpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: shockpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: WebApp Honeypot for detecting Shell Shock exploit attempts.

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

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

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

Back to Category Index

Shockpot-Frontend

  • Website: https://github.com/GovCERT-CZ/Shockpot-Frontend
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Shockpot-Frontend is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Full featured script to visualize statistics from a Shockpot honeypot.

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

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

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

Back to Category Index

slipm-honeypot

  • Website: https://github.com/rshipp/slipm-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: slipm-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple low-interaction port monitoring honeypot.

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

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

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

Back to Category Index

smart-honeypot

  • Website: https://github.com/freak3dot/smart-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: smart-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: PHP Script demonstrating a smart honey pot.

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

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

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

Back to Category Index

SMB Honeypot

  • Website: https://github.com/r0hi7/HoneySMB
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: SMB Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: High interaction SMB service honeypot capable of capturing wannacry-like Malware.

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

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

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

Back to Category Index

SMTPLLMPot

  • Website: https://github.com/referefref/SMTPLLMPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: SMTPLLMPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: A super simple SMTP Honeypot built using GPT3.5.

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

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

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

Back to Category Index

Snare

  • Website: https://github.com/mushorg/snare
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Snare is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Super Next generation Advanced Reactive honeypot.

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

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

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

Back to Category Index

spamd

  • Website: http://man.openbsd.org/cgi-bin/man.cgi?query=spamd%26apropos=0%26sektion=0%26manpath=OpenBSD+Current%26arch=i386%26format=html
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: spamd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

SpamHAT

  • Website: https://github.com/miguelraulb/spamhat
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: SpamHAT is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Spam Honeypot 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: Contents > Honeypots.

Back to Category Index

Spamhole

  • Website: http://www.spamhole.net/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Spamhole is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

ssh-auth-logger

  • Website: https://github.com/JustinAzoff/ssh-auth-logger
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ssh-auth-logger is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low/zero interaction SSH authentication logging honeypot.

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

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

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

Back to Category Index

ssh-honeypot

  • Website: https://github.com/droberson/ssh-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ssh-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Fake sshd that logs IP addresses, usernames, and passwords.

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

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

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

Back to Category Index

ssh-honeypot

  • Website: https://github.com/amv42/sshd-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ssh-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modified version of the OpenSSH deamon that forwards commands to Cowrie where all commands are interpreted and returned.

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

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

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

Back to Category Index

ssh-honeypotd

  • Website: https://github.com/sjinks/ssh-honeypotd
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: ssh-honeypotd is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low-interaction SSH honeypot written in C.

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

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

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

Back to Category Index

sshesame

  • Website: https://github.com/jaksi/sshesame
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sshesame is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Fake SSH server that lets everyone in and logs their activity.

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

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

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

Back to Category Index

sshForShits

  • Website: https://github.com/traetox/sshForShits
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sshForShits is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Framework for a high interaction SSH honeypot.

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

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

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

Back to Category Index

sshhipot

  • Website: https://github.com/magisterquis/sshhipot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sshhipot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: High-interaction MitM SSH honeypot.

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

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

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

Back to Category Index

sshlowpot

  • Website: https://github.com/magisterquis/sshlowpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sshlowpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Yet another no-frills low-interaction SSH honeypot 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: Contents > Honeypots.

Back to Category Index

sshsyrup

  • Website: https://github.com/mkishere/sshsyrup
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sshsyrup is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple SSH Honeypot with features to capture terminal activity and upload to asciinema.org.

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

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

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

Back to Category Index

stack-honeypot

  • Website: https://github.com/CHH/stack-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: stack-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Inserts a trap for spam bots into responses.

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

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

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

Back to Category Index

sticky_elephant

  • Website: https://github.com/betheroot/sticky_elephant
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: sticky_elephant is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Medium interaction postgresql honeypot.

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

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

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

Back to Category Index

StrutsHoneypot

  • Website: https://github.com/Cymmetria/StrutsHoneypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: StrutsHoneypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Struts Apache 2 based honeypot as well as a detection module for Apache 2 servers.

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

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

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

Back to Category Index

Sysdig

  • Website: https://sysdig.com/opensource/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Sysdig is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Open source, system-level exploration allows one to capture system state and activity from a running GNU/Linux instance, then save, filter, and analyze the results.

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

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

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

Back to Category Index

T-Pot

  • Website: https://github.com/dtag-dev-sec/tpotce
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: T-Pot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: All in one honeypot appliance from telecom provider T-Mobile.

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

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

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

Back to Category Index

T-Pot: A Multi-Honeypot Platform

  • Website: https://dtag-dev-sec.github.io/mediator/feature/2015/03/17/concept.html
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: T-Pot: A Multi-Honeypot Platform is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Guides.

Back to Category Index

Tango

  • Website: https://github.com/aplura/Tango
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Tango is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot Intelligence with Splunk.

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

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

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

Back to Category Index

Tanner

  • Website: https://github.com/mushorg/tanner
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Tanner is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Evaluating SNARE 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: Contents > Honeypots.

Back to Category Index

telnet-iot-honeypot

  • Website: https://github.com/Phype/telnet-iot-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: telnet-iot-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python telnet honeypot for catching botnet binaries.

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

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

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

Back to Category Index

TelnetHoney

  • Website: https://github.com/balte/TelnetHoney
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: TelnetHoney is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple telnet honeypot.

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

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

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

Back to Category Index

telnetlogger

  • Website: https://github.com/robertdavidgraham/telnetlogger
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: telnetlogger is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Telnet honeypot designed to track the Mirai botnet.

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

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

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

Back to Category Index

TestDisk & PhotoRec

  • Website: https://www.cgsecurity.org/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: TestDisk & PhotoRec is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

The Art of Deception by Kevin D. Mitnick & William L. Simon, 2002

  • Website: http://www.wiley.com/WileyCDA/WileyTitle/productCd-0471237124.html
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Penetration Testing

What it does: The Art of Deception by Kevin D. Mitnick & William L. Simon, 2002 is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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 Category Index

The Intelligent HoneyNet

  • Website: https://github.com/jpyorre/IntelligentHoneyNet
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: The Intelligent HoneyNet is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Create actionable information from honeypots.

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

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

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

Back to Category Index

Thug

  • Website: https://buffer.github.io/thug/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Thug is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Python-based low-interaction honeyclient.

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

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

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

Back to Category Index

Thug Distributed Task Queuing

  • Website: https://thug-distributed.readthedocs.io/en/latest/index.html
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Thug Distributed Task Queuing is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Tom's Honeypot

  • Website: https://github.com/inguardians/toms_honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Tom's Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction Python honeypot.

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

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

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

Back to Category Index

tomcat-manager-honeypot

  • Website: https://github.com/helospark/tomcat-manager-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: tomcat-manager-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot that mimics Tomcat manager endpoints. Logs requests and saves attacker's WAR file for later study.

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

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

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

Back to Category Index

Trapster Commmunity

  • Website: https://github.com/0xBallpoint/trapster-community
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Trapster Commmunity is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Modural and easy to install Python Honeypot, with comprehensive alerting.

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

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

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

Back to Category Index

Trigona

  • Website: https://www.honeynet.org/project/Trigona
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Trigona is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

troje

  • Website: https://github.com/dutchcoders/troje/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: troje is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot that runs each connection with the service within a separate LXC 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: Contents > Honeypots.

Back to Category Index

twisted-honeypots

  • Website: https://github.com/lanjelot/twisted-honeypots
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: twisted-honeypots is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: SSH, FTP and Telnet honeypots based on Twisted.

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

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

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

Back to Category Index

UDPot Honeypot

  • Website: https://github.com/jekil/UDPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: UDPot Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple UDP/DNS honeypot scripts.

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

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

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

Back to Category Index

URLQuery

  • Website: https://urlquery.net/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: URLQuery is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. 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: Contents > Honeypots.

Back to Category Index

Using a Raspberry Pi honeypot to contribute data to DShield/ISC

  • Website: https://isc.sans.edu/diary/22680
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Using a Raspberry Pi honeypot to contribute data to DShield/ISC is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: The Raspberry Pi based system will allow us to maintain one code base that will make it easier to collect rich logs beyond firewall logs.

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

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

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

Back to Category Index

vEYE

  • Website: https://link.springer.com/article/10.1007%2Fs10115-008-0137-3
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: vEYE is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Behavioral footprinting for self-propagating worm detection and profiling.

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

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

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

Back to Category Index

vmitools

  • Website: http://libvmi.com/
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: vmitools is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: C library with Python bindings that makes it easy to monitor the low-level details of a running virtual machine.

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

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

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

Back to Category Index

vnclowpot

  • Website: https://github.com/magisterquis/vnclowpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: vnclowpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low interaction VNC honeypot.

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

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

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

Back to Category Index

WAPot

  • Website: https://github.com/lcashdol/WAPot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: WAPot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Honeypot that can be used to observe traffic directed at home routers.

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

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

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

Back to Category Index

WebTrap

  • Website: https://github.com/IllusiveNetworks-Labs/WebTrap
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: WebTrap is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Designed to create deceptive webpages to deceive and redirect attackers away from real 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: Contents > Honeypots.

Back to Category Index

WhiteFace Honeypot

  • Website: https://github.com/csirtgadgets/csirtg-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: WhiteFace Honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Twisted based honeypot for WhiteFace.

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

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

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

Back to Category Index

wordpot

  • Website: https://github.com/gbrindisi/wordpot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: wordpot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: WordPress Honeypot.

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

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

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

Back to Category Index

Wordpot-Frontend

  • Website: https://github.com/GovCERT-CZ/Wordpot-Frontend
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Wordpot-Frontend is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Full featured script to visualize statistics from a Wordpot honeypot.

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

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

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

Back to Category Index

wp-smart-honeypot

  • Website: https://github.com/freak3dot/wp-smart-honeypot
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: wp-smart-honeypot is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: WordPress plugin to reduce comment spam with a smarter honeypot.

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

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

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

Back to Category Index

YALIH (Yet Another Low Interaction Honeyclient)

  • Website: https://github.com/Masood-M/yalih
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: YALIH (Yet Another Low Interaction Honeyclient) is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Low-interaction client honeypot designed to detect malicious websites through signature, anomaly, and pattern matching techniques.

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

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

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

Back to Category Index

Yet Another Fake Honeypot (YAFH)

  • Website: https://github.com/fnzv/YAFH
  • Model: Open Source
  • Category: Deception & Honeypots
  • Source Lists: Awesome Honeypots

What it does: Yet Another Fake Honeypot (YAFH) is used in deception & honeypots programs to support early attacker interaction detection and high-confidence alerting. Source summaries describe it as: Simple honeypot 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: Contents > Honeypots.

Back to Category Index

Digital Forensics & DFIR

This category contains 145 documented tools. It focuses on capabilities used for timeline creation, disk and memory evidence analysis, and legal-quality reporting. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Autopsy

  • Website: https://www.sleuthkit.org/autopsy
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cyber Security Tools

What it does: Autopsy is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Digital forensics platform and graphical interface.

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

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

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

Back to Category Index

Caine

  • Website: https://www.caine-live.net
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cyber Security Tools, Awesome Hacking

What it does: Caine is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: CAINE is a Ubuntu-based app that offers a complete forensic environment that provides a graphical interface. This tool can be integrated into existing software tools as a module. It automatically extracts a timeline from RAM.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

FTK Imager

  • Website: https://accessdata.com/product-download/ftk-imager-version-4.2
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cyber Security Tools

What it does: FTK Imager is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic imaging 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: Digital Forensics.

Back to Category Index

The Sleuth Kit (TSK)

  • Website: https://www.sleuthkit.org
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cyber Security Tools

What it does: The Sleuth Kit (TSK) is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A library and collection of command-line tools for digital forensics.

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

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

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

Back to Category Index

  • Website: https://www.x1.com/products/x1-search
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cyber Security Tools

What it does: X1 Search is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic search and data extraction 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: Digital Forensics.

Back to Category Index

/r/computerforensics/

  • Website: https://www.reddit.com/r/computerforensics/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: /r/computerforensics/ is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Subreddit for computer forensics.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Other.

Back to Category Index

A1 Website Download

  • Website: http://www.microsystools.com/products/website-download
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome OSINT

What it does: A1 Website Download is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Download entire websites to disk.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Offline Browsing.

Back to Category Index

acquirepi

  • Website: https://github.com/plonxyz/acquirepi
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: acquirepi is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Successor to 4n6pi, scalable forensic disk imager, designed to run on a Raspberry Pi, powered by libewf.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Imaging.

Back to Category Index

ALEAPP

  • Website: https://github.com/abrignoni/ALEAPP
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ALEAPP is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: An Android Logs Events and Protobuf Parser.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

ALEX

  • Website: https://github.com/prosch88/ALEX
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ALEX is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract files from ADB devices on Windows, Linux and MacOS. Mostly a wrapper for adbutils.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

Andriller

  • Website: https://github.com/den4uk/andriller
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Andriller is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A software utility with a collection of forensic tools for smartphones.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

APFS Fuse

  • Website: https://github.com/sgan81/apfs-fuse
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: APFS Fuse is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A read-only FUSE driver for the new Apple File 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 Forensics > Tools > OS X Forensics.

Back to Category Index

ArtEx

  • Website: https://www.doubleblak.com/index.php
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ArtEx is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Artifact Examiner for iOS Full File System extractions.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

ArtifactExtractor

  • Website: https://github.com/Silv3rHorn/ArtifactExtractor
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ArtifactExtractor is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract common Windows artifacts from source images and VSCs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

Audacity

  • Website: http://sourceforge.net/projects/audacity/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Audacity is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Analyze sound files (mp3, m4a, whatever).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

Autopsy

  • Website: http://www.sleuthkit.org/autopsy/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Hacking, Awesome Forensics

What it does: Autopsy is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A digital forensics platform and graphical interface to and other digital forensics 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 Forensics > Tools > Frameworks.

Back to Category Index

Awesome Anti Forensics

  • Website: https://github.com/remiflavien1/awesome-anti-forensic
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Security

What it does: Awesome Anti Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A collection of awesome tools used to counter forensics activities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Beagle

  • Website: https://github.com/yampelo/beagle
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Beagle is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Transform data sources and logs into graphs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts.

Back to Category Index

BelkaCTF

  • Website: https://belkasoft.com/ctf
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: BelkaCTF is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: CTFs by Belkasoft.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

Belkasoft RAM Capturer

  • Website: https://belkasoft.com/ram-capturer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Belkasoft RAM Capturer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Volatile Memory Acquisition 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 Forensics > Tools > Acquisition.

Back to Category Index

Bkhive and Samdump2

  • Website: http://sourceforge.net/projects/ophcrack/files/samdump2/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Bkhive and Samdump2 is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump SYSTEM and SAM 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: Solve > Forensics.

Back to Category Index

Blauhaunt

  • Website: https://github.com/cgosec/Blauhaunt
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Blauhaunt is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A tool collection for filtering and visualizing logon 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 Forensics > Tools > Windows Artifacts.

Back to Category Index

bstrings

  • Website: https://github.com/EricZimmerman/bstrings
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: bstrings is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Improved strings utility.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Carving.

Back to Category Index

CFF Explorer

  • Website: http://www.ntcore.com/exsuite.php
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: CFF Explorer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: PE 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: Solve > Forensics.

Back to Category Index

chrome-url-dumper

  • Website: https://github.com/eLoopWoo/chrome-url-dumper
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: chrome-url-dumper is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump all local stored infromation collected by Chrome.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Internet Artifacts.

Back to Category Index

ChromeCacheView

  • Website: https://www.nirsoft.net/utils/chrome_cache_view.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ChromeCacheView is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A small utility that reads the cache folder of Google Chrome Web browser, and displays the list of all files currently stored in the cache.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Internet Artifacts.

Back to Category Index

CobaltStrikeScan

  • Website: https://github.com/Apr4h/CobaltStrikeScan
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: CobaltStrikeScan is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Scan files or process memory for Cobalt Strike beacons and parse their configuration.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses.

Back to Category Index

Computer Aided Investigative Environment (CAINE)

  • Website: https://caine-live.net/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Computer Aided Investigative Environment (CAINE) is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Italian GNU/Linux live distribution that pre-packages numerous digital forensics and evidence collection 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 Cybersecurity Blue Team > Operating System distributions.

Back to Category Index

Creddump

  • Website: https://github.com/moyix/creddump
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Creddump is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump windows credentials.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

CyberDefenders

  • Website: https://cyberdefenders.org/blueteam-ctf-challenges/?type=ctf
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: CyberDefenders is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

CybersecurityGuide – Digital Forensics Careers

  • Website: https://cybersecurityguide.org/careers/digital-forensics/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: CybersecurityGuide – Digital Forensics Careers is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Guide on skills, certs, and career paths in cyber forensics.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Other.

Back to Category Index

dc3dd

  • Website: https://sourceforge.net/projects/dc3dd/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: dc3dd is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Improved version of dd.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Imaging.

Back to Category Index

dcfldd

  • Website: https://sourceforge.net/projects/dcfldd/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: dcfldd is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Different improved version of dd (this version has some bugs!, another version is on github ).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Imaging.

Back to Category Index

DefCon CTFs

  • Website: https://archive.ooo
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: DefCon CTFs is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: archive of DEF CON 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: Awesome Forensics > Learn Forensics > CTFs and Challenges.

Back to Category Index

dexter

  • Website: https://github.com/coinbase/dexter
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: dexter is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dexter is a forensics acquisition framework designed to be extensible and secure.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Frameworks.

Back to Category Index

dff

  • Website: https://github.com/arxsys/dff
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: dff is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic 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 Forensics > Tools > Frameworks.

Back to Category Index

DFIR

  • Website: https://www.sans.org/cyber-security-summit/archives/dfir
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Threat Detection

What it does: DFIR is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: , ) - Threat hunting, Blue Team and DFIR summit slides.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources.

Back to Category Index

DFIR-ORC

  • Website: https://github.com/dfir-orc
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome SOC

What it does: DFIR-ORC is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Digital Forensic Challenge Images

  • Website: https://www.ashemery.com/dfir.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Digital Forensic Challenge Images is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Two DFIR challenges with images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > File System Corpora.

Back to Category Index

Digital Forensics Tool Testing Images

  • Website: https://sourceforge.net/projects/dftt/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Digital Forensics Tool Testing Images is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > File System Corpora.

Back to Category Index

Disk Arbitrator

  • Website: https://github.com/aburgh/Disk-Arbitrator
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Disk Arbitrator is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A Mac OS X forensic utility designed to help the user ensure correct forensic procedures are followed during imaging of a disk device.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Disk image handling.

Back to Category Index

Docker Explorer

  • Website: https://github.com/google/docker-explorer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Docker Explorer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extracts and interprets forensic artifacts from disk images of Docker Host 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 Forensics > Tools > Docker Forensics.

Back to Category Index

dof (Docker Forensics Toolkit)

  • Website: https://github.com/docker-forensics-toolkit/toolkit
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: dof (Docker Forensics Toolkit) is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extracts and interprets forensic artifacts from disk images of Docker Host 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 Forensics > Tools > Docker Forensics.

Back to Category Index

Extundelete

  • Website: http://extundelete.sourceforge.net/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Extundelete is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Used for recovering lost data from mountable images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

FireEye Memoryze

  • Website: https://fireeye.market/apps/211368
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: FireEye Memoryze is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A free memory forensic 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 Forensics > Tools > Acquisition.

Back to Category Index

FIT

  • Website: https://github.com/fit-project/fit
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: FIT is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic acquisition of web pages, emails, social media, etc.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

Forensic challenges

  • Website: https://www.amanhardikar.com/mindmaps/ForensicChallenges.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Forensic challenges is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Mindmap of forensic 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: Awesome Forensics > Learn Forensics.

Back to Category Index

ForensicPosters

  • Website: https://github.com/Invoke-IR/ForensicPosters
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ForensicPosters is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Posters of file system structures.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Other.

Back to Category Index

Forensics

  • Website: https://github.com/Cugu/awesome-forensics
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Online Resources > Other Lists Online.

Back to Category Index

Forensics CTFs

  • Website: https://github.com/apsdehal/awesome-ctf/blob/master/README.md#forensics
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Forensics CTFs is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

Forensics StartMe by Stark 4N6

  • Website: https://startme.stark4n6.com
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Forensics StartMe by Stark 4N6 is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > Web.

Back to Category Index

Forensics tools on Wikipedia

  • Website: https://en.wikipedia.org/wiki/List_of_digital_forensics_tools
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Forensics tools on Wikipedia is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Tools.

Back to Category Index

ForensicsFocus

  • Website: https://www.forensicfocus.com/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ForensicsFocus is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > Web.

Back to Category Index

FRED

  • Website: https://www.pinguin.lu/fred
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: FRED is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Cross-platform microsoft registry hive 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 Forensics > Tools > Windows Artifacts.

Back to Category Index

Fsck.ext4

  • Website: http://linux.die.net/man/8/fsck.ext3
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Fsck.ext4 is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Used to fix corrupt filesystems.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

FTK Imager

  • Website: https://www.exterro.com/digital-forensics-software/ftk-imager
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: FTK Imager is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Free imageing tool 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 Forensics > Tools > Imaging.

Back to Category Index

Fuji

  • Website: https://github.com/Lazza/Fuji/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Fuji is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: MacOS forensic acquisition made simple. It creates full file system copies or targeted collection of Mac 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 Forensics > Tools > Acquisition.

Back to Category Index

Ghiro

  • Website: https://github.com/Ghirensics/ghiro
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Ghiro is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A fully automated tool designed to run forensics analysis over a massive amount of images.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Picture Analysis.

Back to Category Index

Grafeas

  • Website: https://grafeas.io/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Grafeas is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Open artifact metadata API to audit and govern your software supply chain.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Supply chain security.

Back to Category Index

Guymager

  • Website: https://sourceforge.net/projects/guymager/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Guymager is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Open source version for disk imageing on linux 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 Forensics > Tools > Imaging.

Back to Category Index

hashlookup-forensic-analyser

  • Website: https://github.com/hashlookup/hashlookup-forensic-analyser
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: hashlookup-forensic-analyser is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A tool to analyse files from a forensic acquisition to find known/unknown hashes from API or using a local Bloom filter.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Frameworks.

Back to Category Index

Hashment

  • Website: https://github.com/hashment/yaffs2-forensic-tool
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Hashment is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Python forensic tool to analyze, dump, and recover deleted files from YAFFS2 partitions.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

hollows_hunter

  • Website: https://github.com/hasherezade/hollows_hunter
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Threat Detection

What it does: hollows_hunter is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Scans all running processes, recognizes and dumps a variety of potentially malicious implants (replaced/implanted PEs, shellcodes, hooks, in-memory patches).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

IE10Analyzer

  • Website: https://github.com/moaistory/IE10Analyzer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: IE10Analyzer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: This tool can parse normal records and recover deleted records in WebCacheV01.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 Forensics > Tools > Internet Artifacts.

Back to Category Index

iLEAPP

  • Website: https://github.com/abrignoni/iLEAPP
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: iLEAPP is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: An iOS Logs, Events, And Plists Parser.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

Incidents

  • Website: https://github.com/veeral-patel/incidents
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Incidents is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Web application for organizing non-trivial security investigations. Built on the idea that incidents are trees of tickets, where some tickets are leads.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Management.

Back to Category Index

InfoStealers

  • Website: https://infostealers.info/en/info
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome OSINT

What it does: InfoStealers is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Indexes darknet-exposed infostealer logs and makes them searchable and actionable for security teams, investigators, researchers, and digital forensics 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

IntelBase

  • Website: https://intelbase.is/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome OSINT

What it does: IntelBase is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensics platform focused on reverse email lookup and email data enrichment.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

iOS Frequent Locations Dumper

  • Website: https://github.com/mac4n6/iOS-Frequent-Locations-Dumper
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: iOS Frequent Locations Dumper is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump the contents of the StateModel#.archive files located in /private/var/mobile/Library/Caches/com.apple.routined/.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

IPED - Indexador e Processador de Evidências Digitais

  • Website: https://github.com/sepinf-inc/IPED
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: IPED - Indexador e Processador de Evidências Digitais is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Brazilian Federal Police Tool for Forensic Investigations.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Frameworks.

Back to Category Index

IvySyn

  • Website: https://gitlab.com/brown-ssl/ivysyn
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Fuzzing

What it does: IvySyn is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: IvySyn is a fully-automated framework for discovering memory error vulnerabilities in Deep Learning (DL) frameworks.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > API.

Back to Category Index

John the Ripper

  • Website: https://www.openwall.com/john/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: John the Ripper is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: 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 Forensics > Tools > Decryption.

Back to Category Index

KeeFarce

  • Website: https://github.com/denandz/KeeFarce
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: KeeFarce is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract KeePass passwords from memory.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Memory Forensics.

Back to Category Index

Kroll Artifact Parser and Extractor (KAPE)

  • Website: https://learn.duffandphelps.com/kape
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Kroll Artifact Parser and Extractor (KAPE) is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Triage 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: Create > Forensics.

Back to Category Index

kube-forensics

  • Website: https://github.com/keikoproj/kube-forensics
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: kube-forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Allows a cluster administrator to dump the current state of a running pod and all its containers so that security professionals can perform off-line forensic 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: Awesome Cybersecurity Blue Team > Cloud platform security > Kubernetes.

Back to Category Index

libewf

  • Website: https://github.com/libyal/libewf
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: libewf is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Libewf is a library and some tools to access the Expert Witness Compression Format (EWF, E01).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Disk image handling.

Back to Category Index

Linux Expl0rer

  • Website: https://github.com/intezer/linux-explorer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Linux Expl0rer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Easy-to-use live forensics toolbox for Linux endpoints written in Python & Flask.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Live Forensics.

Back to Category Index

LOKI

  • Website: https://github.com/ConsensusFuzz/LOKI
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Fuzzing

What it does: LOKI is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: LOKI is a blockchain consensus protocol fuzzing framework that detects the consensus memory related and logic 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 Fuzzing > Tools > Blockchain.

Back to Category Index

MacLocationsScraper

  • Website: https://github.com/mac4n6/Mac-Locations-Scraper
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MacLocationsScraper is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump the contents of the location database files on iOS and 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 Forensics > Tools > OS X Forensics.

Back to Category Index

macMRUParser

  • Website: https://github.com/mac4n6/macMRU-Parser
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: macMRUParser is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Python script to parse the Most Recently Used (MRU) plist files on macOS into a more human friendly format.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > OS X Forensics.

Back to Category Index

Magnet AXIOM

  • Website: https://www.magnetforensics.com/downloadaxiom
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Magnet AXIOM is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Artifact-centric DFIR 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: Create > Forensics.

Back to Category Index

MagnetForensics CTF Challenge

  • Website: https://www.magnetforensics.com/blog/magnet-weekly-ctf-challenge/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MagnetForensics CTF Challenge is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

Maltego

  • Website: http://www.maltego.com/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Penetration Testing

What it does: Maltego is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Proprietary software for open sources intelligence and forensics.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

MalwareTech Labs

  • Website: https://malwaretech.com/labs/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MalwareTech Labs is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

MEAT

  • Website: https://github.com/jfarley248/MEAT
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MEAT is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Perform different kinds of acquisitions on iOS devices.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

MemLabs

  • Website: https://github.com/stuxnet999/MemLabs
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MemLabs is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

MemProcFS

  • Website: https://github.com/ufrisk/MemProcFS
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MemProcFS is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: An easy and convenient way of accessing physical memory as files a virtual file 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 Forensics > Tools > Memory Forensics.

Back to Category Index

MFT-Parsers

  • Website: http://az4n6.blogspot.com/2015/09/whos-your-master-mft-parsers-reviewed.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MFT-Parsers is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Comparison of MFT-Parsers.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

MFTEcmd

  • Website: https://binaryforay.blogspot.com/2018/06/introducing-mftecmd.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MFTEcmd is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: MFT Parser by Eric Zimmerman.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

MFTMactime

  • Website: https://github.com/kero99/mftmactime
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: MFTMactime is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: MFT and USN parser that allows direct extraction in filesystem timeline format (mactime), dump all resident files in the MFT in their original folder structure and run yara rules over them all.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

mig

  • Website: https://github.com/mozilla/mig
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: mig is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Distributed & real time digital forensics at the speed of 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 Forensics > Tools > Live Forensics.

Back to Category Index

Netresec

  • Website: https://www.netresec.com/index.ashx?page=Blog
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Netresec is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > Blogs.

Back to Category Index

NTFS journal parser

  • Website: http://strozfriedberg.github.io/ntfs-linker/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: NTFS journal parser is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

NTFS USN Journal parser

  • Website: https://github.com/PoorBillionaire/USN-Journal-Parser
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: NTFS USN Journal parser is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

NTFSTool

  • Website: https://github.com/thewhiteninja/ntfstool
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: NTFSTool is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Complete NTFS forensics 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 Forensics > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

NW3C Chanllenges

  • Website: https://nw3.ctfd.io
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: NW3C Chanllenges is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

OfflineRegistryView

  • Website: https://www.nirsoft.net/utils/offline_registry_view.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: OfflineRegistryView is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Simple tool for Windows that allows you to read offline Registry files from external drive and view the desired Registry key in .reg file format.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

OpenBackupExtractor

  • Website: https://github.com/vgmoose/OpenBackupExtractor
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: OpenBackupExtractor is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: An app for extracting data from iPhone and iPad backups.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Mobile Forensics.

Back to Category Index

OpenRelik

  • Website: https://openrelik.org/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: OpenRelik is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic platform to store file artifacts and run workflows.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Frameworks.

Back to Category Index

osquery

  • Website: https://github.com/osquery/osquery
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: osquery is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: SQL powered operating system analytics.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Live Forensics.

Back to Category Index

OSX Collect

  • Website: https://github.com/YelpArchive/osxcollector
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: OSX Collect is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Tools > OS X Forensics.

Back to Category Index

PancakeViewer

  • Website: https://github.com/forensicmatt/PancakeViewer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: PancakeViewer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Disk image viewer based in dfvfs, similar to the FTK Imager viewer.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Disk image handling.

Back to Category Index

PCILeech

  • Website: https://github.com/ufrisk/pcileech
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Penetration Testing

What it does: PCILeech is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Uses PCIe hardware devices to read and write from the target system memory via Direct Memory Access (DMA) over PCIe.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

PDF Streams Inflater

  • Website: http://malzilla.sourceforge.net/downloads.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: PDF Streams Inflater is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Find and extract zlib files compressed in PDF 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: Solve > Forensics.

Back to Category Index

photorec

  • Website: https://www.cgsecurity.org/wiki/PhotoRec
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: photorec is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: File carving 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 Forensics > Tools > Carving.

Back to Category Index

Pngcheck

  • Website: http://www.libpng.org/pub/png/apps/pngcheck.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Pngcheck is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Verifies the integrity of PNG and dump all of the chunk-level information in human-readable form.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

Precision Widgets of North Dakota Intrusion

  • Website: https://betweentwodfirns.blogspot.com/2017/11/dfir-ctf-precision-widgets-of-north.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Precision Widgets of North Dakota Intrusion is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

PyShadow

  • Website: https://github.com/alicangnll/pyshadow
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: PyShadow is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A library for Windows to read shadow copies, delete shadow copies, create symbolic links to shadow copies, and create shadow copies.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts.

Back to Category Index

python-ntfs

  • Website: https://github.com/williballenthin/python-ntfs
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: python-ntfs is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: NTFS 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: Awesome Forensics > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

Real Digital Forensics

  • Website: https://www.amzn.com/dp/0321240693
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Malware Analysis

What it does: Real Digital Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Computer.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

RecuperaBit

  • Website: https://github.com/Lazza/RecuperaBit
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: RecuperaBit is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Reconstruct and recover NTFS data.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts > NTFS/MFT Processing.

Back to Category Index

Registry Dumper

  • Website: http://www.kahusecurity.com/posts/registry_dumper_find_and_dump_hidden_registry_keys.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Registry Dumper is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Dump your registry.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

Registry Viewer®

  • Website: https://accessdata.com/product-download/registry-viewer-2-0-0
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Registry Viewer® is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Used to view Windows registries.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

RegRippy

  • Website: https://github.com/airbus-cert/regrippy
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: RegRippy is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A framework for reading and extracting useful forensics data from Windows registry hives.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts.

Back to Category Index

ResourcesExtract

  • Website: http://www.nirsoft.net/utils/resources_extract.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: ResourcesExtract is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract various filetypes from exes.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Forensics.

Back to Category Index

ReverseEngineering Challenges

  • Website: https://challenges.re
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: ReverseEngineering Challenges is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Learn Forensics > CTFs and Challenges.

Back to Category Index

SANS Digital Forensics

  • Website: https://www.sans.org/cybersecurity-focus-areas/digital-forensics-incident-response
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: SANS Digital Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > Web.

Back to Category Index

SANS Investigative Forensics Toolkit (sift)

  • Website: https://github.com/teamdfir/sift
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: SANS Investigative Forensics Toolkit (sift) is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Linux distribution for forensic 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: Awesome Forensics > Tools > Distributions.

Back to Category Index

SANS Posters

  • Website: https://www.sans.org/posters
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: SANS Posters is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Free posters provided by SANS.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Other.

Back to Category Index

Shellbags

  • Website: https://github.com/williballenthin/shellbags
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Shellbags is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Investigate NT_USER.dat 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: Solve > Forensics.

Back to Category Index

sherloq

  • Website: https://github.com/GuidoBartoli/sherloq
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: sherloq is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: An open-source digital photographic image forensic toolset.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Picture Analysis.

Back to Category Index

sleuthkit

  • Website: https://github.com/sleuthkit/sleuthkit
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Hacking, Awesome Forensics

What it does: sleuthkit is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A library and collection of command-line digital forensics 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 Forensics > Tools > Frameworks.

Back to Category Index

Snow

  • Website: https://sbmlabs.com/notes/snow_whitespace_steganography_tool
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: Snow is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A Whitespace Steganography 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: Solve > Forensics.

Back to Category Index

Social Engineering

  • Website: https://github.com/giuliacassara/awesome-social-engineering
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Social Engineering is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 Category Index

Sonicvisualizer

  • Website: https://www.sonicvisualiser.org
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Sonicvisualizer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Tools > Steganography.

Back to Category Index

Steghide

  • Website: https://github.com/StegHigh/steghide
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Steghide is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: is a steganography program that hides data in various kinds of image and audio 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 Forensics > Tools > Steganography.

Back to Category Index

swap_digger

  • Website: https://github.com/sevagas/swap_digger
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: swap_digger is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A bash script used to automate Linux swap analysis, automating swap extraction and searches for Linux user credentials, Web form credentials, Web form emails, etc.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Carving.

Back to Category Index

The Art of Memory Forensics

  • Website: https://amzn.com/dp/1118825098
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Malware Analysis

What it does: The Art of Memory Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Detecting.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

This Week In 4n6

  • Website: https://thisweekin4n6.com/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: This Week In 4n6 is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Weekly updates for forensics.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Blogs.

Back to Category Index

Timeline Explorer

  • Website: https://binaryforay.blogspot.com/2017/04/introducing-timeline-explorer-v0400.html
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Timeline Explorer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Timeline Analysis tool for CSV and Excel files. Built for SANS FOR508 students.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Timeline Analysis.

Back to Category Index

timeliner

  • Website: https://github.com/airbus-cert/timeliner
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: timeliner is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A rewrite of mactime, a bodyfile reader.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Timeline Analysis.

Back to Category Index

TriageHasher

  • Website: https://github.com/FlipForensics/TriageHasher
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: TriageHasher is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A flexible hashing tool designed for triage collections on Windows, Linux and MacOS. Only hash files with a given extension and location.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

TRRespass

  • Website: https://github.com/vusec/trrespass
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Penetration Testing

What it does: TRRespass is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Many-sided rowhammer tool suite able to reverse engineer the contents of DDR3 and DDR4 memory chips protected by Target Row Refresh mitigations.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

turbinia

  • Website: https://github.com/google/turbinia
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: turbinia is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Turbinia is an open-source framework for deploying, managing, and running forensic workloads on cloud platforms.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Frameworks.

Back to Category Index

UFADE

  • Website: https://github.com/prosch88/UFADE
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: UFADE is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract files from iOS devices on Linux and MacOS. Mostly a wrapper for pymobiledevice3. Creates iTunes-style backups and advanced logical backups.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

unfurl

  • Website: https://github.com/obsidianforensics/unfurl
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: unfurl is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Extract and visualize data from URLs.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Internet Artifacts.

Back to Category Index

unix_collector

  • Website: https://github.com/op7ic/unix_collector
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: unix_collector is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: A live forensic collection script for UNIX-like systems as a single script.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

USBRip

  • Website: https://github.com/snovvcrash/usbrip
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome CTF

What it does: USBRip is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Simple CLI forensics tool for tracking USB device artifacts (history of USB events) on GNU/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: Solve > Forensics.

Back to Category Index

Wavsteg

  • Website: https://github.com/samolds/wavsteg
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Wavsteg is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: is a steganography program that hides data in various kinds of image and audio 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 Forensics > Tools > Steganography.

Back to Category Index

WinFE

  • Website: https://www.winfe.net/home
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: WinFE is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Windows Forensics enviroment.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Distributions.

Back to Category Index

WinSearchDBAnalyzer

  • Website: https://github.com/moaistory/WinSearchDBAnalyzer
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: WinSearchDBAnalyzer is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: This tool can parse normal records and recover deleted records in Windows.edb.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Internet Artifacts.

Back to Category Index

WinTriage

  • Website: https://www.securizame.com/wintriage-the-triage-tool-for-windows-dfirers/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: WinTriage is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Wintriage is a live response tool that extracts Windows artifacts. It must be executed with local or domain administrator privileges and recommended to be done from an external drive.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Acquisition.

Back to Category Index

Wombat Forensics

  • Website: https://github.com/pjrinaldi/wombatforensics
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Wombat Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Forensic GUI 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 Forensics > Tools > Frameworks.

Back to Category Index

xmount

  • Website: https://www.pinguin.lu/xmount
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: xmount is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. Source summaries describe it as: Convert between different disk image formats.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Disk image handling.

Back to Category Index

Zena Forensics

  • Website: https://blog.digital-forensics.it/
  • Model: Open Source
  • Category: Digital Forensics & DFIR
  • Source Lists: Awesome Forensics

What it does: Zena Forensics is used in digital forensics & dfir programs to support timeline creation, disk and memory evidence analysis, and legal-quality reporting. 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 > Resources > Blogs.

Back to Category Index

Email Security

This category contains 10 documented tools. It focuses on capabilities used for phishing prevention, impersonation defense, and mailbox incident response. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Active Directory Control Paths

  • Website: https://github.com/ANSSI-FR/AD-control-paths
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Active Directory Control Paths is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Visualize and graph Active Directory permission configs ("control relations") to audit questions such as "Who can read the CEO's email?" and similar.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses > Active Directory.

Back to Category Index

Gophish

  • Website: https://getgophish.com/
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: Gophish is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Powerful, open-source phishing framework that makes it easy to test your organization's exposure to phishing.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

King Phisher

  • Website: https://github.com/securestate/king-phisher
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: King Phisher is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Phishing campaign toolkit used for creating and managing multiple simultaneous phishing attacks with custom email and server content.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

mailspoof

  • Website: https://github.com/serain/mailspoof
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: mailspoof is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Scans SPF and DMARC records for issues that could allow email spoofing.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Phishing awareness and reporting.

Back to Category Index

NotifySecurity

  • Website: https://github.com/certsocietegenerale/NotifySecurity
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: NotifySecurity is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Outlook add-in used to help your users to report suspicious e-mails to 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: Awesome Cybersecurity Blue Team > Phishing awareness and reporting.

Back to Category Index

OpenNMS

  • Website: https://opennms.org/
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OpenNMS is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Free and feature-rich networking monitoring system supporting multiple configurations, a variety of alerting mechanisms (email, XMPP, SMS), and numerous data collection methods (SNMP, HTTP, JDBC, etc).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Service and performance monitoring.

Back to Category Index

Phishing Intelligence Engine (PIE)

  • Website: https://github.com/LogRhythm-Labs/PIE
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Phishing Intelligence Engine (PIE) is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Framework that will assist with the detection and response to phishing 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 Cybersecurity Blue Team > Phishing awareness and reporting.

Back to Category Index

Secure Email Gateway

  • Website: https://www.proofpoint.com/fr/threat-reference/email-gateway
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome SOC

What it does: Secure Email Gateway is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: ** (SEG):.

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

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

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Sublime Detection Rules

  • Website: https://github.com/sublime-security/sublime-rules
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Threat Detection

What it does: Sublime Detection Rules is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Email attack detection, response, and hunting rules.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Detection Rules.

Back to Category Index

Swordphish

  • Website: https://github.com/certsocietegenerale/swordphish-awareness
  • Model: Open Source
  • Category: Email Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Swordphish is used in email security programs to support phishing prevention, impersonation defense, and mailbox incident response. Source summaries describe it as: Platform allowing to create and manage (fake) phishing campaigns intended to train people in identifying suspicious mails.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Phishing awareness and reporting.

Back to Category Index

Endpoint Security

This category contains 56 documented tools. It focuses on capabilities used for process telemetry analysis, malware containment, and endpoint hardening. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Amber

  • Website: https://github.com/EgeBalci/amber
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: Amber is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Reflective PE packer for converting native PE files to position-independent shellcode.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Anti-virus Evasion Tools.

Back to Category Index

AMExtractor

  • Website: https://github.com/ir193/AMExtractor
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: AMExtractor is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: AMExtractor can dump out the physical content of your Android device even without kernel source 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

Android Storage Extractor

  • Website: https://github.com/51j0/Android-Storage-Extractor
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Android Storage Extractor is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A tool to extract local data storage of an Android application in one click.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Mobile / Android / iOS.

Back to Category Index

android-security-awesome

  • Website: https://github.com/ashishb/android-security-awesome
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: android-security-awesome is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A collection of android security related resources. A lot of work is happening in academia and industry on tools to perform dynamic analysis, static analysis and reverse engineering of android apps.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

AntiVirus Evasion Tool (AVET)

  • Website: https://github.com/govolution/avet
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: AntiVirus Evasion Tool (AVET) is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Post-process exploits containing executable files targeted for Windows machines to avoid being recognized by antivirus 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 > Anti-virus Evasion Tools.

Back to Category Index

Apktool

  • Website: https://github.com/iBotPeaches/Apktool
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Cyber Security Tools

What it does: Apktool is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A tool for reverse engineering Android apk 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

auditd configuration

  • Website: https://github.com/Neo23x0/auditd
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: auditd configuration is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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 > Tools > Endpoint Monitoring > Configuration.

Back to Category Index

AV / EP / EPP / EDR / XDR

  • Website: https://usa.kaspersky.com/blog/introducing-kedr-optimum/27062/?reseller=usa_regular-sm_acq_ona_smm__onl_b2c_lii_post_sm-team_&utmsource=linkedin&utm_medium=social&utm_campaign=us_regular-sm_en0177&utm_content=sm-post&utm_term=us_linkedin_organic_pmgk1776sk4g1qp
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: AV / EP / EPP / EDR / XDR is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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 Category Index

CIMSweep

  • Website: https://github.com/mattifestation/CimSweep
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: CIMSweep is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: , , but it relies on CrowdStrike EDR, but it needs an agent to be installed.

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

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

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

ClamAv

  • Website: http://www.clamav.net/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: ClamAv is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: ClamAV® is an open-source antivirus engine for detecting trojans, viruses, malware & other malicious threats.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Anti-Virus / Anti-Malware.

Back to Category Index

DocBleach

  • Website: https://github.com/docbleach/DocBleach
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: DocBleach is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: An open-source Content Disarm & Reconstruct software sanitizing Office, PDF and RTF Documents.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Content Disarm & Reconstruct.

Back to Category Index

dotPeek

  • Website: https://www.jetbrains.com/decompiler/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Cyber Security Tools, Awesome Hacking

What it does: dotPeek is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Free-of-charge standalone tool based on ReSharper's bundled decompiler.

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

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

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Endpoint Detection and Response

  • Website: https://www.gartner.com/reviews/market/endpoint-detection-and-response-solutions
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: Endpoint Detection and Response is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

enjarify

  • Website: https://github.com/Storyyeller/enjarify
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: enjarify is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A tool for translating Dalvik bytecode to equivalent Java bytecode.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Mobile / Android / iOS.

Back to Category Index

Fastfinder

  • Website: https://github.com/codeyourweb/fastfinder
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Forensics

What it does: Fastfinder is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Fast customisable cross-platform suspicious file finder. Supports md5/sha1/sha256 hashs, litteral/wildcard strings, regular expressions and YARA rules. Can easily be packed to be deployed on any windows / linux host.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Anti-Virus / Anti-Malware.

Back to Category Index

Fleet device management

  • Website: https://github.com/fleetdm/fleet
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Fleet device management is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Fleet is the lightweight, programmable telemetry platform for servers and workstations. Get comprehensive, customizable data from all your devices and operating 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 Security > Endpoint > Configuration Management.

Back to Category Index

frida

  • Website: https://github.com/frida/frida
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: frida is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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: Awesome Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

go-audit

  • Website: https://github.com/slackhq/go-audit
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: go-audit is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: An alternative to the Linux auditd daemon.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

google-authenticator

  • Website: https://github.com/google/google-authenticator
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: google-authenticator is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms, as well as a pluggable authentication module (PAM). One-time passcodes are generated using open standards developed by the Initiative for Open Authentication (OATH) (which is unrelated to OAuth). These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (TOTP) algorithm specified in RFC 6238.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Authentication.

Back to Category Index

GraphQL Voyager

  • Website: https://graphql-kit.com/graphql-voyager/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: GraphQL Voyager is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Represent any GraphQL API as an interactive graph, letting you explore data models from any Web site with a GraphQL query endpoint.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

hardened_malloc

  • Website: https://github.com/GrapheneOS/hardened_malloc
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: hardened_malloc is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Hardened allocator designed for modern systems. It has integration into Android's Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-based platforms. It will gain more portability / integration over 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

Hyperion

  • Website: http://nullsecurity.net/tools/binary.html
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: Hyperion is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Runtime encryptor for 32-bit portable executables ("PE .exes").

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Anti-virus Evasion Tools.

Back to Category Index

jadx

  • Website: https://github.com/skylot/jadx
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Cyber Security Tools, Awesome Hacking, Awesome CTF

What it does: jadx is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Command line and GUI tools for produce Java source code from Android Dex and Apk 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

Kolide Fleet

  • Website: https://github.com/kolide/fleet
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: Kolide Fleet is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A flexible control server for osquery fleets.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

LiME

  • Website: https://github.com/504ensicsLabs/LiME.git
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Incident Response, Awesome Forensics

What it does: LiME is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Loadable Kernel Module (LKM), which allows the acquisition of volatile memory from Linux and Linux-based devices, formerly called DMD.

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

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

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Linux Malware Detect

  • Website: https://www.rfxn.com/projects/linux-malware-detect/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Linux Malware Detect is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A malware scanner for Linux designed around the threats faced in shared hosted 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 Security > Endpoint > Anti-Virus / Anti-Malware.

Back to Category Index

macOS Fortress

  • Website: https://github.com/essandess/macOS-Fortress
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: macOS Fortress is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Automated configuration of kernel-level, OS-level, and client-level security features including privatizing proxying and anti-virus scanning 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 Cybersecurity Blue Team > macOS-based defenses.

Back to Category Index

Maigret

  • Website: https://github.com/soxoj/maigret
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome OSINT

What it does: Maigret is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Maigret collect a dossier on a person by username only, checking for accounts on a huge number of sites and gathering all the available information from web pages.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Forensics.

Back to Category Index

mig

  • Website: http://mig.mozilla.org/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: mig is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: MIG is a platform to perform investigative surgery on remote endpoints. It enables investigators to obtain information from large numbers of systems in parallel, thus accelerating investigation of incidents and day-to-day operations 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 > Endpoint > Forensics.

Back to Category Index

Mobile Security Wiki

  • Website: https://mobilesecuritywiki.com/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Mobile Security Wiki is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A collection of mobile security 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

osquery-configuration

  • Website: https://github.com/palantir/osquery-configuration
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: osquery-configuration is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A repository for using osquery for incident detection and response.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring > Configuration.

Back to Category Index

OSSEC

  • Website: https://github.com/ossec/ossec-hids
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: OSSEC is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: An open-source Host-based Intrusion Detection System (HIDS).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

OWASP Mobile Security Testing Guide

  • Website: https://github.com/OWASP/owasp-mstg
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: OWASP Mobile Security Testing Guide is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A comprehensive manual for mobile app security testing and reverse engineering.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Mobile / Android / iOS.

Back to Category Index

peCloakCapstone

  • Website: https://github.com/v-p-b/peCloakCapstone
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: peCloakCapstone is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Multi-platform fork of the peCloak.py automated malware antivirus evasion 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 > Anti-virus Evasion Tools.

Back to Category Index

POFR

  • Website: https://github.com/gmagklaras/pofr
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Forensics

What it does: POFR is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: The Penguin OS Flight Recorder collects, stores and organizes for further analysis process execution, file access and network/socket endpoint data from the Linux 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 Forensics > Tools > Live Forensics.

Back to Category Index

Quark-Engine

  • Website: https://github.com/quark-engine/quark-engine
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: Quark-Engine is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: An Obfuscation-Neglect Android Malware Scoring 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 Malware Analysis > Detection and Classification.

Back to Category Index

reFlutter

  • Website: https://github.com/ptswarm/reFlutter
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: reFlutter is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Flutter Reverse Engineering 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

Rekall

  • Website: https://github.com/google/rekall
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Forensics

What it does: Rekall is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: The Rekall Framework is a completely open collection of tools, implemented in Python under the Apache and GNU General Public License, for the extraction and analysis of digital artifacts computer 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 Forensics > Tools > Memory Forensics.

Back to Category Index

rkhunter

  • Website: http://rkhunter.sourceforge.net/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: rkhunter is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: POSIX-compliant Bash script that scans a host for various signs of malware.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Anti-Virus / Anti-Malware.

Back to Category Index

Sekoia XDR

  • Website: https://www.sekoia.io/en/product/xdr/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: Sekoia XDR is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Shellter

  • Website: https://www.shellterproject.com/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: Shellter is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Dynamic shellcode injection tool, and the first truly dynamic PE infector ever created.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Anti-virus Evasion Tools.

Back to Category Index

Splunking the Endpoint: Threat Hunting with Sysmon

  • Website: https://medium.com/@haggis_m/splunking-the-endpoint-threat-hunting-with-sysmon-9dd956e3e1bd
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: Splunking the Endpoint: Threat Hunting with Sysmon is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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 > Resources > Windows > Sysmon.

Back to Category Index

Stegcloak

  • Website: https://github.com/kurolabs/stegcloak
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Stegcloak is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Securely assign Digital Authenticity to any written text.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Authentication.

Back to Category Index

Sysdig

  • Website: https://github.com/draios/sysdig
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: Sysdig is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: A tool for deep Linux system visibility, with native support for containers. Think about sysdig as strace + tcpdump + htop + iftop + lsof + ...awesome sauce.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

Sysmon for Linux

  • Website: https://github.com/Sysinternals/SysmonForLinux
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: Sysmon for Linux is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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 > Tools > Endpoint Monitoring.

Back to Category Index

sysmon-DFIR

  • Website: https://github.com/MHaggis/sysmon-dfir
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: sysmon-DFIR is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Sources, configuration and how to detect evil things utilizing Microsoft Sysmon.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring > Configuration.

Back to Category Index

Themis

  • Website: https://github.com/cossacklabs/themis
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: Themis is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: High-level multi-platform cryptographic framework for protecting sensitive data: secure messaging with forward secrecy and secure data storage (AES256GCM), suits for building end-to-end encrypted 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

UDcide

  • Website: https://github.com/UDcide/udcide
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security

What it does: UDcide is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Android Malware Behavior 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 Security > Endpoint > Mobile / Android / iOS.

Back to Category Index

UniByAv

  • Website: https://github.com/Mr-Un1k0d3r/UniByAv
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: UniByAv is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Simple obfuscator that takes raw shellcode and generates Anti-Virus friendly executables by using a brute-forcable, 32-bit XOR key.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Anti-virus Evasion Tools.

Back to Category Index

Veil

  • Website: https://www.veil-framework.com/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Penetration Testing

What it does: Veil is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Generate metasploit payloads that bypass common anti-virus solutions.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Anti-virus Evasion Tools.

Back to Category Index

Volatility

  • Website: https://github.com/volatilityfoundation/volatility
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Incident Response, Awesome CTF, Awesome Forensics

What it does: Volatility is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Python based memory extraction and analysis 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 Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Wazuh

  • Website: https://wazuh.com/
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Wazuh is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Open source, multiplatform agent-based security monitoring based on a fork of OSSEC HIDS.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Endpoint Detection and Response (EDR).

Back to Category Index

WithSecure Elements EDR

  • Website: https://www.withsecure.com/us-en/solutions/software-and-services/elements-endpoint-detection-and-response
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: WithSecure Elements EDR is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

XDR Gartner market guide

  • Website: https://www.trellix.com/fr-fr/solutions/gartner-report-market-guide-xdr.html
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome SOC

What it does: XDR Gartner market guide is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. 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 > Nice to read.

Back to Category Index

Zeek Agent

  • Website: https://github.com/zeek/zeek-agent
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome Threat Detection

What it does: Zeek Agent is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: An endpoint monitoring agent that provides host activity to Zeek.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

Zscaler Global Threat Map Dashboard

  • Website: https://threatlabz.zscaler.com/cloud-insights/threat-map-dashboard
  • Model: Open Source
  • Category: Endpoint Security
  • Source Lists: Awesome OSINT

What it does: Zscaler Global Threat Map Dashboard is used in endpoint security programs to support process telemetry analysis, malware containment, and endpoint hardening. Source summaries describe it as: Illustrates those we've seen in the past 24 hours, consisting of threats detected by our antivirus engines, malware and advanced persistent threats.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Fuzzing & Software Assurance

This category contains 127 documented tools. It focuses on capabilities used for automated input mutation testing to uncover reliability and security defects. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

A Review of Machine Learning Applications in Fuzzing, 2019

  • Website: https://arxiv.org/abs/1906.11133
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: A Review of Machine Learning Applications in Fuzzing, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

AFL++

  • Website: https://github.com/AFLplusplus/AFLplusplus
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: AFL++ is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: AFL++ is a superior fork to Google's AFL - more speed, more and better mutations, more and better instrumentation, custom module support, etc.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > File.

Back to Category Index

AmpFuzz: Fuzzing for Amplification DDoS Vulnerabilities, 2022

  • Website: https://www.usenix.org/system/files/sec22-krupp.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: AmpFuzz: Fuzzing for Amplification DDoS Vulnerabilities, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Analysis of DTLS Implementations Using Protocol State Fuzzing, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/fiterau-brostean
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Analysis of DTLS Implementations Using Protocol State Fuzzing, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Angora

  • Website: https://github.com/AngoraFuzzer/Angora
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Angora is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Angora is a mutation-based coverage guided fuzzer. The main goal of Angora is to increase branch coverage by solving path constraints without symbolic execution.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > File.

Back to Category Index

Angora: Efficient Fuzzing by Principled Search, 2018

  • Website: http://web.cs.ucdavis.edu/~hchen/paper/chen2018angora.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Angora: Efficient Fuzzing by Principled Search, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

AntiFuzz: Impeding Fuzzing Audits of Binary Executables, 2019

  • Website: https://www.usenix.org/conference/usenixsecurity19/presentation/guler
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: AntiFuzz: Impeding Fuzzing Audits of Binary Executables, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Atheris

  • Website: https://pypi.org/project/atheris/
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Atheris is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Coverage-guided Python fuzzing engine based off of libFuzzer that supports fuzzing of Python code but also native extensions written for CPython.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Fuzzing.

Back to Category Index

BEACON : Directed Grey-Box Fuzzing with Provable Path Pruning, 2022

  • Website: https://qingkaishi.github.io/public_pdfs/SP22.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: BEACON : Directed Grey-Box Fuzzing with Provable Path Pruning, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

  • Website: https://www.usenix.org/system/files/sec22-garbelini.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: BrakTooth: Causing Havoc on Bluetooth Link Manager via Directed Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Breaking Through Binaries: Compiler-quality Instrumentation for Better Binary-only Fuzzing, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/nagy
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Breaking Through Binaries: Compiler-quality Instrumentation for Better Binary-only Fuzzing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

CollAFL: Path Sensitive Fuzzing, 2018

  • Website: http://chao.100871.net/papers/oakland18.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: CollAFL: Path Sensitive Fuzzing, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Complementing Model Learning with Mutation-Based Fuzzing, 2016

  • Website: https://arxiv.org/abs/1611.02429
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Complementing Model Learning with Mutation-Based Fuzzing, 2016 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Constraint-guided Directed Greybox Fuzzing, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/lee-gwangmu
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Constraint-guided Directed Greybox Fuzzing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

CorbFuzz

  • Website: https://github.com/shouc/corbfuzz
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: CorbFuzz is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: CorbFuzz is a state-aware fuzzer for generating as much reponses from a web application as possible without need of setting up database, etc.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Web.

Back to Category Index

Coverage-based Greybox Fuzzing as Markov Chain, 2016

  • Website: https://ieeexplore.ieee.org/abstract/document/8233151
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Coverage-based Greybox Fuzzing as Markov Chain, 2016 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Coverage-Guided Fuzzing for Deep Neural Networks, 2018

  • Website: https://arxiv.org/abs/1809.01266
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Coverage-Guided Fuzzing for Deep Neural Networks, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Deep Reinforcement Fuzzing, 2018

  • Website: https://arxiv.org/abs/1801.04589
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Deep Reinforcement Fuzzing, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Designing New Operating Primitives to Improve Fuzzing Performance, 2017

  • Website: http://iisp.gatech.edu/sites/default/files/images/designing_new_operating_primitives_to_improve_fuzzing_performance_vt.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Designing New Operating Primitives to Improve Fuzzing Performance, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

DIFUZE: Interface Aware Fuzzing for Kernel Drivers, 2017

  • Website: https://acmccs.github.io/papers/p2123-corinaA.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: DIFUZE: Interface Aware Fuzzing for Kernel Drivers, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

DifuzzRTL

  • Website: https://github.com/compsec-snu/difuzz-rtl
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: DifuzzRTL is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: DifuzzRTL is a differential fuzz testing approach for CPU verification.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > CPU.

Back to Category Index

DIFUZZRTL: Differential Fuzz Testing to Find CPU Bugs, 2021

  • Website: https://lifeasageek.github.io/papers/jaewon-difuzzrtl.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: DIFUZZRTL: Differential Fuzz Testing to Find CPU Bugs, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

DLFuzz: Differential Fuzzing Testing of Deep Learning Systems, 2018

  • Website: https://arxiv.org/abs/1808.09413
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: DLFuzz: Differential Fuzzing Testing of Deep Learning Systems, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Dowsing for overflows: a guided fuzzer to find buffer boundary violations, 2013

  • Website: http://enigma.usenix.org/sites/default/files/sec13_proceedings_interior.pdf#page=57
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Dowsing for overflows: a guided fuzzer to find buffer boundary violations, 2013 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Drifuzz: Harvesting Bugs in Device Drivers from Golden Seeds, 2022

  • Website: https://www.usenix.org/system/files/sec22-shen-zekun.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Drifuzz: Harvesting Bugs in Device Drivers from Golden Seeds, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

DriveFuzz: Discovering Autonomous Driving Bugs through Driving Quality-Guided Fuzzing, 2022

  • Website: https://chungkim.io/doc/ccs22-drivefuzz.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: DriveFuzz: Discovering Autonomous Driving Bugs through Driving Quality-Guided Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

EcoFuzz: Adaptive Energy-Saving Greybox Fuzzing as a Variant of the Adversarial Multi-Armed Bandit, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/yue
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: EcoFuzz: Adaptive Energy-Saving Greybox Fuzzing as a Variant of the Adversarial Multi-Armed Bandit, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Effective File Format Fuzzing

  • Website: https://youtu.be/qTTwqFRD1H8
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Effective File Format Fuzzing is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: , Black Hat Europe 2016.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Talks.

Back to Category Index

Effective Seed Scheduling for Fuzzing with Graph Centrality Analysis, 2022

  • Website: https://arxiv.org/pdf/2203.12064.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Effective Seed Scheduling for Fuzzing with Graph Centrality Analysis, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

eFuzz: A Fuzzer for DLMS/COSEM Electricity Meters, 2016

  • Website: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.817.5616&rep=rep1&type=pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: eFuzz: A Fuzzer for DLMS/COSEM Electricity Meters, 2016 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

EnFuzz: From Ensemble Learning to Ensemble Fuzzing, 2018

  • Website: https://arxiv.org/abs/1807.00182
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: EnFuzz: From Ensemble Learning to Ensemble Fuzzing, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Evaluating Fuzz Testing, 2018

  • Website: http://www.cs.umd.edu/~mwh/papers/fuzzeval.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Evaluating Fuzz Testing, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Faster Fuzzing: Reinitialization with Deep Neural Models, 2017

  • Website: https://arxiv.org/abs/1711.02807
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Faster Fuzzing: Reinitialization with Deep Neural Models, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

FIXREVERTER: A Realistic Bug Injection Methodology for Benchmarking Fuzz Testing, 2022

  • Website: https://www.usenix.org/system/files/sec22-zhang-zenong.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FIXREVERTER: A Realistic Bug Injection Methodology for Benchmarking Fuzz Testing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fluffy

  • Website: https://github.com/snuspl/fluffy
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fluffy is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Fluffy is a multi-transaction differential fuzzer for finding consensus bugs in Ethereum.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Blockchain.

Back to Category Index

FREEDOM: Engineering a State-of-the-Art DOM Fuzzer, 2020

  • Website: https://gts3.org/assets/papers/2020/xu:freedom.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FREEDOM: Engineering a State-of-the-Art DOM Fuzzer, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Full-speed Fuzzing: Reducing Fuzzing Overhead through Coverage-guided Tracing, 2019

  • Website: https://www.computer.org/csdl/proceedings-article/sp/2019/666000b122/19skgbGVFEQ
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Full-speed Fuzzing: Reducing Fuzzing Overhead through Coverage-guided Tracing, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Fuzz on the Beach: Fuzzing Solana Smart Contracts, 2023

  • Website: https://arxiv.org/pdf/2309.03006.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzz on the Beach: Fuzzing Solana Smart Contracts, 2023 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

FuzzBench

  • Website: https://google.github.io/fuzzbench/
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: FuzzBench is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Free service that evaluates fuzzers on a wide variety of real-world benchmarks, at Google scale.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Fuzzing.

Back to Category Index

FuzzGen: Automatic Fuzzer Generation, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/ispoglou
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FuzzGen: Automatic Fuzzer Generation, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

FuzzGuard: Filtering out Unreachable Inputs in Directed Grey-box Fuzzing through Deep Learning, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/zong
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FuzzGuard: Filtering out Unreachable Inputs in Directed Grey-box Fuzzing through Deep Learning, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fuzzification: Anti-Fuzzing Techniques, 2019

  • Website: https://www.usenix.org/conference/usenixsecurity19/presentation/jung
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzification: Anti-Fuzzing Techniques, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fuzzing Error Handling Code using Context-Sensitive Software Fault Injection, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/jiang
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing Error Handling Code using Context-Sensitive Software Fault Injection, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fuzzing File Systems via Two-Dimensional Input Space Exploration, 2019

  • Website: https://www.computer.org/csdl/proceedings-article/sp/2019/666000a594/19skfLYOpaw
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing File Systems via Two-Dimensional Input Space Exploration, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Fuzzing for Software Security Testing and Quality Assurance, 2nd Edition

  • Website: https://www.amazon.com/Fuzzing-Software-Security-Testing-Assurance/dp/1608078507/
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing for Software Security Testing and Quality Assurance, 2nd Edition is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: (2018).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Books.

Back to Category Index

Fuzzing Hardware Like Software, 2022

  • Website: https://www.usenix.org/system/files/sec22-trippel.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing Hardware Like Software, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fuzzing JavaScript Engines with Aspect-preserving Mutation, 2020

  • Website: https://jakkdu.github.io/pubs/2020/park:die.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing JavaScript Engines with Aspect-preserving Mutation, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Fuzzing Labs - Patrick Ventuzelo

  • Website: https://www.youtube.com/channel/UCGD1Qt2jgnFRjrfAITGdNfQ
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing Labs - Patrick Ventuzelo is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: , Youtube.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Talks.

Back to Category Index

Fuzzing with Code Fragments, 2012

  • Website: https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final73.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing with Code Fragments, 2012 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Fuzzing-101

  • Website: https://github.com/antonio-morales/Fuzzing101
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing-101 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > Books.

Back to Category Index

Fuzzle: Making a Puzzle for Fuzzers, 2022

  • Website: https://softsec.kaist.ac.kr/~sangkilc/papers/lee-ase22.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzle: Making a Puzzle for Fuzzers, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > The others.

Back to Category Index

FuzzOrigin: Detecting UXSS vulnerabilities in Browsers through Origin Fuzzing, 2022

  • Website: https://www.usenix.org/system/files/sec22-kim.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FuzzOrigin: Detecting UXSS vulnerabilities in Browsers through Origin Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

FuzzUSB: Hybrid Stateful Fuzzing of USB Gadget Stacks, 2022

  • Website: https://github.com/purseclab/fuzzusb/blob/main/paper/fuzzusb.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: FuzzUSB: Hybrid Stateful Fuzzing of USB Gadget Stacks, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Fuzzware: Using Precise MMIO Modeling for Effective Firmware Fuzzing, 2022

  • Website: https://www.usenix.org/system/files/sec22-scharnowski.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Fuzzware: Using Precise MMIO Modeling for Effective Firmware Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Greybox Fuzzing of Distributed Systems, 2023

  • Website: https://arxiv.org/pdf/2305.02601.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Greybox Fuzzing of Distributed Systems, 2023 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

GREYONE: Data Flow Sensitive Fuzzing, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/gan
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: GREYONE: Data Flow Sensitive Fuzzing, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Hardware Support to Improve Fuzzing Performance and Precision, 2021

  • Website: https://gts3.org/assets/papers/2021/ding:snap.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Hardware Support to Improve Fuzzing Performance and Precision, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Hawkeye: Towards a Desired Directed Grey-box Fuzzer, 2018

  • Website: https://chenbihuan.github.io/paper/ccs18-chen-hawkeye.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Hawkeye: Towards a Desired Directed Grey-box Fuzzer, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Hopper: Interpretative Fuzzing for Libraries, 2023

  • Website: https://arxiv.org/pdf/2309.03496.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Hopper: Interpretative Fuzzing for Libraries, 2023 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Hybrid fuzz testing: Discovering software bugs via fuzzing and symbolic execution, 2012

  • Website: https://pdfs.semanticscholar.org/488a/b1e313f5109153f2c74e3b5d86d41e9b4b71.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Hybrid fuzz testing: Discovering software bugs via fuzzing and symbolic execution, 2012 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > The others.

Back to Category Index

HyperFuzzer: An Efficient Hybrid Fuzzer For Virtual CPUs, 2021

  • Website: https://www.microsoft.com/en-us/research/uploads/prod/2021/09/hyperfuzzer-ccs21.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: HyperFuzzer: An Efficient Hybrid Fuzzer For Virtual CPUs, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Ifuzzer: An evolutionary interpreter fuzzer using genetic programming, 2016

  • Website: https://www.cs.vu.nl/~herbertb/download/papers/ifuzzer-esorics16.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Ifuzzer: An evolutionary interpreter fuzzer using genetic programming, 2016 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > The others.

Back to Category Index

IJON: Exploring Deep State Spaces via Fuzzing, 2020

  • Website: https://www.syssec.ruhr-uni-bochum.de/media/emma/veroeffentlichungen/2020/02/27/IJON-Oakland20.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: IJON: Exploring Deep State Spaces via Fuzzing, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

IMF: Inferred Model-based Fuzzer, 2017

  • Website: http://daramg.gift/paper/han-ccs2017.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: IMF: Inferred Model-based Fuzzer, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Jigsaw: Efficient and Scalable Path Constraints Fuzzing, 2022

  • Website: https://www.cs.ucr.edu/~csong/oakland22-jigsaw.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Jigsaw: Efficient and Scalable Path Constraints Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

JIT-Picking: Differential Fuzzing of JavaScript Engines, 2022

  • Website: https://publications.cispa.saarland/3773/1/2022-CCS-JIT-Fuzzing.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: JIT-Picking: Differential Fuzzing of JavaScript Engines, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

kAFL: Hardware-Assisted Feedback Fuzzing for OS Kernels, 2017

  • Website: https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/schumilo
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: kAFL: Hardware-Assisted Feedback Fuzzing for OS Kernels, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Krace: Data Race Fuzzing for Kernel File Systems, 2020

  • Website: https://www.cc.gatech.edu/~mxu80/pubs/xu:krace.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Krace: Data Race Fuzzing for Kernel File Systems, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Learn&Fuzz: Machine Learning for Input Fuzzing, 2017

  • Website: https://arxiv.org/abs/1701.07232
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Learn&Fuzz: Machine Learning for Input Fuzzing, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Learning to Fuzz from Symbolic Execution with Application to Smart Contracts, 2019

  • Website: https://files.sri.inf.ethz.ch/website/papers/ccs19-ilf.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Learning to Fuzz from Symbolic Execution with Application to Smart Contracts, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

LibAFL: A Framework to Build Modular and Reusable Fuzzers, 2022

  • Website: https://www.s3.eurecom.fr/docs/ccs22_fioraldi.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: LibAFL: A Framework to Build Modular and Reusable Fuzzers, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Matryoshka: fuzzing deeply nested branches, 2019

  • Website: https://web.cs.ucdavis.edu/~hchen/paper/chen2019matryoshka.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Matryoshka: fuzzing deeply nested branches, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

MC^2: Rigorous and Efficient Directed Greybox Fuzzing, 2022

  • Website: https://arxiv.org/pdf/2208.14530.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MC^2: Rigorous and Efficient Directed Greybox Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

MEUZZ: Smart Seed Scheduling for Hybrid Fuzzing, 2020

  • Website: https://arxiv.org/abs/2002.08568
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MEUZZ: Smart Seed Scheduling for Hybrid Fuzzing, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

MoonLight: Effective Fuzzing with Near-Optimal Corpus Distillation, 2019

  • Website: https://arxiv.org/abs/1905.13055
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MoonLight: Effective Fuzzing with Near-Optimal Corpus Distillation, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

MoonShine: Optimizing OS Fuzzer Seed Selection with Trace Distillation, 2018

  • Website: https://www.usenix.org/conference/usenixsecurity18/presentation/pailoor
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MoonShine: Optimizing OS Fuzzer Seed Selection with Trace Distillation, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

MorFuzz

  • Website: https://github.com/sycuricon/MorFuzz
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MorFuzz is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: MorFuzz is a generic RISC-V processor fuzzing framework that can efficiently detect software triggerable functional 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 Fuzzing > Tools > CPU.

Back to Category Index

Morphuzz: Bending (Input) Space to Fuzz Virtual Devices, 2022

  • Website: https://www.usenix.org/system/files/sec22-bulekov.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Morphuzz: Bending (Input) Space to Fuzz Virtual Devices, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

MTF-Storm:a high performance fuzzer for Modbus/TCP, 2018

  • Website: https://doi.org/10.1109/ETFA.2018.8502600
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MTF-Storm:a high performance fuzzer for Modbus/TCP, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > The others.

Back to Category Index

MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference, 2022

  • Website: https://www.usenix.org/system/files/sec22-myung.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

NestFuzz: Enhancing Fuzzing with Comprehensive Understanding of Input Processing Logic, 2023

  • Website: https://secsys.fudan.edu.cn/_upload/article/files/56/ed/788960544d56a38258aca7d3c8b5/216e599a-d6f6-4308-aa0b-ef45166a8431.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: NestFuzz: Enhancing Fuzzing with Comprehensive Understanding of Input Processing Logic, 2023 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

NEUZZ: Efficient Fuzzing with Neural Program Learning, 2018

  • Website: https://arxiv.org/abs/1807.05620
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: NEUZZ: Efficient Fuzzing with Neural Program Learning, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

NEUZZ: Efficient Fuzzing with Neural Program Smoothing, 2019

  • Website: https://www.computer.org/csdl/proceedings-article/sp/2019/666000a900/19skg5XghG0
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: NEUZZ: Efficient Fuzzing with Neural Program Smoothing, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Not all bytes are equal: Neural byte sieve for fuzzing, 2017

  • Website: https://arxiv.org/abs/1711.04596
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Not all bytes are equal: Neural byte sieve for fuzzing, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

NTFUZZ: Enabling Type-Aware Kernel Fuzzing on Windows with Static Binary Analysis, 2021

  • Website: https://softsec.kaist.ac.kr/~jschoi/data/oakland2021.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: NTFUZZ: Enabling Type-Aware Kernel Fuzzing on Windows with Static Binary Analysis, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Nyx: Greybox Hypervisor Fuzzing using Fast Snapshots and Affine Types, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/schumilo
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Nyx: Greybox Hypervisor Fuzzing using Fast Snapshots and Affine Types, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

One Engine to Fuzz 'em All: Generic Language Processor Testing with Semantic Validation, 2021

  • Website: https://huhong789.github.io/papers/polyglot-oakland2021.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: One Engine to Fuzz 'em All: Generic Language Processor Testing with Semantic Validation, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

OneFuzz

  • Website: https://github.com/microsoft/onefuzz
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OneFuzz is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Self-hosted Fuzzing-as-a-Service (FaaS) 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: Awesome Cybersecurity Blue Team > DevSecOps > Fuzzing.

Back to Category Index

Open Source Fuzzing Tools, 1st Edition

  • Website: https://www.amazon.com/Open-Source-Fuzzing-Tools-Rathaus/dp/1597491950/
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Open Source Fuzzing Tools, 1st Edition is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: (2007).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Books.

Back to Category Index

Optimizing Seed Selection for Fuzzing, 2014

  • Website: https://softsec.kaist.ac.kr/~sangkilc/papers/rebert-usenixsec14.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Optimizing Seed Selection for Fuzzing, 2014 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

OSS-Fuzz - Google's continuous fuzzing service for open source software, 2017

  • Website: https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/serebryany
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: OSS-Fuzz - Google's continuous fuzzing service for open source software, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Pangolin:Incremental Hybrid Fuzzing with Polyhedral Path Abstraction, 2020

  • Website: https://qingkaishi.github.io/public_pdfs/SP2020.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Pangolin:Incremental Hybrid Fuzzing with Polyhedral Path Abstraction, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

ParmeSan: Sanitizer-guided Greybox Fuzzing, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/osterlund
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: ParmeSan: Sanitizer-guided Greybox Fuzzing, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

PATA: Fuzzing with Path Aware Taint Analysis, 2022

  • Website: http://www.wingtecher.com/themes/WingTecherResearch/assets/papers/sp22.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: PATA: Fuzzing with Path Aware Taint Analysis, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Profile-Driven System Optimizations for Accelerated Greybox Fuzzing, 2023

  • Website: https://users.cs.utah.edu/~snagy/papers/23CCS.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Profile-Driven System Optimizations for Accelerated Greybox Fuzzing, 2023 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Program-Adaptive Mutational Fuzzing, 2015

  • Website: https://softsec.kaist.ac.kr/~sangkilc/papers/cha-oakland15.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Program-Adaptive Mutational Fuzzing, 2015 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Protocol State Fuzzing of TLS Implementations, 2015

  • Website: https://www.usenix.org/conference/usenixsecurity15/technical-sessions/presentation/de-ruiter
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Protocol State Fuzzing of TLS Implementations, 2015 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

QSYM : A Practical Concolic Execution Engine Tailored for Hybrid Fuzzing, 2018

  • Website: https://www.usenix.org/conference/usenixsecurity18/presentation/yun
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: QSYM : A Practical Concolic Execution Engine Tailored for Hybrid Fuzzing, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Razzer: Finding Kernel Race Bugs through Fuzzing, 2019

  • Website: https://www.computer.org/csdl/proceedings-article/sp/2019/666000a296/19skfwZLirm
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Razzer: Finding Kernel Race Bugs through Fuzzing, 2019 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Regression Greybox Fuzzing, 2021

  • Website: https://mboehme.github.io/paper/CCS21.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Regression Greybox Fuzzing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

RetroWrite: Statically Instrumenting COTS Binaries for Fuzzing and Sanitization, 2020

  • Website: https://www.semanticscholar.org/paper/RetroWrite%3A-Statically-Instrumenting-COTS-Binaries-Dinesh-Burow/845cafb153b0e4b9943c6d9b6a7e42c14845a0d6
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: RetroWrite: Statically Instrumenting COTS Binaries for Fuzzing and Sanitization, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Same Coverage, Less Bloat: Accelerating Binary-only Fuzzing with Coverage-preserving Coverage-guided Tracing, 2021

  • Website: https://people.cs.vt.edu/snagy2/papers/21CCS.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Same Coverage, Less Bloat: Accelerating Binary-only Fuzzing with Coverage-preserving Coverage-guided Tracing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Scheduling Black-box Mutational Fuzzing, 2013

  • Website: https://softsec.kaist.ac.kr/~sangkilc/papers/woo-ccs13.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Scheduling Black-box Mutational Fuzzing, 2013 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SemFuzz: Semantics-based Automatic Generation of Proof-of-Concept Exploits, 2017

  • Website: https://www.informatics.indiana.edu/xw7/papers/p2139-you.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SemFuzz: Semantics-based Automatic Generation of Proof-of-Concept Exploits, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SFuzz: Slice-based Fuzzing for Real-Time Operating Systems, 2022

  • Website: https://huhong789.github.io/papers/chen:sfuzz.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SFuzz: Slice-based Fuzzing for Real-Time Operating Systems, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SGXFuzz: Efficiently Synthesizing Nested Structures for SGX Enclave Fuzzing, 2022

  • Website: https://www.usenix.org/system/files/sec22-cloosters.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SGXFuzz: Efficiently Synthesizing Nested Structures for SGX Enclave Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Skyfire: Data-Driven Seed Generation for Fuzzing, 2017

  • Website: https://www.ieee-security.org/TC/SP2017/papers/42.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Skyfire: Data-Driven Seed Generation for Fuzzing, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

SlowFuzz: Automated Domain-Independent Detection of Algorithmic Complexity Vulnerabilities, 2017

  • Website: https://arxiv.org/pdf/1708.08437.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SlowFuzz: Automated Domain-Independent Detection of Algorithmic Complexity Vulnerabilities, 2017 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SoFi: Reflection-Augmented Fuzzing for JavaScript Engines, 2021

  • Website: https://dl.acm.org/doi/pdf/10.1145/3460120.3484823
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SoFi: Reflection-Augmented Fuzzing for JavaScript Engines, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SpecDoctor: Differential Fuzz Testing to Find Transient Execution Vulnerabilities, 2022

  • Website: https://compsec.snu.ac.kr/papers/jaewon-specdoctor.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SpecDoctor: Differential Fuzz Testing to Find Transient Execution Vulnerabilities, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

SpecFuzz

  • Website: https://github.com/tudinfse/SpecFuzz
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SpecFuzz is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: SpecFuzz is a tool to enable fuzzing for Spectre vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > CPU.

Back to Category Index

SpecFuzz: Bringing Spectre-type vulnerabilities to the surface, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/oleksenko
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: SpecFuzz: Bringing Spectre-type vulnerabilities to the surface, 2020 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Squirrel

  • Website: https://github.com/s3team/Squirrel
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Squirrel is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Squirrel is a fuzzer for database managment systems (DBMSs).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > DBMS.

Back to Category Index

Stateful Greybox Fuzzing, 2022

  • Website: https://www.usenix.org/system/files/sec22-ba.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Stateful Greybox Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

StateFuzz: System Call-Based State-Aware Linux Driver Fuzzing, 2022

  • Website: https://www.usenix.org/system/files/sec22-zhao-bodong.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: StateFuzz: System Call-Based State-Aware Linux Driver Fuzzing, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

STOCHFUZZ: Sound and Cost-effective Fuzzing of Stripped Binaries by Incremental and Stochastic Rewriting, 2021

  • Website: https://www.cs.purdue.edu/homes/zhan3299/res/SP21b.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: STOCHFUZZ: Sound and Cost-effective Fuzzing of Stripped Binaries by Incremental and Stochastic Rewriting, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

Systematic Fuzzing and Testing of TLS Libraries, 2016

  • Website: https://www.nds.rub.de/media/nds/veroeffentlichungen/2016/10/19/tls-attacker-ccs16.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Systematic Fuzzing and Testing of TLS Libraries, 2016 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

T-Fuzz: fuzzing by program transformation, 2018

  • Website: https://nebelwelt.net/publications/files/18Oakland.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: T-Fuzz: fuzzing by program transformation, 2018 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

T-Reqs: HTTP Request Smuggling with Differential Fuzzing, 2021

  • Website: https://bahruz.me/papers/ccs2021treqs.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: T-Reqs: HTTP Request Smuggling with Differential Fuzzing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Taming compiler fuzzers, 2013

  • Website: https://www.cs.utah.edu/~regehr/papers/pldi13.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Taming compiler fuzzers, 2013 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

TEFuzz

  • Website: https://github.com/seclab-fudan/TEFuzz/
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: TEFuzz is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: TEFuzz is a tailored fuzzing-based framework to facilitate the detection and exploitation of template escape 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 Fuzzing > Tools > Web.

Back to Category Index

The Art, Science, and Engineering of Fuzzing: A Survey

  • Website: https://ieeexplore.ieee.org/document/8863940
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: The Art, Science, and Engineering of Fuzzing: A Survey is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: (2019) -.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Books.

Back to Category Index

TheHuzz: Instruction Fuzzing of Processors Using Golden-Reference Models for Finding Software-Exploitable Vulnerabilities, 2022

  • Website: https://www.usenix.org/system/files/sec22-kande.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: TheHuzz: Instruction Fuzzing of Processors Using Golden-Reference Models for Finding Software-Exploitable Vulnerabilities, 2022 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

Transynther

  • Website: https://github.com/vernamlab/Medusa
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Transynther is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Transynther automatically generates and tests building blocks for Meltdown attacks with various faults and microcode assists.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > CPU.

Back to Category Index

UNIFUZZ: A Holistic and Pragmatic Metrics-Driven Platform for Evaluating Fuzzers, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/li-yuwei
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: UNIFUZZ: A Holistic and Pragmatic Metrics-Driven Platform for Evaluating Fuzzers, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 > USENIX Security.

Back to Category Index

V-SHUTTLE: Scalable and Semantics-Aware Hypervisor Fuzzing, 2021

  • Website: https://nesa.zju.edu.cn/download/ppt/pgn_slides_V-SHUTTLE.pdf
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: V-SHUTTLE: Scalable and Semantics-Aware Hypervisor Fuzzing, 2021 is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. 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 Category Index

Witcher

  • Website: https://github.com/sefcom/Witcher
  • Model: Open Source
  • Category: Fuzzing & Software Assurance
  • Source Lists: Awesome Fuzzing

What it does: Witcher is used in fuzzing & software assurance programs to support automated input mutation testing to uncover reliability and security defects. Source summaries describe it as: Witcher is a web application fuzzer that utilizes mutational fuzzing to explore web applications and fault escalation to detect command and SQL injection vulnerabilities.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Web.

Back to Category Index

GRC & Compliance

This category contains 7 documented tools. It focuses on capabilities used for control mapping, evidence collection, and policy governance workflows. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Catching attackers with go-audit and a logging pipeline

  • Website: https://summitroute.com/blog/2016/12/25/Catching_attackers_with_go-audit_and_a_logging_pipeline/
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Threat Detection

What it does: Catching attackers with go-audit and a logging pipeline is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. 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 > Resources.

Back to Category Index

Chef InSpec

  • Website: https://www.chef.io/products/chef-inspec
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Chef InSpec is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. Source summaries describe it as: Language for describing security and compliance rules, which become automated tests that can be run against IT infrastructures to discover and report on non-compliance.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Compliance testing and reporting.

Back to Category Index

Firejail

  • Website: https://firejail.wordpress.com/
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Firejail is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. Source summaries describe it as: SUID program that reduces the risk of security breaches by restricting the running environment of untrusted applications using Linux namespaces and seccomp-bpf.

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Host-based tools > Sandboxes.

Back to Category Index

OpenSCAP Base

  • Website: https://www.open-scap.org/tools/openscap-base/
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OpenSCAP Base is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. Source summaries describe it as: Both a library and a command line tool (oscap) used to evaluate a system against SCAP baseline profiles to report on the security posture of the scanned system(s).

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

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Compliance testing and reporting.

Back to Category Index

SyzScope: Revealing High-Risk Security Impacts of Fuzzer-Exposed Bugs in Linux kernel, 2022

  • Website: https://www.usenix.org/system/files/sec22-zou.pdf
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Fuzzing

What it does: SyzScope: Revealing High-Risk Security Impacts of Fuzzer-Exposed Bugs in Linux kernel, 2022 is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. 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 > USENIX Security.

Back to Category Index

w3af

  • Website: http://w3af.org/
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Security

What it does: w3af is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. Source summaries describe it as: w3af is a Web Application Attack and Audit Framework. The project’s goal is to create a framework to help you secure your web applications by finding and exploiting all web application vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Windows Secure Host Baseline

  • Website: https://github.com/nsacyber/Windows-Secure-Host-Baseline
  • Model: Open Source
  • Category: GRC & Compliance
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Windows Secure Host Baseline is used in grc & compliance programs to support control mapping, evidence collection, and policy governance workflows. Source summaries describe it as: Group Policy objects, compliance checks, and configuration tools that provide an automated and flexible approach for securely deploying and maintaining the latest releases of Windows 10.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses.

Back to Category Index

General Security

This category contains 28 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

BackBox

  • Website: https://www.backbox.org
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Cyber Security Tools

What it does: BackBox is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Ubuntu-based Linux distribution for security and 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: Linux Distributions.

Back to Category Index

ansible-os-hardening

  • Website: https://github.com/dev-sec/ansible-os-hardening
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: ansible-os-hardening is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Ansible role for OS hardening.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > DevOps.

Back to Category Index

Apache Metron (incubating)

  • Website: https://github.com/apache/incubator-metron
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Apache Metron (incubating) is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Metron integrates a variety of open source big data technologies in order to offer a centralized tool for security monitoring and 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: Awesome Security > Big Data.

Back to Category Index

Awesome Security Hardening

  • Website: https://github.com/decalage2/awesome-security-hardening
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Awesome Security Hardening is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A collection of awesome security hardening guides, best practices, checklists, benchmarks, tools and other 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 Security > Other Awesome Lists > Other Security Awesome Lists.

Back to Category Index

Bearer

  • Website: https://github.com/Bearer/bearer
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Bearer is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Scan code for security risks and vulnerabilities leading to sensitive data exposures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

Checkov

  • Website: https://github.com/bridgecrewio/checkov/
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Checkov is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A static analysis tool for infrastucture as code (Terraform).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

Cyber Security Career Guide

  • Website: https://www.manning.com/books/cyber-security-career-guide
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Cyber Security Career Guide is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Kickstart a career in cyber security by learning how to adapt your existing technical and non-technical skills. (early access, published continuously, final release Summer 2022).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

Cyber Threat Hunting

  • Website: https://www.manning.com/books/cyber-threat-hunting
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Cyber Threat Hunting is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Practical guide to cyber threat hunting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

Cyclops

  • Website: https://github.com/v8blink/Chromium-based-XSS-Taint-Tracking
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Cyclops is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Cyclops is a web browser with XSS detection feature, it is chromium-based xss detection that used to find the flows from a source to a sink.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

data_hacking

  • Website: https://github.com/ClickSecurity/data_hacking
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: data_hacking is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Examples of using IPython, Pandas, and Scikit Learn to get the most out of your security data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Big Data.

Back to Category Index

dotgpg

  • Website: https://github.com/ConradIrwin/dotgpg
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: dotgpg is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A tool for backing up and versioning your production secrets or shared passwords securely and 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: Awesome Security > Datastores.

Back to Category Index

Full Stack Python Security

  • Website: https://www.manning.com/books/full-stack-python-security
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Full Stack Python Security is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A comprehensive look at cybersecurity for Python 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 Security > Web > Development.

Back to Category Index

Hardening Windows 10

  • Website: https://www.hardenwindows10forsecurity.com/
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Hardening Windows 10 is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Guide for hardening Windows 10.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

How to Hack Like a Legend

  • Website: https://amzn.to/2uWh1Up
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: How to Hack Like a Legend is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A hacker’s tale breaking into a secretive offshore company, Sparc Flow, 2018.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

How to Hack Like a Pornstar

  • Website: https://books2read.com/u/bWzdBx
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: How to Hack Like a Pornstar is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A step by step process for breaking into a BANK, Sparc Flow, 2017.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

How to Investigate Like a Rockstar

  • Website: https://books2read.com/u/4jDWoZ
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: How to Investigate Like a Rockstar is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Live a real crisis to master the secrets of forensic analysis, Sparc Flow, 2017.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > EBooks.

Back to Category Index

is-website-vulnerable

  • Website: https://github.com/lirantal/is-website-vulnerable
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: is-website-vulnerable is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: finds publicly known security vulnerabilities in a website's frontend JavaScript libraries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

lists

  • Website: https://github.com/jnv/lists
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: lists is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The definitive list of (awesome) lists curated on GitHub.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Making Sense of Cyber Security

  • Website: https://www.manning.com/books/making-sense-of-cyber-security
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Making Sense of Cyber Security is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A jargon-free, practical guide to the key concepts, terminology, and technologies of cybersecurity perfect for anyone planning or implementing a security strategy. (early access, published continuously, final release early 2022).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

OpenSOC

  • Website: https://github.com/OpenSOC/opensoc
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: OpenSOC is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: OpenSOC integrates a variety of open source big data technologies in order to offer a centralized tool for security monitoring and 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: Awesome Security > Big Data.

Back to Category Index

redoctober

  • Website: https://github.com/cloudflare/redoctober
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: redoctober is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Server for two-man rule style file encryption and decryption.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Security Acronyms

  • Website: https://github.com/cloudsecurelab/security-acronyms
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Security Acronyms is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A curated list of security related acronyms and concepts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

shellclear

  • Website: https://github.com/rusty-ferris-club/shellclear
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: shellclear is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: It helps you to Secure your shell history commands by finding sensitive commands in your all history commands and allowing you to clean them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Terminal.

Back to Category Index

Sqreen

  • Website: https://www.sqreen.io/
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Sqreen is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Sqreen is a Runtime Application Self-Protection (RASP) solution for software teams. An in-app agent instruments and monitors the app. Suspicious user activities are reported and attacks are blocked at runtime without code modification or traffic redirection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Runtime Application Self-Protection.

Back to Category Index

Teller

  • Website: https://github.com/spectralops/teller
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Teller is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: a secrets management tool for devops and developers - manage secrets across multiple vaults and keystores from a single 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 Security > DevOps.

Back to Category Index

TFSec

  • Website: https://github.com/tfsec/tfsec/
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: TFSec is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A static analysis tool for infrastucture as code (Terraform).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

Whonix

  • Website: https://www.whonix.org
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security, Awesome Cyber Security Tools

What it does: Whonix is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Privacy-focused Linux distribution that leverages Tor for anonymous communication.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Workbench

  • Website: http://workbench.readthedocs.org/
  • Model: Open Source
  • Category: General Security
  • Source Lists: Awesome Security

What it does: Workbench is used in general security programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A scalable python framework for security research and development 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 Security > Big Data.

Back to Category Index

Hacking

This category contains 30 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Bugcrowd

  • Website: https://www.bugcrowd.com/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Bugcrowd is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > Bug bounty - Earn Some Money.

Back to Category Index

ebowla

  • Website: https://github.com/Genetic-Malware/Ebowla
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: ebowla is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Framework for Making Environmental Keyed Payloads.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Post exploitation > tools.

Back to Category Index

EnCase

  • Website: https://www.guidancesoftware.com/products/Pages/encase-forensic/overview.aspx
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: EnCase is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The shared technology within a suite of digital investigations products by Guidance 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: Forensic > Tools.

Back to Category Index

Findsubdomains

  • Website: https://findsubdomains.com/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Findsubdomains is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A subdomains discovery tool that collects all possible subdomains from open source internet and validates them through various tools to provide accurate results.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

fuzzy.land

  • Website: https://fuzzy.land/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: fuzzy.land is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Website by an Austrian group. Lots of challenges taken from CTFs they participated in.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Web.

Back to Category Index

Gruyere

  • Website: https://google-gruyere.appspot.com/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Gruyere is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > Web.

Back to Category Index

Hack The Box

  • Website: https://www.hackthebox.eu
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking, Awesome CTF

What it does: Hack The Box is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: a free site to perform pentesting in a variety of different 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: Resources > Wargames.

Back to Category Index

Hackerone

  • Website: https://www.hackerone.com/start-hacking
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Hackerone is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > Bug bounty - Earn Some Money.

Back to Category Index

HackingLab

  • Website: https://www.hacking-lab.com/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: HackingLab is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > System.

Back to Category Index

IPED - Indexador e Processador de Evidências Digitais

  • Website: https://servicos.dpf.gov.br/ferramentas/IPED/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: IPED - Indexador e Processador de Evidências Digitais is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Brazilian Federal Police Tool for Forensic Investigation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Forensic > Tools.

Back to Category Index

mimikatz

  • Website: https://github.com/gentilkiwi/mimikatz
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: mimikatz is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A little tool to play with Windows 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: System > Tools.

Back to Category Index

Missing Semester

  • Website: https://missing.csail.mit.edu/2020/course-shell/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Missing Semester is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Tutorials.

Back to Category Index

Others

  • Website: https://www.owasp.org/index.php/OWASP_Vulnerable_Web_Applications_Directory_Project#tab=On-Line_apps
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Others is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > Web.

Back to Category Index

OverTheWire - Drifter

  • Website: http://overthewire.org/wargames/drifter/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: OverTheWire - Drifter is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > System.

Back to Category Index

OverTheWire - Krypton

  • Website: http://overthewire.org/wargames/krypton/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: OverTheWire - Krypton is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > Cryptography.

Back to Category Index

OverTheWire - Semtex

  • Website: http://overthewire.org/wargames/semtex/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: OverTheWire - Semtex is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > System.

Back to Category Index

OverTheWire - Vortex

  • Website: http://overthewire.org/wargames/vortex/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: OverTheWire - Vortex is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Wargame > System.

Back to Category Index

pwnable.kr

  • Website: http://pwnable.kr/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking, Awesome CTF

What it does: pwnable.kr is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Provide various pwn challenges regarding system 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: Resources > Wargames.

Back to Category Index

Roppers Computing Fundamentals

  • Website: https://www.roppers.org/courses/fundamentals
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Roppers Computing Fundamentals is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Tutorials.

Back to Category Index

Roppers Practical Networking

  • Website: https://www.roppers.org/courses/networking
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Roppers Practical Networking is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A hands-on, wildly practical introduction to networking and making packets dance. No wasted time, no memorizing, just learning the fundamentals.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: ETC.

Back to Category Index

  • Website: https://inventory.raw.pm/operating_systems.html
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Security, Awesome Hacking

What it does: Security related Operating Systems @ Rawsec is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Complete list of security related operating 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 Security > Operating Systems > Online resources.

Back to Category Index

silenttrinity

  • Website: https://github.com/byt3bl33d3r/SILENTTRINITY
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: silenttrinity is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A post exploitation tool that uses iron python to get past powershell restrictions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Post exploitation > tools.

Back to Category Index

SmashTheStack

  • Website: http://smashthestack.org/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking, Awesome CTF

What it does: SmashTheStack is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Wargames.

Back to Category Index

sqlmap

  • Website: https://github.com/sqlmapproject/sqlmap
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking, Awesome CTF, Awesome Web Security

What it does: sqlmap is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Automatic 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: Awesome Web Security > Tools > Offensive > SQL Injection.

Back to Category Index

Strong node.js

  • Website: https://github.com/jesusprubio/strong-node
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Strong node.js is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: An exhaustive checklist to assist in the source code security analysis of a node.js web service.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Web > General.

Back to Category Index

SubFinder

  • Website: https://github.com/subfinder/subfinder
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: SubFinder is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: SubFinder is a subdomain discovery tool that discovers valid subdomains for any target using passive online sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Web > Tools.

Back to Category Index

The Cyberclopaedia

  • Website: https://cr0mll.github.io/cyberclopaedia/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: The Cyberclopaedia is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The open-source encyclopedia of 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: ETC.

Back to Category Index

tools.web-max.ca

  • Website: http://tools.web-max.ca/encode_decode.php
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: tools.web-max.ca is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: base64 base85 md4,5 hash, sha1 hash encoding/decoding.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Web > Tools.

Back to Category Index

Understanding the basics of Linux Binary Exploitation

  • Website: https://github.com/r0hi7/BinExp
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking

What it does: Understanding the basics of Linux Binary Exploitation is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Tutorials.

Back to Category Index

Webhacking.kr

  • Website: http://webhacking.kr/
  • Model: Open Source
  • Category: Hacking
  • Source Lists: Awesome Hacking, Awesome CTF

What it does: Webhacking.kr is used in hacking programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Wargames.

Back to Category Index

Identity & Access Security

This category contains 6 documented tools. It focuses on capabilities used for identity lifecycle control, adaptive authentication, and privileged access governance. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Firezone

  • Website: https://www.firezone.dev/
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Firezone is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. Source summaries describe it as: Self-hosted VPN server built on WireGuard that supports MFA and SSO.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

Identity Threat Detection and Response

  • Website: https://www.semperis.com/blog/evaluating-identity-threat-detection-response-solutions/
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome SOC

What it does: Identity Threat Detection and Response is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. Source summaries describe it as: ** (ITDR) for identity and AD/AAD security (audit logs, or specific security monitoring solutions):.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

LunaSec

  • Website: https://github.com/lunasec-io/lunasec
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome Security

What it does: LunaSec is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. Source summaries describe it as: Database for PII with automatic encryption/tokenization, sandboxed components for handling data, and centralized authorization 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 Security > Datastores.

Back to Category Index

Security bastion (PAM) and Active Directory tiering mode: how to reconcile the two paradigms?

  • Website: https://www.riskinsight-wavestone.com/en/2022/10/security-bastion-pam-and-active-directory-tiering-mode-how-to-reconcile-the-two-paradigms/
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome SOC

What it does: Security bastion (PAM) and Active Directory tiering mode: how to reconcile the two paradigms? is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. 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 Category Index

Security Checklist by OWASP

  • Website: https://owasp.org/www-project-application-security-verification-standard/
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome Security

What it does: Security Checklist by OWASP is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. Source summaries describe it as: A checklist by OWASP for testing web applications based on assurance level. Covers multiple topics like Architecture, IAM, Sanitization, Cryptography and Secure Configuration.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

Wallix PAM

  • Website: https://www.wallix.com/privileged-access-management/
  • Model: Open Source
  • Category: Identity & Access Security
  • Source Lists: Awesome SOC

What it does: Wallix PAM is used in identity & access security programs to support identity lifecycle control, adaptive authentication, and privileged access governance. 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 > Harden SOC/CSIRT environment.

Back to Category Index

Incident Response

This category contains 174 documented tools. It focuses on capabilities used for containment coordination, evidence collection, and post-incident timeline reconstruction. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

CIRCL

  • Website: https://www.circl.lu/services
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cyber Security Tools

What it does: CIRCL is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Computer Incident Response Center Luxembourg; provides threat intelligence feeds and malware 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: Malware Analysis > Threat Intelligence.

Back to Category Index

11 strategies for a world-class SOC

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/11-strategies-of-a-world-class-cybersecurity-operations-center.pdf
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: 11 strategies for a world-class SOC is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: , Strategy 3: Build a SOC Structure to Match Your Organizational Needs, pages 101-123.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Fundamental concepts > Concepts, tools, missions, attack lifecycle, red/blue/purple teams > MITRE references:.

Back to Category Index

AccessData FTK Imager

  • Website: http://accessdata.com/product-download/?/support/adownloads#FTKImager
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: AccessData FTK Imager is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Forensics tool whose main purpose is to preview recoverable data from a disk of any kind. FTK Imager can also acquire live memory and paging file on 32bit and 64bit 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 Incident Response > IR Tools Collection > Disk Image Creation Tools.

Back to Category Index

AChoir

  • Website: https://github.com/OMENScan/AChoir
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: AChoir is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Framework/scripting tool to standardize and simplify the process of scripting live acquisition utilities 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 Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Acquire

  • Website: https://github.com/fox-it/acquire
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Acquire is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Acquire is a tool to quickly gather forensic artifacts from disk images or a live system into a lightweight container. This makes Acquire an excellent tool to, among others, speedup the process of digital forensic triage. It uses to gather that information from the raw disk, if possible.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

APTSimulator

  • Website: https://github.com/NextronSystems/APTSimulator
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: APTSimulator is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A Windows Batch script that uses a set of tools and output files to make a system look as if it was compromised.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

Art of Memory Forensics

  • Website: https://www.amazon.com/Art-Memory-Forensics-Detecting-Malware/dp/1118825098/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Art of Memory Forensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Detecting Malware and Threats in Windows, Linux, and Mac Memory.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

artifactcollector

  • Website: https://github.com/forensicanalysis/artifactcollector
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: artifactcollector is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The artifactcollector project provides a software that collects forensic artifacts on 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 Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Atomic Red Team (ART)

  • Website: https://github.com/redcanaryco/atomic-red-team
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Atomic Red Team (ART) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Small and highly portable detection tests mapped to the MITRE ATT&CK 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 Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

Aurora Incident Response

  • Website: https://github.com/cyb3rfox/Aurora-Incident-Response
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Aurora Incident Response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Platform developed to build easily a detailed timeline of an incident.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Timeline Tools.

Back to Category Index

AutoMacTC

  • Website: https://github.com/CrowdStrike/automactc
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: AutoMacTC is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Modular, automated forensic triage collection framework designed to access various forensic artifacts on macOS, parse them, and present them in formats viable for 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: Awesome Cybersecurity Blue Team > Incident Response tools > Evidence collection.

Back to Category Index

AutoTTP

  • Website: https://github.com/jymcheong/AutoTTP
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: AutoTTP is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automated Tactics Techniques & Procedures. Re-running complex sequences manually for regression tests, product evaluations, generate data for 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 Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

AVML

  • Website: https://github.com/microsoft/avml
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: AVML is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A portable volatile memory acquisition tool for 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 Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Awesome Forensics

  • Website: https://github.com/cugu/awesome-forensics
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Awesome Forensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A curated list of awesome forensic analysis tools 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 Incident Response > IR Tools Collection > Other Lists.

Back to Category Index

aws_ir

  • Website: https://github.com/ThreatResponse/aws_ir
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: aws_ir is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automates your incident response with zero security preparedness assumptions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools.

Back to Category Index

Azure AD Incident Response Powershell

  • Website: https://github.com/reprise99/kql-for-dfir/tree/main/Azure%20Active%20Directory
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: Azure AD Incident Response Powershell is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Belkasoft Evidence Center

  • Website: https://belkasoft.com/ec
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Belkasoft Evidence Center is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The toolkit will quickly extract digital evidence from multiple sources by analyzing hard drives, drive images, memory dumps, iOS, Blackberry and Android backups, UFED, JTAG and chip-off dumps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Belkasoft Live RAM Capturer

  • Website: http://belkasoft.com/ram-capturer
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Belkasoft Live RAM Capturer is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Tiny free forensic tool to reliably extract the entire content of the computer’s volatile memory – even if protected by an active anti-debugging or anti-dumping 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 Incident Response > IR Tools Collection > Memory Imaging Tools.

Back to Category Index

Bitscout

  • Website: https://github.com/vitaly-kamluk/bitscout
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Bitscout is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Bitscout by Vitaly Kamluk helps you build your fully-trusted customizable LiveCD/LiveUSB image to be used for remote digital forensics (or perhaps any other task of your choice). It is meant to be transparent and monitorable by the owner of the system, forensically sound, customizable and compact.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Disk Image Creation Tools.

Back to Category Index

Caldera

  • Website: https://github.com/mitre/caldera
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Caldera is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automated adversary emulation system that performs post-compromise adversarial behavior within Windows Enterprise networks. It generates plans during operation using a planning system and a pre-configured adversary model based on the Adversarial Tactics, Techniques & Common Knowledge (ATT&CK™) 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 Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

CAPA

  • Website: https://github.com/mandiant/capa
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: CAPA is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: detects capabilities in executable files. You run it against a PE, ELF, .NET module, or shellcode file and it tells you what it thinks the program can do.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

CAPEv2

  • Website: https://github.com/kevoreilly/CAPEv2
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: CAPEv2 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Malware Configuration And Payload 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 Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

CCF-VM

  • Website: https://github.com/rough007/CCF-VM
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: CCF-VM is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: CyLR CDQR Forensics Virtual Machine (CCF-VM): An all-in-one solution to parsing collected data, making it easily searchable with built-in common searches, enable searching of single and multiple hosts 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 Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

CIFv2

  • Website: https://github.com/csirtgadgets/massive-octo-spice
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: CIFv2 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: CIF is a cyber threat intelligence management system. CIF allows you to combine known malicious threat information from many sources and use that information for identification (incident response), detection (IDS) and mitigation (null route).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

CimSweep

  • Website: https://github.com/PowerShellMafia/CimSweep
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: CimSweep is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A suite of CIM/WMI-based tools that enable the ability to perform incident response and hunting operations remotely across all versions of 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 Cybersecurity Blue Team > Security monitoring > Threat hunting.

Back to Category Index

CIRTkit

  • Website: https://github.com/byt3smith/CIRTKit
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: CIRTkit is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: CIRTKit is not just a collection of tools, but also a framework to aid in the ongoing unification of Incident Response and Forensics investigation processes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

CIRTKit

  • Website: https://github.com/opensourcesec/CIRTKit
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: CIRTKit is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Scriptable Digital Forensics and Incident Response (DFIR) toolkit built on Viper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > IR management consoles.

Back to Category Index

Cold Disk Quick Response

  • Website: https://github.com/rough007/CDQR
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Cold Disk Quick Response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Streamlined list of parsers to quickly analyze a forensic image file (dd, E01, .vmdk, etc) and output nine reports.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Computer Aided Investigative Environment (CAINE)

  • Website: http://www.caine-live.net/index.html
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Computer Aided Investigative Environment (CAINE) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Contains numerous tools that help investigators during their analysis, including forensic evidence collection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

Crowd Response

  • Website: http://www.crowdstrike.com/community-tools/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Crowd Response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Lightweight Windows console application designed to aid in the gathering of system information for incident response and security engagements. It features numerous modules and output formats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Cuckoo

  • Website: https://github.com/cuckoosandbox/cuckoo
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cyber Security Tools

What it does: Cuckoo is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Open Source Highly configurable sandboxing 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 Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Cuckoo-modified

  • Website: https://github.com/spender-sandbox/cuckoo-modified
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Cuckoo-modified is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Heavily modified Cuckoo fork developed 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: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Cutter

  • Website: https://github.com/rizinorg/cutter
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Cutter is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free and Open Source Reverse Engineering Platform powered by rizin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Cyber Triage

  • Website: http://www.cybertriage.com
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Cyber Triage is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Cyber Triage has a lightweight collection tool that is free to use. It collects source files (such as registry hives and event logs), but also parses them on the live host so that it can also collect the executables that the startup items, scheduled, tasks, etc. refer to. It's output is a JSON file that can be imported into the free version of Cyber Triage. Cyber Triage is made by Sleuth Kit Labs, which also makes Autopsy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

CyberCPR

  • Website: https://www.cybercpr.com
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: CyberCPR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Community and commercial incident management tool with Need-to-Know built in to support GDPR compliance while handling sensitive incidents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

CyLR

  • Website: https://github.com/orlikoski/CyLR
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Hacking

What it does: CyLR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The CyLR tool collects forensic artifacts from hosts with NTFS file systems quickly, securely and minimizes impact to the host.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Cyphon

  • Website: https://medevel.com/cyphon/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Cyphon is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Cyphon eliminates the headaches of incident management by streamlining a multitude of related tasks through a single platform. It receives, processes and triages events to provide an all-encompassing solution for your analytic workflow — aggregating data, bundling and prioritizing alerts, and empowering analysts to investigate and document incidents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

DFIR ORC

  • Website: https://dfir-orc.github.io/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: DFIR ORC is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: DFIR ORC is a collection of specialized tools dedicated to reliably parse and collect critical artifacts such as the MFT, registry hives or event logs. DFIR ORC collects data, but does not analyze it: it is not meant to triage machines. It provides a forensically relevant snapshot of machines running Microsoft Windows. The code can be found on .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

DFIRTrack

  • Website: https://github.com/dfirtrack/dfirtrack
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: DFIRTrack is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Incident Response tracking application handling one or more incidents via cases and tasks with a lot of affected systems and artifacts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

DFTimewolf

  • Website: https://github.com/log2timeline/dftimewolf
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: DFTimewolf is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Framework for orchestrating forensic collection, processing and data export using GRR and Rekall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

Didier Stevens Suite

  • Website: https://github.com/DidierStevens/DidierStevensSuite
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Didier Stevens Suite is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Tool collection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Lists.

Back to Category Index

Diffy

  • Website: https://github.com/Netflix-Skunkworks/diffy
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Diffy is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: DFIR tool developed by Netflix's SIRT that allows an investigator to quickly scope a compromise across cloud instances (Linux instances on AWS, currently) during an incident and efficiently triaging those instances for followup actions by showing differences against a baseline.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Digital Forensics and Incident Response: Incident response techniques and procedures to respond to modern cyber threats

  • Website: https://www.amazon.com/Digital-Forensics-Incident-Response-techniques/dp/183864900X
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Digital Forensics and Incident Response: Incident response techniques and procedures to respond to modern cyber threats is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: by Gerard Johansen.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Digital Forensics Artifact Knowledge Base

  • Website: https://github.com/ForensicArtifacts/artifacts-kb
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Digital Forensics Artifact Knowledge Base is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Digital Forensics Artifact Knowledge Base.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Knowledge Bases.

Back to Category Index

Digital Forensics Discord Server

  • Website: https://discordapp.com/invite/JUqe9Ek
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Digital Forensics Discord Server is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Community of 8,000+ working professionals from Law Enforcement, Private Sector, and Forensic Vendors. Additionally, plenty of students and hobbyists! 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 Incident Response > IR Tools Collection > Communities.

Back to Category Index

Digital Forensocs Incident Response Git

  • Website: https://github.com/soufianetahiri/Digital-Forensics-Incident-Response
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: Digital Forensocs Incident Response Git is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 > Nice to read.

Back to Category Index

Dissect

  • Website: https://github.com/fox-it/dissect
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Dissect is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Dissect is a digital forensics & incident response framework and toolset that allows you to quickly access and analyse forensic artefacts from various disk and file formats, developed by Fox-IT (part of NCC Group).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

domfind

  • Website: https://github.com/diogo-fernan/domfind
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: domfind is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Python DNS crawler for finding identical domain names under different TLDs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Doorman

  • Website: https://github.com/mwielgoszewski/doorman
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Doorman is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: osquery fleet manager that allows remote management of osquery configurations retrieved by nodes. It takes advantage of osquery's TLS configuration, logger, and distributed read/write endpoints, to give administrators visibility across a fleet of devices with minimal overhead and intrusiveness.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

DumpsterFire

  • Website: https://github.com/TryCatchHCF/DumpsterFire
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: DumpsterFire is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Modular, menu-driven, cross-platform tool for building repeatable, time-delayed, distributed security events. Easily create custom event chains for Blue Team drills and sensor / alert mapping. Red Teams can create decoy incidents, distractions, and lures to support and scale their 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 Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

Eric Zimmerman Tools

  • Website: https://ericzimmerman.github.io/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Eric Zimmerman Tools is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: An updated list of forensic tools created by Eric Zimmerman, an instructor for SANS institute.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Lists.

Back to Category Index

FastIR Collector

  • Website: https://github.com/SekoiaLab/Fastir_Collector
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: FastIR Collector is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Tool that collects different artifacts on live Windows systems and records the results in csv files. With the analyses of these artifacts, an early compromise can be detected.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

FastIR Collector Linux

  • Website: https://github.com/SekoiaLab/Fastir_Collector_Linux
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: FastIR Collector Linux is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: FastIR for Linux collects different artifacts on live Linux and records the results in CSV 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 Incident Response > IR Tools Collection > Linux Evidence Collection.

Back to Category Index

Fenrir

  • Website: https://github.com/Neo23x0/Fenrir
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Fenrir is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Simple IOC scanner. It allows scanning any Linux/Unix/OSX system for IOCs in plain bash. Created by the creators of THOR and LOKI.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Scanner Tools.

Back to Category Index

Forensic Artifacts

  • Website: https://github.com/ForensicArtifacts/artifacts
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics, Awesome SOC

What it does: Forensic Artifacts is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

GetData Forensic Imager

  • Website: http://www.forensicimager.com/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: GetData Forensic Imager is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Windows based program that will acquire, convert, or verify a forensic image in one of the following common forensic file formats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Disk Image Creation Tools.

Back to Category Index

grr

  • Website: https://github.com/google/grr
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team, Awesome Forensics

What it does: grr is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Incident response framework focused on remote live forensics consisting of a Python agent installed on assets and Python-based server infrastructure enabling analysts to quickly triage attacks and perform analysis remotely.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

Guymager

  • Website: http://guymager.sourceforge.net
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Guymager is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free forensic imager for media acquisition on 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 Incident Response > IR Tools Collection > Disk Image Creation Tools.

Back to Category Index

HELK

  • Website: https://github.com/Cyb3rWard0g/HELK
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: HELK is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A Hunting ELK (Elasticsearch, Logstash, Kibana) with advanced analytic 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 Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Hindsight

  • Website: https://github.com/obsidianforensics/hindsight
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Hindsight is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Internet history forensics for Google Chrome/Chromium.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Hoarder

  • Website: https://github.com/muteb/Hoarder
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Hoarder is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Collecting the most valuable artifacts for forensics or incident response investigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

How Dropbox Security builds tools for threat detection and incident response

  • Website: https://dropbox.tech/security/how-dropbox-security-builds-better-tools-for-threat-detection-and-incident-response
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Threat Detection

What it does: How Dropbox Security builds tools for threat detection and incident response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 > Resources.

Back to Category Index

imagemounter

  • Website: https://github.com/ralphje/imagemounter
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: imagemounter is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Command line utility and Python package to ease the (un)mounting of forensic disk images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Improving Social Maturity of Cybersecurity Incident Response Teams

  • Website: https://edu.anarcho-copy.org/Against%20Security%20-%20Self%20Security/GMU_Cybersecurity_Incident_Response_Team_social_maturity_handbook.pdf
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: Improving Social Maturity of Cybersecurity Incident Response Teams is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 Category Index

Incident Response & Computer Forensics, 3rd ed

  • Website: https://www.google.fr/books/edition/Incident_Response_Computer_Forensics_Thi/LuWINQEACAAJ?hl=fr
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: Incident Response & Computer Forensics, 3rd ed is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 > Nice to read.

Back to Category Index

Incident Response & Computer Forensics, Third Edition

  • Website: https://www.amazon.com/Incident-Response-Computer-Forensics-Third/dp/0071798684/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Incident Response & Computer Forensics, Third Edition is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The definitive guide to incident response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Incident response reference guide

  • Website: https://www.linkedin.com/posts/the-cyber-security-hub_incident-response-reference-guide-activity-7033563558642642944-0zav?utm_source=share&utm_medium=member_desktop
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: Incident response reference guide is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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: Must read > For a CERT/CSIRT.

Back to Category Index

Incident Response Techniques for Ransomware Attacks

  • Website: https://www.amazon.com/Incident-Response-Techniques-Ransomware-Attacks/dp/180324044X
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Incident Response Techniques for Ransomware Attacks is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A great guide to build an incident response strategy for ransomware attacks. By Oleg Skulkin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Incident Response with Threat Intelligence

  • Website: https://www.amazon.com/Incident-response-Threat-Intelligence-intelligence-based/dp/1801072957
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Incident Response with Threat Intelligence is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Great reference to build an incident response plan based also on Threat Intelligence. By Roberto Martinez.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Intelligence-Driven Incident Response

  • Website: https://www.amazon.com/Intelligence-Driven-Incident-Response-Outwitting-Adversary-ebook-dp-B074ZRN5T7/dp/B074ZRN5T7
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Intelligence-Driven Incident Response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: By Scott J. Roberts, Rebekah Brown.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Introduction to DFIR

  • Website: https://medium.com/@sroberts/introduction-to-dfir-d35d5de4c180/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Introduction to DFIR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: By Scott J. Roberts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

Invoke-LiveResponse

  • Website: https://github.com/mgreen27/Invoke-LiveResponse
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Invoke-LiveResponse is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Invoke-LiveResponse is a live response tool for targeted collection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

IOC Finder

  • Website: https://www.fireeye.com/services/freeware/ioc-finder.html
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: IOC Finder is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free tool from Mandiant for collecting host system data and reporting the presence of Indicators of Compromise (IOCs). Support for Windows only. No longer maintained. Only fully supported up to Windows 7 / Windows Server 2008 R2.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

IR lessons on cloud ID compromise

  • Website: https://www.microsoft.com/en-us/security/blog/2023/12/05/microsoft-incident-response-lessons-on-preventing-cloud-identity-compromise/?msockid=07788c7fcb0c689a2a5d98f6ca0169fb
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: IR lessons on cloud ID compromise is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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: Must read > For a CERT/CSIRT.

Back to Category Index

IR Mitigations tasks

  • Website: https://board.flexibleir.com/b/VtdssIfCJ6Z2LYLED/1
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: IR Mitigations tasks is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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: Must read > For a CERT/CSIRT.

Back to Category Index

ir-rescue

  • Website: https://github.com/diogo-fernan/ir-rescue
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: ir-rescue is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: ir-rescue is a Windows Batch script and a Unix Bash script to comprehensively collect host forensic data during incident response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > Evidence collection.

Back to Category Index

IREC

  • Website: https://binalyze.com/products/irec-free/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: IREC is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: All-in-one IR Evidence Collector which captures RAM Image, $MFT, EventLogs, WMI Scripts, Registry Hives, System Restore Points and much more. It is FREE, lightning fast and easy to use.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

IRIS

  • Website: https://github.com/dfir-iris/iris-web
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: IRIS is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: IRIS is a web collaborative platform for incident response analysts allowing to share investigations at a technical level.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

IRM

  • Website: https://github.com/certsocietegenerale/IRM
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: IRM is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Incident Response Methodologies by CERT Societe Generale.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Playbooks.

Back to Category Index

IRTriage

  • Website: https://github.com/AJMartel/IRTriage
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: IRTriage is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Incident Response Triage - Windows Evidence Collection for Forensic 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: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Joe Sandbox (Community)

  • Website: https://www.joesandbox.com/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome SOC

What it does: Joe Sandbox (Community) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Joe Sandbox detects and analyzes potential malicious files and URLs on Windows, Android, Mac OS, Linux, and iOS for suspicious activities; providing comprehensive and detailed analysis reports.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Kansa

  • Website: https://github.com/davehull/Kansa/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Kansa is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Modular incident response framework in PowerShell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

KAPE

  • Website: https://www.kroll.com/en/services/cyber-risk/incident-response-litigation-support/kroll-artifact-parser-extractor-kape
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: KAPE is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Kroll Artifact Parser and Extractor (KAPE) by Eric Zimmerman. A triage tool that finds the most prevalent digital artifacts and then parses them quickly. Great and thorough when time is of the essence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Knockknock

  • Website: https://objective-see.com/products/knockknock.html
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Knockknock is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Displays persistent items(scripts, commands, binaries, etc.) that are set to execute automatically on OSX.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > OSX Evidence Collection.

Back to Category Index

Kuiper

  • Website: https://github.com/DFIRKuiper/Kuiper
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Kuiper is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Digital Forensics Investigation 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: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Limacharlie

  • Website: https://www.limacharlie.io/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Limacharlie is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Endpoint security platform composed of a collection of small projects all working together that gives you a cross-platform (Windows, OSX, Linux, Android and iOS) low-level environment for managing and pushing additional modules into memory to extend its functionality.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Linux Memory Grabber

  • Website: https://github.com/halpomeranz/lmg/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Linux Memory Grabber is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Script for dumping Linux memory and creating Volatility profiles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Imaging Tools.

Back to Category Index

List of various Security APIs

  • Website: https://github.com/deralexxx/security-apis
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: List of various Security APIs is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Collective list of public JSON APIs for use in 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 Incident Response > IR Tools Collection > Other Lists.

Back to Category Index

Live Response Collection

  • Website: https://www.brimorlabs.com/tools/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Live Response Collection is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automated tool that collects volatile data from Windows, OSX, and *nix based operating 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 Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

LOKI

  • Website: https://github.com/Neo23x0/Loki
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Incident Response, Awesome Cyber Security Tools, Awesome Forensics, Awesome SOC

What it does: LOKI is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free IR scanner for scanning endpoint with yara rules and other indicators(IOCs).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

macOS Artifact Parsing Tool (mac_apt)

  • Website: https://github.com/ydkhatri/mac_apt
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: macOS Artifact Parsing Tool (mac_apt) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Plugin based forensics framework for quick mac triage that works on live machines, disk images or individual artifact 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 Incident Response > IR Tools Collection > OSX Evidence Collection.

Back to Category Index

Magnet ACQUIRE

  • Website: https://www.magnetforensics.com/magnet-acquire/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Magnet ACQUIRE is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: ACQUIRE by Magnet Forensics allows various types of disk acquisitions to be performed on Windows, Linux, and OS X as well as mobile operating 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 Incident Response > IR Tools Collection > Disk Image Creation Tools.

Back to Category Index

MAGNET DumpIt

  • Website: https://github.com/MagnetForensics/dumpit-linux
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: MAGNET DumpIt is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Fast memory acquisition open source tool for Linux written in Rust. Generate full memory crash dumps of Linux 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 Incident Response > IR Tools Collection > Linux Evidence Collection.

Back to Category Index

MAGNET DumpIt

  • Website: https://www.magnetforensics.com/resources/magnet-dumpit-for-windows
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: MAGNET DumpIt is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Fast memory acquisition tool for Windows (x86, x64, ARM64). Generate full memory crash dumps of Windows 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 Incident Response > IR Tools Collection > Memory Imaging Tools.

Back to Category Index

Magnet RAM Capture

  • Website: https://www.magnetforensics.com/free-tool-magnet-ram-capture/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Magnet RAM Capture is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free imaging tool designed to capture the physical memory of a suspect’s computer. Supports recent versions of 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 Incident Response > IR Tools Collection > Memory Imaging Tools.

Back to Category Index

MalConfScan

  • Website: https://github.com/JPCERTCC/MalConfScan
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: MalConfScan is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: MalConfScan is a Volatility plugin extracts configuration data of known malware. Volatility is an open-source memory forensics framework for incident response and malware analysis. This tool searches for malware in memory images and dumps configuration data. In addition, this tool has a function to list strings to which malicious code refers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Margarita Shotgun

  • Website: https://github.com/ThreatResponse/margaritashotgun
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: Margarita Shotgun is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Command line utility (that works with or without Amazon EC2 instances) to parallelize remote memory acquisition.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > Evidence collection.

Back to Category Index

Meerkat

  • Website: https://github.com/TonyPhipps/Meerkat
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Incident Response

What it does: Meerkat is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: PowerShell-based Windows artifact collection for threat hunting and incident response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Memoryze

  • Website: https://www.fireeye.com/services/freeware/memoryze.html
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Memoryze is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free memory forensic software that helps incident responders find evil in live memory. Memoryze can acquire and/or analyze memory images, and on live systems, can include the paging file in its 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: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Metadefender Cloud

  • Website: https://www.metadefender.com
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Metadefender Cloud is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free threat intelligence platform providing multiscanning, data sanitization and vulnerability assessment 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 Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Metta

  • Website: https://github.com/uber-common/metta
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Metta is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automated information security preparedness tool to do adversarial simulation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

MFT Browser

  • Website: https://github.com/kacos2000/MFT_Browser
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: MFT Browser is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: MFT directory tree reconstruction & record info.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Microsoft ProcDump

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Microsoft ProcDump is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Dumps any running Win32 processes memory image on the fly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Process Dump Tools.

Back to Category Index

Morgue

  • Website: https://github.com/etsy/morgue
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Morgue is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: PHP Web app by Etsy for managing postmortems.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Timeline Tools.

Back to Category Index

MozDef

  • Website: https://github.com/mozilla/MozDef
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: MozDef is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Automates the security incident handling process and facilitate the real-time activities of incident handlers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

Munin

  • Website: https://github.com/Neo23x0/munin
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Munin is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Online hash checker for VirusTotal and other services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

MutableSecurity

  • Website: https://github.com/MutableSecurity/mutablesecurity
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Security, Awesome Incident Response

What it does: MutableSecurity is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: CLI program for automating the setup, configuration, and use of cybersecurity solutions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Network Flight Simulator

  • Website: https://github.com/alphasoc/flightsim
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Network Flight Simulator is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: flightsim is a lightweight utility used to generate malicious network traffic and help security teams to evaluate security controls and network visibility.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

nightHawk

  • Website: https://github.com/biggiesmallsAG/nightHawkResponse
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: nightHawk is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Application built for asynchronous forensic data presentation using ElasticSearch as the backend. It's designed to ingest Redline collections.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

NST - Network Security Toolkit

  • Website: https://sourceforge.net/projects/nst/files/latest/download?source=files
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: NST - Network Security Toolkit is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Linux distribution that includes a vast collection of best-of-breed open source network security applications useful to the network security professional.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

Obsidian

  • Website: https://obsidian.md
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome OSINT

What it does: Obsidian is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Knowledge base and note-taking tool ideal for OSINT case management.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Open Computer Forensics Architecture

  • Website: http://sourceforge.net/projects/ocfa/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Open Computer Forensics Architecture is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Another popular distributed open-source computer forensics framework. This framework was built on Linux platform and uses postgreSQL database for storing data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Orochi

  • Website: https://github.com/LDO-CERT/orochi
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Orochi is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Orochi is an open source framework for collaborative forensic memory dump 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: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

OSForensics

  • Website: http://www.osforensics.com/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: OSForensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Tool to acquire live memory on 32-bit and 64-bit systems. A dump of an individual process’s memory space or physical memory dump can be done.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Imaging Tools.

Back to Category Index

osquery

  • Website: https://osquery.io/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: osquery is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Easily ask questions about your Linux and macOS infrastructure using a SQL-like query language; the provided incident-response pack helps you detect and respond to breaches.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

OSX Auditor

  • Website: https://github.com/jipegit/OSXAuditor
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Forensics

What it does: OSX Auditor is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 Cybersecurity Blue Team > Incident Response tools > Evidence collection.

Back to Category Index

OSX Collector

  • Website: https://github.com/yelp/osxcollector
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: OSX Collector is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: OSX Auditor offshoot for live response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > OSX Evidence Collection.

Back to Category Index

OSXCollector

  • Website: https://github.com/Yelp/osxcollector
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OSXCollector is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Forensic evidence collection & analysis toolkit 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 Cybersecurity Blue Team > Incident Response tools > Evidence collection.

Back to Category Index

PagerDuty Incident Response Documentation

  • Website: https://response.pagerduty.com/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: PagerDuty Incident Response Documentation is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Documents that describe parts of the PagerDuty Incident Response process. It provides information not only on preparing for an incident, but also what to do during and after. Source is available on .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Playbooks.

Back to Category Index

PALADIN

  • Website: https://sumuri.com/software/paladin/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: PALADIN is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Modified Linux distribution to perform various forensics task in a forensically sound manner. It comes with many open source forensics tools included.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

Panorama

  • Website: https://github.com/AlmCo/Panorama
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Panorama is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Fast incident overview on live Windows 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 Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Plaso

  • Website: https://github.com/log2timeline/plaso
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Plaso is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: a Python-based backend engine for the tool log2timeline.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Timeline Tools.

Back to Category Index

PMDump

  • Website: http://www.ntsecurity.nu/toolbox/pmdump/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: PMDump is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Tool that lets you dump the memory contents of a process to a file without stopping the 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 Incident Response > IR Tools Collection > Process Dump Tools.

Back to Category Index

PowerForensics

  • Website: https://github.com/Invoke-IR/PowerForensics
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Forensics

What it does: PowerForensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: All in one PowerShell-based platform to perform live hard disk forensic 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: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

PowerSponse

  • Website: https://github.com/swisscom/PowerSponse
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: PowerSponse is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: PowerSponse is a PowerShell module focused on targeted containment and remediation during security incident response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Practical Memory Forensics

  • Website: https://www.amazon.com/Practical-Memory-Forensics-Jumpstart-effective/dp/1801070334
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Practical Memory Forensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The definitive guide to practice memory forensics. By Svetlana Ostrovskaya and Oleg Skulkin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Books.

Back to Category Index

PSRecon

  • Website: https://github.com/gfoss/PSRecon/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: PSRecon is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: PSRecon gathers data from a remote Windows host using PowerShell (v2 or later), organizes the data into folders, hashes all extracted data, hashes PowerShell and various system properties, and sends the data off to the security team. The data can be pushed to a share, sent over email, or retained locally.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

PyaraScanner

  • Website: https://github.com/nogoodconfig/pyarascanner
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: PyaraScanner is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Very simple multi-threaded many-rules to many-files YARA scanning Python script for malware zoos and IR.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Raccine

  • Website: https://github.com/Neo23x0/Raccine
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Raccine is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A Simple Ransomware Protection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Radare2

  • Website: https://github.com/radareorg/radare2
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Radare2 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Reverse engineering framework and command-line toolset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

RaQet

  • Website: https://raqet.github.io/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: RaQet is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Unconventional remote acquisition and triaging tool that allows triage a disk of a remote computer (client) that is restarted with a purposely built forensic 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 Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

rastrea2r

  • Website: https://github.com/rastrea2r/rastrea2r
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: rastrea2r is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Multi-platform tool for triaging suspected IOCs on many endpoints simultaneously and that integrates with antivirus consoles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

RedHunt-OS

  • Website: https://github.com/redhuntlabs/RedHunt-OS
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: RedHunt-OS is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A Virtual Machine for Adversary Emulation and Threat Hunting. RedHunt aims to be a one stop shop for all your threat emulation and threat hunting needs by integrating attacker's arsenal as well as defender's toolkit to actively identify the threats in your environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

Redline

  • Website: https://www.fireeye.com/services/freeware/redline.html
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: Redline is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Provides host investigative capabilities to users to find signs of malicious activity through memory and file analysis, and the development of a threat assessment profile.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Threat hunting.

Back to Category Index

RegRipper

  • Website: https://github.com/keydet89/RegRipper3.0
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: RegRipper is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Open source tool, written in Perl, for extracting/parsing information (keys, values, data) from the Registry and presenting it for 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: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Reverse.IT

  • Website: https://www.reverse.it/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Reverse.IT is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Alternative domain for the Hybrid-Analysis tool provided by CrowdStrike.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Rizin

  • Website: https://github.com/rizinorg/rizin
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Rizin is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: UNIX-like reverse engineering framework and command-line toolset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

RTIR

  • Website: https://www.bestpractical.com/rtir/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: RTIR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Request Tracker for Incident Response (RTIR) is the premier open source incident handling system targeted for computer security teams. We worked with over a dozen CERT and CSIRT teams around the world to help you handle the ever-increasing volume of incident reports. RTIR builds on all the features of Request Tracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

Sandia Cyber Omni Tracker (SCOT)

  • Website: https://github.com/sandialabs/scot
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Sandia Cyber Omni Tracker (SCOT) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Incident Response collaboration and knowledge capture tool focused on flexibility and ease of use. Our goal is to add value to the incident response process without burdening the user.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

SANS Investigative Forensic Toolkit (SIFT) Workstation

  • Website: http://digital-forensics.sans.org/community/downloads
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: SANS Investigative Forensic Toolkit (SIFT) Workstation is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Demonstrates that advanced incident response capabilities and deep dive digital forensic techniques to intrusions can be accomplished using cutting-edge open-source tools that are freely available and frequently updated.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

Scout2

  • Website: https://nccgroup.github.io/Scout2/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Scout2 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Security tool that lets Amazon Web Services administrators assess their environment's security posture.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Security Onion

  • Website: https://github.com/Security-Onion-Solutions/security-onion
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Security Onion is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: An open-source Linux distribution for threat hunting, security monitoring, and log management. It includes ELK, Snort, Suricata, Zeek, Wazuh, Sguil, and many other 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 Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

Slack DFIR channel

  • Website: https://dfircommunity.slack.com
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Slack DFIR channel is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Slack DFIR Communitiy channel - .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Communities.

Back to Category Index

SOC Multi-tool

  • Website: https://github.com/zdhenard42/SOC-Multitool
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: SOC Multi-tool is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A powerful and user-friendly browser extension that streamlines investigations for 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 Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

SOC/IR hierarchy of needs

  • Website: https://github.com/swannman/ircapabilities
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: SOC/IR hierarchy of needs is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 Category Index

SP800-86, integration forensics techniques into IR

  • Website: https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-86.pdf
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome SOC

What it does: SP800-86, integration forensics techniques into IR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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: Must read > For a CERT/CSIRT.

Back to Category Index

SPECTR3

  • Website: https://github.com/alpine-sec/SPECTR3
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: SPECTR3 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Acquire, triage and investigate remote evidence via portable iSCSI readonly access.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Spyre

  • Website: https://github.com/spyre-project/spyre
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Spyre is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Simple YARA-based IOC scanner 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 Incident Response > IR Tools Collection > Scanner Tools.

Back to Category Index

sqhunter

  • Website: https://github.com/0x4d31/sqhunter
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: sqhunter is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Threat hunter based on osquery and Salt Open (SaltStack) that can issue ad-hoc or distributed queries without the need for osquery's tls plugin. sqhunter allows you to query open network sockets and check them against threat intelligence sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

sysmon-config

  • Website: https://github.com/SwiftOnSecurity/sysmon-config
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: sysmon-config is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Sysmon configuration file template with default high-quality event tracing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring > Configuration.

Back to Category Index

sysmon-modular

  • Website: https://github.com/olafhartong/sysmon-modular
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: sysmon-modular is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A repository of sysmon configuration modules. It also includes a of Sysmon configurations to MITRE ATT&CK techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring > Configuration.

Back to Category Index

TAPIR

  • Website: https://github.com/tap-ir/tapir
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Forensics

What it does: TAPIR is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: TAPIR (Trustable Artifacts Parser for Incident Response) is a multi-user, client/server, incident response 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 Forensics > Tools > Frameworks.

Back to Category Index

The Appliance for Digital Investigation and Analysis (ADIA)

  • Website: https://forensics.cert.org/#ADIA
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: The Appliance for Digital Investigation and Analysis (ADIA) is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: VMware-based appliance used for digital investigation and acquisition and is built entirely from public domain software. Among the tools contained in ADIA are Autopsy, the Sleuth Kit, the Digital Forensics Framework, log2timeline, Xplico, and Wireshark. Most of the system maintenance uses Webmin. It is designed for small-to-medium sized digital investigations and acquisitions. The appliance runs under Linux, Windows, and Mac OS. Both i386 (32-bit) and x86_64 (64-bit) versions are available.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Linux Distributions.

Back to Category Index

The ESF Playground

  • Website: https://themittenmac.com/the-esf-playground/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: The ESF Playground is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A tool to view the events in Apple Endpoint Security Framework (ESF) in real 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 Incident Response > IR Tools Collection > OSX Evidence Collection.

Back to Category Index

The Future of Incident Response

  • Website: https://www.youtube.com/watch?v=bDcx4UNpKNc
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome OSINT, Awesome Threat Detection, Awesome Web Security

What it does: The Future of Incident Response is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. 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 Incident Response > IR Tools Collection > Videos.

Back to Category Index

The Sleuth Kit & Autopsy

  • Website: http://www.sleuthkit.org
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: The Sleuth Kit & Autopsy is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Unix and Windows based tool which helps in forensic analysis of computers. It comes with various tools which helps in digital forensics. These tools help in analyzing disk images, performing in-depth analysis of file systems, and various other 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 Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

TheHive

  • Website: https://thehive-project.org/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome SOC

What it does: TheHive is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Scalable 3-in-1 open source and free solution designed to make life easier for SOCs, CSIRTs, CERTs and any information security practitioner dealing with security incidents that need to be investigated and acted upon swiftly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > IR management consoles.

Back to Category Index

Threat.Zone

  • Website: https://app.threat.zone
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Threat.Zone is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Cloud based threat analysis platform which include sandbox, CDR and interactive analysis for 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 Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

threat_note

  • Website: https://github.com/defpoint/threat_note
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: threat_note is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Web application built by Defense Point Security to allow security researchers the ability to add and retrieve indicators related to their research.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > IR management consoles.

Back to Category Index

Timesketch

  • Website: https://github.com/google/timesketch
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Timesketch is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Open source tool for collaborative forensic timeline 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: Awesome Incident Response > IR Tools Collection > Timeline Tools.

Back to Category Index

traceroute-circl

  • Website: https://github.com/CIRCL/traceroute-circl
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: traceroute-circl is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Extended traceroute to support the activities of CSIRT (or CERT) operators. Usually CSIRT team have to handle incidents based on IP addresses received. Created by Computer Emergency Response Center Luxembourg.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

UAC

  • Website: https://github.com/tclahr/uac
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Forensics, Awesome SOC

What it does: UAC is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: UAC (Unix-like Artifacts Collector) is a Live Response collection script for Incident Response that makes use of native binaries and tools to automate the collection of AIX, Android, ESXi, FreeBSD, Linux, macOS, NetBSD, NetScaler, OpenBSD and Solaris systems artifacts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Valkyrie Comodo

  • Website: https://valkyrie.comodo.com
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Valkyrie Comodo is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Valkyrie uses run-time behavior and hundreds of features from a file to perform 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: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Velociraptor

  • Website: https://github.com/Velocidex/velociraptor
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection, Awesome Forensics

What it does: Velociraptor is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Velociraptor is a tool for collecting host based state information using Velocidex Query Language (VQL) queries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Viper

  • Website: https://github.com/viper-framework/viper
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: Viper is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Binary analysis and management framework enabling easy organization of malware and exploit samples.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Volatility

  • Website: https://www.volatilityfoundation.org/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Cyber Security Tools

What it does: Volatility is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Advanced memory forensics 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 Cybersecurity Blue Team > Incident Response tools.

Back to Category Index

Volatility 3

  • Website: https://github.com/volatilityfoundation/volatility3
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Volatility 3 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: The volatile memory extraction framework (successor of Volatility).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Windows Events Attack Samples

  • Website: https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Windows Events Attack Samples is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: A repo of Windows event samples (EVTX) associated with ATT&CK techniques ().

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Knowledge Bases.

Back to Category Index

Windows Registry Knowledge Base

  • Website: https://github.com/libyal/winreg-kb
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Windows Registry Knowledge Base is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Windows Registry Knowledge Base.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Knowledge Bases.

Back to Category Index

WindowsSCOPE

  • Website: http://www.windowsscope.com/windowsscope-cyber-forensics/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: WindowsSCOPE is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Memory forensics and reverse engineering tool used for analyzing volatile memory offering the capability of analyzing the Windows kernel, drivers, DLLs, and virtual and physical memory.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

X-Ray 2.0

  • Website: https://www.raymond.cc/blog/xray/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: X-Ray 2.0 is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Windows utility (poorly maintained or no longer maintained) to submit virus samples to AV vendors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

X-Ways Forensics

  • Website: http://www.x-ways.net/forensics/
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: X-Ways Forensics is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Forensics tool for Disk cloning and imaging. It can be used to find deleted files and disk 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: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Yomi

  • Website: https://yomi.yoroi.company
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Yomi is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Free MultiSandbox managed and hosted by Yoroi.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Zentral

  • Website: https://github.com/zentralopensource/zentral
  • Model: Open Source
  • Category: Incident Response
  • Source Lists: Awesome Incident Response

What it does: Zentral is used in incident response programs to support containment coordination, evidence collection, and post-incident timeline reconstruction. Source summaries describe it as: Combines osquery's powerful endpoint inventory features with a flexible notification and action framework. This enables one to identify and react to changes on OS X and Linux clients.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

Malware Analysis

This category contains 13 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

/r/csirt_tools

  • Website: https://www.reddit.com/r/csirt_tools/
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: /r/csirt_tools is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Subreddit for CSIRT.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

/r/ReverseEngineering

  • Website: https://www.reddit.com/r/ReverseEngineering
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: /r/ReverseEngineering is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Other.

Back to Category Index

Awesome YARA

  • Website: https://github.com/InQuest/awesome-yara
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Penetration Testing, Awesome Threat Detection, Awesome Forensics

What it does: Awesome YARA is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Security > Other Awesome Lists > Other Security Awesome Lists.

Back to Category Index

CTFs

  • Website: https://github.com/apsdehal/awesome-ctf
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: CTFs is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Online Resources > Other Lists Online.

Back to Category Index

Executable Packing

  • Website: https://github.com/dhondta/awesome-executable-packing
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: Executable Packing is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Related Awesome Lists.

Back to Category Index

File Formats posters

  • Website: https://github.com/corkami/pics
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: File Formats posters is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Nice visualization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

Honeypots

  • Website: https://github.com/paralax/awesome-honeypots
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: Honeypots is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Online Resources > Other Lists Online.

Back to Category Index

Incident-Response

  • Website: https://github.com/meirwah/awesome-incident-response
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis, Awesome Forensics

What it does: Incident-Response is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Infosec

  • Website: https://github.com/onlurking/awesome-infosec
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: Infosec is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Information security resources for pentesting, forensics, 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 Category Index

Kernel Mode

  • Website: http://www.kernelmode.info/forum/
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: Kernel Mode is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: An active 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 > Other.

Back to Category Index

Security

  • Website: https://github.com/sbilly/awesome-security
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Forensics

What it does: Security is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Online Resources > Other Lists Online.

Back to Category Index

The Rootkit Arsenal

  • Website: https://amzn.com/dp/144962636X
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: The Rootkit Arsenal is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Rootkit Arsenal:.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

Windows Registry specification

  • Website: https://github.com/msuhanov/regf/blob/master/Windows%20registry%20file%20format%20specification.md
  • Model: Open Source
  • Category: Malware Analysis
  • Source Lists: Awesome Malware Analysis

What it does: Windows Registry specification is used in malware analysis programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Other.

Back to Category Index

Malware Analysis & Reverse Engineering

This category contains 425 documented tools. It focuses on capabilities used for sample triage, static/dynamic analysis, and malware behavior profiling. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

010 Editor

  • Website: https://www.sweetscape.com/010editor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: 010 Editor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Powerful hex and text 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: Malware Analysis > Static Analysis > Hex Editor.

Back to Category Index

API Monitor

  • Website: http://www.rohitab.com/apimonitor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: API Monitor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Monitors and controls API calls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > APIs / DLLs.

Back to Category Index

APISpy

  • Website: http://www.ragoo.com/APISpy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: APISpy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Captures and analyzes API calls made by 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: Malware Analysis > Dynamic Analysis Tools.

Back to Category Index

BinText

  • Website: https://www.majorgeeks.com/files/details/bintext.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: BinText is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extracts ASCII, Unicode, and Resource strings from 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: Malware Analysis > Static Analysis > Strings.

Back to Category Index

Bless

  • Website: https://github.com/afrantzis/bless
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Bless is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: High-performance, full-featured 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: Malware Analysis > Static Analysis > Hex Editor.

Back to Category Index

CFF Explorer

  • Website: https://ntcore.com/explorer-suite
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: CFF Explorer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Inspect and analyze Portable Executable (PE) 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: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

CFR

  • Website: http://www.benf.org/other/cfr
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools, Awesome Web Security

What it does: CFR is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Another java decompiler 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 > Decompiler.

Back to Category Index

ComputeHash

  • Website: https://www.subisoft.net/ComputeHash.aspx
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ComputeHash is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Calculates MD5, SHA1, SHA256, SHA384, and SHA512 hashes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

Cutter

  • Website: https://cutter.re
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Cutter is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Qt and C++ GUI powered by Radare2.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering.

Back to Category Index

Dependency Walker

  • Website: https://dependencywalker.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Dependency Walker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Builds hierarchical tree diagram of dependent modules.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

DLL Export Viewer

  • Website: https://www.nirsoft.net/utils/dll_export_viewer.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: DLL Export Viewer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Displays exported functions and their addresses for DLL 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: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

dnSpy

  • Website: https://github.com/dnSpy/dnSpy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: dnSpy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: .NET debugger and assembly 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: Reverse Engineering > .NET Decompilers.

Back to Category Index

Exeinfo PE

  • Website: https://exeinfo-pe.en.uptodown.com/windows
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Exeinfo PE is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Analyze Windows PE header information, packer detection, and gives hints on how to unpack.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Identification.

Back to Category Index

FernFlower

  • Website: https://github.com/fesh0r/fernflower
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: FernFlower is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: IntelliJ's Java decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Java Decompilers.

Back to Category Index

file

  • Website: https://linux.die.net/man/1/file
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: file is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Determine file type.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Identification.

Back to Category Index

flare-floss

  • Website: https://github.com/mandiant/flare-floss
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools, Awesome Forensics

What it does: flare-floss is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Static analysis tool to automatically deobfuscate strings from malware binaries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Strings.

Back to Category Index

GET-FileHash

  • Website: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?view=powershell-7.4
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: GET-FileHash is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Computes hash value for a file using a specified hash algorithm (Microsoft PowerShell module).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

Ghidra

  • Website: https://ghidra-sre.org
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools, Awesome Hacking, Awesome CTF

What it does: Ghidra is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A software reverse engineering (SRE) suite of tools developed by NSA's Research Directorate in support of the Cybersecurity mission.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Disassemblers and debuggers.

Back to Category Index

Handle

  • Website: https://learn.microsoft.com/en-us/sysinternals/downloads/handle
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Handle is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Lists open handles for system processes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > APIs / DLLs.

Back to Category Index

HashMyFiles

  • Website: https://www.nirsoft.net/utils/hash_my_files.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: HashMyFiles is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Calculates MD5 and SHA1 hashes of one or more 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: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

Hex Workshop

  • Website: http://www.hexworkshop.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Hex Workshop is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Visualizes data through graphical representations and charts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Hex Editor.

Back to Category Index

hexitor

  • Website: https://github.com/briansteffens/hexitor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: hexitor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: terminal 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: Malware Analysis > Static Analysis > Hex Editor.

Back to Category Index

HxD

  • Website: https://mh-nexus.de/en/hxd
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: HxD is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Fast hex editor with raw disk editing 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: Malware Analysis > Static Analysis > Hex Editor.

Back to Category Index

IDA Pro

  • Website: https://www.hex-rays.com/ida-pro
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: IDA Pro is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Interactive disassembler and debugger.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering.

Back to Category Index

IgorWare Hasher

  • Website: https://www.igorware.com/hasher
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: IgorWare Hasher is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free SHA-1, MD5, and CRC32 hash generator 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: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

ILSpy

  • Website: https://github.com/icsharpcode/ILSpy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools, Awesome Hacking

What it does: ILSpy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: an open-source .NET assembly browser and decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Decompilers.

Back to Category Index

impfuzzy

  • Website: https://github.com/JPCERTCC/impfuzzy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: impfuzzy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Calculates Fuzzy Hash from import API of PE 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: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

JD-GUI

  • Website: http://java-decompiler.github.io
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: JD-GUI is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Decompiler for Java bytecode.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Java Decompilers.

Back to Category Index

JustDecompile

  • Website: https://www.telerik.com/products/decompiler.aspx
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: JustDecompile is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free .NET decompiler from Telerik.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > .NET Decompilers.

Back to Category Index

KapeFiles

  • Website: https://github.com/EricZimmerman/KapeFiles
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: KapeFiles is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool for acquiring and processing forensic artifacts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Identification.

Back to Category Index

Krakatau

  • Website: https://github.com/Storyyeller/krakatau
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Krakatau is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Java decompiler, assembler, and disassembler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Java Decompilers.

Back to Category Index

Lazy Office Analyzer

  • Website: https://github.com/tehsyntx/loffice
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Lazy Office Analyzer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extracts URLs, VB-script, and JavaScript from Office documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Microsoft Office.

Back to Category Index

ListDLLs

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/listdlls
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ListDLLs is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Lists all the DLLs loaded into processes (SysInternals).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > APIs / DLLs.

Back to Category Index

md5sum

  • Website: https://www.man7.org/linux/man-pages/man1/md5sum.1.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: md5sum is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compute and check MD5 message digest.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

OfficeMalScanner

  • Website: https://www.aldeid.com/wiki/OfficeMalScanner/OfficeMalScanner
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: OfficeMalScanner is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Scans MS Office documents for malicious traces.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Microsoft Office.

Back to Category Index

OfficeScan

  • Website: https://support.trendmicro.com/en-us/home/pages/technical-support/office-scan
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: OfficeScan is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Analyzes Microsoft Office documents for malware and other threats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Microsoft Office.

Back to Category Index

ole-tools

  • Website: https://github.com/decalage2/oletools
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ole-tools is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extracts VBA macros from Office files and detects obfuscation techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Microsoft Office.

Back to Category Index

PDF-XChange

  • Website: https://www.tracker-software.com/product/pdf-xchange-editor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PDF-XChange is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: In-depth analysis and editing of PDF documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > PDF.

Back to Category Index

pdfunite

  • Website: https://manpages.ubuntu.com/manpages/jammy/man1/pdfunite.1.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: pdfunite is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Merges multiple PDF files into a single file.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > PDF.

Back to Category Index

PE Explorer

  • Website: https://pe-explorer.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PE Explorer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Inspects Windows applications and libraries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

pe-bear

  • Website: https://github.com/hasherezade/pe-bear
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: pe-bear is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Multiplatform reversing tool for PE 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: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

pehash

  • Website: https://github.com/knowmalware/pehash
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: pehash is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compilation of peHash implementations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

PEiD

  • Website: https://www.aldeid.com/wiki/PEiD
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PEiD is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Detects common packers, cryptors, and compilers for PE 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: Malware Analysis > Static Analysis > File Identification.

Back to Category Index

PEPack

  • Website: https://pev.sourceforge.io/doc/manual/en_us/ch06s05.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PEPack is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python library for inspecting and manipulating PE 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: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

PeStudio

  • Website: https://pestudio.en.lo4d.com/windows
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PeStudio is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Examines executable files in depth.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

PEView

  • Website: https://www.aldeid.com/wiki/PEView
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: PEView is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Lightweight utility for inspecting PE 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: Malware Analysis > Static Analysis > Inspector.

Back to Category Index

ProcDot

  • Website: https://www.cert.at/en/downloads/software/software-procdot
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ProcDot is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Visualizes process and thread 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: Malware Analysis > Dynamic Analysis Tools.

Back to Category Index

Procyon

  • Website: https://bitbucket.org/mstrobel/procyon
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Procyon is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Java decompiler for modern Java 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: Reverse Engineering > Java Decompilers.

Back to Category Index

Radare2

  • Website: https://rada.re/n
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Radare2 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open-source reverse engineering 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: Reverse Engineering.

Back to Category Index

Regshot

  • Website: http://www.nikopol.org/regshot
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Regshot is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Takes snapshots of the Registry and compares them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Dynamic Analysis Tools.

Back to Category Index

Resource Hacker

  • Website: https://www.angusj.com/resourcehacker
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Resource Hacker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Resource editor for Windows 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: Malware Analysis > Static Analysis > Resource Editor.

Back to Category Index

Resource Tuner

  • Website: https://www.restuner.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: Resource Tuner is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Allows you to edit resources within executables and DLLs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Resource Editor.

Back to Category Index

sha256sum

  • Website: https://www.man7.org/linux/man-pages/man1/sha256sum.1.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: sha256sum is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compute and check SHA256 message digest.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

sha512sum

  • Website: https://www.man7.org/linux/man-pages/man1/sha512sum.1.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: sha512sum is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compute and check SHA512 message digest.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

SpiderMonkey

  • Website: https://blog.didierstevens.com/programs/spidermonkey
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: SpiderMonkey is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Modified Mozilla JavaScript implementation for malware 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: Malware Analysis > Static Analysis > PDF.

Back to Category Index

ssdeep

  • Website: https://ssdeep-project.github.io/ssdeep/index.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ssdeep is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Computes Context Triggered Piecewise Hashes (CTPH) for fuzzy matching.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Signature.

Back to Category Index

strings

  • Website: https://www.man7.org/linux/man-pages/man1/strings.1.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: strings is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Print sequences of printable characters in 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: Malware Analysis > Static Analysis > Strings.

Back to Category Index

StringsDump

  • Website: https://github.com/mwrlabs/stringsdump
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: StringsDump is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extracts and identifies text from binary 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: Malware Analysis > Static Analysis > Strings.

Back to Category Index

TrID

  • Website: https://trid.en.softonic.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: TrID is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Use pattern database to determine file types, gives a likelihood of detected type.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > File Identification.

Back to Category Index

ViperMonkey

  • Website: https://github.com/decalage2/ViperMonkey
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: ViperMonkey is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: VBA parser and emulation engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Microsoft Office.

Back to Category Index

VMProtect

  • Website: https://vmpsoft.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: VMProtect is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Anti-debugging and anti-VM software protection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > Anti-Analysis Detector.

Back to Category Index

WinAPIOverride

  • Website: http://jacquelin.potier.free.fr/winapioverride32/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: WinAPIOverride is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Monitors, intercepts, and logs API calls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > APIs / DLLs.

Back to Category Index

x64dbg

  • Website: https://x64dbg.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cyber Security Tools

What it does: x64dbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open-source debugger 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: Reverse Engineering.

Back to Category Index

/r/Malware

  • Website: https://www.reddit.com/r/Malware
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: /r/Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The malware subreddit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

AbuseIPDB

  • Website: https://www.abuseipdb.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome OSINT

What it does: AbuseIPDB is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Repository of abuses reported by system administrators for IPs, Domains, and subnets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

ACSTIS

  • Website: https://github.com/tijme/angularjs-csti-scanner
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: ACSTIS is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: ACSTIS helps you to scan certain web applications for AngularJS Client-Side Template Injection (sometimes referred to as CSTI, sandbox escape or sandbox bypass). It supports scanning a single request but also crawling the entire web application for the AngularJS CSTI vulnerability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

al-khaser

  • Website: https://github.com/LordNoteworthy/al-khaser
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: al-khaser is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A PoC malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Miscellaneous.

Back to Category Index

Aleph

  • Website: https://github.com/merces/aleph
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Aleph is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open Source Malware 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: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

AnalyzePDF

  • Website: https://github.com/hiddenillusion/AnalyzePDF
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: AnalyzePDF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

AnalyzePE

  • Website: https://github.com/hiddenillusion/AnalyzePE
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: AnalyzePE is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Wrapper for a.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Androguard

  • Website: https://github.com/androguard/androguard
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Honeypots, Awesome Cyber Security Tools, Awesome CTF

What it does: Androguard is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reverse engineering, Malware and goodware analysis of Android applications 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: Penetration Testing > Mobile Penetration Testing.

Back to Category Index

androguard

  • Website: https://code.google.com/p/androguard/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: androguard is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reverse engineering, malware and goodware analysis of Android 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: Reverse Engineering > Tools > Other.

Back to Category Index

AndroTotal

  • Website: https://andrototal.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: AndroTotal is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free online analysis of APKs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

angr

  • Website: https://github.com/angr/angr
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: angr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: platform-agnostic binary analysis 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

angr

  • Website: https://angr.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: angr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Platform-agnostic binary analysis 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

anlyz.io

  • Website: https://sandbox.anlyz.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: anlyz.io is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Online sandbox.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Anonymouse.org

  • Website: http://anonymouse.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Anonymouse.org is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A free, web based anonymizer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Anonymizers.

Back to Category Index

antinet

  • Website: https://github.com/0xd4d/antinet
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: antinet is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: .NET anti-managed debugger and anti-profiler 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: Reverse Engineering > Tools > Other.

Back to Category Index

any.run

  • Website: https://app.any.run/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: any.run is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Interactive online malware analysis service for dynamic and static research of most types of threats using any environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Assemblyline

  • Website: https://cybercentrecanada.github.io/assemblyline4_docs/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Assemblyline is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A scalable file triage and malware analysis system integrating the cyber security community's best 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 Malware Analysis > Detection and Classification.

Back to Category Index

Awesome Malware

  • Website: https://github.com/fabacab/awesome-malware
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Awesome Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Curated collection of awesome malware, botnets, and other post-exploitation 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 Category Index

Awesome Malware Analysis

  • Website: https://github.com/rshipp/awesome-malware-analysis
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Security, Awesome Forensics

What it does: Awesome Malware Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Security > Other Awesome Lists > Other Security Awesome Lists.

Back to Category Index

badips.com

  • Website: https://www.badips.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: badips.com is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Community based IP blacklist service.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Balbuzard

  • Website: https://bitbucket.org/decalage/balbuzard/wiki/Home
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Balbuzard is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

bamfdetect

  • Website: https://github.com/bwall/bamfdetect
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: bamfdetect is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Identifies and extracts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

BAP

  • Website: https://github.com/BinaryAnalysisPlatform/bap
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: BAP is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Multiplatform and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

BARF

  • Website: https://github.com/programa-stic/barf-project
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: BARF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Binary Analysis and Reverse engineering 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Binary ninja

  • Website: https://binary.ninja/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools, Awesome CTF

What it does: Binary ninja is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A reversing engineering 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: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

BinaryAlert

  • Website: https://github.com/airbnb/binaryalert
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Threat Detection

What it does: BinaryAlert is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Serverless, real-time & retroactive malware detection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

binarypig

  • Website: https://github.com/endgameinc/binarypig
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Security

What it does: binarypig is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Scalable Binary Data Extraction in Hadoop. Malware Processing and Analytics over Pig, Exploration through Django, Twitter Bootstrap, and Elasticsearch.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Big Data.

Back to Category Index

binnavi

  • Website: https://github.com/google/binnavi
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: binnavi is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Binary analysis IDE for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

BinText

  • Website: https://web.archive.org/web/http://www.mcafee.com/kr/downloads/free-tools/bintext.aspx
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: BinText is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A small, very fast and powerful text extractor that will be of particular interest to programmers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

Binwalk

  • Website: https://github.com/devttys0/binwalk
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome CTF

What it does: Binwalk is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Fast, easy to use tool for analyzing, reverse engineering, and extracting firmware images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Binwalk

  • Website: https://github.com/ReFirmLabs/binwalk
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Binwalk is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Detects signatures, unpacks archives, visualizes entropy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

BlackLight

  • Website: https://www.blackbagtech.com/blacklight.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: BlackLight is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Windows/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 Malware Analysis > Memory Forensics.

Back to Category Index

BlockBlock

  • Website: https://objective-see.com/products/blockblock.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: BlockBlock is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Monitors common persistence locations and alerts whenever a persistent component is added, which helps to detect and prevent malware installation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > macOS-based defenses.

Back to Category Index

BluePill

  • Website: https://github.com/season-lab/bluepill
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: BluePill is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Framework for executing and debugging evasive malware and protected executables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

BoomBox

  • Website: https://github.com/nbeede/BoomBox
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: BoomBox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automatic deployment of Cuckoo.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

boomerang

  • Website: https://github.com/EmersonElectricCo/boomerang
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: boomerang is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool designed.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

box-js

  • Website: https://github.com/CapacitorSet/box-js
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: box-js is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool for studying JavaScript.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

boxxy

  • Website: https://github.com/kpcyrd/boxxy-rs
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: boxxy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Linkable sandbox 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Brida

  • Website: https://github.com/federicodotta/Brida
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Brida is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Burp Suite extension that, working as a bridge between Burp and Frida, lets you use and manipulate applications' own methods while tampering the traffic exchanged between the applications and their back-end services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Browserling

  • Website: https://www.browserling.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome OSINT

What it does: Browserling is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Browserling is an online sandbox that lets users safely test potentially malicious links across browsers and operating systems in real 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

bulk_extractor

  • Website: https://github.com/simsong/bulk_extractor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response, Awesome Cyber Security Tools, Awesome Forensics

What it does: bulk_extractor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Computer forensics tool that scans a disk image, a file, or a directory of files and extracts useful information without parsing the file system or file system structures. Because of ignoring the file system structure, the program distinguishes itself in terms of speed and thoroughness.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Evidence Collection.

Back to Category Index

Bytecode Viewer

  • Website: https://github.com/Konloch/bytecode-viewer
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Bytecode Viewer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Combines.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

capa

  • Website: https://github.com/fireeye/capa
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Threat Detection

What it does: capa is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An open-source tool to identify capabilities in executable 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 Malware Analysis > Detection and Classification.

Back to Category Index

Capstone

  • Website: https://github.com/aquynh/capstone
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking

What it does: Capstone is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Capstone

  • Website: http://www.capstone-engine.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Capstone is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Lightweight multi-platform, multi-architecture disassembly 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Charles Proxy

  • Website: https://charlesproxy.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Charles Proxy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A cross-platform GUI web debugging proxy to view intercepted HTTP and HTTPS/SSL live traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

chkrootkit

  • Website: http://www.chkrootkit.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: chkrootkit is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Local Linux rootkit detection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Clean MX

  • Website: http://support.clean-mx.com/clean-mx/viruses.php
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Clean MX is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Realtime.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

CLEANLY ESCAPING THE CHROME SANDBOX

  • Website: https://theori.io/research/escaping-chrome-sandbox
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Web Security

What it does: CLEANLY ESCAPING THE CHROME SANDBOX is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

codebro

  • Website: https://github.com/hugsy/codebro
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: codebro is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Web based code browser using.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

CodeEngn

  • Website: http://codeengn.com/challenges/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: CodeEngn is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: (Korean).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reverse Engineering.

Back to Category Index

Contagio

  • Website: http://contagiodump.blogspot.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Contagio is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A collection of recent.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Crackmes

  • Website: https://crackmes.one/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome CTF

What it does: Crackmes is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reverse Engineering 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: Resources > Wargames.

Back to Category Index

Crackmes.de

  • Website: http://crackmes.de/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Crackmes.de is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The world first and largest community website for crackmes and reversemes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reverse Engineering.

Back to Category Index

CRITs

  • Website: https://crits.github.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: CRITs is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Web-based tool which combines an analytic engine with a cyber threat 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 Incident Response > IR Tools Collection > Other Tools.

Back to Category Index

Cryptam

  • Website: http://www.cryptam.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Cryptam is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Analyze suspicious office documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

CryptoKnight

  • Website: https://github.com/AbertayMachineLearningGroup/CryptoKnight
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: CryptoKnight is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automated cryptographic algorithm reverse engineering and classification 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 Malware Analysis > Miscellaneous.

Back to Category Index

Cuckoo Sandbox

  • Website: https://cuckoosandbox.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Cuckoo Sandbox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Leading open source automated malware analysis 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 Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

cuckoo-modified

  • Website: https://github.com/brad-accuvant/cuckoo-modified
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: cuckoo-modified is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Modified.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

cuckoo-modified-api

  • Website: https://github.com/keithjjones/cuckoo-modified-api
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: cuckoo-modified-api is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python library to control a cuckoo-modified sandbox.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Cutter

  • Website: https://github.com/radareorg/cutter
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking

What it does: Cutter is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a decompiler based on radare2.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

CWSandbox / GFI Sandbox

  • Website: https://www.gfi.com/products-and-solutions/all-products
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Honeypots

What it does: CWSandbox / GFI Sandbox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Contents > Honeypots.

Back to Category Index

DAMM

  • Website: https://github.com/504ensicsLabs/DAMM
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: DAMM is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Differential Analysis of.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Memory Forensics.

Back to Category Index

DarunGrim

  • Website: https://github.com/ohjeongwook/DarunGrim
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: DarunGrim is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: executable differ.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

DBeaver

  • Website: https://github.com/dbeaver/dbeaver
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: DBeaver is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a DB 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: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

DC3-MWCP

  • Website: https://github.com/Defense-Cyber-Crime-Center/DC3-MWCP
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: DC3-MWCP is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Miscellaneous.

Back to Category Index

de4dot

  • Website: https://github.com/0xd4d/de4dot
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking

What it does: de4dot is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: .NET deobfuscator and unpacker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Deobfuscators.

Back to Category Index

DECAF (Dynamic Executable Code Analysis Framework)

  • Website: https://github.com/sycurelab/DECAF
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: DECAF (Dynamic Executable Code Analysis Framework) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

DeepViz

  • Website: https://www.deepviz.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: DeepViz is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Multi-format file analyzer with.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

DemoHunter

  • Website: https://github.com/RevengeComing/DemonHunter
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: DemoHunter is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Low interaction Distributed Honeypots.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Honeypots.

Back to Category Index

Dependencies

  • Website: https://github.com/lucasg/Dependencies
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Dependencies is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a FOSS replacement to Dependency Walker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

Desenmascara.me

  • Website: http://desenmascara.me
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Desenmascara.me is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: One click tool to retrieve 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 Malware Analysis > Domain Analysis.

Back to Category Index

Detect It Easy(DiE)

  • Website: https://github.com/horsicq/Detect-It-Easy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: Detect It Easy(DiE) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Program for determining types of files for Windows, Linux and 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Detecting Malware Beacons Using Splunk

  • Website: https://pleasefeedthegeek.wordpress.com/2012/12/20/detecting-malware-beacons-using-splunk/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: Detecting Malware Beacons Using Splunk is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Resources.

Back to Category Index

Detox

  • Website: http://relentless-coding.org/projects/jsdetox/install
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome CTF

What it does: Detox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A Javascript malware 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: Solve > Reversing.

Back to Category Index

detux

  • Website: https://github.com/detuxsandbox/detux/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: detux is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A sandbox developed to do.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

dex2jar

  • Website: https://github.com/pxb1988/dex2jar
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: dex2jar is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Tools to work with Android .dex and Java .class 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: Reverse Engineering > Tools > Other.

Back to Category Index

Dig

  • Website: https://networking.ringofsaturn.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Dig is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free online dig and other.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

diStorm

  • Website: http://www.ragestorm.net/distorm/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: diStorm is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Disassembler for analyzing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

dnSpy

  • Website: https://github.com/0xd4d/dnSpy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Hacking

What it does: dnSpy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: .NET assembly editor, decompiler, and debugger.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

dnstwist

  • Website: https://github.com/elceef/dnstwist
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: dnstwist is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Domain name permutation engine for detecting typo squatting, phishing and corporate espionage.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

DOM based Angular sandbox escapes

  • Website: http://blog.portswigger.net/2017/05/dom-based-angularjs-sandbox-escapes.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Web Security

What it does: DOM based Angular sandbox escapes is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > AngularJS.

Back to Category Index

DRAKVUF

  • Website: https://github.com/tklengyel/drakvuf
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: DRAKVUF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Dynamic malware 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: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

drltrace

  • Website: https://github.com/mxmssh/drltrace
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: drltrace is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: shared library calls tracing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

dynStruct

  • Website: https://github.com/ampotos/dynStruct
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: dynStruct is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: structures recovery via dynamic instrumentation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

Ember

  • Website: https://github.com/endgameinc/ember
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Threat Detection

What it does: Ember is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: () - The EMBER dataset is a collection of features from PE files that serve as a benchmark dataset for 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 Threat Detection and Hunting > Dataset.

Back to Category Index

Evan's Debugger

  • Website: http://www.codef00.com/projects#debugger
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Evan's Debugger is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: OllyDbg-like debugger for GNU/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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Evan's Debugger (EDB)

  • Website: http://codef00.com/projects#debugger
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Evan's Debugger (EDB) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

evolve

  • Website: https://github.com/JamesHabben/evolve
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: evolve is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Web interface for the Volatility Memory Forensics 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 Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

EVTXtract

  • Website: https://github.com/williballenthin/EVTXtract
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: EVTXtract is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Carve 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 Malware Analysis > File Carving.

Back to Category Index

ex_pe_xor

  • Website: http://hooked-on-mnemonics.blogspot.com/2014/04/expexorpy.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ex_pe_xor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Deobfuscation.

Back to Category Index

Exeinfo PE

  • Website: http://exeinfo.pe.hu/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Exeinfo PE is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Packer, compressor detector, unpack.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

ExifTool

  • Website: https://sno.phy.queensu.ca/~phil/exiftool/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ExifTool is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Read, write and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Exploit Database

  • Website: https://www.exploit-db.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Hacking

What it does: Exploit Database is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Non-profit project hosting exploits for software vulnerabilities, provided as a public service by Offensive 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 Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

FAME

  • Website: https://certsocietegenerale.github.io/fame/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: FAME is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A malware 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: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

File Scanning Framework

  • Website: https://github.com/EmersonElectricCo/fsf
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: File Scanning Framework is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Detection and Classification.

Back to Category Index

filescan.io

  • Website: https://www.filescan.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: filescan.io is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Static malware analysis, VBA/Powershell/VBS/JS Emulation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

FindAES

  • Website: https://sourceforge.net/projects/findaes/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: FindAES is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Find AES.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Memory Forensics.

Back to Category Index

Firebug

  • Website: https://getfirebug.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Firebug is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Firefox extension for web 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 Malware Analysis > Browser Malware.

Back to Category Index

firmware.re

  • Website: http://firmware.re/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: firmware.re is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Unpacks, scans and analyzes almost any.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

FLARE VM

  • Website: https://github.com/fireeye/flare-vm
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response, Awesome CTF

What it does: FLARE VM is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A fully customizable, Windows-based security distribution for malware analysis, incident response, 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: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

FLOSS

  • Website: https://github.com/fireeye/flare-floss
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: FLOSS is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The FireEye Labs Obfuscated.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

fn2yara

  • Website: https://github.com/cmu-sei/pharos
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: fn2yara is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The Pharos binary analysis 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Foremost

  • Website: http://foremost.sourceforge.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: Foremost is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extract particular kind of files using headers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > File Carving.

Back to Category Index

FPort

  • Website: https://www.mcafee.com/us/downloads/free-tools/fport.aspx
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: FPort is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reports.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Fridax

  • Website: https://github.com/NorthwaveNL/fridax
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Fridax is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Read variables and intercept/hook functions in Xamarin/Mono JIT and AOT compiled iOS/Android 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

GDB

  • Website: http://www.sourceware.org/gdb/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: GDB is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The GNU debugger.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

GEF

  • Website: https://github.com/hugsy/gef
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: GEF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: GDB Enhanced Features, for exploiters.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Generic File Parser

  • Website: https://github.com/uppusaikiran/generic-parser
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Generic File Parser is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A Single Library Parser to extract meta information,static analysis and detect macros within the 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 Malware Analysis > Detection and Classification.

Back to Category Index

Ghidra

  • Website: https://github.com/NationalSecurityAgency/ghidra
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: Ghidra is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A software reverse engineering (SRE) framework created and maintained by the National Security Agency Research Directorate.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Ghidra

  • Website: https://www.ghidra-sre.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Ghidra is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Suite of free software reverse engineering tools developed by NSA's Research Directorate originally exposed in WikiLeaks's "Vault 7" publication and now maintained as open source 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

HaboMalHunter

  • Website: https://github.com/Tencent/HaboMalHunter
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: HaboMalHunter is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An Automated Malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

hachoir3

  • Website: https://github.com/vstinner/hachoir3
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: hachoir3 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Hachoir is a Python library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > File Carving.

Back to Category Index

hackers-grep

  • Website: https://github.com/codypierce/hackers-grep
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: hackers-grep is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A utility to.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Hacking the Xbox by Andrew Huang, 2003

  • Website: https://nostarch.com/xbox.htm
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Hacking the Xbox by Andrew Huang, 2003 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Reverse Engineering > Reverse Engineering Books.

Back to Category Index

HashCheck

  • Website: https://github.com/gurnec/HashCheck
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: HashCheck is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Windows shell extension.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

hashdeep

  • Website: https://github.com/jessek/hashdeep
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: hashdeep is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compute digest hashes with.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Hex-Rays

  • Website: https://www.hex-rays.com/products/decompiler/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Hex-Rays is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Decompilers.

Back to Category Index

Honeytrap

  • Website: https://github.com/honeytrap/honeytrap
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Honeytrap is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Advanced Honeypot framework written in Go that can be connected with other honeypot 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 Malware Analysis > Malware Collection > Honeypots.

Back to Category Index

Hopper

  • Website: https://www.hopperapp.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools, Awesome Hacking

What it does: Hopper is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A OS X and Linux Disassembler/Decompiler for 32/64-bit Windows/Mac/Linux/iOS executables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Hopper

  • Website: http://www.hopperapp.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome CTF

What it does: Hopper is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reverse engineering tool (disassembler) for OSX and 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: Solve > Reversing.

Back to Category Index

Hudson Rock

  • Website: https://www.hudsonrock.com/threat-intelligence-cybercrime-tools
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome OSINT

What it does: Hudson Rock is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: is a free cybercrime intelligence toolkit to check exposure in Infostealer malware infection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

HxD

  • Website: http://mh-nexus.de/en/hxd/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: HxD is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A hex editor which, additionally to raw disk editing and modifying of main memory (RAM), handles files of any size.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Hex editors.

Back to Category Index

Hybrid Analysis

  • Website: https://www.hybrid-analysis.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response, Awesome Honeypots, Awesome OSINT, Awesome Cyber Security Tools

What it does: Hybrid Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free malware analysis service powered by Payload Security that detects and analyzes unknown threats using a unique Hybrid Analysis technology.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Iaitō

  • Website: https://github.com/hteso/iaito
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Web Security

What it does: Iaitō is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Qt and C++ GUI for radare2 reverse engineering framework 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 > Disassembler.

Back to Category Index

IDA Pro

  • Website: https://www.hex-rays.com/products/ida/index.shtml
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: IDA Pro is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

IDR

  • Website: https://github.com/crypto2011/IDR
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: IDR is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Interactive Delphi Reconstructor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

ILSpy

  • Website: http://ilspy.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ILSpy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: ILSpy is the open-source .NET assembly browser and decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Immunity Debugger

  • Website: http://debugger.immunityinc.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Immunity Debugger is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Debugger for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Immunity Debugger

  • Website: https://immunityinc.com/products/debugger/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Immunity Debugger is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Powerful way to write exploits and analyze malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Infosec - CERT-PA

  • Website: https://infosec.cert-pa.it/analyze/submission.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Infosec - CERT-PA is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Malware samples collection and 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: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

InQuest Deep File Inspection

  • Website: https://labs.inquest.net/dfi
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: InQuest Deep File Inspection is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Upload common malware lures for Deep File Inspection and heuristical 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: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

InQuest Labs

  • Website: https://labs.inquest.net
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: InQuest Labs is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Evergrowing searchable corpus of malicious Microsoft documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Interactive Disassembler (IDA Pro)

  • Website: https://www.hex-rays.com/products/ida/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: Interactive Disassembler (IDA Pro) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Proprietary multi-processor disassembler and debugger for Windows, GNU/Linux, or macOS; also has a free version, .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Intezer

  • Website: https://analyze.intezer.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: Intezer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Intezer Analyze dives into Windows binaries to detect micro-code similarities to known threats, in order to provide accurate yet easy-to-understand results.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

inVtero.net

  • Website: https://github.com/ShaneK2/inVtero.net
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response, Awesome Forensics

What it does: inVtero.net is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Advanced memory analysis for Windows x64 with nested hypervisor support.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

IPinfo

  • Website: https://github.com/hiddenillusion/IPinfo
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: IPinfo is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Gather 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: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

IRMA

  • Website: http://irma.quarkslab.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: IRMA is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An asynchronous and customizable.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

JA3: SSL/TLS Client Fingerprinting for Malware Detection

  • Website: https://engineering.salesforce.com/open-sourcing-ja3-92c9e53c3c41
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: JA3: SSL/TLS Client Fingerprinting for Malware Detection is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Resources > Fingerprinting.

Back to Category Index

JAD

  • Website: http://varaneckas.com/jad/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: JAD is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: JAD Java Decompiler (closed-source, unmaintained).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Decompilers.

Back to Category Index

Java Decompiler

  • Website: http://jd.benow.ca/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Java Decompiler is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Decompile and inspect Java apps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

Java IDX Parser

  • Website: https://github.com/Rurik/Java_IDX_Parser/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Java IDX Parser is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Parses Java.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

Javascript Mallware Collection

  • Website: https://github.com/HynekPetrak/javascript-malware-collection
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Javascript Mallware Collection is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of almost 40.000 javascript malware samples.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

JD-GUI

  • Website: https://github.com/java-decompiler/jd-gui
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: JD-GUI is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Decompilers.

Back to Category Index

Joe Sandbox

  • Website: https://www.joesecurity.org
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Joe Sandbox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Deep malware analysis with Joe Sandbox.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Jotti

  • Website: https://virusscan.jotti.org/en
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Jotti is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free online multi-AV scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

JS Beautifier

  • Website: http://jsbeautifier.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: JS Beautifier is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: JavaScript unpacking and deobfuscation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

JS Beautifier

  • Website: https://github.com/beautify-web/js-beautify
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: JS Beautifier is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Deobfuscators.

Back to Category Index

JS Nice

  • Website: http://jsnice.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: JS Nice is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a web service guessing JS variables names and types based on the model derived from open source.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Deobfuscators.

Back to Category Index

JSDetox

  • Website: http://www.relentless-coding.com/projects/jsdetox/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: JSDetox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: JavaScript.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

jsunpack-n

  • Website: https://github.com/urule99/jsunpack-n
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: jsunpack-n is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Browser Malware.

Back to Category Index

Kaitai Struct

  • Website: https://github.com/kaitai-io/kaitai_struct
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Kaitai Struct is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a DSL for creating parsers in a variety of programming languages. The Web IDE is particularly useful for reverse-engineering.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

Krakatau

  • Website: https://github.com/Storyyeller/Krakatau
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking, Awesome CTF

What it does: Krakatau is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: the best decompiler I have used. Is able to decompile apps written in Scala and Kotlin into Java code. JD-GUI and Luyten have failed to do it fully.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

Learning Malware Analysis

  • Website: https://www.packtpub.com/networking-and-servers/learning-malware-analysis
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Learning Malware Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Learning Malware Analysis: Explore the concepts, tools, and techniques to analuze and investigate Windows malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

Lena151: Reversing With Lena

  • Website: https://archive.org/details/lena151
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Lena151: Reversing With Lena is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tutorials.

Back to Category Index

libemu

  • Website: http://libemu.carnivore.it/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: libemu is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Library and tools for x86 shellcode.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

LIEF

  • Website: https://lief.quarkslab.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: LIEF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: LIEF provides a cross-platform library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Limon

  • Website: https://github.com/monnappa22/Limon
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Limon is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Sandbox for Analyzing Linux Malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

ltrace

  • Website: http://ltrace.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ltrace is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Dynamic analysis for Linux executables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Luyten

  • Website: https://github.com/deathmarine/Luyten
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Luyten is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: one of the best, though a bit slow, hangs on some binaries and not very well maintained.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Decompilers.

Back to Category Index

mac-a-mal

  • Website: https://github.com/phdphuc/mac-a-mal
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: mac-a-mal is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An automated 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Machinae

  • Website: https://github.com/hurricanelabs/machinae
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Machinae is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: OSINT tool for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Machine Learning for Encrypted Malware Traffic Classification

  • Website: https://dl.acm.org/doi/pdf/10.1145/3097983.3098163
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: Machine Learning for Encrypted Malware Traffic Classification is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Resources > Research Papers.

Back to Category Index

mailchecker

  • Website: https://github.com/FGRibreau/mailchecker
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: mailchecker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Cross-language.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Malfunction

  • Website: https://github.com/Dynetics/Malfunction
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malfunction is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Catalog and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Malheur

  • Website: https://github.com/rieck/malheur
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malheur is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automatic sandboxed 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: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

malice.io

  • Website: https://github.com/maliceio/malice
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: malice.io is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Massively scalable malware analysis 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 Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Malicious Software

  • Website: https://zeltser.com/malicious-software/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malicious Software is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

malpdfobj

  • Website: https://github.com/9b/malpdfobj
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: malpdfobj is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Deconstruct malicious PDFs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

Malpedia

  • Website: https://malpedia.caad.fkie.fraunhofer.de/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malpedia is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A resource providing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Malshare

  • Website: https://malshare.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malshare is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Large repository of malware actively.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

MalSploitBase

  • Website: https://github.com/misterch0c/malSploitBase
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: MalSploitBase is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A 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 Malware Analysis > Miscellaneous.

Back to Category Index

malsub

  • Website: https://github.com/diogo-fernan/malsub
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: malsub is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A Python RESTful API framework for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

MaltegoVT

  • Website: https://github.com/michael-yip/MaltegoVT
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: MaltegoVT is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Maltego transform.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

  • Website: https://cse.google.com/cse/home?cx=011750002002865445766%3Apc60zx1rliu
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware Analysis Search is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Other.

Back to Category Index

Malware config

  • Website: https://malwareconfig.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware config is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extract, decode and display online.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Malware Museum

  • Website: https://archive.org/details/malwaremuseum
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware Museum is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Miscellaneous.

Back to Category Index

Malware Organiser

  • Website: https://github.com/uppusaikiran/malware-organiser
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware Organiser is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A simple tool to organise large malicious/benign files into a organised Structure.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Miscellaneous.

Back to Category Index

Malware Persistence

  • Website: https://github.com/Karneades/malware-persistence
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Threat Detection

What it does: Malware Persistence is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of various information focused on malware persistence: detection (techniques), response, pitfalls and the log collection (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 Threat Detection and Hunting > Resources.

Back to Category Index

Malware Samples and Traffic

  • Website: http://malware-traffic-analysis.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware Samples and Traffic is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: This.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

  • Website: https://addons.mozilla.org/fr/firefox/addon/malware-search-plusplusplus/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malware Search+++ is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Firefox extension allows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

malware-jail

  • Website: https://github.com/HynekPetrak/malware-jail
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Web Security

What it does: malware-jail is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Sandbox for semi-automatic Javascript malware analysis, deobfuscation and payload extraction 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 > Detecting.

Back to Category Index

MalwareAnalyser.io

  • Website: https://malwareanalyser.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: MalwareAnalyser.io is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Online malware anomaly-based static analyser with heuristic detection engine powered by data mining and machine learning.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

MalwareBazaar

  • Website: https://bazaar.abuse.ch/browse/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome OSINT

What it does: MalwareBazaar is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Search and download confirmed malware samples by hash, family, tag, and other criteria.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Malwarehouse

  • Website: https://github.com/sroberts/malwarehouse
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Malwarehouse is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Store, tag, and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

Malwr

  • Website: https://malwr.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Malwr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free malware analysis service and 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: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Malzilla

  • Website: http://malzilla.sourceforge.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking, Awesome CTF

What it does: Malzilla is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Analyze malicious web pages.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

Manalyze

  • Website: https://github.com/JusticeRage/Manalyze
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Manalyze is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Static analyzer for PE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Mastering Malware Analysis

  • Website: https://www.packtpub.com/networking-and-servers/mastering-malware-analysis
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Mastering Malware Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Mastering Malware Analysis: The complete malware analyst's guide to combating malicious software, APT, cybercime, and IoT 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: Resources > Books.

Back to Category Index

Mastering Reverse Engineering

  • Website: https://www.packtpub.com/networking-and-servers/mastering-reverse-engineering
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Mastering Reverse Engineering is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Mastering Reverse Engineering: Re-engineer your ethical 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 > Books.

Back to Category Index

MASTIFF

  • Website: https://github.com/KoreLogicSecurity/mastiff
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: MASTIFF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Static analysis framework that automates the process of extracting key characteristics from a number of different file formats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Medusa

  • Website: https://github.com/wisk/medusa
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Medusa is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open source, cross-platform interactive disassembler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

MHN

  • Website: https://github.com/pwnlandia/mhn
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: MHN is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: MHN is a centralized server for management and data collection of honeypots. MHN allows you to deploy sensors quickly and to collect data immediately, viewable from a neat web interface.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Honeypots.

Back to Category Index

mitmproxy

  • Website: https://github.com/mitmproxy/mitmproxy
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking, Awesome Web Security

What it does: mitmproxy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers 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: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

Mnemosyne

  • Website: https://github.com/johnnykv/mnemosyne
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Mnemosyne is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A normalizer for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Honeypots.

Back to Category Index

Multi rbl

  • Website: http://multirbl.valli.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Multi rbl is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Multiple DNS blacklist and forward.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

MultiScanner

  • Website: https://github.com/mitre/multiscanner
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: MultiScanner is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: File analysis framework written in Python that assists in evaluating a set of files by automatically running a suite of tools against them and aggregating the output.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

Muninn

  • Website: https://github.com/ytisf/muninn
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Muninn is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A script to automate portions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Memory Forensics.

Back to Category Index

mwcollectd

  • Website: https://www.openhub.net/p/mwcollectd
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Honeypots

What it does: mwcollectd is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Versatile malware collection daemon, uniting the best features of nepenthes and honeytrap.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Nauz File Detector(NFD)

  • Website: https://github.com/horsicq/Nauz-File-Detector
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Nauz File Detector(NFD) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Linker/Compiler/Tool detector for Windows, Linux and 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 Malware Analysis > Detection and Classification.

Back to Category Index

NetworkTotal

  • Website: https://www.networktotal.com/index.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: NetworkTotal is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A service that analyzes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

NoMoreXOR

  • Website: https://github.com/hiddenillusion/NoMoreXOR
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: NoMoreXOR is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Guess a 256 byte.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

Noriben

  • Website: https://github.com/Rurik/Noriben
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Noriben is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Uses Sysinternals Procmon to.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

NormShield Services

  • Website: https://services.normshield.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: NormShield Services is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free API Services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

nsrllookup

  • Website: https://github.com/rjhansen/nsrllookup
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: nsrllookup is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool for looking.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

objdump

  • Website: https://en.wikipedia.org/wiki/Objdump
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: objdump is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Part of GNU binutils,.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

OfficeMalScanner

  • Website: http://www.reconstructer.org/code.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: OfficeMalScanner is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Scan for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

Oh My Malware

  • Website: https://ohmymalware.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: Oh My Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A video series focused on malware execution and investigations using Elastic 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 Threat Detection and Hunting > Resources.

Back to Category Index

olevba

  • Website: http://www.decalage.info/python/olevba
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: olevba is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A script for parsing OLE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

OllyDbg

  • Website: http://www.ollydbg.de/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Cyber Security Tools, Awesome Hacking

What it does: OllyDbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: x86 debugger for Windows binaries that emphasizes binary code 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: Awesome Penetration Testing > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

OllyDumpEx

  • Website: https://low-priority.appspot.com/ollydumpex/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: OllyDumpEx is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Dump memory.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Open Malware

  • Website: http://www.offensivecomputing.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Open Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > General.

Back to Category Index

Origami PDF

  • Website: https://code.google.com/archive/p/origami-pdf
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Origami PDF is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

PackerAttacker

  • Website: https://github.com/BromiumLabs/PackerAttacker
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PackerAttacker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A generic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

packerid

  • Website: https://github.com/sooshie/packerid
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: packerid is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A cross-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: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Pafish

  • Website: https://github.com/a0rtega/pafish
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools

What it does: Pafish is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Detects virtual machines and malware analysis 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: Malware Analysis > Static Analysis > Anti-Analysis Detector.

Back to Category Index

PANDA

  • Website: https://github.com/moyix/panda
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PANDA is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Platform for Architecture-Neutral.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

PDF Examiner

  • Website: http://www.pdfexaminer.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PDF Examiner is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Analyse suspicious PDF 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 Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

PDF Tools

  • Website: https://blog.didierstevens.com/programs/pdf-tools/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools

What it does: PDF Tools is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Scans for PDF keywords indicating JavaScript or actions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Documents and Shellcode.

Back to Category Index

PDF X-Ray Lite

  • Website: https://github.com/9b/pdfxray_lite
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PDF X-Ray Lite is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A PDF 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 Malware Analysis > Documents and Shellcode.

Back to Category Index

PE-bear

  • Website: https://hshrzd.wordpress.com/pe-bear/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PE-bear is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reversing tool for PE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

PEDA

  • Website: https://github.com/longld/peda
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome CTF

What it does: PEDA is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python Exploit Development Assistance for GDB.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

peepdf

  • Website: http://eternal-todo.com/tools/peepdf-pdf-analysis-tool
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: peepdf is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: 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 Malware Analysis > Documents and Shellcode.

Back to Category Index

PEframe

  • Website: https://github.com/guelfoweb/peframe
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PEframe is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: PEframe is an open source tool to perform static analysis on Portable Executable malware and malicious MS Office documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

pestudio

  • Website: https://winitor.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: pestudio is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Perform static analysis of 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

PEV

  • Website: http://pev.sourceforge.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PEV is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A multiplatform toolkit to work with PE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

PEview

  • Website: http://wjradburn.com/software/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: PEview is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A quick and easy way to view the structure and content of 32-bit Portable Executable (PE) and Component Object File Format (COFF) 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: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

plasma

  • Website: https://github.com/plasma-disassembler/plasma
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Web Security

What it does: plasma is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Plasma is an interactive disassembler for x86/ARM/MIPS 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

plasma

  • Website: https://github.com/joelpx/plasma
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: plasma is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An interactive disassembler for x86/ARM/MIPS which can generate indented pseudo-code with colored syntax.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Polichombr

  • Website: https://github.com/ANSSI-FR/polichombr
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Polichombr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A malware 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: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

Pompelmi

  • Website: https://github.com/pompelmi/pompelmi
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Security

What it does: Pompelmi is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Node.js file-upload malware scanner with MIME sniffing, ZIP-bomb protection and optional YARA rules.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

PortEx

  • Website: https://github.com/katjahahn/PortEx
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PortEx is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Java library to analyse PE files with a special focus on malware analysis and PE malformation robustness.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

PPEE (puppy)

  • Website: https://www.mzrst.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PPEE (puppy) is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A Professional PE file Explorer for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Practical Malware Analysis

  • Website: https://amzn.com/dp/1593272901
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Practical Malware Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: The Hands-On.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

Practical Malware Analysis Starter Kit

  • Website: https://bluesoul.me/practical-malware-analysis-starter-kit/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Practical Malware Analysis Starter Kit is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Other.

Back to Category Index

Practical Reverse Engineering

  • Website: https://www.amzn.com/dp/1118787315/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Practical Reverse Engineering is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Books.

Back to Category Index

Practical Reverse Engineering by Bruce Dang et al., 2014

  • Website: http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118787315.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Practical Reverse Engineering by Bruce Dang et al., 2014 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Reverse Engineering > Reverse Engineering Books.

Back to Category Index

Privoxy

  • Website: http://www.privoxy.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Privoxy is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An open source proxy server with some.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Anonymizers.

Back to Category Index

ProcDot

  • Website: http://www.procdot.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ProcDot is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A graphical malware analysis tool kit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Process Explorer

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Process Explorer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Process Hacker

  • Website: http://processhacker.sourceforge.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Process Hacker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Tool that monitors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Process Monitor

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools

What it does: Process Monitor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Monitors and logs real-time file system, Registry, and process/thread activity (SysInternals).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

procyon

  • Website: https://bitbucket.org/mstrobel/procyon/wiki/Java%20Decompiler
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: procyon is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Decompilers.

Back to Category Index

Protobuf inspector

  • Website: https://github.com/jmendeth/protobuf-inspector
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Protobuf inspector is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

PSTools

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/pstools
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PSTools is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

pwndbg

  • Website: https://github.com/pwndbg/pwndbg
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: pwndbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: GDB plug-in that eases debugging with GDB, with a focus on features needed by low-level software developers, hardware hackers, reverse-engineers, and exploit 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Pyew

  • Website: https://github.com/joxeankoret/pyew
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Pyew is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python tool for malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

PyInstaller Extractor

  • Website: https://github.com/extremecoders-re/pyinstxtractor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: PyInstaller Extractor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Deobfuscation.

Back to Category Index

PyREBox

  • Website: https://github.com/Cisco-Talos/pyrebox
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: PyREBox is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python scriptable Reverse Engineering sandbox by Cisco-Talos.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

python-evt

  • Website: https://github.com/williballenthin/python-evt
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Forensics

What it does: python-evt is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Pure Python parser for classic Windows Event Log files (.evt).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts.

Back to Category Index

python-registry

  • Website: http://www.williballenthin.com/registry/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: python-registry is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: 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 Malware Analysis > Windows Artifacts.

Back to Category Index

Qiling Framework

  • Website: https://www.qiling.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Qiling Framework is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Cross platform emulation and sanboxing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

QKD

  • Website: https://github.com/ispras/qemu/releases/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: QKD is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: QEMU with embedded WinDbg.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Qubes OS

  • Website: https://qubes-os.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Qubes OS is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Desktop environment built atop the Xen hypervisor project that runs each end-user program in its own virtual machine intended to provide strict security controls to constrain the reach of any successful malware exploit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Operating System distributions.

Back to Category Index

QuickSand

  • Website: https://www.quicksand.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: QuickSand is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: QuickSand is a compact C 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 Malware Analysis > Documents and Shellcode.

Back to Category Index

RABCDAsm

  • Website: https://github.com/CyberShadow/RABCDAsm
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: RABCDAsm is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of utilities including an ActionScript 3 assembler/disassembler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

Radare2

  • Website: http://www.radare.org/r/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Radare2 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Reverse engineering framework, with.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Radare2

  • Website: http://rada.re/r/index.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Radare2 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open source, crossplatform reverse engineering 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

radare2

  • Website: https://github.com/radare/radare2
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking, Awesome CTF, Awesome Web Security

What it does: radare2 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Unix-like reverse engineering framework and commandline tools 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: Reverse Engineering > Tools > Disassemblers and debuggers.

Back to Category Index

Ragpicker

  • Website: https://github.com/robbyFux/Ragpicker
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Ragpicker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Plugin based malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Recomposer

  • Website: https://github.com/secretsquirrel/recomposer
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Recomposer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A helper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

recon

  • Website: https://github.com/rusty-ferris-club/recon
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Security, Awesome Forensics

What it does: recon is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a fast Rust based CLI that uses SQL to query over files, code, or malware with content classification and processing for security experts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

RegRipper

  • Website: http://brettshavers.cc/index.php/brettsblog/tags/tag/regripper/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: RegRipper is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Windows Artifacts.

Back to Category Index

RegShot

  • Website: https://sourceforge.net/projects/regshot/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: RegShot is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Registry compare utility.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Rekall

  • Website: http://www.rekall-forensic.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: Rekall is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open source tool (and library) for the extraction of digital artifacts from volatile memory (RAM) samples.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > IR management consoles.

Back to Category Index

REMnux

  • Website: https://remnux.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools, Awesome CTF, Awesome Forensics, Awesome SOC

What it does: REMnux is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Distro for reverse-engineering and analyzing malicious 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

RetDec

  • Website: https://retdec.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: RetDec is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Retargetable machine-code decompiler with an.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

retdec

  • Website: https://github.com/avast-tl/retdec
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: retdec is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Decompilers.

Back to Category Index

Reverse Engineering for Beginners by Dennis Yurichev

  • Website: http://beginners.re/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Reverse Engineering for Beginners by Dennis Yurichev is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Reverse Engineering > Reverse Engineering Books.

Back to Category Index

Reverse engineering the analyst: building machine learning models for the SOC

  • Website: https://www.mandiant.com/resources/blog/build-machine-learning-models-for-the-soc
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: Reverse engineering the analyst: building machine learning models for the SOC is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Resources > Data Science.

Back to Category Index

Reversing.kr

  • Website: http://www.reversing.kr/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Reversing.kr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: This site tests your ability to Cracking & Reverse Code Engineering.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reverse Engineering.

Back to Category Index

Rootkits and Bootkits

  • Website: https://www.amazon.com/dp/1593277164
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Rootkits and Bootkits is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Rootkits and Bootkits: Reversing Modern Malware and Next Generation Threats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Books.

Back to Category Index

ROPMEMU

  • Website: https://github.com/Cisco-Talos/ROPMEMU
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ROPMEMU is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A framework to analyze, dissect.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

RPISEC Malware Analysis

  • Website: https://github.com/RPISEC/Malware
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: RPISEC Malware Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: These are the.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

rVMI

  • Website: https://github.com/fireeye/rVMI
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: rVMI is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Debugger on steroids; inspect userspace processes, kernel drivers, and preboot environments in a single 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

sandboxapi

  • Website: https://github.com/InQuest/python-sandboxapi
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: sandboxapi is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Minimal, consistent Python API for building integrations with malware sandboxes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

Santoku Linux

  • Website: https://santoku-linux.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Santoku Linux is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Linux distribution for mobile.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Miscellaneous.

Back to Category Index

Scalpel

  • Website: https://github.com/sleuthkit/scalpel
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Scalpel is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Another data carving.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > File Carving.

Back to Category Index

ScratchABit

  • Website: https://github.com/pfalcon/ScratchABit
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: ScratchABit is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Easily retargetable and hackable interactive disassembler with IDAPython-compatible plugin API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Disassemblers and debuggers.

Back to Category Index

Scylla Imports Reconstructor

  • Website: https://github.com/NtQuery/Scylla
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Scylla Imports Reconstructor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Find and fix.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

ScyllaHide

  • Website: https://github.com/x64dbg/ScyllaHide
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ScyllaHide is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An Anti-Anti-Debug library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

SecurityTrails

  • Website: https://securitytrails.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SecurityTrails is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Historical and current WHOIS,.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

SEE

  • Website: https://github.com/F-Secure/see
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SEE is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Sandboxed Execution Environment (SEE).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

SEKOIA Dropper Analysis

  • Website: https://malware.sekoia.fr/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SEKOIA Dropper Analysis is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Online dropper analysis (Js, VBScript, Microsoft Office, PDF).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

SFlock

  • Website: https://github.com/jbremer/sflock
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SFlock is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Nested archive.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > File Carving.

Back to Category Index

simples.kr

  • Website: http://simples.kr/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: simples.kr is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: (Korean).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reverse Engineering.

Back to Category Index

SMRT

  • Website: https://github.com/pidydx/SMRT
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SMRT is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Sublime Malware Research Tool, a.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

snowman

  • Website: https://github.com/yegord/snowman
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: snowman is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Decompilers.

Back to Category Index

SpamCop

  • Website: https://www.spamcop.net/bl.shtml
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SpamCop is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: IP based spam block list.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

SpamHaus

  • Website: https://www.spamhaus.org/lookup/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SpamHaus is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Block list based on.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Spidermonkey

  • Website: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Spidermonkey is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Documents and Shellcode.

Back to Category Index

ssdeep

  • Website: https://ssdeep-project.github.io/ssdeep/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ssdeep is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Compute fuzzy hashes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

stoQ

  • Website: http://stoq.punchcyber.com
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: stoQ is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Distributed content 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: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

strace

  • Website: https://sourceforge.net/projects/strace/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: strace is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Dynamic analysis for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

StringSifter

  • Website: https://github.com/fireeye/stringsifter
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: StringSifter is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A machine learning tool that ranks strings based on their relevance for malware 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: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Sucuri SiteCheck

  • Website: https://sitecheck.sucuri.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Sucuri SiteCheck is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free Website Malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

SWF Investigator

  • Website: https://labs.adobe.com/technologies/swfinvestigator/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: SWF Investigator is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Browser Malware.

Back to Category Index

swftools

  • Website: http://www.swftools.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome CTF

What it does: swftools is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of utilities to work with SWF 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 Malware Analysis > Browser Malware.

Back to Category Index

Synalize It

  • Website: https://www.synalysis.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Synalize It is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Binary files examination and editing > Hex editors.

Back to Category Index

Talos Intelligence

  • Website: https://talosintelligence.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Talos Intelligence is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Search for IP, 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 Malware Analysis > Domain Analysis.

Back to Category Index

TekDefense Automater

  • Website: http://www.tekdefense.com/automater/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: TekDefense Automater is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: OSINT 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 Malware Analysis > Domain Analysis.

Back to Category Index

TensorFuzz: Debugging Neural Networks with Coverage-Guided Fuzzing, 2018

  • Website: https://arxiv.org/abs/1807.10875
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Fuzzing

What it does: TensorFuzz: Debugging Neural Networks with Coverage-Guided Fuzzing, 2018 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

Thale's Cyberthreat Map

  • Website: https://cds.thalesgroup.com/en/cyberthreat/hitmap
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome OSINT

What it does: Thale's Cyberthreat Map is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Discover cybersecurity trends with Thales' Cyberthreat map. Explore targeted areas, frequent attacks, affected sectors, and prevalent malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

The Art of Memory Forensics

  • Website: https://memoryanalysis.net/amf/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Forensics

What it does: The Art of Memory Forensics is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Detecting Malware and Threats in Windows, Linux, and Mac Memory.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Books.

Back to Category Index

theZoo

  • Website: https://github.com/ytisf/theZoo
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Threat Detection

What it does: theZoo is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A repository of LIVE malwares.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Threat Hunting for Fileless Malware

  • Website: https://www.countercept.com/our-thinking/threat-hunting-for-fileless-malware/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Threat Detection

What it does: Threat Hunting for Fileless Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 > Resources.

Back to Category Index

Thug

  • Website: https://github.com/buffer/thug
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Thug is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Low interaction honeyclient, for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Honeypots.

Back to Category Index

Tor

  • Website: https://www.torproject.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome OSINT

What it does: Tor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free software and onion routed overlay network that helps you defend against traffic 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: Awesome Malware Analysis > Malware Collection > Anonymizers.

Back to Category Index

totalhash.py

  • Website: https://gist.github.com/gleblanc1783/3c8e6b379fa9d646d401b96ab5c7877f
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: totalhash.py is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Detection and Classification.

Back to Category Index

TotalRecall

  • Website: https://github.com/sketchymoose/TotalRecall
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: TotalRecall is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Script based.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Memory Forensics.

Back to Category Index

Tracker h3x

  • Website: http://tracker.h3x.eu/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Tracker h3x is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Agregator for malware corpus tracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

TrID

  • Website: http://mark0.net/soft-trid-e.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: TrID is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: File identifier.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Triton

  • Website: https://triton.quarkslab.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Triton is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A dynamic binary analysis (DBA) 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Udis86

  • Website: https://github.com/vmt/udis86
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Udis86 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Disassembler library and 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

UEFITool

  • Website: https://github.com/LongSoft/UEFITool
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: UEFITool is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: UEFI firmware image viewer and 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

uncompyle6

  • Website: https://github.com/rocky/python-uncompyle6/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking

What it does: uncompyle6 is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: decompiler for the over 20 releases and 20 years of CPython.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Decompilers.

Back to Category Index

unpacker

  • Website: https://github.com/malwaremusings/unpacker/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: unpacker is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automated malware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

unxor

  • Website: https://github.com/tomchop/unxor/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: unxor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Guess XOR keys using.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

un{i}packer

  • Website: https://github.com/unipacker/unipacker
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: un{i}packer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automatic and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

UPX

  • Website: http://upx.sourceforge.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: UPX is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: the Ultimate Packer (and unpacker) for eXecutables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Other.

Back to Category Index

URLhaus

  • Website: https://urlhaus.abuse.ch/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome OSINT

What it does: URLhaus is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: URLhaus shares malicious URLs to combat malware and botnet threats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

URLQuery

  • Website: http://urlquery.net/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome OSINT

What it does: URLQuery is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Domain Analysis.

Back to Category Index

urlscan.io

  • Website: https://urlscan.io/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome OSINT, Awesome Web Security

What it does: urlscan.io is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Service which analyses websites and the resources they request 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

usbmon

  • Website: https://www.kernel.org/doc/Documentation/usb/usbmon.txt
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: usbmon is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: USB capture for 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: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

USBPcap

  • Website: https://github.com/desowin/usbpcap
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: USBPcap is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: USB capture 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: Reverse Engineering > Tools > Execution logging and tracing.

Back to Category Index

vduddu malware repo

  • Website: https://github.com/vduddu/Malware
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: vduddu malware repo is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Collection of.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Veles

  • Website: https://github.com/codilime/veles
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: Veles is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: a visualizer for statistical properties of blobs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Reverse Engineering > Tools > Binary files examination and editing > Other.

Back to Category Index

Viper

  • Website: http://viper.li/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Viper is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A binary management and analysis framework for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Storage and Workflow.

Back to Category Index

VirtualDeobfuscator

  • Website: https://github.com/jnraber/VirtualDeobfuscator
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: VirtualDeobfuscator is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Deobfuscation.

Back to Category Index

ViruSign

  • Website: http://www.virussign.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ViruSign is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Malware database that detected 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 Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

VirusShare

  • Website: https://virusshare.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: VirusShare is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Malware repository, registration.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Visualize_Logs

  • Website: https://github.com/keithjjones/visualize_logs
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: Visualize_Logs is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open source visualization library and command line tools for logs (Cuckoo, Procmon, more to come).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Sandboxing/Reversing Tools.

Back to Category Index

Vivisect

  • Website: https://github.com/vivisect/vivisect
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Vivisect is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Python tool for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

VMCloak

  • Website: https://github.com/hatching/vmcloak
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Honeypots

What it does: VMCloak is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Automated Virtual Machine Generation and Cloaking for Cuckoo Sandbox.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

VolDiff

  • Website: https://github.com/aim4r/VolDiff
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: VolDiff is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Malware Memory Footprint Analysis based on Volatility.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Voltron

  • Website: https://github.com/snare/voltron
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: Voltron is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Extensible debugger UI toolkit 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

VolUtility

  • Website: https://github.com/kevthehermit/VolUtility
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Forensics

What it does: VolUtility is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Web App for Volatility 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 Forensics > Tools > Memory Forensics.

Back to Category Index

VX Underground

  • Website: http://vx-underground.org/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: VX Underground is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Massive and growing collection of free malware samples.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

VX Vault

  • Website: http://vxvault.net
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: VX Vault is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Active collection of malware samples.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

WDBGARK

  • Website: https://github.com/swwwolf/wdbgark
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: WDBGARK is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Memory Forensics.

Back to Category Index

WDK/WinDbg

  • Website: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: WDK/WinDbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Windows Driver Kit and WinDbg.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Whois

  • Website: https://whois.domaintools.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Whois is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: DomainTools free online whois.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

WinDbg

  • Website: https://developer.microsoft.com/en-us/windows/hardware/download-windbg
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: WinDbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: multipurpose debugger for the Microsoft Windows computer operating system, used to debug user mode applications, device drivers, and the kernel-mode memory dumps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

WinDbg

  • Website: https://developer.microsoft.com/en-us/windows/hardware/windows-driver-kit
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: WinDbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Memory Forensics.

Back to Category Index

WindowsIR: Malware

  • Website: http://windowsir.blogspot.com/p/malware.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: WindowsIR: Malware is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Harlan.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Other.

Back to Category Index

WinHex

  • Website: http://www.winhex.com/winhex/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: WinHex is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A hexadecimal editor, helpful in the realm of computer forensics, data recovery, low-level data processing, and IT 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: Reverse Engineering > Tools > Binary files examination and editing > Hex editors.

Back to Category Index

wxHexEditor

  • Website: https://github.com/EUA/wxHexEditor
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: wxHexEditor is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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: Reverse Engineering > Tools > Binary files examination and editing > Hex editors.

Back to Category Index

X64dbg

  • Website: https://github.com/x64dbg/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: X64dbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An open-source x64/x32 debugger 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

x64dbg

  • Website: http://x64dbg.com/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Penetration Testing

What it does: x64dbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Open source x64/x32 debugger 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 > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

x64dbg

  • Website: https://github.com/x64dbg/x64dbg
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Hacking

What it does: x64dbg is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: An open-source x64/x32 debugger 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: Reverse Engineering > Tools > Disassemblers and debuggers.

Back to Category Index

XORBruteForcer

  • Website: http://eternal-todo.com/var/scripts/xorbruteforcer
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: XORBruteForcer is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. 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 Malware Analysis > Deobfuscation.

Back to Category Index

XORSearch & XORStrings

  • Website: https://blog.didierstevens.com/programs/xorsearch/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Cyber Security Tools

What it does: XORSearch & XORStrings is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Searches for strings in XOR, ROL, ROT, or SHIFT encoded binary 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: Malware Analysis > Static Analysis > Strings.

Back to Category Index

xortool

  • Website: https://github.com/hellman/xortool
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis, Awesome Hacking, Awesome CTF

What it does: xortool is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A tool to analyze multi-byte xor cipher.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Deobfuscation.

Back to Category Index

xxxswf

  • Website: http://hooked-on-mnemonics.blogspot.com/2011/12/xxxswfpy.html
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: xxxswf is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Browser Malware.

Back to Category Index

YARA

  • Website: https://plusvic.github.io/yara/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: YARA is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Pattern matching tool for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Yara Finder

  • Website: https://github.com/uppusaikiran/yara-finder
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Yara Finder is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A simple tool to yara match the file against various yara rules to find the indicators of suspicion.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Yara rules generator

  • Website: https://github.com/Neo23x0/yarGen
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Yara rules generator is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Generate.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Detection and Classification.

Back to Category Index

Zeltser's List

  • Website: https://zeltser.com/automated-malware-analysis/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Zeltser's List is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Online Scanners and Sandboxes.

Back to Category Index

Zeltser's List

  • Website: https://zeltser.com/lookup-malicious-websites/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Zeltser's List is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Zeltser's Sources

  • Website: https://zeltser.com/malware-sample-sources/
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Zeltser's Sources is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: A list.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Zeus Source Code

  • Website: https://github.com/Visgean/Zeus
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: Zeus Source Code is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Source for the Zeus.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

ZScalar Zulu

  • Website: https://zulu.zscaler.com/#
  • Model: Open Source
  • Category: Malware Analysis & Reverse Engineering
  • Source Lists: Awesome Malware Analysis

What it does: ZScalar Zulu is used in malware analysis & reverse engineering programs to support sample triage, static/dynamic analysis, and malware behavior profiling. Source summaries describe it as: Zulu URL Risk Analyzer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Mobile Security

This category contains 12 documented tools. It focuses on capabilities used for mobile app hardening, runtime protections, and endpoint device posture enforcement. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Apk2Gold

  • Website: https://github.com/lxdvs/apk2gold
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome CTF

What it does: Apk2Gold is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Yet another Android decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

APKinspector

  • Website: https://github.com/honeynet/apkinspector/
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Honeypots

What it does: APKinspector is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Powerful GUI tool for analysts to analyze the Android 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: Contents > Honeypots.

Back to Category Index

ApkTool

  • Website: http://ibotpeaches.github.io/Apktool/
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome CTF

What it does: ApkTool is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Android Decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Charm: Facilitating Dynamic Analysis of Device Drivers of Mobile Systems, 2018

  • Website: https://www.usenix.org/conference/usenixsecurity18/presentation/talebi
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Fuzzing

What it does: Charm: Facilitating Dynamic Analysis of Device Drivers of Mobile Systems, 2018 is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. 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 > USENIX Security.

Back to Category Index

Decompiler.com

  • Website: https://www.decompiler.com/
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Hacking

What it does: Decompiler.com is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Java, Android, Python, C# online decompiler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Web > Tools.

Back to Category Index

Evolutionary Fuzzing of Android OS Vendor System Services, 2019

  • Website: https://arxiv.org/abs/1906.00621
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Fuzzing

What it does: Evolutionary Fuzzing of Android OS Vendor System Services, 2019 is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

FANS: Fuzzing Android Native System Services via Automated Interface Analysis, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/liu
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Fuzzing

What it does: FANS: Fuzzing Android Native System Services via Automated Interface Analysis, 2020 is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. 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 > USENIX Security.

Back to Category Index

FingerprintJS

  • Website: https://github.com/fingerprintjs/fingerprintjs
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Security

What it does: FingerprintJS is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Identifies browser and hybrid mobile application users even when they purge data storage. Allows you to detect account takeovers, account sharing and repeated malicious activity.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Fraud prevention.

Back to Category Index

FingerprintJS Android

  • Website: https://github.com/fingerprintjs/fingerprint-android
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Security

What it does: FingerprintJS Android is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Identifies Android application users even when they purge data storage. Allows you to detect account takeovers, account sharing and repeated malicious activity.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Fraud prevention.

Back to Category Index

Frida

  • Website: https://www.frida.re
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome Honeypots, Awesome Penetration Testing

What it does: Frida is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. 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: Awesome Penetration Testing > Reverse Engineering > Reverse Engineering Tools.

Back to Category Index

Java Decompilers

  • Website: http://www.javadecompilers.com
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome CTF

What it does: Java Decompilers is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: An online decompiler for Java and Android APKs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Objection

  • Website: https://github.com/sensepost/objection
  • Model: Open Source
  • Category: Mobile Security
  • Source Lists: Awesome CTF

What it does: Objection is used in mobile security programs to support mobile app hardening, runtime protections, and endpoint device posture enforcement. Source summaries describe it as: Runtime Mobile Exploration.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Network Security Monitoring

This category contains 398 documented tools. It focuses on capabilities used for traffic inspection, anomaly detection, and packet-level investigations. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Aircrack-ng

  • Website: https://www.aircrack-ng.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cyber Security Tools

What it does: Aircrack-ng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Suite of tools for wireless network 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: Penetration Testing.

Back to Category Index

Fakenet-NG

  • Website: https://github.com/mandiant/flare-fakenet-ng
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cyber Security Tools

What it does: Fakenet-NG is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fake network environment for malware 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: Malware Analysis > Dynamic Analysis Tools.

Back to Category Index

ACLight

  • Website: https://github.com/cyberark/ACLight
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: ACLight is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Script for advanced discovery of sensitive Privileged Accounts - includes Shadow Admins.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

AIEngine

  • Website: https://bitbucket.org/camp0/aiengine
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: AIEngine is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: AIEngine is a next generation interactive/programmable Python/Ruby/Java/Lua packet inspection engine with capabilities of learning without any human intervention, NIDS(Network Intrusion Detection System) functionality, DNS domain classification, network collector, network forensics and many others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

Aircrack-ng

  • Website: http://www.aircrack-ng.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: Aircrack-ng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Aircrack is 802.11 WEP and WPA-PSK keys cracking 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: Awesome Penetration Testing > Network Tools > Wireless Network Tools.

Back to Category Index

Airgeddon

  • Website: https://github.com/v1s1t0r1sh3r3/airgeddon
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Airgeddon is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Multi-use bash script for Linux systems to audit wireless 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Amass

  • Website: https://github.com/owasp-amass/amass
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome OSINT

What it does: Amass is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: The amass tool searches Internet data sources, performs brute force subdomain enumeration, searches web archives, and uses machine learning to generate additional subdomain name guesses. DNS name resolution is performed across many public servers so the authoritative server will see the traffic coming from different locations. 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 Security > Network > Scanning / Pentesting.

Back to Category Index

Amass

  • Website: https://github.com/OWASP/Amass
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Amass is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: In-depth subdomain enumeration tool that performs scraping, recursive brute forcing, crawling of web archives, name altering and reverse DNS sweeping.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

Amun

  • Website: https://github.com/zeroq/amun
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Amun is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Amun Python-based low-interaction Honeypot.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Anevicon

  • Website: https://github.com/rozgo/anevicon
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: Anevicon is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: The most powerful UDP-based load generator, written in Rust.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

Apache Spot (incubating)

  • Website: https://github.com/apache/incubator-spot
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Apache Spot (incubating) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Apache Spot is open source software for leveraging insights from flow and packet 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: Awesome Security > Big Data.

Back to Category Index

AQUATONE

  • Website: https://github.com/michenriksen/aquatone
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: AQUATONE is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Subdomain discovery tool utilizing various open sources producing a report that can be used as input to other 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Arachni

  • Website: http://www.arachni-scanner.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Arachni is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scriptable framework for evaluating the security of 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Argos

  • Website: http://www.few.vu.nl/argos/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Argos is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Emulator for capturing zero-day 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: Contents > Network and Artifact Analysis.

Back to Category Index

Arkime

  • Website: https://github.com/arkime/arkime
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Arkime is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Augments your current security infrastructure to store and index network traffic in standard PCAP format, providing fast, indexed access.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

ASlookup

  • Website: https://aslookup.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: ASlookup is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: a useful tool for exploring autonomous systems and all related info (CIDR, ASN, Org...).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

authoscope

  • Website: https://github.com/kpcyrd/authoscope
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: authoscope is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scriptable network authentication 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 > Web Exploitation.

Back to Category Index

Automated Whitebox Fuzz Testing, 2008

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2017/09/Automated-Whitebox-Fuzz-Testing-paper-Patrice-Godefroid.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Automated Whitebox Fuzz Testing, 2008 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Awesome PCAP Tools

  • Website: https://github.com/caesar0301/awesome-pcaptools
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: Awesome PCAP Tools is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A collection of tools developed by other researchers in the Computer Science area to process network traces.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

badtouch

  • Website: https://github.com/kpcyrd/badtouch
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: badtouch is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scriptable network authentication 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: Web > Tools.

Back to Category Index

BetterCAP

  • Website: https://www.bettercap.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: BetterCAP is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Modular, portable and easily extensible MITM 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

BGP.he.net

  • Website: https://bgp.he.net
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: BGP.he.net is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free BGP and network intelligence 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: Awesome OSINT > ↑ Speciality Search Engines.

Back to Category Index

BGP.tools

  • Website: https://bgp.tools
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: BGP.tools is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Modern BGP toolkit for network reconnaissance and 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: Awesome OSINT > ↑ Speciality Search Engines.

Back to Category Index

Bgpview.io

  • Website: https://bgpview.io
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Bgpview.io is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: The website bgpview.io allows you to look up detailed information about ASNs, IPs, and BGP routes on the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

bittwist

  • Website: http://bittwist.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: bittwist is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Simple yet powerful libpcap-based Ethernet packet generator useful in simulating networking traffic or scenario, testing firewall, IDS, and IPS, and troubleshooting various network problems.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

Bluesky

  • Website: https://bsky.app
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Bluesky is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Decentralized social network built on the AT Protocol.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Major Social Networks.

Back to Category Index

Boofuzz

  • Website: https://github.com/jtpereyda/boofuzz
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Boofuzz is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fuzzing engine and fuzz testing 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 Security > Network > Scanning / Pentesting.

Back to Category Index

BoopSuite

  • Website: https://github.com/MisterBianco/BoopSuite
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: BoopSuite is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Suite of tools written in Python for wireless auditing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

BoxyHQ

  • Website: https://github.com/retracedhq/retraced
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: BoxyHQ is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source API for security and compliance audit logging.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

Brim

  • Website: https://github.com/brimsec/brim
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Brim is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A desktop application to efficiently search large packet captures and Zeek logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Bro

  • Website: https://www.bro.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Bro is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Protocol analyzer that operates at incredible.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Bro-Osquery

  • Website: https://svs.informatik.uni-hamburg.de/publications/2018/2018-05-31-Haas-QueryCon-Bro-Osquery.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Bro-Osquery is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Large-Scale Host and Network Monitoring Using Open-Source 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 Threat Detection and Hunting > Resources.

Back to Category Index

BroYara

  • Website: https://github.com/hempnall/broyara
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: BroYara is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Use Yara rules from Bro.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Bully

  • Website: http://git.kali.org/gitweb/?p=packages/bully.git;a=summary
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Bully is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Implementation of the WPS brute force attack, written in C.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

BunkerWeb

  • Website: https://github.com/bunkerity/bunkerweb
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: BunkerWeb is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: BunkerWeb is a full-featured open-source web server with ModeSecurity WAF, HTTPS with transparent Let's Encrypt renewal, automatic ban of strange behaviors based on HTTP codes, bot and bad IPs block, connection limits, state-of-the-art security presets, Web UI and much 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 Security > Web > Web Application Firewall.

Back to Category Index

CapTipper

  • Website: https://github.com/omriher/CapTipper
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: CapTipper is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Malicious HTTP traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Censys

  • Website: https://www.censys.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Censys is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Collects data on hosts and websites through daily ZMap and ZGrab scans.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Network device discovery tools.

Back to Category Index

Center for International Earth Science Information Network

  • Website: http://www.ciesin.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Center for International Earth Science Information Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Data and Statistics.

Back to Category Index

chopshop

  • Website: https://github.com/MITRECND/chopshop
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: chopshop is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Framework to aid analysts in the creation and execution of pynids-based decoders and detectors of APT tradecraft.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

cicd-goat

  • Website: https://github.com/cider-security-research/cicd-goat
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: cicd-goat is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

Cilium

  • Website: https://cilium.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Cilium is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source software for transparently securing the network connectivity between application services deployed using Linux container management platforms like Docker and Kubernetes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

cirt-fuzzer

  • Website: http://www.cirt.dk/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: cirt-fuzzer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A simple TCP/UDP protocol 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: Network > Tools.

Back to Category Index

CloudFail

  • Website: https://github.com/m0rtem/CloudFail
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: CloudFail is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Unmask server IP addresses hidden behind Cloudflare by searching old database records and detecting misconfigured DNS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

CloudShark

  • Website: https://www.cloudshark.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: CloudShark is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Web-based tool for packet 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: Awesome Malware Analysis > Network.

Back to Category Index

cms-explorer

  • Website: https://code.google.com/archive/p/cms-explorer/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: cms-explorer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Reveal the specific modules, plugins, components and themes that various websites powered by content management systems are running.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

CodeAlchemist: Semantics-Aware Code Generation to Find Vulnerabilities in JavaScript Engines, 2019

  • Website: https://daramg.gift/paper/han-ndss2019.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: CodeAlchemist: Semantics-Aware Code Generation to Find Vulnerabilities in JavaScript Engines, 2019 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Cognito Scanner

  • Website: https://github.com/padok-team/cognito-scanner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Cognito Scanner is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: CLI tool to pentest Cognito AWS instance. It implements three attacks: unwanted account creation, account oracle and identity pool escalation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

Community Honey Network

  • Website: https://communityhoneynetwork.readthedocs.io/en/stable/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Community Honey Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: CHN aims to make deployments honeypots and honeypot management tools easy and flexible. The default deployment method uses Docker Compose and Docker to deploy with a few simple commands.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

COMODO automated sandbox

  • Website: https://help.comodo.com/topic-72-1-451-4768-.html
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: COMODO automated sandbox is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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: Contents > Network and Artifact Analysis.

Back to Category Index

Conpot

  • Website: http://conpot.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Honeypots

What it does: Conpot is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: ICS/SCADA Honeypot. Conpot is a low interactive server side Industrial Control Systems honeypot designed to be easy to deploy, modify and extend. By providing a range of common industrial control protocols we created the basics to build your own system, capable to emulate complex infrastructures to convince an adversary that he just found a huge industrial complex. To improve the deceptive capabilities, we also provided the possibility to server a custom human machine interface to increase the honeypots attack surface. The response times of the services can be artificially delayed to mimic the behaviour of a system under constant load. Because we are providing complete stacks of the protocols, Conpot can be accessed with productive HMI's or extended with real hardware. Conpot is developed under the umbrella of the Honeynet Project and on the shoulders of a couple of very big giants.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Context-Sensitive and Directional Concurrency Fuzzing for Data-Race Detection, 2022

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2022-296-paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Context-Sensitive and Directional Concurrency Fuzzing for Data-Race Detection, 2022 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Cowpatty

  • Website: https://github.com/joswr1ght/cowpatty
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Cowpatty is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Brute-force dictionary attack against WPA-PSK.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

CrackMapExec

  • Website: https://github.com/byt3bl33d3r/CrackMapExec
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: CrackMapExec is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Swiss army knife for pentesting 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 > Network Tools.

Back to Category Index

Crowd Inspect

  • Website: https://www.crowdstrike.com/resources/community-tools/crowdinspect-tool/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Crowd Inspect is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free tool for Windows systems aimed to alert you to the presence of malware that may be communicating over the network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Host-based tools.

Back to Category Index

CrowdSec

  • Website: https://github.com/crowdsecurity/crowdsec
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome OSINT

What it does: CrowdSec is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: CrowdSec is a free, modern & collaborative behavior detection engine, coupled with a global IP reputation network. It stacks on Fail2Ban's philosophy but is IPV6 compatible and 60x faster (Go vs Python), uses Grok patterns to parse logs and YAML scenario to identify behaviors. CrowdSec is engineered for modern Cloud / Containers / VM based infrastructures (by decoupling detection and remediation). Once detected, you can remedy threats with various bouncers (firewall block, nginx http 403, Captchas, etc.) while the aggressive IPs can be sent to CrowdSec for curation before being shared among all users to further strengthen 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: Awesome Security > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

CryptoLyzer

  • Website: https://gitlab.com/coroner/cryptolyzer
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: CryptoLyzer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fast and flexible server cryptographic (TLS/SSL/SSH/HTTP) settings analyzer library for Python with CLI.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Transport Layer Security Tools.

Back to Category Index

Cuckoo Sandbox

  • Website: http://www.cuckoosandbox.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Cuckoo Sandbox is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Cuckoo Sandbox is an Open Source software for automating analysis of suspicious files. To do so it makes use of custom components that monitor the behavior of the malicious processes while running in an isolated environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Cyware Threat Response Docker

  • Website: https://hub.docker.com/r/cylabs/cy-threat-response
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Cyware Threat Response Docker is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

D(HE)ater

  • Website: https://github.com/Balasys/dheater
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: D(HE)ater is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: D(HE)ater sends forged cryptographic handshake messages to enforce the Diffie-Hellman key exchange.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

Damn Vulnerable Web Application (DVWA)

  • Website: https://hub.docker.com/r/citizenstig/dvwa/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: Damn Vulnerable Web Application (DVWA) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

Deepfence PacketStreamer

  • Website: https://github.com/deepfence/PacketStreamer
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Deepfence PacketStreamer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: High-performance remote packet capture and collection tool, distributed tcpdump for cloud native 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 Security > Network > Full Packet Capture / Forensic.

Back to Category Index

Deepfence SecretScanner

  • Website: https://github.com/deepfence/SecretScanner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Deepfence SecretScanner is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Find secrets and passwords in container images and file 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 Security > Network > Scanning / Pentesting.

Back to Category Index

Deepfence ThreatMapper

  • Website: https://github.com/deepfence/ThreatMapper
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Deepfence ThreatMapper is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Apache v2, powerful runtime vulnerability scanner for kubernetes, virtual machines and serverless.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

DELTA: A Security Assessment Framework for Software-Defined Networks, 2017

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2017/09/ndss201702A-1LeePaper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: DELTA: A Security Assessment Framework for Software-Defined Networks, 2017 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Denyhosts

  • Website: http://denyhosts.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Denyhosts is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Thwart SSH dictionary based attacks and brute force 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 Security > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

DNS Rebind Toolkit

  • Website: https://github.com/brannondorsey/dns-rebind-toolkit
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Web Security

What it does: DNS Rebind Toolkit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: DNS Rebind Toolkit is a frontend JavaScript framework for developing DNS Rebinding exploits against vulnerable hosts and services on a local area network (LAN) 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 > DNS Rebinding.

Back to Category Index

dnscat2

  • Website: https://github.com/iagox86/dnscat2
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: dnscat2 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Tool designed to create an encrypted command and control channel over the DNS protocol, which is an effective tunnel out of almost every network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

dnschef

  • Website: https://github.com/iphelix/dnschef
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: dnschef is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Highly configurable DNS proxy for 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 Penetration Testing > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

DNSDumpster

  • Website: https://dnsdumpster.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: DNSDumpster is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: is a website that will help you discover hosts related to a specific 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

dnsenum

  • Website: https://github.com/fwaeytens/dnsenum/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: dnsenum is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Perl script that enumerates DNS information from a domain, attempts zone transfers, performs a brute force dictionary style attack, and then performs reverse look-ups on the results.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

dnsmap

  • Website: https://github.com/makefu/dnsmap/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: dnsmap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Passive DNS network mapper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

dnsrecon

  • Website: https://github.com/darkoperator/dnsrecon/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: dnsrecon is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Perform DNS enumeration using direct queries and brute forcing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

dnstracer

  • Website: http://www.mavetju.org/unix/dnstracer.php
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: dnstracer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Determines where a given DNS server gets its information from, and follows the chain of DNS servers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Docker Bench for Security

  • Website: https://hub.docker.com/r/diogomonica/docker-bench-security/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: Docker Bench for Security is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

docker-metasploit

  • Website: https://hub.docker.com/r/remnux/metasploit/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: docker-metasploit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

dorothy2

  • Website: https://github.com/m4rco-/dorothy2
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: dorothy2 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Malware/botnet analysis framework 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: Contents > Network and Artifact Analysis.

Back to Category Index

DPDK

  • Website: http://dpdk.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: DPDK is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: DPDK is a set of libraries and drivers for fast packet 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 Security > Network > Fast Packet Processing.

Back to Category Index

Driller: Augmenting Fuzzing Through Selective Symbolic Execution, 2016

  • Website: https://cancer.shtech.org/wiki/uploads/2016---NDSS---driller-augmenting-fuzzing-through-selective-symbolic-execution.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Driller: Augmenting Fuzzing Through Selective Symbolic Execution, 2016 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Drool

  • Website: https://www.dns-oarc.net/tools/drool
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Drool is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Replay DNS traffic from packet capture files and send it to a specified server, such as for simulating DDoS attacks on the DNS and measuring normal DNS querying.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Dshell

  • Website: https://github.com/USArmyResearchLab/Dshell
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: Dshell is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Extensible network forensic analysis framework written in Python that enables rapid development of plugins to support the dissection of network packet captures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Protocol Analyzers and Sniffers.

Back to Category Index

dsniff

  • Website: https://www.monkey.org/~dugsong/dsniff/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: dsniff is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Collection of tools for network auditing and pentesting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

Earthcam

  • Website: http://www.earthcam.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Earthcam is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: EarthCam is the leading network of live streaming webcams for tourism and entertainment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

EMS: History-Driven Mutation for Coverage-based Fuzzing, 2022

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2022-162-paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: EMS: History-Driven Mutation for Coverage-based Fuzzing, 2022 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Enhancing Memory Error Detection for Large-Scale Applications and Fuzz Testing, 2018

  • Website: https://lifeasageek.github.io/papers/han:meds.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Enhancing Memory Error Detection for Large-Scale Applications and Fuzz Testing, 2018 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Epstein Exposed

  • Website: https://epsteinexposed.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Epstein Exposed is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Comprehensive searchable database of 2M+ DOJ Epstein case documents, 1,700+ persons, flight logs, emails, and network graph visualization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Document and Slides Search.

Back to Category Index

Ettercap

  • Website: http://www.ettercap-project.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Ettercap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Comprehensive, mature suite for machine-in-the-middle 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

European Union Agency for Network and Information Security

  • Website: https://www.enisa.europa.eu/topics/trainings-for-cybersecurity-specialists/online-training-material
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: European Union Agency for Network and Information Security is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: ENISA Cyber Security Training material.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

evilgrade

  • Website: https://github.com/infobyte/evilgrade
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: evilgrade is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Modular framework to take advantage of poor upgrade implementations by injecting fake updates.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

Exonera Tor

  • Website: https://exonerator.torproject.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Exonera Tor is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A database of IP addresses that have been part of the Tor network. It answers the question whether there was a Tor relay running on a given IP address on a given date.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

FakeNet-NG

  • Website: https://github.com/fireeye/flare-fakenet-ng
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: FakeNet-NG is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Next generation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Falco

  • Website: https://falco.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: Falco is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Behavioral activity monitor designed to detect anomalous activity in containerized applications, hosts, and network packet flows by auditing the Linux kernel and enriched by runtime data such as Kubernetes metrics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Cloud platform security.

Back to Category Index

FATT

  • Website: https://github.com/0x4D31/fatt
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: FATT is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A pyshark based script for extracting network metadata and fingerprints from pcap files and live network traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

Favocado: Fuzzing Binding Code of JavaScript Engines Using Semantically Correct Test Cases, 2021

  • Website: https://www.ndss-symposium.org/wp-content/uploads/ndss2021_6A-2_24224_paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Favocado: Fuzzing Binding Code of JavaScript Engines Using Semantically Correct Test Cases, 2021 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Fibratus

  • Website: https://github.com/rabbitstack/fibratus
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Incident Response, Awesome Honeypots, Awesome Penetration Testing, Awesome CTF

What it does: Fibratus is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fibratus is a tool for exploration and tracing of the Windows kernel. It is able to capture the most of the Windows kernel activity - process/thread creation and termination, file system I/O, registry, network activity, DLL loading/unloading and much more. Fibratus has a very simple CLI which encapsulates the machinery to start the kernel event stream collector, set kernel event filters or run the lightweight Python modules called filaments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Windows Evidence Collection.

Back to Category Index

Fiddler

  • Website: https://www.telerik.com/fiddler
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: Fiddler is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free cross-platform web debugging proxy with user-friendly companion 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 > Web Exploitation > Intercepting Web proxies.

Back to Category Index

fierce

  • Website: https://github.com/mschwager/fierce
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: fierce is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Python3 port of the original fierce.pl DNS reconnaissance tool for locating non-contiguous IP space.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Finding Evil on the Network Using JA3/S and HASSH

  • Website: https://engineering.salesforce.com/finding-evil-on-the-network-using-ja3-s-and-hassh-11431a8606e4
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Finding Evil on the Network Using JA3/S and HASSH is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Resources > Fingerprinting.

Back to Category Index

Finding The Real Origin IPs Hiding Behind CloudFlare or TOR

  • Website: https://www.secjuice.com/finding-real-ips-of-origin-servers-behind-cloudflare-or-tor/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Web Security

What it does: Finding The Real Origin IPs Hiding Behind CloudFlare or TOR is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Category Index

Fing

  • Website: https://www.fing.com/products/fing-app/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Fing is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network scanning and host enumeration app that performs NetBIOS, UPnP, Bonjour, SNMP, and various other advanced device fingerprinting techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

FingerprinTLS

  • Website: https://github.com/LeeBrotherston/tls-fingerprinting
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: FingerprinTLS is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A TLS fingerprinting method.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

Finshir

  • Website: https://github.com/isgasho/finshir
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Finshir is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A coroutines-driven Low & Slow traffic generator, written in Rust.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

Firesheep

  • Website: https://codebutler.github.io/firesheep/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Firesheep is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free program for HTTP session hijacking 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: Network > Tools.

Back to Category Index

Firezone

  • Website: https://github.com/firezone/firezone
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Firezone is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open-source VPN server and egress firewall for Linux built on WireGuard that makes it simple to manage secure remote access to your company’s private networks. Firezone is easy to set up (all dependencies are bundled thanks to Chef Omnibus), secure, performant, and self hostable.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > VPN.

Back to Category Index

Flare

  • Website: https://github.com/austin-taylor/flare
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Flare is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An analytical framework for network traffic and behavioral analytics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Fluxion

  • Website: https://github.com/FluxionNetwork/fluxion
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Fluxion is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Suite of automated social engineering based WPA 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 > Network Tools > Wireless Network Tools.

Back to Category Index

friTap

  • Website: https://github.com/fkie-cad/friTap
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: friTap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Intercept SSL/TLS connections with frida; Allows TLS key extraction and decryption of TLS payload as PCAP in real 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

fwknop

  • Website: https://www.cipherdyne.org/fwknop/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: fwknop is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Protects ports via Single Packet Authorization in your firewall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network perimeter defenses.

Back to Category Index

Gatekeeper

  • Website: https://github.com/AltraMayor/gatekeeper
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Gatekeeper is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: First open source Distributed Denial of Service (DDoS) protection 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 Cybersecurity Blue Team > Network perimeter defenses.

Back to Category Index

Geneva (Genetic Evasion)

  • Website: https://censorship.ai/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Geneva (Genetic Evasion) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Novel experimental genetic algorithm that evolves packet-manipulation-based censorship evasion strategies against nation-state level censors to increase availability of otherwise blocked content.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Communications security (COMSEC).

Back to Category Index

Gephi

  • Website: https://gephi.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Gephi is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: is an open-source graph and network visualization 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 OSINT > ↑ Social Network Analysis.

Back to Category Index

Glastopf

  • Website: http://glastopf.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Glastopf is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Glastopf is a Honeypot which emulates thousands of vulnerabilities to gather data from attacks targeting web applications. The principle behind it is very simple: Reply the correct response to the attacker exploiting the web application.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

GQUIC Protocol Analyzer for Zeek

  • Website: https://github.com/salesforce/GQUIC_Protocol_Analyzer
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: GQUIC Protocol Analyzer for Zeek is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

Habu

  • Website: https://github.com/portantier/habu
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: Habu is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Python utility implementing a variety of network attacks, such as ARP poisoning, DHCP starvation, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

Hack+

  • Website: http://hack.plus
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Hack+ is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An Intelligent network of bots that fetch the latest InfoSec content.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Hacking-Lab

  • Website: https://hacking-lab.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome CTF

What it does: Hacking-Lab is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Ethical hacking, computer network and security challenge 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 Category Index

hadoop-pcap

  • Website: https://github.com/RIPE-NCC/hadoop-pcap
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: hadoop-pcap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Hadoop library to read packet capture (PCAP) 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 Security > Big Data.

Back to Category Index

Haka

  • Website: http://www.haka-security.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Haka is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An open source security oriented.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Hale

  • Website: https://github.com/pjlantz/Hale
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: Hale is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Botnet command and control monitor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Hfinger

  • Website: https://github.com/CERT-Polska/hfinger
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Hfinger is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fingerprinting HTTP 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 Threat Detection and Hunting > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

HFL: Hybrid Fuzzing on the Linux Kernel, 2020

  • Website: https://www.unexploitable.systems/publication/kimhfl/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: HFL: Hybrid Fuzzing on the Linux Kernel, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

HFlow2

  • Website: https://projects.honeynet.org/hflow
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: HFlow2 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Data coalesing tool for honeynet/network 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: Contents > Honeypots.

Back to Category Index

HOIC

  • Website: https://sourceforge.net/projects/high-orbit-ion-cannon/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: HOIC is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Updated version of Low Orbit Ion Cannon, has 'boosters' to get around common counter measures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

HoneyDrive

  • Website: http://bruteforce.gr/honeydrive
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: HoneyDrive is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: HoneyDrive is the premier honeypot Linux distro. It is a virtual appliance (OVA) with Xubuntu Desktop 12.04.4 LTS edition installed. It contains over 10 pre-installed and pre-configured honeypot software packages such as Kippo SSH honeypot, Dionaea and Amun malware honeypots, Honeyd low-interaction honeypot, Glastopf web honeypot and Wordpot, Conpot SCADA/ICS honeypot, Thug and PhoneyC honeyclients and more. Additionally it includes many useful pre-configured scripts and utilities to analyze, visualize and process the data it can capture, such as Kippo-Graph, Honeyd-Viz, DionaeaFR, an ELK stack and much more. Lastly, almost 90 well-known malware analysis, forensics and network monitoring related tools are also present in the distribution.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

HoneyPy

  • Website: https://github.com/foospidy/HoneyPy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Honeypots

What it does: HoneyPy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: HoneyPy is a low to medium interaction honeypot. It is intended to be easy to: deploy, extend functionality with plugins, and apply custom configurations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Honeysink

  • Website: http://www.honeynet.org/node/773
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Honeysink is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source network sinkhole that provides a mechanism for detection and prevention of malicious traffic on a given network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

HoneySpider Network

  • Website: https://github.com/CERT-Polska/hsn2-bundle
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: HoneySpider Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Highly-scalable system integrating multiple client honeypots to detect malicious 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: Contents > Honeypots.

Back to Category Index

honeytrap

  • Website: https://github.com/tillmannw/honeytrap
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: honeytrap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Low-interaction honeypot and network security tool written to catch attacks against TCP and UDP services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

HonSSH

  • Website: https://github.com/tnich/honssh
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Honeypots

What it does: HonSSH is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: HonSSH is a high-interaction Honey Pot solution. HonSSH will sit between an attacker and a honey pot, creating two separate SSH connections between them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

HotFuzz: Discovering Algorithmic Denial-of-Service Vulnerabilities Through Guided Micro-Fuzzing, 2020

  • Website: https://www.researchgate.net/publication/339164746_HotFuzz_Discovering_Algorithmic_Denial-of-Service_Vulnerabilities_Through_Guided_Micro-Fuzzing
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: HotFuzz: Discovering Algorithmic Denial-of-Service Vulnerabilities Through Guided Micro-Fuzzing, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

hping3

  • Website: https://github.com/antirez/hping
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: hping3 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network tool able to send custom TCP/IP packets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

HTTPReplay

  • Website: https://github.com/jbremer/httpreplay
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: HTTPReplay is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Library for parsing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

HYPER-CUBE: High-Dimensional Hypervisor Fuzzing, 2020

  • Website: https://www.syssec.ruhr-uni-bochum.de/media/emma/veroeffentlichungen/2020/02/07/Hyper-Cube-NDSS20.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: HYPER-CUBE: High-Dimensional Hypervisor Fuzzing, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

IKEForce

  • Website: https://github.com/SpiderLabs/ikeforce
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: IKEForce is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Command line IPSEC VPN brute forcing tool for Linux that allows group name/ID enumeration and XAUTH brute forcing 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 > Network Tools.

Back to Category Index

imalse

  • Website: https://github.com/hbhzwj/imalse
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: imalse is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Integrated MALware Simulator and Emulator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Network and Artifact Analysis.

Back to Category Index

impacket

  • Website: https://github.com/CoreSecurity/impacket
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: impacket is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Collection of Python classes for working with network protocols.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

Impost

  • Website: http://impost.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Impost is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network security auditing tool designed to analyze the forensics behind compromised and/or vulnerable daemons.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

INetSim

  • Website: http://www.inetsim.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: INetSim is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network service emulation, useful when.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Infection Monkey

  • Website: https://www.guardicore.com/infectionmonkey/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Infection Monkey is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open-source breach and attack simulation (BAS) platform that helps you validate existing controls and identify how attackers might exploit your current network security gaps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

infernal-twin

  • Website: https://github.com/entropy1337/infernal-twin
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: infernal-twin is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Automated wireless hacking 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Innernet

  • Website: https://github.com/tonarino/innernet
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Innernet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free Software private network system that uses WireGuard under the hood, made to be self-hosted.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

INSTRIM: Lightweight Instrumentation for Coverage-guided Fuzzing, 2018

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2018/07/bar2018_14_Hsu_paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: INSTRIM: Lightweight Instrumentation for Coverage-guided Fuzzing, 2018 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains

  • Website: https://www.lockheedmartin.com/content/dam/lockheed/data/corporate/documents/LM-White-Paper-Intel-Driven-Defense.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Resources > Research Papers.

Back to Category Index

Intercepter-NG

  • Website: http://sniff.su/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Intercepter-NG is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Multifunctional network 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: Awesome Penetration Testing > Network Tools.

Back to Category Index

Into the Borg – SSRF inside Google production network

  • Website: https://opnsec.com/2018/07/into-the-borg-ssrf-inside-google-production-network/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Web Security

What it does: Into the Borg – SSRF inside Google production network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > SSRF.

Back to Category Index

IoTFuzzer: Discovering Memory Corruptions in IoT Through App-based Fuzzing, 2018

  • Website: http://wp.internetsociety.org/ndss/wp-content/uploads/sites/25/2018/02/ndss2018_01A-1_Chen_paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: IoTFuzzer: Discovering Memory Corruptions in IoT Through App-based Fuzzing, 2018 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

IPFire

  • Website: https://www.ipfire.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: IPFire is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Hardened GNU/Linux based router and firewall distribution forked from IPCop.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network perimeter defenses > Firewall appliances or distributions.

Back to Category Index

ISP.Tools

  • Website: https://www.isp.tools
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: ISP.Tools is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Is a free platform offering network diagnostic tools (ping, traceroute, MTR, DNS, WHOIS, HTTP, etc.) tailored for ISPs and infrastructure 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

IVRE

  • Website: https://github.com/ivre/ivre
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: IVRE is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network recon framework, published by @cea-sec & @ANSSI-FR. Build your own, self-hosted and fully-controlled alternatives to Criminalip / Shodan / ZoomEye / Censys and GreyNoise, run your Passive DNS service, collect and analyse network intelligence from your sensors, and much 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: Contents > Data Tools.

Back to Category Index

JA3

  • Website: https://github.com/salesforce/ja3
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: JA3 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A method for profiling SSL/TLS Clients and Servers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

JARM

  • Website: https://github.com/salesforce/jarm
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: JARM is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An active Transport Layer Security (TLS) server fingerprinting 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 Threat Detection and Hunting > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

JCS

  • Website: https://github.com/TheM4hd1/JCS
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: JCS is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Joomla Vulnerability Component Scanner with automatic database updater from exploitdb and packetstorm.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Joebox Cloud

  • Website: https://jbxcloud.joesecurity.org/login
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Joebox Cloud is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Analyzes the behavior of malicious files including PEs, PDFs, DOCs, PPTs, XLSs, APKs, URLs and MachOs on Windows, Android and Mac OS X for suspicious activities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Network and Artifact Analysis.

Back to Category Index

joomscan

  • Website: https://www.owasp.org/index.php/Category:OWASP_Joomla_Vulnerability_Scanner_Project
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: joomscan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Joomla vulnerability scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Joy

  • Website: https://github.com/cisco/joy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Joy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A package for capturing and analyzing network flow data and intraflow data, for network research, forensics, and security monitoring.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring.

Back to Category Index

Kaitai Struct

  • Website: http://kaitai.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: Kaitai Struct is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: File formats and network protocols dissection language and web IDE, generating parsers in C++, C#, Java, JavaScript, Perl, PHP, Python, 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 Malware Analysis > Debugging and Reverse Engineering.

Back to Category Index

Kali

  • Website: https://www.kali.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Cyber Security Tools, Awesome CTF

What it does: Kali is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Kali Linux is a Debian-derived Linux distribution designed for digital forensics and penetration testing. Kali Linux is preinstalled with numerous penetration-testing programs, including nmap (a port scanner), Wireshark (a packet analyzer), John the Ripper (a password cracker), and Aircrack-ng (a software suite for penetration-testing wireless LANs).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

KFSensor

  • Website: http://www.keyfocus.net/kfsensor/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: KFSensor is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Windows based honeypot Intrusion Detection System (IDS).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Kismet

  • Website: https://kismetwireless.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Kismet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Wireless network detector, sniffer, and IDS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Kismet

  • Website: https://github.com/kismetwireless/kismet
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Forensics

What it does: Kismet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A passive wireless sniffer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Forensics.

Back to Category Index

Kojoney

  • Website: http://kojoney.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Honeypots

What it does: Kojoney is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Kojoney is a low level interaction honeypot that emulates an SSH server. The daemon is written in Python using the Twisted Conch libraries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

KRACK Detector

  • Website: https://github.com/securingsam/krackdetector
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: KRACK Detector is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Detect and prevent KRACK attacks in your network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

krackattacks-scripts

  • Website: https://github.com/vanhoefm/krackattacks-scripts
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: krackattacks-scripts is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: WPA2 Krack attack scripts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Laika BOSS

  • Website: https://github.com/lmco/laikaboss
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Forensics

What it does: Laika BOSS is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Laika is an object scanner and intrusion detection 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 Forensics > Tools > Frameworks.

Back to Category Index

Lambda-Proxy

  • Website: https://github.com/puresec/lambda-proxy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Lambda-Proxy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Utility for testing SQL Injection vulnerabilities on AWS Lambda serverless functions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

LAN Turtle

  • Website: https://lanturtle.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: LAN Turtle is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Covert "USB Ethernet Adapter" that provides remote access, network intelligence gathering, and MITM capabilities when installed in a local network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Legion

  • Website: https://github.com/GoVanguard/legion
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: Legion is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Graphical semi-automated discovery and reconnaissance framework based on Python 3 and forked from SPARTA.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

libemu

  • Website: https://github.com/buffer/libemu
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: libemu is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Shellcode emulation library, useful for shellcode detection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Network and Artifact Analysis.

Back to Category Index

Life after Speech Recognition: Fuzzing Semantic Misinterpretation for Voice Assistant Applications, 2019

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_08-4_Zhang_paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Life after Speech Recognition: Fuzzing Semantic Misinterpretation for Voice Assistant Applications, 2019 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Live HTTP headers

  • Website: https://addons.mozilla.org/en-US/firefox/addon/http-header-live/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Live HTTP headers is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Live HTTP headers is a free firefox addon to see your browser requests in real time. It shows the entire headers of the requests and can be used to find the security loopholes in implementations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Sniffer.

Back to Category Index

Lonkero

  • Website: https://github.com/bountyyfi/lonkero
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Lonkero is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Enterprise-grade web vulnerability scanner with 60+ attack modules, built in Rust for penetration testing and 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 Security > Network > Scanning / Pentesting.

Back to Category Index

Low Orbit Ion Canon (LOIC)

  • Website: https://github.com/NewEraCracker/LOIC
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Low Orbit Ion Canon (LOIC) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source network stress tool written 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 > Network Tools > DDoS Tools.

Back to Category Index

Lynis

  • Website: https://cisofy.com/lynis/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: Lynis is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: an open source security auditing tool for Linux/Unix.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

  • Website: https://go.mail.ru/search_social
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Mail.Ru Social Network Search is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Malcolm

  • Website: https://github.com/idaholab/Malcolm
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Malcolm is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Malcolm is a powerful, 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: Awesome Malware Analysis > Network.

Back to Category Index

Malcom

  • Website: https://github.com/tomchop/malcom
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Malcom is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Malware Communications.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

mallory

  • Website: https://github.com/justmao945/mallory
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: mallory is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: HTTP/HTTPS proxy over SSH.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

Maltrail

  • Website: https://github.com/stamparm/maltrail
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: Maltrail is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Malicious network traffic detection 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 Cybersecurity Blue Team > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

Mass Scan

  • Website: https://github.com/robertdavidgraham/masscan
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: Mass Scan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: TCP port scanner, spews SYN packets asynchronously, scanning entire Internet in under 5 minutes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Masscanned

  • Website: https://github.com/ivre/masscanned
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Masscanned is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Let's be scanned. A low-interaction honeypot focused on network scanners and bots. It integrates very well with IVRE to build a self-hosted alternative to GreyNoise.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Matano

  • Website: https://github.com/matanolabs/matano
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Incident Response, Awesome Threat Detection

What it does: Matano is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An open source security lake platform (SIEM alternative) for threat hunting, detection and response on AWS. Matano lets you write advanced detections as code (using python) to correlate and alert on threats in realtime.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

Memcrashed

  • Website: https://github.com/649/Memcrashed-DDoS-Exploit
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Memcrashed is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: DDoS attack tool for sending forged UDP packets to vulnerable Memcached servers obtained using Shodan API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

Mercury

  • Website: https://github.com/cisco/mercury
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Mercury is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network fingerprinting and packet metadata capture.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

Metasploit Framework

  • Website: https://github.com/rapid7/metasploit-framework
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: Metasploit Framework is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A tool for developing and executing exploit code against a remote target machine. Other important sub-projects include the Opcode Database, shellcode archive and related research.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

mhn-core-docker

  • Website: https://github.com/MattCarothers/mhn-core-docker
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: mhn-core-docker is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Core elements of the Modern Honey Network implemented in 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: Contents > Honeypots.

Back to Category Index

MITMf

  • Website: https://github.com/byt3bl33d3r/MITMf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: MITMf is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Framework for Man-In-The-Middle 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

mitmproxy

  • Website: https://mitmproxy.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots, Awesome Penetration Testing

What it does: mitmproxy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Interactive TLS-capable intercepting HTTP proxy for penetration testers and software 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 > Web Exploitation > Intercepting Web proxies.

Back to Category Index

mitmsocks4j

  • Website: https://github.com/Akdeniz/mitmsocks4j
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: mitmsocks4j is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Man-in-the-middle SOCKS Proxy for Java.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

MobFuzz: Adaptive Multi-objective Optimization in Gray-box Fuzzing, 2022

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2022-314-paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: MobFuzz: Adaptive Multi-objective Optimization in Gray-box Fuzzing, 2022 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Modern Honey Network

  • Website: https://github.com/threatstream/mhn
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Modern Honey Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Multi-snort and honeypot sensor management, uses a network of VMs, small footprint SNORT installations, stealthy dionaeas, and a centralized server for management.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Modern Honeynet Network

  • Website: http://threatstream.github.io/mhn/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Modern Honeynet Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Streamlines deployment and management of secure honeypots.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Moloch

  • Website: https://github.com/aol/moloch
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: Moloch is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Moloch is an open source, large scale IPv4 packet capturing (PCAP), indexing and database system. A simple web interface is provided for PCAP browsing, searching, and exporting. APIs are exposed that allow PCAP data and JSON-formatted session data to be downloaded directly. Simple security is implemented by using HTTPS and HTTP digest password support or by using apache in front. Moloch is not meant to replace IDS engines but instead work along side them to store and index all the network traffic in standard PCAP format, providing fast access. Moloch is built to be deployed across many systems and can scale to handle multiple gigabits/sec of traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Full Packet Capture / Forensic.

Back to Category Index

Monit

  • Website: https://linoxide.com/monitoring-2/monit-linux/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome CTF

What it does: Monit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A linux tool to check a host on the network (and other non-network activities).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Networking.

Back to Category Index

monsoon

  • Website: https://github.com/RedTeamPentesting/monsoon
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: monsoon is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Very flexible and fast interactive HTTP enumeration/fuzzing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

Montage: A Neural Network Language Model-Guided JavaScript Engine Fuzzer, 2020

  • Website: https://www.usenix.org/conference/usenixsecurity20/presentation/lee-suyoung
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Montage: A Neural Network Language Model-Guided JavaScript Engine Fuzzer, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > USENIX Security.

Back to Category Index

Morpheus

  • Website: https://github.com/r00t-3xp10it/morpheus
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Morpheus is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Automated ettercap TCP/IP Hijacking 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

Nachricht

  • Website: https://nachricht.co/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Nachricht is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: With Nachricht.co you can send self-destructive and encrypted one-way messages over the Internet. You don't even need to miss out the messenger or social network of your choice. We are an independent, secure and fully free service!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Nagios

  • Website: https://nagios.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Nagios is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Popular network and service monitoring solution and reporting 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: Awesome Cybersecurity Blue Team > Security monitoring > Service and performance monitoring.

Back to Category Index

Ncrack

  • Website: https://nmap.org/ncrack/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Ncrack is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: High-speed network authentication cracking tool built to help companies secure their networks by proactively testing all their hosts and networking devices for poor passwords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

Nessus

  • Website: https://www.tenable.com/products/nessus-vulnerability-scanner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Nessus is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Commercial vulnerability management, configuration, and compliance assessment platform, sold by Tenable.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners.

Back to Category Index

Netcap

  • Website: https://github.com/dreadl0ck/netcap
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Netcap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A framework for secure and scalable network traffic 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: Awesome Threat Detection and Hunting > Tools > Network Monitoring.

Back to Category Index

netdiscover

  • Website: https://github.com/netdiscover-scanner/netdiscover
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: netdiscover is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network address discovery scanner, based on ARP sweeps, developed mainly for those wireless networks without a DHCP 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

netmap

  • Website: http://info.iet.unipi.it/~luigi/netmap/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: netmap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: netmap is a framework for high speed packet I/O. Together with its companion VALE software switch, it is implemented as a single kernel module and available for FreeBSD, Linux and now also 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 Security > Network > Fast Packet Processing.

Back to Category Index

Netresec's PCAP repo list

  • Website: https://www.netresec.com/?page=PcapFiles
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection, Awesome Forensics

What it does: Netresec's PCAP repo list is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A list of public packet capture repositories, which are freely available on the Internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Dataset.

Back to Category Index

netsniff-ng

  • Website: http://netsniff-ng.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: netsniff-ng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: netsniff-ng is a free Linux networking toolkit, a Swiss army knife for your daily Linux network plumbing if you will. Its gain of performance is reached by zero-copy mechanisms, so that on packet reception and transmission the kernel does not need to copy packets from kernel space to user space and vice versa.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

netsniff-ng

  • Website: https://github.com/netsniff-ng/netsniff-ng
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: netsniff-ng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Swiss army knife for network sniffing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Protocol Analyzers and Sniffers.

Back to Category Index

Netsparker Application Security Scanner

  • Website: https://www.netsparker.com/pricing/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Netsparker Application Security Scanner is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Application security scanner to automatically find security flaws.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners.

Back to Category Index

Network Forensics: Tracking Hackers through Cyberspace

  • Website: https://www.pearson.com/en-us/subject-catalog/p/Davidoff-Network-Forensics-Tracking-Hackers-through-Cyberspace/P200000009228
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Forensics

What it does: Network Forensics: Tracking Hackers through Cyberspace is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Learn to recognize hackers’ tracks and uncover network-based evidence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Books.

Back to Category Index

Network Security Toolkit (NST)

  • Website: http://networksecuritytoolkit.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Network Security Toolkit (NST) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fedora-based GNU/Linux bootable live Operating System designed to provide easy access to best-of-breed open source network security 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 > Operating System Distributions.

Back to Category Index

Network-segmentation-cheat-sheet

  • Website: https://github.com/sergiomarotco/Network-segmentation-cheat-sheet
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome SOC

What it does: Network-segmentation-cheat-sheet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: This project was created to publish the best practices for segmentation of the corporate network of any company. In general, the schemes in this project are suitable for any company.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: IT achitecture of a SOC > Disconnect (as much as possible) SOC from monitored environment > Enclave:.

Back to Category Index

NetworkMiner

  • Website: http://www.netresec.com/?page=NetworkMiner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Hacking, Awesome CTF

What it does: NetworkMiner is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A Network Forensic Analysis Tool (NFAT).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Netz

  • Website: https://github.com/spectralops/netz
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: Netz is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Discover internet-wide misconfigurations, using zgrab2 and others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

Netzob

  • Website: https://github.com/netzob/netzob
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Netzob is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Reverse engineering, traffic generation and fuzzing of communication protocols.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Protocol Analyzers and Sniffers.

Back to Category Index

NexFil

  • Website: https://github.com/thewhiteh4t/nexfil
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: NexFil is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: checks username from almost all social network sites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Nexpose

  • Website: https://www.rapid7.com/products/nexpose/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Nexpose is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Commercial vulnerability and risk management assessment engine that integrates with Metasploit, sold by Rapid7.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners.

Back to Category Index

ngrep

  • Website: http://ngrep.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: ngrep is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: ngrep strives to provide most of GNU grep's common features, applying them to the network layer. ngrep is a pcap-aware tool that will allow you to specify extended regular or hexadecimal expressions to match against data payloads of packets. It currently recognizes IPv4/6, TCP, UDP, ICMPv4/6, IGMP and Raw across Ethernet, PPP, SLIP, FDDI, Token Ring and null interfaces, and understands BPF filter logic in the same fashion as more common packet sniffing tools, such as tcpdump and snoop.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

ngrep

  • Website: https://github.com/jpr5/ngrep
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: ngrep is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Search through network traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

Nikto

  • Website: https://github.com/sullo/nikto
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Nikto is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Noisy but fast black box web server and web application vulnerability scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Nipe

  • Website: https://github.com/GouveaHeitor/nipe
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking, Awesome CTF

What it does: Nipe is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Script to redirect all traffic from the machine to the Tor network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Nmap

  • Website: https://nmap.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Cyber Security Tools, Awesome Hacking, Awesome CTF

What it does: Nmap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Nmap is a free and open source utility for network discovery and security auditing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Not All Coverage Measurements Are Equal: Fuzzing by Coverage Accounting for Input Prioritization, 2020

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2020/02/24422.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Not All Coverage Measurements Are Equal: Fuzzing by Coverage Accounting for Input Prioritization, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

ntopng

  • Website: http://www.ntop.org/products/traffic-analysis/ntop/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: ntopng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Ntopng is a network traffic probe that shows the network usage, similar to what the popular top Unix command does.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

ntopng

  • Website: https://github.com/ntop/ntopng
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: ntopng is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A web-based network traffic monitoring 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 Threat Detection and Hunting > Tools > Network Monitoring.

Back to Category Index

nuclei

  • Website: https://github.com/projectdiscovery/nuclei
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: nuclei is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Nuclei is a fast tool for configurable targeted scanning based on templates offering massive extensibility and ease of use 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

official Kali Linux

  • Website: https://hub.docker.com/r/kalilinux/kali-linux-docker/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: official Kali Linux is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

official OWASP ZAP

  • Website: https://github.com/zaproxy/zaproxy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: official OWASP ZAP is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

official WPScan

  • Website: https://hub.docker.com/r/wpscanteam/wpscan/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: official WPScan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

Open Data Network

  • Website: http://www.opendatanetwork.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Open Data Network is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Data and Statistics.

Back to Category Index

OpenFlow Honeypot (OFPot)

  • Website: https://github.com/upa/ofpot
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: OpenFlow Honeypot (OFPot) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Redirects traffic for unused IPs to a honeypot, built on POX.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

opensnitch

  • Website: https://github.com/evilsocket/opensnitch
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: opensnitch is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: OpenSnitch is a GNU/Linux port of the Little Snitch application firewall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

OpenVAS

  • Website: http://www.openvas.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: OpenVAS is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: OpenVAS is a framework of several services and tools offering a comprehensive and powerful vulnerability scanning and vulnerability management solution.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners.

Back to Category Index

OpenVPN

  • Website: https://openvpn.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: OpenVPN is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: OpenVPN is an open source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities. It uses a custom security protocol that utilizes SSL/TLS for key exchange.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

OpenZITI

  • Website: https://openziti.github.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OpenZITI is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source initiative focused on bringing Zero Trust to any application via an overlay network, tunelling applications, and numerous SDKs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

OPNsense

  • Website: https://opnsense.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: OPNsense is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: is an open source, easy-to-use and easy-to-build FreeBSD based firewall and routing platform. OPNsense includes most of the features available in expensive commercial firewalls, and more in many cases. It brings the rich feature set of commercial offerings with the benefits of open and verifiable sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network perimeter defenses > Firewall appliances or distributions.

Back to Category Index

ORA

  • Website: http://www.casos.cs.cmu.edu/projects/ora/software.php
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: ORA is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Social Network Analysis.

Back to Category Index

oregano

  • Website: https://github.com/nametoolong/oregano
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: oregano is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Python module that runs as a machine-in-the-middle (MITM) accepting Tor client 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

Osintgraph

  • Website: https://github.com/XD-MHLOO/Osintgraph
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Osintgraph is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Tool that maps your target’s Instagram data and relationships in Neo4j for social network 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: Awesome OSINT > Social Media Tools > ↑ Instagram.

Back to Category Index

ovizart

  • Website: https://github.com/oguzy/ovizart
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: ovizart is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Visual analysis for network traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Data Tools.

Back to Category Index

OWASP Juice Shop

  • Website: https://hub.docker.com/r/bkimminich/juice-shop
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: OWASP Juice Shop is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

OWASP Mutillidae II Web Pen-Test Practice Application

  • Website: https://hub.docker.com/r/citizenstig/nowasp/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: OWASP Mutillidae II Web Pen-Test Practice Application is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

OWASP NodeGoat

  • Website: https://github.com/owasp/nodegoat#option-3---run-nodegoat-on-docker
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: OWASP NodeGoat is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

OWASP Security Shepherd

  • Website: https://hub.docker.com/r/ismisepaul/securityshepherd/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: OWASP Security Shepherd is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

OWASP WebGoat Project docker image

  • Website: https://hub.docker.com/r/danmx/docker-owasp-webgoat/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: OWASP WebGoat Project docker image is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

OWASP WrongSecrets

  • Website: https://hub.docker.com/r/jeroenwillemsen/wrongsecrets
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: OWASP WrongSecrets is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

OwlH

  • Website: https://www.owlh.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: OwlH is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Helps manage network IDS at scale by visualizing Suricata, Zeek, and Moloch life cycles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

Packet Squirrel

  • Website: https://www.hak5.org/gear/packet-squirrel
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Packet Squirrel is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Ethernet multi-tool designed to enable covert remote access, painless packet captures, and secure VPN connections with the flip of a switch.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Packet Storm

  • Website: https://packetstormsecurity.com/files/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Packet Storm is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Compendium of exploits, advisories, tools, and other security-related resources aggregated from across the industry.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

PACKET_MMAP/TPACKET/AF_PACKET

  • Website: https://elixir.bootlin.com/linux/latest/source/Documentation/networking/packet_mmap.rst
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: PACKET_MMAP/TPACKET/AF_PACKET is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: It's fine to use PACKET_MMAP to improve the performance of the capture and transmission process in 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 Security > Network > Fast Packet Processing.

Back to Category Index

PacketTotal

  • Website: https://packettotal.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: PacketTotal is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Simple, free, high-quality packet capture file analysis facilitating the quick detection of network-borne malware (using Zeek and Suricata IDS signatures under the hood).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

padding-oracle-attacker

  • Website: https://github.com/KishanBagaria/padding-oracle-attacker
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome CTF

What it does: padding-oracle-attacker is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: padding-oracle-attacker is a CLI tool and library to execute padding oracle attacks (which decrypts data encrypted in CBC mode) easily, with support for concurrent network requests and an elegant UI.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Paros

  • Website: http://sourceforge.net/projects/paros/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Paros is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A Java-based HTTP/HTTPS proxy for assessing web application vulnerability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

Passive Network Audit Framework (pnaf)

  • Website: https://github.com/jusafing/pnaf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Passive Network Audit Framework (pnaf) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Framework that combines multiple passive and automated analysis techniques in order to provide a security assessment of network platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

passivedns-client

  • Website: https://github.com/chrislee35/passivedns-client
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: passivedns-client is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Library and query tool for querying several passive DNS providers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

PCAP-ATTACK

  • Website: https://github.com/sbousseaden/PCAP-ATTACK
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: PCAP-ATTACK is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A repo of PCAP samples for different ATT&CK techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Dataset.

Back to Category Index

PcapViz

  • Website: https://github.com/mateuszk87/PcapViz
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: PcapViz is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network topology and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

PeriScope: An Effective Probing and Fuzzing Framework for the Hardware-OS Boundary, 2019

  • Website: https://people.cs.kuleuven.be/~stijn.volckaert/papers/2019_NDSS_PeriScope.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: PeriScope: An Effective Probing and Fuzzing Framework for the Hardware-OS Boundary, 2019 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

PETEP

  • Website: https://github.com/Warxim/petep
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: PETEP is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Extensible TCP/UDP proxy with GUI for traffic analysis & modification with SSL/TLS support.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

PF_RING

  • Website: http://www.ntop.org/products/packet-capture/pf_ring/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: PF_RING is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: PF_RING is a new type of network socket that dramatically improves the packet capture speed.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Fast Packet Processing.

Back to Category Index

PF_RING ZC (Zero Copy)

  • Website: http://www.ntop.org/products/packet-capture/pf_ring/pf_ring-zc-zero-copy/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: PF_RING ZC (Zero Copy) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: PF_RING ZC (Zero Copy) is a flexible packet processing framework that allows you to achieve 1/10 Gbit line rate packet processing (both RX and TX) at any packet size. It implements zero copy operations including patterns for inter-process and inter-VM (KVM) communications.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Fast Packet Processing.

Back to Category Index

PFQ

  • Website: https://github.com/pfq/PFQ
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: PFQ is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: PFQ is a functional networking framework designed for the Linux operating system that allows efficient packets capture/transmission (10G and beyond), in-kernel functional processing and packets steering across sockets/end-points.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Fast Packet Processing.

Back to Category Index

pfSense

  • Website: https://www.pfsense.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: pfSense is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: FreeBSD firewall and router distribution forked from m0n0wall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network perimeter defenses > Firewall appliances or distributions.

Back to Category Index

PGFUZZ: Policy-Guided Fuzzing for Robotic Vehicles, 2021

  • Website: https://beerkay.github.io/papers/Berkay2021PGFuzzNDSS.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: PGFUZZ: Policy-Guided Fuzzing for Robotic Vehicles, 2021 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

pig

  • Website: https://github.com/rafael-santiago/pig
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: pig is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: GNU/Linux packet crafting 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

pivotsuite

  • Website: https://github.com/RedTeamOperations/PivotSuite
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: pivotsuite is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Portable, platform independent and powerful network pivoting 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: Awesome Penetration Testing > Network Tools.

Back to Category Index

Pompem

  • Website: https://github.com/rfunix/Pompem
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Pompem is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Pompem is an open source tool, which is designed to automate the search for exploits in major databases. Developed in Python, has a system of advanced search, thus facilitating the work of pentesters and ethical hackers. In its current version, performs searches in databases: Exploit-db, 1337day, Packetstorm 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 > Network > Scanning / Pentesting.

Back to Category Index

Postman

  • Website: https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?hl=en
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome CTF

What it does: Postman is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Add on for chrome for debugging network 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: Solve > Web.

Back to Category Index

Praeda

  • Website: http://h.foofus.net/?page_id=218
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Praeda is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Automated multi-function printer data harvester for gathering usable data 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 > Network Tools.

Back to Category Index

Printer Exploitation Toolkit (PRET)

  • Website: https://github.com/RUB-NDS/PRET
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Printer Exploitation Toolkit (PRET) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Tool for printer security testing capable of IP and USB connectivity, fuzzing, and exploitation of PostScript, PJL, and PCL printer language 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 > Network Tools.

Back to Category Index

PSKracker

  • Website: https://github.com/soxrok2212/PSKracker
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: PSKracker is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Collection of WPA/WPA2/WPS default algorithms, password generators, and PIN generators written in C.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

pwnagotchi

  • Website: https://github.com/evilsocket/pwnagotchi
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: pwnagotchi is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Deep reinforcement learning based AI that learns from the Wi-Fi environment and instruments BetterCAP in order to maximize the WPA key material captured.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Pylibemu

  • Website: https://github.com/buffer/pylibemu
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Pylibemu is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Libemu Cython wrapper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Network and Artifact Analysis.

Back to Category Index

Python ICAP Yara

  • Website: https://github.com/RamadhanAmizudin/python-icap-yara
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Python ICAP Yara is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

QueenSono

  • Website: https://github.com/ariary/QueenSono
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: QueenSono is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Client/Server Binaries for data exfiltration with ICMP. Useful in a network where ICMP protocol is less monitored than others (which is a common 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 > Exfiltration Tools.

Back to Category Index

Radware Live Cyber Threat Map

  • Website: https://livethreatmap.radware.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Radware Live Cyber Threat Map is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Radware's Live Threat Map presents near real-time information about cyberattacks as they occur, based on our global threat deception network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

RDFP

  • Website: https://github.com/yahoo/rdfp
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: RDFP is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Zeek Remote desktop fingerprinting script based on (Fingerprint All The 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 Threat Detection and Hunting > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

Real Intelligence Threat Analysis (RITA)

  • Website: https://github.com/activecm/rita
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Real Intelligence Threat Analysis (RITA) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source framework for network traffic analysis that ingests Zeek logs and detects beaconing, DNS tunneling, 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 Cybersecurity Blue Team > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

Reaver

  • Website: https://code.google.com/archive/p/reaver-wps
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Reaver is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Brute force attack against WiFi Protected Setup.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

Recog

  • Website: https://github.com/rapid7/recog
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Recog is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A framework for identifying products, services, operating systems, and hardware by matching fingerprints against data returned from various network probes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

REDQUEEN: Fuzzing with Input-to-State Correspondence, 2019

  • Website: https://www.syssec.ruhr-uni-bochum.de/media/emma/veroeffentlichungen/2018/12/17/NDSS19-Redqueen.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: REDQUEEN: Fuzzing with Input-to-State Correspondence, 2019 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Reinforcement Learning-based Hierarchical Seed Scheduling for Greybox Fuzzing, 2021

  • Website: https://www.cs.ucr.edu/~heng/pubs/afl-hier.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Reinforcement Learning-based Hierarchical Seed Scheduling for Greybox Fuzzing, 2021 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Respounder

  • Website: https://github.com/codeexpress/respounder
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Respounder is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Detects the presence of the Responder LLMNR/NBT-NS/MDNS poisoner on a network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

RFISandbox

  • Website: https://monkey.org/~jose/software/rfi-sandbox/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: RFISandbox is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: PHP 5.x script sandbox built on top of .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Network and Artifact Analysis.

Back to Category Index

routersploit

  • Website: https://github.com/reverse-shell/routersploit
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: routersploit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source exploitation framework similar to Metasploit but dedicated to embedded devices.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

rshijack

  • Website: https://github.com/kpcyrd/rshijack
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: rshijack is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: TCP connection hijacker, Rust rewrite of shijack.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

rspamd

  • Website: https://github.com/rspamd/rspamd
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: rspamd is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fast, free and open-source spam filtering 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 Security > Network > Anti-Spam.

Back to Category Index

RustNet

  • Website: https://github.com/domcyrus/rustnet
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Forensics

What it does: RustNet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A cross-platform network monitoring terminal UI providing real-time visibility into network 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 Forensics > Tools > Network Forensics.

Back to Category Index

RustScan

  • Website: https://github.com/RustScan/RustScan
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: RustScan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Faster Nmap scanning with Rust. Take a 17 minute Nmap scan down to 19 seconds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

RustScan

  • Website: https://github.com/rustscan/rustscan
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: RustScan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Extremely fast port scanner built with Rust, designed to scan all ports in a couple of seconds and utilizes nmap to perform port enumeration in a fraction of the 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

s7scan

  • Website: https://github.com/klsecservices/s7scan
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: s7scan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scanner for enumerating Siemens S7 PLCs on a TCP/IP or LLC network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Industrial Control and SCADA Systems.

Back to Category Index

Scammer-List

  • Website: https://scammerlist.now.sh/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Scammer-List is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A free open source AI based Scam and Spam Finder with a free API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Anti-Spam.

Back to Category Index

ScanCannon

  • Website: https://github.com/johnnyxmas/ScanCannon
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: ScanCannon is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: POSIX-compliant BASH script to quickly enumerate large networks by calling masscan to quickly identify open ports and then nmap to gain details on the systems/services on those 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

scanless

  • Website: https://github.com/vesche/scanless
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: scanless is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Utility for using websites to perform port scans on your behalf so as not to reveal your own IP.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

scapy

  • Website: https://github.com/gpotter2/awesome-scapy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: scapy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scapy: the python-based interactive packet manipulation program & library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

scapy

  • Website: https://github.com/secdev/scapy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: scapy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Python-based interactive packet manipulation program and library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

Scapy

  • Website: https://github.com/secdev/awesome-scapy
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Scapy is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A Python tool and library for low level packet creation and manipulation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

Search Abuseipdb

  • Website: https://github.com/oseasfr/search-abuseipdb
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Search Abuseipdb is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Tool to query IPs, ranges and ASN blocks in AbuseIPDB via API with CIDR notation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

SecApps

  • Website: https://secapps.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SecApps is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: In-browser web application security testing 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: Awesome Penetration Testing > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

SecTools

  • Website: http://sectools.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: SecTools is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Top 125 Network 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 Category Index

Security Ninjas

  • Website: https://hub.docker.com/r/opendns/security-ninjas/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Hacking

What it does: Security Ninjas is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Security > Network > Docker Images for Penetration Testing & Security.

Back to Category Index

SecurityTrails

  • Website: https://securitytrails.com/dns-trails
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: SecurityTrails is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: API to search current and historical DNS records, current and historical WHOIS, technologies used by sites and whois search for phone, email, address, IPs etc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Semantic-Informed Driver Fuzzing Without Both the Hardware Devices and the Emulators, 2022

  • Website: https://www.ndss-symposium.org/wp-content/uploads/2022-345-paper.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Semantic-Informed Driver Fuzzing Without Both the Hardware Devices and the Emulators, 2022 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

Send Hardest Problems My Way: Probabilistic Path Prioritization for Hybrid Fuzzing, 2019

  • Website: https://www.cs.ucr.edu/~heng/pubs/digfuzz_ndss19.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Send Hardest Problems My Way: Probabilistic Path Prioritization for Hybrid Fuzzing, 2019 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

SendMeSpamIDS.py

  • Website: https://github.com/johestephan/VerySimpleHoneypot
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: SendMeSpamIDS.py is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Simple SMTP fetch all IDS and analyzer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Sentinel Visualizer

  • Website: http://www.fmsasg.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Sentinel Visualizer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Social Network Analysis.

Back to Category Index

Shodan

  • Website: https://www.shodan.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome OSINT, Awesome Hacking, Awesome Web Security

What it does: Shodan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Shodan is a search engine for the IOT(Internet of Things) that allows you to search variety of servers that are connected to the internet using various searching filters.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Network device discovery tools.

Back to Category Index

SigPloit

  • Website: https://github.com/SigPloiter/SigPloit
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SigPloit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Signaling security testing framework dedicated to telecom security for researching vulnerabilites in the signaling protocols used in mobile (cellular phone) 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 > Network Tools.

Back to Category Index

SIREN

  • Website: https://github.com/blaverick62/SIREN
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: SIREN is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Semi-Intelligent HoneyPot Network - HoneyNet Intelligent Virtual Environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

skipfish

  • Website: https://www.kali.org/tools/skipfish/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: skipfish is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Performant and adaptable active web application security 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: Awesome Penetration Testing > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

SlowLoris

  • Website: https://github.com/gkbrk/slowloris
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SlowLoris is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: DoS tool that uses low bandwidth on the attacking side.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

Smart Install Exploitation Tool (SIET)

  • Website: https://github.com/Sab0tag3d/SIET
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Smart Install Exploitation Tool (SIET) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Scripts for identifying Cisco Smart Install-enabled switches on a network and then manipulating them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools.

Back to Category Index

smbmap

  • Website: https://github.com/ShawnDEvans/smbmap
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: smbmap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Handy SMB enumeration 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

sniffglue

  • Website: https://github.com/kpcyrd/sniffglue
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: sniffglue is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Secure multithreaded packet sniffer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Protocol Analyzers and Sniffers.

Back to Category Index

Snort

  • Website: https://www.snort.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome OSINT

What it does: Snort is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Snort is a free and open source network intrusion prevention system (NIPS) and network intrusion detection system (NIDS)created by Martin Roesch in 1998. Snort is now developed by Sourcefire, of which Roesch is the founder and CTO. In 2009, Snort entered InfoWorld's Open Source Hall of Fame as one of the "greatest [pieces of] open source software of all 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 Security > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

Snort

  • Website: https://snort.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Snort is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Widely-deployed, Free Software IPS capable of real-time packet analysis, traffic logging, and custom rule-based triggers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

snort

  • Website: https://github.com/snort3/snort3
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: snort is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open Source Intrusion Prevention 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

Spam Scanner

  • Website: https://github.com/spamscanner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Spam Scanner is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Anti-Spam Scanning Service and Anti-Spam API 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 Security > Network > Anti-Spam.

Back to Category Index

SpamAssassin

  • Website: https://spamassassin.apache.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: SpamAssassin is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A powerful and popular email spam filter employing a variety of detection technique.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Anti-Spam.

Back to Category Index

SPARTA

  • Website: https://sparta.secforce.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SPARTA is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Graphical interface offering scriptable, configurable access to existing network infrastructure scanning and enumeration 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 > Network Tools.

Back to Category Index

SQLmate

  • Website: https://github.com/UltimateHackers/sqlmate
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SQLmate is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Friend of sqlmap that identifies SQLi vulnerabilities based on a given dork and (optional) 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Squey

  • Website: https://squey.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Forensics

What it does: Squey is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Logs/PCAP visualization software designed to detect anomalies and weak signals in large amounts of data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Forensics.

Back to Category Index

Squidmagic

  • Website: https://github.com/ch3k1/squidmagic
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: Squidmagic is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: squidmagic is a 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 Malware Analysis > Network.

Back to Category Index

SSH MITM

  • Website: https://github.com/jtesta/ssh-mitm
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: SSH MITM is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Intercept SSH connections with a proxy; all plaintext passwords and sessions are logged to disk.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

ssh-audit

  • Website: https://github.com/jtesta/ssh-audit
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: ssh-audit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: SSH server & client auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Secure Shell Tools.

Back to Category Index

SSHGuard

  • Website: http://www.sshguard.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: SSHGuard is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A software to protect services in addition to SSH, written in C.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

SSLyze

  • Website: https://github.com/nabla-c0d3/sslyze
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: SSLyze is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fast and comprehensive TLS/SSL configuration analyzer to help identify security mis-configurations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Transport Layer Security Tools.

Back to Category Index

Stealth

  • Website: https://fbb-git.gitlab.io/stealth/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Stealth is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: File integrity checker that leaves virtually no sediment. Controller runs from another machine, which makes it hard for an attacker to know that the file system is being checked at defined pseudo random intervals over SSH. Highly recommended for small to medium deployments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

stenographer

  • Website: https://github.com/google/stenographer
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: stenographer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Packet capture solution which aims to quickly spool all packets to disk, then provide simple, fast access to subsets of those packets. It stores as much history as it possible, managing disk usage, and deleting when disk limits are hit. It's ideal for capturing the traffic just before and during an incident, without the need explicit need to store all of the network traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

subbrute

  • Website: https://github.com/TheRook/subbrute
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: subbrute is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: DNS meta-query spider that enumerates DNS records, and subdomains.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Sublist3r

  • Website: https://github.com/aboul3la/Sublist3r
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cyber Security Tools, Awesome Web Security

What it does: Sublist3r is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Sublist3r is a multi-threaded sub-domain enumeration tool for penetration testers 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: Penetration Testing > Information Gathering > Passive Information Gathering.

Back to Category Index

Substation

  • Website: https://github.com/brexhq/substation
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Threat Detection

What it does: Substation is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Substation is a cloud native data pipeline and transformation toolkit 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 Threat Detection and Hunting > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

Suricata

  • Website: http://suricata-ids.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Suricata is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Suricata is a high performance Network IDS, IPS and Network Security Monitoring engine. Open Source and owned by a community run non-profit foundation, the Open Information Security Foundation (OISF). Suricata is developed by the OISF and its supporting vendors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

Suricata

  • Website: https://suricata-ids.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Suricata is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free, cross-platform, IDS/IPS with on- and off-line analysis modes and deep packet inspection capabilities that is also scriptable with Lua.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

sylkie

  • Website: https://dlrobertson.github.io/sylkie/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: sylkie is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Command line tool and library for testing networks for common address spoofing security vulnerabilities in IPv6 networks using the Neighbor Discovery Protocol.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Proxies and Machine-in-the-Middle (MITM) Tools.

Back to Category Index

T-Pot Honeypot Distro

  • Website: http://dtag-dev-sec.github.io/mediator/feature/2017/11/07/t-pot-17.10.html
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: T-Pot Honeypot Distro is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: T-Pot is based on the network installer of Ubuntu Server 16/17.x LTS. The honeypot daemons as well as other support components being used have been containerized using docker. This allows us to run multiple honeypot daemons on the same network interface while maintaining a small footprint and constrain each honeypot within its own environment. Installation over vanilla Ubuntu - - This script will install T-Pot 16.04/17.10 on a fresh Ubuntu 16.04.x LTS (64bit). It is intended to be used on hosted servers, where an Ubuntu base image is given and there is no ability to install custom ISO images. Successfully tested on vanilla Ubuntu 16.04.3 in VMware.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

T50

  • Website: https://gitlab.com/fredericopissarra/t50/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: T50 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Faster network stress 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 > Network Tools > DDoS Tools.

Back to Category Index

Tang

  • Website: https://github.com/latchset/tang
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Tang is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Server for binding data to network presence; provides data to clients only when they are on a certain (secured) network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Policy enforcement.

Back to Category Index

Tcpdump

  • Website: http://www.tcpdump.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing, Awesome Hacking

What it does: Tcpdump is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A powerful command-line packet analyzer; and libpcap, a portable C/C++ library for network traffic capture.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Protocol Analyzers and Sniffers.

Back to Category Index

tcpflow

  • Website: https://github.com/simsong/tcpflow
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: tcpflow is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis and debugging. Each TCP flow is stored in its own file. Thus, the typical TCP flow will be stored in two files, one for each direction. tcpflow can also process stored 'tcpdump' packet flows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Full Packet Capture / Forensic.

Back to Category Index

tcpick

  • Website: http://tcpick.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: tcpick is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Trach and reassemble TCP streams.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

tcpreplay

  • Website: https://tcpreplay.appneta.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: tcpreplay is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Suite of free Open Source utilities for editing and replaying previously captured network traffic originally designed to replay malicious traffic patterns to Intrusion Detection/Prevention 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

tcpxtract

  • Website: http://tcpxtract.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: tcpxtract is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Extract files from network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Network.

Back to Category Index

TerraSigma

  • Website: https://github.com/Khadinxc/TerraSigma
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: TerraSigma is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A repository of all SIGMA rules converted to Microsoft Sentinel Terraform Scheduled analytic resources. The repository runs on a weekly schedule to update the repository and align with the up to date version of the SIGMA rules repository. Proper entity mapping is completed for the rules to ensure the repo is plug-and-play.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

testssl.sh

  • Website: https://github.com/drwetter/testssl.sh
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: testssl.sh is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Command line tool which checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as some cryptographic flaws.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Transport Layer Security Tools.

Back to Category Index

tgcd

  • Website: http://tgcd.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: tgcd is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Simple Unix network utility to extend the accessibility of TCP/IP based network services beyond firewalls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

THC Hydra

  • Website: https://github.com/vanhauser-thc/thc-hydra
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: THC Hydra is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Online password cracking tool with built-in support for many network protocols, including HTTP, SMB, FTP, telnet, ICQ, MySQL, LDAP, IMAP, VNC, 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 > Network Tools.

Back to Category Index

The Art of Network Penetration Testing, 2020

  • Website: https://www.manning.com/books/the-art-of-network-penetration-testing
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: The Art of Network Penetration Testing, 2020 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Category Index

The Practice of Network Security Monitoring

  • Website: https://nostarch.com/nsm
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Forensics

What it does: The Practice of Network Security Monitoring is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Understanding Incident Detection and Response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Books.

Back to Category Index

tinc

  • Website: https://tinc-vpn.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: tinc is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free Software mesh VPN implemented entirely in userspace that supports expandable network space, bridged ethernet segments, 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 Cybersecurity Blue Team > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

TL:DR: VPN leaks users’ IPs via WebRTC. I’ve tested seventy VPN providers and 16 of them leaks users’ IPs via WebRTC (23%)

  • Website: https://voidsec.com/vpn-leak/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Web Security

What it does: TL:DR: VPN leaks users’ IPs via WebRTC. I’ve tested seventy VPN providers and 16 of them leaks users’ IPs via WebRTC (23%) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 Category Index

TLS Beyond the Browser: Combining End Host and Network Data to Understand Application Behavior

  • Website: https://dl.acm.org/doi/pdf/10.1145/3355369.3355601
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: TLS Beyond the Browser: Combining End Host and Network Data to Understand Application Behavior is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Resources > Fingerprinting.

Back to Category Index

TLS Fingerprints

  • Website: https://tlsfingerprint.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: TLS Fingerprints is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: collected from the University of Colorado Boulder campus network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Fingerprinting.

Back to Category Index

tls_prober

  • Website: https://github.com/WestpointLtd/tls_prober
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: tls_prober is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Fingerprint a server's SSL/TLS implementation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Transport Layer Security Tools.

Back to Category Index

tlsmate

  • Website: https://gitlab.com/guballa/tlsmate
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: tlsmate is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Framework to create arbitrary TLS test cases. Comes with a TLS server scanner plugin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Transport Layer Security Tools.

Back to Category Index

Tor

  • Website: https://torproject.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Tor is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Censorship circumvention and anonymizing overlay network providing distributed, cryptographically verified name services (.onion domains) to enhance publisher privacy and service availability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses.

Back to Category Index

TorForge

  • Website: https://github.com/jery0843/torforge
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: TorForge is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Advanced transparent Tor proxy with kernel-level iptables routing, post-quantum encryption (Kyber768), kill switch, steganography mode, and AI-powered circuit selection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > VPN.

Back to Category Index

TraceWrangler

  • Website: https://www.tracewrangler.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: TraceWrangler is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network capture file toolkit that can edit and merge pcap or pcapng files with batch editing 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

Tracexploit

  • Website: https://code.google.com/archive/p/tracexploit/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Tracexploit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Replay network packets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Tsunami

  • Website: https://github.com/google/tsunami-security-scanner
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: Tsunami is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: General purpose network security scanner with an extensible plugin system for detecting high severity vulnerabilities with high confidence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

tsurugi

  • Website: https://tsurugi-linux.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Forensics

What it does: tsurugi is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: heavily customized Linux distribution that designed to support DFIR investigations, malware analysis and OSINT activities. It is based on Ubuntu 20.04(64-bit with a 5.15.12 custom kernel).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Scanning / Pentesting.

Back to Category Index

UFONet

  • Website: https://github.com/epsylon/ufonet
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: UFONet is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Abuses OSI layer 7 HTTP to create/manage 'zombies' and to conduct different attacks using; GET/POST, multithreading, proxies, origin spoofing methods, cache evasion techniques, etc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > DDoS Tools.

Back to Category Index

Unfetter

  • Website: https://github.com/unfetter-analytic/unfetter
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Unfetter is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: A reference implementation provides a framework for collecting events (process creation, network connections, Window Event Logs, etc.) from a client machine and performing CAR analytics to detect potential adversary activity.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Use Python & Pandas to Create a D3 Force Directed Network Diagram

  • Website: http://www.austintaylor.io/d3/python/pandas/2016/02/01/create-d3-chart-python-force-directed/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Use Python & Pandas to Create a D3 Force Directed Network Diagram is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Resources.

Back to Category Index

VAST

  • Website: https://github.com/tenzir/vast
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: VAST is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source security data pipeline engine for structured event data, supporting high-volume telemetry ingestion, compaction, and retrieval; purpose-built for security content execution, guided threat hunting, and large-scale investigation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

VesselFinder

  • Website: https://www.vesselfinder.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: VesselFinder is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: a FREE AIS vessel tracking web site. VesselFinder displays real time ship positions and marine traffic detected by global AIS network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Maritime.

Back to Category Index

VirusBay

  • Website: https://beta.virusbay.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Malware Analysis

What it does: VirusBay is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Community-Based malware repository and social network.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Malware Collection > Malware Corpora.

Back to Category Index

Visual Investigative Scenarios

  • Website: https://vis.occrp.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Visual Investigative Scenarios is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Social Network Analysis.

Back to Category Index

Vulnerability as a service: Heartbleed

  • Website: https://hub.docker.com/r/hmlio/vaas-cve-2014-0160/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: Vulnerability as a service: Heartbleed is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

Vulnerability as a service: Shellshock

  • Website: https://hub.docker.com/r/hmlio/vaas-cve-2014-6271/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: Vulnerability as a service: Shellshock is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

Vulnerable WordPress Installation

  • Website: https://hub.docker.com/r/wpscanteam/vulnerablewordpress/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: Vulnerable WordPress Installation is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > Intentionally Vulnerable Systems > Intentionally Vulnerable Systems as Docker Containers.

Back to Category Index

VulnHub

  • Website: https://www.vulnhub.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome CTF

What it does: VulnHub is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: VM-based for practical in digital security, computer application & network administration.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Vuls

  • Website: https://github.com/future-architect/vuls
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Vuls is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Agentless vulnerability scanner for GNU/Linux and FreeBSD, 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 > Network Vulnerability Scanners.

Back to Category Index

Vuzzer: Application-aware evolutionary fuzzing, 2017

  • Website: https://www.ndss-symposium.org/ndss2017/ndss-2017-programme/vuzzer-application-aware-evolutionary-fuzzing/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: Vuzzer: Application-aware evolutionary fuzzing, 2017 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

w3af

  • Website: https://github.com/andresriancho/w3af
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: w3af is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Web application attack and audit 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Wapiti

  • Website: http://wapiti.sourceforge.net/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Wapiti is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Black box web application vulnerability scanner with built-in 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

wazuh

  • Website: https://github.com/wazuh/wazuh
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Threat Detection

What it does: wazuh is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Wazuh is a free and open source XDR platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. Great tool foor all kind of deployments, it includes SIEM capabitilies (indexing + searching + WUI).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Security Information & Event Management.

Back to Category Index

WebReaver

  • Website: https://www.webreaver.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: WebReaver is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Commercial, graphical web application vulnerability scanner designed 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

What You Corrupt Is Not What You Crash: Challenges in Fuzzing Embedded Devices, 2018

  • Website: http://s3.eurecom.fr/docs/ndss18_muench.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: What You Corrupt Is Not What You Crash: Challenges in Fuzzing Embedded Devices, 2018 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

WhoisDomBot

  • Website: https://t.me/WhoisDomBot
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: WhoisDomBot is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Whois lookup for domains/IPs + dig/trace.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Wifi Jammer

  • Website: https://n0where.net/wifijammer/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Hacking

What it does: Wifi Jammer is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Free program to jam all wifi clients in range.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Network > Tools.

Back to Category Index

WiFi Pineapple

  • Website: https://www.wifipineapple.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: WiFi Pineapple is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Wireless auditing and penetration 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: Awesome Penetration Testing > Network Tools > Wireless Network Tools.

Back to Category Index

wifi-arsenal

  • Website: https://github.com/0x90/wifi-arsenal
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: wifi-arsenal is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Resources for Wi-Fi Pentesting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Wireless Network Tools.

Back to Category Index

WiFi-Pumpkin

  • Website: https://github.com/P0cL4bs/WiFi-Pumpkin
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: WiFi-Pumpkin is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Framework for rogue Wi-Fi access point 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: Awesome Penetration Testing > Network Tools > Wireless Network Tools.

Back to Category Index

Wifite

  • Website: https://github.com/derv82/wifite
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Wifite is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Automated wireless attack 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 > Network Tools > Wireless Network Tools.

Back to Category Index

WINNIE : Fuzzing Windows Applications with Harness Synthesis and Fast Cloning, 2021

  • Website: https://taesoo.kim/pubs/2021/jung:winnie.pdf
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Fuzzing

What it does: WINNIE : Fuzzing Windows Applications with Harness Synthesis and Fast Cloning, 2021 is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > The Network and Distributed System Security Symposium (NDSS).

Back to Category Index

WireEdit

  • Website: https://wireedit.com/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: WireEdit is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Full stack WYSIWYG pcap editor (requires a free license to edit packets).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Traffic Replay and Editing Tools.

Back to Category Index

wireshark

  • Website: https://www.wireshark.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Cybersecurity Blue Team, Awesome Penetration Testing, Awesome Cyber Security Tools, Awesome Hacking, Awesome CTF, Awesome Forensics

What it does: wireshark is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Wireshark is a free and open-source packet analyzer. It is used for network troubleshooting, analysis, software and communications protocol development, and education. Wireshark is very similar to tcpdump, but has a graphical front-end, plus some integrated sorting and filtering options.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

Wireshark Extensions

  • Website: https://www.honeynet.org/project/WiresharkExtensions
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Honeypots

What it does: Wireshark Extensions is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Apply Snort IDS rules and signatures against packet capture files using Wireshark.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

WPScan

  • Website: https://wpscan.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: WPScan is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Black box WordPress vulnerability scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Vulnerability Scanners > Web Vulnerability Scanners.

Back to Category Index

Wynyard Group

  • Website: https://wynyardgroup.com
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: Wynyard Group is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. 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 > ↑ Social Network Analysis.

Back to Category Index

Xplico

  • Website: http://www.xplico.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security

What it does: Xplico is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: The goal of Xplico is extract from an internet traffic capture the applications data contained. For example, from a pcap file Xplico extracts each email (POP, IMAP, and SMTP protocols), all HTTP contents, each VoIP call (SIP), FTP, TFTP, and so on. Xplico isn’t a network protocol analyzer. Xplico is an open source Network Forensic Analysis Tool (NFAT).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Full Packet Capture / Forensic.

Back to Category Index

Zarp

  • Website: https://github.com/hatRiot/zarp
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing

What it does: Zarp is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Network attack tool centered around the exploitation of local 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 > Network Tools.

Back to Category Index

Zeek

  • Website: https://zeek.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: Zeek is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Zeek is a powerful network analysis framework that is much different from the typical IDS you may know.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

Zeek

  • Website: https://github.com/zeek/zeek
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Zeek is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: (formerly Bro) - A network security monitoring 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 Threat Detection and Hunting > Tools > Network Monitoring.

Back to Category Index

Zeek

  • Website: https://www.zeek.org
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome CTF

What it does: Zeek is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An open-source network security monitor.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Networking.

Back to Category Index

Zeek Analysis Tools (ZAT)

  • Website: https://github.com/SuperCowPowers/zat
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Threat Detection

What it does: Zeek Analysis Tools (ZAT) is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Processing and analysis of Zeek network data with Pandas, scikit-learn, Kafka and Spark.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

zeek2es

  • Website: https://github.com/corelight/zeek2es
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Security, Awesome Threat Detection

What it does: zeek2es is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: An open source tool to convert Zeek logs to Elastic/OpenSearch. You can also output pure JSON from Zeek's TSV logs!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

zmap

  • Website: https://zmap.io/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: zmap is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Open source network scanner that enables researchers to easily perform Internet-wide network studies.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

ZoomEye

  • Website: https://www.zoomeye.org/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: ZoomEye is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: Search engine for cyberspace that lets the user find specific network components.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Network device discovery tools.

Back to Category Index

ZoomEye

  • Website: https://www.zoomeye.ai/
  • Model: Open Source
  • Category: Network Security Monitoring
  • Source Lists: Awesome OSINT

What it does: ZoomEye is used in network security monitoring programs to support traffic inspection, anomaly detection, and packet-level investigations. Source summaries describe it as: ZoomEye is a cyberspace search engine for IPs, domains, internet asset discovery, and exposure analysis of servers, routers, and webcams.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

OSINT & Reconnaissance

This category contains 1254 documented tools. It focuses on capabilities used for asset discovery, external exposure mapping, and intelligence collection. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

0bin

  • Website: https://0bin.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 0bin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

192 (UK)

  • Website: http://www.192.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 192 (UK) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search by person, business, address. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

1st Headlines

  • Website: http://www.1stheadlines.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 1st Headlines is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

  • Website: http://www.2lingual.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 2lingual Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

411 (US)

  • Website: http://www.411.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 411 (US) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search by person, phone number, address, and business. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

  • Website: https://4chansearch.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: 4chan Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

A penetration tester’s guide to sub-domain enumeration

  • Website: https://blog.appsecco.com/a-penetration-testers-guide-to-sub-domain-enumeration-7d842d5570f6
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: A penetration tester’s guide to sub-domain enumeration is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Sub Domain Enumeration.

Back to Category Index

aa419 Fake Sites Database

  • Website: https://db.aa419.org/fakebankslist.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: aa419 Fake Sites Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The site lists fraudulent websites, such as fake banks and online scams, identified by the Artists Against 419 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

aadinternals

  • Website: https://aadinternals.com/osint
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: aadinternals is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Provides tools and insights for advanced analysis and security testing of Azure Active Directory (AAD) and Microsoft 365.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Abine

  • Website: https://www.abine.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Abine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Abusech

  • Website: https://hunting.abuse.ch
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Abusech is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Hunt across all abuse.ch platforms with one simple query.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Academia

  • Website: http://academia.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Academia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a platform for sharing academic research.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Expert Search.

Back to Category Index

Academia

  • Website: https://www.academia.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Academia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Academic Journals

  • Website: http://www.academicjournals.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Academic Journals is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Accuranker

  • Website: https://www.accuranker.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Accuranker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Adium

  • Website: https://adium.im
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Adium is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Aeon

  • Website: http://www.aeontimeline.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Aeon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

African Journal Online

  • Website: http://www.ajol.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: African Journal Online is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is the world's largest and preeminent platform of African-published scholarly journals.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Agence France-Presse (AFP)

  • Website: http://www.afp.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Agence France-Presse (AFP) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

AgentFNS_Bot

  • Website: https://t.me/AgentFNS_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AgentFNS_Bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free instant counterparty check using official data (INN/OGRN).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

AGOA Data Center

  • Website: http://agoa.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AGOA Data Center is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Ahmia

  • Website: https://ahmia.fi
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ahmia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Dark Web Search Engines.

Back to Category Index

ahrefs

  • Website: https://ahrefs.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ahrefs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A tool for backlink research, organic traffic research, keyword research, content marketing & 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

AidData

  • Website: http://aiddata.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AidData is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

  • Website: https://open-search.aleph-networks.eu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Aleph Open Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Dark Web Search Engines.

Back to Category Index

All-in-One

  • Website: http://all-io.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: All-in-One is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

Alleba (Philippines)

  • Website: http://www.alleba.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Alleba (Philippines) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Philippines search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Main National Search Engines.

Back to Category Index

  • Website: http://www.allstocks.com/links
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AllStocksLinks is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

AllTheInternet

  • Website: http://www.alltheinternet.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AllTheInternet is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

Alltop

  • Website: http://alltop.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Alltop is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

AllYouCanRead

  • Website: http://www.allyoucanread.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AllYouCanRead is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

American Society of Civil Engineers

  • Website: http://ascelibrary.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: American Society of Civil Engineers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

AnalyzeID

  • Website: https://analyzeid.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AnalyzeID is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find Other Websites Owned By The Same Person.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Code Search.

Back to Category Index

Ancestry

  • Website: http://www.ancestry.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ancestry is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Premium data, free trial with credit card.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Answers.com

  • Website: http://www.answers.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Answers.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Aol

  • Website: https://search.aol.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Aol is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The web for America.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

AP

  • Website: http://hosted.ap.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AP is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Apify's Google Maps Scraper

  • Website: https://apify.com/compass/crawler-google-places
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Apify's Google Maps Scraper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Apollo.io

  • Website: https://www.apollo.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Apollo.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free B2B Phone Number & Email Finder. 1200 credits per user/year for free plan.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

APT Groups and Operations

  • Website: https://docs.google.com/spreadsheets/u/0/d/1H9_xaxQHpWaa4O_Son4Gx0YOIzlcBWMsdvePFX68EKU/pubhtml?pli=1#
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: APT Groups and Operations is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Know about Threat Actors, sponsored countries, their tools, methods, etc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

APTWiki

  • Website: https://apt.threatradar.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: APTWiki is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Historical wiki with 214 actor entries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Arbor.js

  • Website: http://arborjs.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Arbor.js is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

ArcGIS

  • Website: https://livingatlas.arcgis.com/en/browse/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ArcGIS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Archive.is

  • Website: http://archive.is
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Archive.is is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that allows you to archive a snapshot of you websites that will always remains online evenif the original page disappears.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Web History and Website Capture.

Back to Category Index

Arctic Shift

  • Website: https://github.com/ArthurHeitmann/arctic_shift
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Arctic Shift is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A tool for accessing and interacting with large dumps of Reddit data, offering an API and web interface for research and moderation purposes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

ArkhamMirror

  • Website: https://github.com/mantisfury/ArkhamMirror
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ArkhamMirror is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Local-first AI document intelligence with offline RAG, contradiction detection, knowledge graphs, and vision AI table 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 OSINT > ↑ Other Tools.

Back to Category Index

Ask

  • Website: https://www.ask.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ask is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Ask something and get a answer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Ask

  • Website: http://www.ask.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ask is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Atlas

  • Website: https://atlas.co
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Atlas is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Atlasify

  • Website: http://www.atlasify.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Atlasify is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Atom

  • Website: https://browser.ru/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Atom is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Audiense

  • Website: https://www.audiense.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Audiense is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool to identify relevant audience, discover actionable insights and inform strategies to grow your business.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

AVinfoBot

  • Website: https://t.me/AVskp_Bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AVinfoBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Used-car history via plate/VIN/phone.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

avtocodbot

  • Website: https://t.me/avtocodbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: avtocodbot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paid VIN/plate lookup.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

avtogram_bot

  • Website: https://telegram.me/ABTOGRAMBOT
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: avtogram_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paid car reports (VIN/plate): accidents, fines, liens.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

AvtoNomer

  • Website: https://t.me/avtonomerbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AvtoNomer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Finds vehicle photos by plate via platesmania.com.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Aware-online.com

  • Website: https://www.aware-online.com/en/osint-tools
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Aware-online.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Curated collection of OSINT tools and methodologies for investigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Resources.

Back to Category Index

Awasu

  • Website: http://www.awasu.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Awasu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

AWS Public Datasets

  • Website: http://aws.amazon.com/datasets
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: AWS Public Datasets is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Azure Tenant Resolution by PingCastle

  • Website: https://tenantresolution.pingcastle.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Azure Tenant Resolution by PingCastle is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for Azure Tenant using its domain name or its ID.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Baidu (China)

  • Website: http://www.baidu.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Baidu (China) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The major search engine used in China.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Main National Search Engines.

Back to Category Index

Baidu Images

  • Website: https://image.baidu.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Baidu Images is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Baidu Maps

  • Website: https://map.baidu.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Baidu Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Bank for International Settlements Statistics

  • Website: http://www.bis.org/statistics/index.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bank for International Settlements Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Barcode Reader

  • Website: http://online-barcode-reader.inliteresearch.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Barcode Reader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Decode barcodes in C#, VB, Java, C\C++, Delphi, PHP and other languages.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Barkov.net

  • Website: http://vk.barkov.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Barkov.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

Base

  • Website: http://www.base-search.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Base is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Batchgeo

  • Website: http://batchgeo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Batchgeo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Beaker

  • Website: http://beakernotebook.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Beaker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

BeanPaste

  • Website: https://beanpaste.fun/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BeanPaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A tiny way to share text.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

BeenVerified

  • Website: https://www.backgroundchecks.com/solutions/beenverified
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BeenVerified is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ People Investigations.

Back to Category Index

Befunky

  • Website: https://www.befunky.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Befunky is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Bellingcat

  • Website: https://www.bellingcat.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bellingcat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Bellingcat Online Researcher Survey: Tool Wishes

  • Website: https://docs.google.com/spreadsheets/d/1vNJRMrlwI7i06diBJtRJWrvt4YuPOqlbUV5o00P_YmE/edit#gid=1378107220
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bellingcat Online Researcher Survey: Tool Wishes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Wishlist of OSINT tools from a February Bellingcat survey.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Resources.

Back to Category Index

Bellingcat's Online Investigation Toolkit

  • Website: http://bit.ly/bcattools
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bellingcat's Online Investigation Toolkit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Other Resources.

Back to Category Index

Bendobrown

  • Website: https://www.youtube.com/c/Bendobrown
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bendobrown is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Videos.

Back to Category Index

Berkely Library: Data Lab

  • Website: http://www.lib.berkeley.edu/libraries/data-lab
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Berkely Library: Data Lab is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Betaface

  • Website: https://www.betaface.com/demo.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Betaface is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Better Business Bureau

  • Website: http://www.bbb.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Better Business Bureau is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

BeVigil

  • Website: https://bevigil.com/search
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BeVigil is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for assets like Subdomains, URLs, Parameters in mobile 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

BeVigil-CLI

  • Website: https://github.com/Bevigil/BeVigil-OSINT-CLI
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BeVigil-CLI is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A unified command line interface and python library for using BeVigil OSINT API to search for assets such as subdomains, URLs, applications indexed from mobile 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 OSINT > ↑ Other Tools.

Back to Category Index

Beyond

  • Website: http://www.beyond.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Beyond is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Bi.Zone

  • Website: https://gti.bi.zone/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bi.Zone is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: 148 threat groups with detailed TTPs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Bibsonomy

  • Website: http://www.bibsonomy.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bibsonomy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Bing

  • Website: https://www.bing.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bing is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Microsoft´s search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Bing Images

  • Website: https://www.bing.com/images
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bing Images is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Bing Maps

  • Website: http://www.bing.com/maps
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bing Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Bing Videos

  • Website: http://www.bing.com/?scope=video
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bing Videos is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Bing Webmaster Tools

  • Website: http://www.bing.com/toolbox/webmaster
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bing Webmaster Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

BinGoo

  • Website: https://github.com/Hood3dRob1n/BinGoo
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: BinGoo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: GNU/Linux bash based Bing and Google Dorking 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

Bitdefender Threat Map

  • Website: https://threatmap.bitdefender.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bitdefender Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Cyberthreat Real Time Map by Bitdefender.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Bitwarden

  • Website: https://bitwarden.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bitwarden is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Open-source password manager with cross-platform support.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Bizeurope

  • Website: http://www.bizeurope.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bizeurope is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Bizint

  • Website: http://www.bizint.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bizint is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Biznar

  • Website: http://biznar.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Biznar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Blackbird

  • Website: https://github.com/p1ngul1n0/blackbird
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Blackbird is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for accounts associated with a given email across various platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Blacklist Checker

  • Website: https://blacklistchecker.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Blacklist Checker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Blacklist Checker is anemail blacklist checker, monitor and API that checks 100+ blacklists in seconds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

BlackWidow

  • Website: http://softbytelabs.com/wp/blackwidow/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BlackWidow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web History and Website Capture.

Back to Category Index

BlindElephant

  • Website: http://blindelephant.sourceforge.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: BlindElephant is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Web application fingerprinter.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

Bloomberg

  • Website: http://www.bloomberg.com/research/company/overview/overview.asp
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bloomberg is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

bmi_np_bot

  • Website: https://t.me/MNProbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: bmi_np_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Identifies phone-number operator and basic info.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Boardreader

  • Website: http://boardreader.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Boardreader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

Bottlenose

  • Website: http://bottlenose.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bottlenose is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

boxcryptor

  • Website: https://www.boxcryptor.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: boxcryptor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

BP Statistical Review of World Energy

  • Website: http://www.bp.com/en/global/corporate/energy-economics/statistical-review-of-world-energy.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BP Statistical Review of World Energy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

bpaste

  • Website: https://bpa.st/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: bpaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Welcome to bpaste, this site is a pastebin. It allows you to share code with others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Brandwatch

  • Website: https://www.brandwatch.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Brandwatch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Brave

  • Website: https://search.brave.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Brave is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a private, independent, and transparent search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Brave

  • Website: https://brave.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Brave is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an open-source web browser that allows you to completely block ads and website trackers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Browsers.

Back to Category Index

BreachHQ

  • Website: https://breach-hq.com/threat-actors
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BreachHQ is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Provides a list of all known cyber threat actors also referred to as malicious actors, APT groups or hackers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Bridge.Leslibres

  • Website: https://bridge.leslibres.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bridge.Leslibres is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Bridge.Suumitsu

  • Website: https://bridge.suumitsu.eu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bridge.Suumitsu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

BrightCloud

  • Website: https://brightcloud.com/tools/url-ip-lookup.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BrightCloud is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Checks the reputation, category, and potential threats associated with a URL or IP address.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Bromite

  • Website: https://www.bromite.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bromite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Bromite is a Chromium fork with ad blocking and enhanced privacy; take back your browser. Works only on 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: Awesome OSINT > ↑ Browsers.

Back to Category Index

Browserleaks

  • Website: https://browserleaks.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Browserleaks is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: BrowserLeaks tests your browser for privacy and fingerprinting 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

Buffer

  • Website: https://buffer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Buffer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Built With Flarum

  • Website: https://builtwithflarum.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Built With Flarum is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

BuiltWith

  • Website: http://builtwith.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BuiltWith is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that will help you find out all the technologies used to build a particular 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

BunkerWeb Live Cyber Attack Threat Map

  • Website: https://threatmap.bunkerweb.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: BunkerWeb Live Cyber Attack Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Live cyber attack blocked by BunkerWeb, the open source and next generation Web Application Firewall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Bureau Van Dijk

  • Website: http://www.bvdinfo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Bureau Van Dijk is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Business Source

  • Website: https://www.ebscohost.com/academic/business-source-complete
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Business Source is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Buzz sumo

  • Website: http://buzzsumo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Buzz sumo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: "Use our content insights to generate ideas, create high-performing content, monitor your performance and identify influencers.".

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

CachedView

  • Website: http://cachedview.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CachedView is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web History and Website Capture.

Back to Category Index

Cacoo

  • Website: https://cacoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cacoo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

CallerID Test

  • Website: https://calleridtest.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CallerID Test is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Get caller ID and telco carrier information back from a phone number.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

CampusCareerCenter

  • Website: http://www.campuscareercenter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CampusCareerCenter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Canada411

  • Website: http://www.canada411.ca
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Canada411 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search by person, phone number, and business. Free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Canadian Business Research

  • Website: https://www.canada.ca/en/services/business/research.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Canadian Business Research is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Canva

  • Website: https://www.canva.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Canva is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Captin Fact

  • Website: https://captainfact.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Captin Fact is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Fact Checking.

Back to Category Index

CareerBuilder

  • Website: http://www.careerbuilder.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CareerBuilder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Carrot2

  • Website: https://search.carrot2.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Carrot2 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Organizes your search results into topics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Visual Search and Clustering Search Engines.

Back to Category Index

CartoDB

  • Website: https://cartodb.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CartoDB is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Caselaw Access Project

  • Website: https://case.law/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Caselaw Access Project is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Collection of full text of historical (not up-to-date) cases from United States state appellate courts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

CashedPages

  • Website: http://www.cachedpages.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CashedPages is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web History and Website Capture.

Back to Category Index

Castrick

  • Website: https://castrickclues.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Castrick is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find social media accounts with email, username and phone number.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

CCleaner

  • Website: https://www.piriform.com/ccleaner
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CCleaner is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

CCTV

  • Website: https://github.com/IvanGlinkin/CCTV
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CCTV is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Close-Circuit Telegram Vision revolutionizes location tracking with its open-source design and Telegram API integration. Offering precise tracking within 50-100 meters, users can monitor others in real-time for logistics or safety, redefining how we navigate our surroundings.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Censys

  • Website: https://search.censys.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Censys is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searcher that monitors and analyzes devices.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Censys

  • Website: https://censys.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: Censys is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Censys is a search engine that allows computer scientists to ask questions about the devices and networks that compose the Internet 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

CentBrowser

  • Website: http://www.centbrowser.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CentBrowser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

CentOS Pastebin Service

  • Website: https://paste.centos.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CentOS Pastebin Service is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Stikked is an Open-Source PHP Pastebin, with the aim of keeping a simple and easy to use user interface.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Central Ops

  • Website: http://centralops.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Central Ops is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

CEPII

  • Website: http://www.cepii.fr/CEPII/en/welcome.asp
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CEPII is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

ChangeDetect

  • Website: http://www.changedetect.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ChangeDetect is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

ChangeDetection

  • Website: http://www.changedetection.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ChangeDetection is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

ChangeDetection.io

  • Website: https://changedetection.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ChangeDetection.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

ChangeDetection.io Open Source

  • Website: https://github.com/dgtlmoon/changedetection.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ChangeDetection.io Open Source is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Chart.js

  • Website: http://www.chartjs.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Chart.js is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a javascript library that allows you to create charts easly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

chartblocks

  • Website: http://www.chartblocks.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: chartblocks is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

ChatSearchRobot

  • Website: https://t.me/ChatSearchRobot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ChatSearchRobot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Finds chats with similar topics; 709k+ VK chats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Chatsecure

  • Website: https://chatsecure.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Chatsecure is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Check

  • Website: https://meedan.com/check
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Fact Checking.

Back to Category Index

Check Point Live Cyber Threat Map

  • Website: https://threatmap.checkpoint.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Check Point Live Cyber Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Explore the top cyber threats of 2025, including ransomware, infostealers, and cloud vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

CheckUser

  • Website: https://checkuser.vercel.app/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CheckUser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: search username across social 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 OSINT > ↑ Username Check.

Back to Category Index

Chrome

  • Website: https://www.google.com/chrome
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Chrome is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Cipherstick

  • Website: https://cipherstick.tech
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cipherstick is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free OSINT Puzzles - No Account Needed!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Resources.

Back to Category Index

Circos

  • Website: http://circos.ca
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Circos is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Cisco Talos Intelligence

  • Website: https://talosintelligence.com/reputation_center
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cisco Talos Intelligence is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: IP and Domain Reputation Center for real-time threat detection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Cisco Talos Intelligence

  • Website: https://talosintelligence.com/ebc_spam
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cisco Talos Intelligence is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

CiteSeerX

  • Website: http://citeseer.ist.psu.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CiteSeerX is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

cl1p

  • Website: https://Cl1p.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: cl1p is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The Internet Clipboard.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Clarify

  • Website: https://clarify.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Clarify is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Clarify

  • Website: http://clarify.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Clarify is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Classmates

  • Website: http://www.classmates.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Classmates is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: High-school focused people search. Free acounts allow creating a profile and viewing other members. Premium account required to contact other 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: Awesome OSINT > ↑ People Investigations.

Back to Category Index

ClerkBot

  • Website: https://t.me/clerksecretbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ClerkBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Phone + username lookup; vehicle info.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Clip Blast

  • Website: http://www.clipblast.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Clip Blast is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Cloudflare Radar

  • Website: https://radar.cloudflare.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cloudflare Radar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Internet traffic patterns, attacks, and technology trends.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Clustermaps

  • Website: https://clustrmaps.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Clustermaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find people and address information associated with them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

CNN

  • Website: http://edition.cnn.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CNN is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Code Finder

  • Website: https://codefinder.dev/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Code Finder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The ultimate search engine for finding GitHub 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 OSINT > ↑ Code Search.

Back to Category Index

College Recruiter

  • Website: https://www.collegerecruiter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: College Recruiter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Colorbrewer

  • Website: http://colorbrewer2.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Colorbrewer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Columbus Project

  • Website: https://github.com/elmasy-com/columbus
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Columbus Project is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Columbus Project is an advanced subdomain discovery service with fast, powerful and easy to use API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ DNS.

Back to Category Index

commie

  • Website: https://commie.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: commie is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: commie is a pastebin script with line commenting support.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Comodo Dragon

  • Website: https://www.comodo.com/home/browsers-toolbars/browser.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Comodo Dragon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Company Registration Round the World

  • Website: http://www.commercial-register.sg.ch/home/worldwide.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Company Registration Round the World is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Company Research Resources by Country Comparably

  • Website: https://www.comparably.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Company Research Resources by Country Comparably is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

CompeteShark

  • Website: http://competeshark.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CompeteShark is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

ContactOut

  • Website: https://contactout.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ContactOut is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Unlock the world's most accurate contact data. Find emails & phone for 300M 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 OSINT > ↑ People Investigations.

Back to Category Index

Context

  • Website: https://ctxt.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Context is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Share whatever you see with others in seconds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

ControlC Pastebin

  • Website: https://Controlc.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ControlC Pastebin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The easiest way to host your text.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Coowon

  • Website: http://coowon.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Coowon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Core

  • Website: https://core.ac.uk/search
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Core is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Corporate Information

  • Website: http://www.corporateinformation.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Corporate Information is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Aggregated information from publicly available sources on publicly traded companies worldwide.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

CorporationWiki

  • Website: https://www.corporationwiki.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CorporationWiki is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Craiglist

  • Website: http://losangeles.craigslist.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Craiglist is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

creately

  • Website: http://creately.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: creately is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

creationdatebot

  • Website: https://t.me/creationdatebot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: creationdatebot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Approx. Telegram account creation date.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

CredenShow

  • Website: https://credenshow.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CredenShow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Identify your compromised credentials before others do.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

creepy

  • Website: https://github.com/ilektrojohn/creepy
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: creepy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Geolocation OSINT 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Crossfilter

  • Website: http://square.github.io/crossfilter
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Crossfilter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

CrowdMap

  • Website: https://crowdmap.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CrowdMap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

CrunchBase

  • Website: http://www.crunchbase.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CrunchBase is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Business information database, with a focus on investment, acquisition, and executive data. Ancillary focus on market research and connecting founders and investors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

CrunchBase

  • Website: https://www.crunchbase.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CrunchBase is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Detailed information on startup businesses, with a specific focus on funding sources and funding procedures used by specific businesses.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

Cryptobin

  • Website: https://cryptobin.co/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cryptobin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The Ultimate Secure Pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

CryptoBot

  • Website: https://t.me/CryptoBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CryptoBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Anonymous crypto wallet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

csvkit

  • Website: https://github.com/wireservice/csvkit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: csvkit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

CTLRQ Address Lookup

  • Website: https://ctrlq.org/maps/address
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CTLRQ Address Lookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Cupidcr4wl

  • Website: https://github.com/OSINTI4L/cupidcr4wl
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cupidcr4wl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Username and phone number search tool that crawls adult content platforms to see if a targeted account or person is present.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Cutapaste

  • Website: https://cutapaste.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cutapaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Short Code and Share.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

CVFox

  • Website: http://www.cvfox.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: CVFox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Cyber Alert

  • Website: http://www.cyberalert.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cyber Alert is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Cyberbro

  • Website: https://github.com/stanfrbd/cyberbro
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cyberbro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A self-hosted application, available as a Dockerized, for effortless searching and reputation checking of observables. Extracts IoCs from raw input and check their reputation using multiple services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Cybergeist

  • Website: https://cybergeist.io/threat-actor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cybergeist is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Cybergeist.io generates intelligence profiles about key threats and threat context that is actively being discussed and reported upon across the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Cyotek WebCopy

  • Website: http://www.cyotek.com/cyotek-webcopy
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Cyotek WebCopy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a free tool for automatically downloading the content of a website onto your local device.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Offline Browsing.

Back to Category Index

D3js

  • Website: https://d3js.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: D3js is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a powerful data visualization javascript library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

DailyEarth

  • Website: http://dailyearth.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DailyEarth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

DailyMotion

  • Website: http://www.dailymotion.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DailyMotion is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Dark Web Informer

  • Website: https://darkwebinformer.com/threat-actor-database/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dark Web Informer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tracking 854 Threat Actors as of 29th of May 2025.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Data Visualization Catalogue

  • Website: http://datavizcatalogue.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Data Visualization Catalogue is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Data.com Connect

  • Website: https://connect.data.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Data.com Connect is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Data.gov.uk

  • Website: https://data.gov.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Data.gov.uk is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Databases - start.me

  • Website: https://start.me/p/QRENnO/databases
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: Databases - start.me is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Various databases which you can use for your OSINT research 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

DataSploit

  • Website: https://github.com/upgoingstar/datasploit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: DataSploit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT visualizer utilizing Shodan, Censys, Clearbit, EmailHunter, FullContact, and Zoomeye behind the scenes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Datasploit

  • Website: https://github.com/DataSploit/datasploit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Datasploit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool to perform various OSINT techniques on usernames, emails addresses, and domains.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Datawrapper

  • Website: https://datawrapper.de
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Datawrapper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

datXpert

  • Website: https://telegram.me/datxpertbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: datXpert is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Leak search via IntelX.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Daum (South Korea)

  • Website: https://www.daum.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Daum (South Korea) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

DBPedia

  • Website: http://wiki.dbpedia.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DBPedia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

dCallsBot

  • Website: https://t.me/dCallsBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: dCallsBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Anonymous calls, masking, eSIM/DID.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

de digger

  • Website: https://www.dedigger.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: de digger is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that allows you to find any types of files that are publicly available in a Google Drive.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ File Search.

Back to Category Index

Dedicated or Not

  • Website: http://dedicatedornot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dedicated or Not is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Defuse

  • Website: https://defuse.ca/pastebin.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Defuse is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Encrypted Pastebin - Keep your data private and secure!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

DeHashed

  • Website: https://dehashed.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DeHashed is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: DeHashed helps prevent ATO with our extensive data set & breach notification solution. Match employee and consumer logins against the world’s largest repository of aggregated publicly available assets leaked from third-party breaches. Secure passwords before criminals can abuse stolen information, and protect your enterprise.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Dehashed CLI

  • Website: https://github.com/hmaverickadams/DeHashed-API-Tool
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dehashed CLI is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Command-line tool for searching breach databases via DeHashed API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Deltafeed

  • Website: http://bitreading.com/deltafeed
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Deltafeed is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Depix

  • Website: https://github.com/beurtschipper/Depix
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Depix is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for recovering passwords from pixelized screenshots (by de-pixelating text).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Detectiva

  • Website: http://detectiva.link/rezervBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Detectiva is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Phone/email lookup with 6 search types.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Deturl

  • Website: http://deturl.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Deturl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Download a YouTube video from any web page.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Dice

  • Website: http://www.dice.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dice is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

DiffChecker

  • Website: https://www.diffchecker.com/image-diff/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DiffChecker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

DiggReader

  • Website: http://digg.com/login?next=%2Freader
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DiggReader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

digiKam

  • Website: https://www.digikam.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: digiKam is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Digital Footprint Check

  • Website: https://www.digitalfootprintcheck.com/free-checker.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Digital Footprint Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Check for registered username on 100s of sites for free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Disconnect

  • Website: https://disconnect.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Disconnect is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

  • Website: https://search.disconnect.me/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Disconnect Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Stop search engines from tracking your searches.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Discord Sensor

  • Website: https://telegram.me/discordsensorbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Discord Sensor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Retrieves Discord account data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Discoshell

  • Website: https://github.com/foozzi/discoshell
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Discoshell is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A simple discovery script that uses popular tools like subfinder, amass, puredns, alterx, massdns and others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

DNS History

  • Website: https://completedns.com/dns-history/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DNS History is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

DNSStuff

  • Website: http://www.dnsstuff.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DNSStuff is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

DNSViz

  • Website: http://dnsviz.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DNSViz is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Do Not Track

  • Website: http://donottrack.us
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Do Not Track is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

DocumentCloud

  • Website: https://www.documentcloud.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DocumentCloud is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Platform for analyzing, annotating, and publishing documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Document and Slides Search.

Back to Category Index

Dolphin Radar

  • Website: https://www.dolphinradar.com/web-viewer-for-instagram
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dolphin Radar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An Instagram Post Viewer lets you view posts, stories, and profiles from public accounts with ease. Free viewer limit: 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 OSINT > Social Media Tools > ↑ Instagram.

Back to Category Index

Domain Crawler

  • Website: http://www.domaincrawler.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Domain Crawler is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Domain Dossier

  • Website: http://centralops.net/co/DomainDossier.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Domain Dossier is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Domain Tools

  • Website: http://whois.domaintools.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Domain Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Whois lookup and domain/ip historical data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

domain_analyzer

  • Website: https://github.com/eldraco/domain_analyzer
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: domain_analyzer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Analyze the security of any domain by finding all the information possible 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 > Reconnaissance > Sub Domain Enumeration.

Back to Category Index

Dominoc925

  • Website: https://dominoc925-pages.appspot.com/mapplets/cs_mgrs.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dominoc925 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

dork-cli

  • Website: https://github.com/jgor/dork-cli
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: dork-cli is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Command line Google dork 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

dorkbot

  • Website: https://github.com/utiso/dorkbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: dorkbot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Command-line tool to scan Google (or other) search results for vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

DorkGenius

  • Website: https://dorkgenius.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DorkGenius is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: DorkGenius is the ultimate tool for generating custom search queries for Google, Bing, and DuckDuckGo. - Our cutting-edge app uses the power of AI to help you create advanced search queries that can find exactly what you're looking for on the web.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Google Dorks Tools.

Back to Category Index

DorkGPT

  • Website: https://www.dorkgpt.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DorkGPT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Artificial intelligence that generates advanced search queries to find specific or hidden information on the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Google Dorks Tools.

Back to Category Index

DownloadHelper

  • Website: http://www.downloadhelper.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DownloadHelper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Download any video from any websites, it just works!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

doxbin

  • Website: https://doxbin.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: doxbin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A dox style pastebin ran by hackers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

DPA International

  • Website: http://www.dpa-international.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DPA International is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

dpaste

  • Website: https://Dpaste.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: dpaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

dpaste2

  • Website: https://Dpaste.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: dpaste2 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

Draugiem (Latvia)

  • Website: https://www.draugiem.lv
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Draugiem (Latvia) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

Dropmark

  • Website: http://www.dropmark.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dropmark is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

DualMaps

  • Website: https://www.mapchannels.com/dualmaps7/map.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DualMaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

DuckDuckGo

  • Website: https://duckduckgo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DuckDuckGo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: an Internet search engine that emphasizes protecting searchers' privacy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

DuckDuckGo URL scraper

  • Website: https://github.com/its0x08/duckduckgo
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: DuckDuckGo URL scraper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A simple DuckDuckGo URL scraper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Dupli Checker

  • Website: https://www.duplichecker.com/reverse-image-search.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Dupli Checker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: You can search for an image by uploading + with URL or typing the keyword or any word you want to explore related to images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

dygraphs

  • Website: http://dygraphs.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: dygraphs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

easely

  • Website: http://www.easel.ly
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: easely is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Easy whois

  • Website: https://www.easywhois.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Easy whois is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

EasyVIN

  • Website: https://t.me/EasyVINbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EasyVIN is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Cheap VIN/plate history check.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

EDGAR U.S. Securities and Exchange Commission Filings

  • Website: http://www.edgar-online.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EDGAR U.S. Securities and Exchange Commission Filings is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Periodic reports and extensive corporate disclosures from all businesses publicly traded in the United States.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

Edge

  • Website: https://www.microsoft.com/en-us/windows/microsoft-edge/microsoft-edge
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Edge is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

egrul_bot

  • Website: https://t.me/egrul_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: egrul_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free counterparty-check bot.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

eHow

  • Website: http://www.ehow.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: eHow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

eInvestigator

  • Website: https://www.einvestigator.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: eInvestigator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Elsevier

  • Website: https://www.elsevier.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Elsevier is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Eluta (Canada)

  • Website: http://www.eluta.ca
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Eluta (Canada) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Email Address Validator

  • Website: http://www.email-validator.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Email Address Validator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Improve deliverability, reduce bounce rates, prevent fraud and minimize funnel 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

Email Format

  • Website: http://email-format.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Email Format is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that allows you to find email address formats used by different companies.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Email Permutator

  • Website: https://www.polished.app/email-permutator/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Email Permutator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a powerful tool designed to aid professionals in generating a range of potential email addresses for a specific contact.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

EmailHippo

  • Website: https://tools.verifyemailaddress.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EmailHippo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an email address verification platform that will check whether a given email address exist or not.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

EmailRep

  • Website: https://emailrep.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EmailRep is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Email address reputation and risk scoring service.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Emergent

  • Website: http://www.emergent.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Emergent is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Fact Checking.

Back to Category Index

EmobileTracker.com

  • Website: https://www.emobiletracker.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EmobileTracker.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a service specifically designed to Track Mobile Number, Location on Google Map including information such as the owner's Name,Location,Country,Telecom provider.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

EncSF MP

  • Website: http://encfsmp.sourceforge.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EncSF MP is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Eniro (Sweden)

  • Website: http://www.eniro.se
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Eniro (Sweden) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Epic Privacy Browser

  • Website: https://www.epicbrowser.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Epic Privacy Browser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

EpicVIN

  • Website: https://epicvin.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EpicVIN is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Vehicle reports are compiled from various data sources, including historical accident records from state agencies and other entities like NMVTIS. License plate lookup that returns VIN and car millage.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Vehicle / Automobile Research.

Back to Category Index

Epieos

  • Website: https://epieos.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Epieos is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for social accounts with e-mail and phone.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Epieos Tools

  • Website: https://tools.epieos.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Epieos Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Collection of OSINT tools for email investigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Eraser

  • Website: http://eraser.heidi.ie
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Eraser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

espi0n/Dockerfiles

  • Website: https://github.com/espi0n/Dockerfiles
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: espi0n/Dockerfiles is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Dockerfiles for various OSINT tools 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Esri

  • Website: http://www.esri.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Esri is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

ETDA

  • Website: https://apt.etda.or.th/cgi-bin/listgroups.cgi
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ETDA is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for Threat Actor groups and their 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 OSINT > ↑ Threat Actor Search.

Back to Category Index

Etools

  • Website: http://www.etools.ch
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Etools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

Etusivu

  • Website: https://pastebin.fi/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Etusivu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: It's an open source clone of pastebin.com. Default Language is Finnish.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Eurojobs

  • Website: https://www.eurojobs.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Eurojobs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Europages

  • Website: http://www.europages.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Europages is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

European Business Register

  • Website: http://www.ebr.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: European Business Register is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

European Union Open Data Portal

  • Website: http://open-data.europa.eu/en/data
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: European Union Open Data Portal is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Eurostat

  • Website: http://ec.europa.eu/eurostat
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Eurostat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Exhibit

  • Website: http://www.simile-widgets.org/exhibit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Exhibit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

EXIFEditor.io

  • Website: https://exifeditor.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Forensics

What it does: EXIFEditor.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: In-browser, privacy first EXIF Viewer/Editor/Analysis tool (Zero Sign Up). Home to the The EXIF Guide, and The EXIF Quiz.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Metadata Forensics.

Back to Category Index

ExifLooter

  • Website: https://github.com/aydinnyunus/exiflooter
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ExifLooter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

ExifTool

  • Website: http://www.sno.phy.queensu.ca/~phil/exiftool
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome CTF

What it does: ExifTool is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

ExpertiseFinder

  • Website: http://www.expertisefinder.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ExpertiseFinder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

ExpertPages

  • Website: http://expertpages.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ExpertPages is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Experts.com

  • Website: http://www.experts.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Experts.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

ExportData

  • Website: https://www.exportdata.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ExportData is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Data export tool for historical tweets, followers & followings and historical trends.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

eyedex

  • Website: https://www.eyedex.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: eyedex is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Open directory search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ File Search.

Back to Category Index

EyeTON

  • Website: https://telegram.me/istoneyebot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: EyeTON is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: TON wallet graph + linked profiles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

EyeWitness

  • Website: https://github.com/ChrisTruncer/EyeWitness
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: EyeWitness is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: EyeWitness is designed to take screenshots of websites, provide some server header info, and identify default credentials if possible 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

Ezilon

  • Website: http://www.ezilon.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ezilon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Faceagle

  • Website: https://faceagle.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Faceagle is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Faceagle is a face recognition search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

FaceCheck.ID

  • Website: https://facecheck.id
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FaceCheck.ID is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Facial recognition search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Fact Check

  • Website: http://www.factcheck.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Fact Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Fact Checking.

Back to Category Index

Factiva

  • Website: https://global.factiva.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Factiva is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Factiva

  • Website: http://www.dowjones.com/factiva
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Factiva is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

FaganFinder

  • Website: http://www.faganfinder.com/engines
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FaganFinder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

  • Website: https://familysearch.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Family Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Popular genealogy site. Free, but registration required. Funded by The Church Of Jesus Christ of Latter-day Saints.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

FamilyTreeNow

  • Website: https://familytreenow.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FamilyTreeNow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Research family and geneology, no registration required, can search addresses, phone numbers, and email addresses as well as associations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Fanpage Karma

  • Website: http://www.fanpagekarma.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Fanpage Karma is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Facebook.

Back to Category Index

fast-recon

  • Website: https://github.com/DanMcInerney/fast-recon
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: fast-recon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Perform Google dorks against 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

FaviconHash

  • Website: https://kriztalz.sh/favicon-hash/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FaviconHash is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Generate favicon hashes of a website for use on Shodan, VirusTotal, Censys, ZoomEye or FOFA.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

FaxVIN

  • Website: https://www.faxvin.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FaxVIN is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Vehicle History Reports. A license plate lookup tool that returns info like VIN, make & model of vehicle, age, and numerous other details.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Vehicle / Automobile Research.

Back to Category Index

Federal Bureau of Prisons - Inmate Locator (US)

  • Website: http://www.bop.gov/inmateloc
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Federal Bureau of Prisons - Inmate Locator (US) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search federal inmates incarcerated from 1982 to the present.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Feed Exileed

  • Website: http://feed.exileed.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Feed Exileed is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Feed Filter Maker

  • Website: http://feed.janicek.co
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Feed Filter Maker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

FeedBooster

  • Website: http://www.qsensei.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FeedBooster is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Feederator

  • Website: http://www.feederator.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Feederator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Feedly

  • Website: http://www.feedly.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Feedly is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

FeedReader

  • Website: http://www.feedreader.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FeedReader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

FetchRSS

  • Website: http://fetchrss.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FetchRSS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

FileListing

  • Website: https://filelisting.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FileListing is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ File Search.

Back to Category Index

FilePursuit

  • Website: https://filepursuit.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FilePursuit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ File Search.

Back to Category Index

Filesec.io

  • Website: https://filesec.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Filesec.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Central resource cataloging malicious file extensions, their risks, OS and mitigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ File Search.

Back to Category Index

FileVault

  • Website: https://support.apple.com/en-us/HT204837
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FileVault is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Filmot

  • Website: https://filmot.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Filmot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search within YouTube subtitles. Indexing over 573 million captions across 528 million videos and 45 million channels.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Find osint tool

  • Website: https://find.osint-tool.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Find osint tool is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches multiple OSINT tools to find information across various sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Find YouTube Video

  • Website: https://findyoutubevideo.thetechrobo.ca/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Find YouTube Video is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches currently 5 YouTube archives for specific videos by ID, which is really useful for finding deleted or private YouTube videos.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Find-pdf-doc

  • Website: http://www.findpdfdoc.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Find-pdf-doc is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Document and Slides Search.

Back to Category Index

FindStickerCreator

  • Website: https://t.me/SPOwnerBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FindStickerCreator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Finds creator of any Telegram sticker pack.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Firefox

  • Website: https://www.mozilla.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Firefox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Fish4Jobs

  • Website: http://www.fish4.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Fish4Jobs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Flash Earth

  • Website: http://www.flashearth.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Flash Earth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Flickr

  • Website: https://flickr.com/search/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Flickr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Flipboard

  • Website: https://flipboard.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Flipboard is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Flipboard

  • Website: http://flipboard.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Flipboard is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Flot

  • Website: http://www.flotcharts.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Flot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

FOCA

  • Website: https://github.com/ElevenPaths/FOCA
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Forensics, Awesome Web Security

What it does: FOCA is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: FOCA (Fingerprinting Organizations with Collected Archives) is a tool used mainly to find metadata and hidden information in the documents its scans 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

FOCA (Fingerprinting Organizations with Collected Archives)

  • Website: https://www.elevenpaths.com/labstools/foca/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: FOCA (Fingerprinting Organizations with Collected Archives) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Automated document harvester that searches Google, Bing, and DuckDuckGo to find and extrapolate internal company organizational structures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Metadata harvesting and analysis.

Back to Category Index

FOFA

  • Website: https://en.fofa.info/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FOFA is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Asset search 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

FOFA

  • Website: https://fofa.so/?locale=en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: FOFA is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Cyberspace Search Engine 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Fold3 (US Military Records)

  • Website: http://www.fold3.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Fold3 (US Military Records) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search military records. Search filters limited with free access. Premium access requires subscription.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Foller.me

  • Website: http://foller.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Foller.me is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Follow.net

  • Website: http://follow.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Follow.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

FollowThatPage

  • Website: http://www.followthatpage.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FollowThatPage is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Forbes Global 2000

  • Website: http://www.forbes.com/global2000/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Forbes Global 2000 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Forensically

  • Website: https://29a.ch/photo-forensics/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Forensically is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

FortiGuard Labs

  • Website: https://www.fortiguard.com/threat-actor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FortiGuard Labs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Powered by FortiGuard Labs, our Threat Actor Encyclopedia provides actionable insights, helping security teams prepare and streamline advanced threat hunting and response.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Fortiguard Labs

  • Website: https://fortiguard.fortinet.com/threat-map
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Fortiguard Labs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: FortiGuard Outbreak Alerts provides key information about on-going cybersecurity attack with significant ramifications affecting numerous companies, organizations and industries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

FotoForensics

  • Website: http://www.fotoforensics.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FotoForensics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

Frame by Frame

  • Website: https://chrome.google.com/webstore/detail/frame-by-frame/cclnaabdfgnehogonpeddbgejclcjneh/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Frame by Frame is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Browser plugin that allows you to watch YouTube videos frame by frame.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

France24

  • Website: http://www.france24.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: France24 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Free Full PDF

  • Website: http://www.freefullpdf.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Free Full PDF is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Document and Slides Search.

Back to Category Index

Freebase

  • Website: https://developers.google.com/freebase
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Freebase is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

FreeCarrierLookup

  • Website: https://freecarrierlookup.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FreeCarrierLookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: enter a phone number and we'll return the carrier name and whether the number is wireless or landline. We also return the email-to-SMS and email-to-MMS gateway addresses for USA and Canadian* phone numbers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Friendpaste

  • Website: https://friendpaste.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Friendpaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paste stuff to your friends.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Full Fact

  • Website: https://fullfact.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Full Fact is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Fact Checking.

Back to Category Index

FullHunt

  • Website: https://fullhunt.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FullHunt is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: FullHunt is an OSINT tool focused on identifying and protecting internet-exposed assets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

FusionCharts

  • Website: http://www.fusioncharts.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: FusionCharts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Gapminder World

  • Website: http://www.gapminder.org/data
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Gapminder World is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Genealogy Bank

  • Website: http://www.genealogybank.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Genealogy Bank is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Premium data, free trial with credit card.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

  • Website: http://www.genealogylinks.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Genealogy Links is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Genealogy directory with over 50K links.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Geocreepy

  • Website: http://www.geocreepy.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Geocreepy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

GeoGig

  • Website: http://geogig.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoGig is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

GeoGuessr.ai

  • Website: https://geoguessr.ai
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoGuessr.ai is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI-powered geolocation tool for identifying locations from images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

GeoInfer

  • Website: https://geoinfer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoInfer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Image geolocation tool, no EXIF data 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: Awesome OSINT > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

GeoMacFinder

  • Website: https://t.me/geomacbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoMacFinder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Finds Wi-Fi AP location by MAC/BSSID.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

GeoNames

  • Website: http://www.geonames.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoNames is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Geosearch

  • Website: http://www.geosearchtool.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Geosearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

GeoSpy

  • Website: https://geospy.web.app/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GeoSpy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI based image osint 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 OSINT > ↑ Image Analysis.

Back to Category Index

Gerdoo (Iran)

  • Website: http://gerdoo.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Gerdoo (Iran) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Getairplane

  • Website: https://telegram.me/getairplane_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Getairplane is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Phone → flight history (20 years).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

getChatList

  • Website: https://telegram.me/getchatlistbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: getChatList is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Shows user’s group list.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

GetSendGifts

  • Website: https://telegram.me/GetSendGiftsProBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GetSendGifts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Shows who sent Telegram gifts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Ghostery

  • Website: https://www.ghostery.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ghostery is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

GhostProject

  • Website: https://ghostproject.fr/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: GhostProject is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searchable database of billions of cleartext passwords, partially visible for free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > OSINT Online Resources.

Back to Category Index

Ghunt

  • Website: https://github.com/mxrch/GHunt
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ghunt is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Investigate Google emails and documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Gibiru

  • Website: https://gibiru.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Gibiru is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Gibiru provides “uncensored search results” without collecting personal data like logging users’ IP addresses or search queries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

  • Website: https://github.com/search?type=code
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GitHub Code Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: GitHub's enhanced code search with advanced filtering.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Code Search.

Back to Category Index

GitHub gist

  • Website: https://gist.github.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GitHub gist is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

github-dorks

  • Website: https://github.com/techgaun/github-dorks
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: github-dorks is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: CLI tool to scan GitHub repos/organizations for potential sensitive information 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

github_monitor

  • Website: https://github.com/misiektoja/github_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: github_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of GitHub users' activities including profile and repository changes with support for email alerts, CSV logging, detection when a user blocks or unblocks you 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 OSINT > Social Media Tools > ↑ GitHub.

Back to Category Index

GithubRecon

  • Website: https://kriztalz.sh/github-recon/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GithubRecon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Lookup Github users by username or email and gather associated data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ GitHub.

Back to Category Index

Gitrecon

  • Website: https://github.com/atiilla/gitrecon
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Gitrecon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Node.js tool to scan GitHub repositories for exposed email addresses and names.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

gitrob

  • Website: https://github.com/michenriksen/Gitrob
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: gitrob is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reconnaissance tool for GitHub organizations 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Glassdoor

  • Website: https://www.glassdoor.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Glassdoor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Glit

  • Website: https://github.com/shadawck/glit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Glit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Retrieve all mails of users related to a git repository, a git user or a git organization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

globalEdge

  • Website: http://globaledge.msu.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: globalEdge is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

globalEDGE Database of International Business Statistics

  • Website: http://globaledge.msu.edu/tools-and-data/dibs
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: globalEDGE Database of International Business Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

GlobalExperts

  • Website: http://www.theglobalexperts.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GlobalExperts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

gmapcatcher

  • Website: https://github.com/heldersepu/gmapcatcher
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: gmapcatcher is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

Gnu Icecat

  • Website: https://icecatbrowser.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Gnu Icecat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

GNU PG

  • Website: https://www.gnupg.org/download/index.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GNU PG is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Goo (Japan)

  • Website: http://www.goo.ne.jp
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Goo (Japan) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

GoodFirms

  • Website: https://www.goodfirms.co/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GoodFirms is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

GooDork

  • Website: https://github.com/k3170makan/GooDork
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: GooDork is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Command line Google dorking 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

Goodsearch

  • Website: https://www.goodsearch.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Goodsearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a search engine for shopping deals online.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Goofram

  • Website: http://www.goofram.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Goofram is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

Google Adwords

  • Website: http://adwords.google.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Adwords is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Get monthly keyword volume data and stats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Keywords Discovery and Research.

Back to Category Index

Google Alerts

  • Website: http://www.google.com/alerts
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Alerts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A content change detection and notification service.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Web Monitoring.

Back to Category Index

  • Website: http://www.google.com/cse
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Custom Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Google Developers: Charts

  • Website: https://developers.google.com/chart
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Developers: Charts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Google Earth

  • Website: http://www.google.com/earth
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Earth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Google Earth Pro

  • Website: https://www.google.com/intl/en/earth/versions/#earth-pro
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Earth Pro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Google Finance

  • Website: https://www.google.com/finance
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Finance is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Google Groups

  • Website: https://groups.google.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Groups is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

Google Hacking Database

  • Website: https://www.exploit-db.com/google-hacking-database/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT, Awesome Cyber Security Tools

What it does: Google Hacking Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The GHDB is an index of search queries (we call them dorks) used to find publicly available information, intended for pentesters 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

Google Image

  • Website: https://images.google.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Image is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Google Lens

  • Website: https://lens.google.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Lens is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Google Maps

  • Website: https://www.google.com/maps
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Google My Maps

  • Website: https://www.google.com/maps/about/mymaps
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google My Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Google Public Data Explorer

  • Website: http://www.google.com/publicdata/directory
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Public Data Explorer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Google Scholar

  • Website: https://scholar.google.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Scholar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

  • Website: https://www.google.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Most popular search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

  • Website: https://www.google.com/trends
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Google Trends is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: See how many users are searching for specific keywords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Keywords Discovery and Research.

Back to Category Index

gOSINT

  • Website: https://github.com/Nhoya/gOSINT
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: gOSINT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT tool with multiple modules and a telegram scraper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Government of Canada Open Data

  • Website: http://open.canada.ca/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Government of Canada Open Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

GPG Tools

  • Website: https://gpgtools.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GPG Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

GPSVisualizer

  • Website: http://www.gpsvisualizer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GPSVisualizer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

GraphX

  • Website: http://spark.apache.org/graphx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GraphX is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

GraphyStories

  • Website: http://app.graphystories.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GraphyStories is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

GrassGIS

  • Website: http://grass.osgeo.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GrassGIS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

GrayhatWarfare

  • Website: https://grayhatwarfare.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GrayhatWarfare is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches and indexes open Amazon S3 buckets, allowing users to find and explore potentially exposed data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

grep.app

  • Website: https://grep.app/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: grep.app is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches code from the entire github public repositories for a given specific string or using regular expression.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Code Search.

Back to Category Index

Grey Guide

  • Website: http://greyguide.isti.cnr.it
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Grey Guide is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Grey Literature Strategies

  • Website: http://greylitstrategies.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Grey Literature Strategies is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Grey Literature – List of Gateways

  • Website: http://csulb.libguides.com/graylit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Grey Literature – List of Gateways is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

GreyNet International

  • Website: http://www.greynet.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GreyNet International is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

GreyNoise

  • Website: https://viz.greynoise.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GreyNoise is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search Exposed Internet assets, Malicious IP's.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

GroupDa

  • Website: https://groupda.com/telegram/group/search
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GroupDa is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Can be used for Searching Telegram Channels. Search by Category, Countries and Language.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

GSDF

  • Website: https://github.com/We5ter/GSDF
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: GSDF is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Domain searcher named GoogleSSLdomainFinder 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 > Reconnaissance > Sub Domain Enumeration.

Back to Category Index

GSIL

  • Website: https://github.com/FeeiCN/GSIL
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: GSIL is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Github Sensitive Information Leakage(Github敏感信息泄露)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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Guardian Project

  • Website: https://guardianproject.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Guardian Project is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Guerrilla Mail

  • Website: https://www.guerrillamail.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Guerrilla Mail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

GuideStar

  • Website: http://www.guidestar.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: GuideStar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

GyoiThon

  • Website: https://github.com/gyoisamurai/GyoiThon
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: GyoiThon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: GyoiThon is an Intelligence Gathering tool using Machine Learning.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

h8mail

  • Website: https://github.com/khast3x/h8mail
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: h8mail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Password Breach Hunting and Email OSINT, locally or using premium services. Supports chasing down related email.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Hacking Cryptocurrency Miners with OSINT Techniques

  • Website: https://medium.com/@s3yfullah/hacking-cryptocurrency-miners-with-osint-techniques-677bbb3e0157
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: Hacking Cryptocurrency Miners with OSINT Techniques is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > OSINT.

Back to Category Index

  • Website: https://www.harmari.com/search/unified
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Harmari (Unified Listings Search) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

HARO

  • Website: http://www.helpareporter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HARO is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

HashBin

  • Website: https://hashb.in/#Q===
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HashBin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: HashBin is a paste bin that never sees the contents of its pastes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

hastebin

  • Website: https://www.toptal.com/developers/hastebin/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: hastebin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

Have I Been Pwned

  • Website: https://haveibeenpwned.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Web Security

What it does: Have I Been Pwned is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search across multiple data breaches to see if your email address has been compromised.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Engineering Database.

Back to Category Index

HCL Threat Map

  • Website: https://www.hcltech.com/hcl-threat-map
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HCL Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Cyber Threat Map by HCLTech.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Headhunter

  • Website: http://www.headhunter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Headhunter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

HeadlineSpot

  • Website: http://www.headlinespot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HeadlineSpot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Here

  • Website: http://here.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Here is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

HEROIC.NOW

  • Website: https://heroic.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HEROIC.NOW is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Has your data been leaked on the dark web? Scan your identities for FREE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

HIB Ransomed

  • Website: https://haveibeenransom.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HIB Ransomed is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Because people have the right to know if their data has been leaked.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

Highcharts

  • Website: http://www.highcharts.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Highcharts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

HighWire: Free Online Full-text Articles

  • Website: http://highwire.stanford.edu/lists/freeart.dtl
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HighWire: Free Online Full-text Articles is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

HimeraSearch

  • Website: https://t.me/HimeraNeGBL8Pro1dp_Search_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HimeraSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT/HUMINT search: phones, emails, vehicles, people, courts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

HIS Piers

  • Website: https://www.ihs.com/products/piers.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HIS Piers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Hohli

  • Website: http://charts.hohli.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hohli is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Holehe

  • Website: https://github.com/megadose/holehe
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Holehe is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: allows you to check if the mail is used on different sites like twitter, instagram and will retrieve information on sites with the forgotten password function.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Homemetry

  • Website: https://homemetry.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Homemetry is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reverse address search and allows searching for properties for sale/rent.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Hooey webprint

  • Website: http://www.hooeeywebprint.com.s3-website-us-east-1.amazonaws.com/download.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hooey webprint is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

Hootsuite

  • Website: http://hootsuite.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hootsuite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Hoovers

  • Website: http://www.hoovers.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hoovers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Hotspot Shield

  • Website: https://www.hotspotshield.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hotspot Shield is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

HTTPs Everywhere

  • Website: https://www.eff.org/https-everywhere/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HTTPs Everywhere is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

HTTrack

  • Website: http://www.httrack.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HTTrack is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Allows you to download a World Wide Web site from the Internet to a local directory, building recursively all directories, getting HTML, images, and other files from the server to your computer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Offline Browsing.

Back to Category Index

Human Development Reports

  • Website: http://hdr.undp.org/en/global-reports
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Human Development Reports is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Hunchly

  • Website: https://www.hunch.ly/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hunchly is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Hunchly is a web capture tool designed specifically for online investigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Hunter Search Engine

  • Website: https://hunter.how/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hunter Search Engine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search Exposed Internet assets, open web directories and many 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

Hunter.io

  • Website: https://hunter.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: Hunter.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Data broker providing a Web search interface for discovering the email addresses and other organizational details of a company.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Data Broker and Search Engine Services.

Back to Category Index

Hyperlapse

  • Website: https://github.com/TeehanLax/Hyperlapse.js
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Hyperlapse is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

HypeStat

  • Website: https://www.hypestat.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: HypeStat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

IBM X-Force Exchange Current Malicious Activity

  • Website: https://exchange.xforce.ibmcloud.com/activity/map
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IBM X-Force Exchange Current Malicious Activity is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Icann Lookup

  • Website: https://lookup.icann.org/en/lookup
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Icann Lookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The site allows you to look up domain registration information (WHOIS) on the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Iconosquare

  • Website: http://iconosquare.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Iconosquare is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Instagram.

Back to Category Index

IDCrawl

  • Website: https://www.idcrawl.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IDCrawl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for a name in popular social 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 OSINT > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

IDCrawl

  • Website: https://www.idcrawl.com/username
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IDCrawl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for a username in popular social 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 OSINT > ↑ Username Check.

Back to Category Index

Idealist

  • Website: http://www.idealist.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Idealist is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

ideone

  • Website: https://Ideone.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ideone is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

IKnowYour.Dad

  • Website: https://iknowyour.dad/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IKnowYour.Dad is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Data Breach Search Engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

  • Website: http://www.ilo.org/global/research/global-reports/weso/2015/lang--en/index.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ILO World Employment and Social Outlook Trends is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

ILOSTAT

  • Website: http://www.ilo.org/ilostat/faces/oracle/webcenter/portalapp/pagehierarchy/Page137.jspx?_afrLoop=443508925711569&clean=true#%40%3F_afrLoop%3D443508925711569%26clean%3Dtrue%26_adf.ctrl-state%3Dl4dwldaf3_9
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ILOSTAT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Image Identification Project

  • Website: https://www.imageidentify.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Image Identification Project is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Image Raider

  • Website: https://www.imageraider.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Image Raider is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is our reverse image search tool for completing individual searches. When you upload an image to this page, we'll scour the internet to find its source and all of the other pages where it has been posted.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

image-match

  • Website: https://github.com/ascribe/image-match
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: image-match is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Quickly search over billions of images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

IMF World Economic Outlook Database

  • Website: http://www.imf.org/external/ns/cs.aspx?id=28
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IMF World Economic Outlook Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

ImgOps

  • Website: https://imgops.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ImgOps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

Imgur

  • Website: http://imgur.com/search?q=
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Imgur is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The most popular image hosting website used by redditors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Impersonal.me

  • Website: http://www.impersonal.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Impersonal.me is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ General Search.

Back to Category Index

Imperva Live Threat Map

  • Website: https://www.imperva.com/cyber-threat-attack-map/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Imperva Live Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A real-time global view of DDoS attacks, hacking attempts, and bot assaults mitigated by Imperva security services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

ImpulseAdventure

  • Website: http://www.impulseadventure.com/photo/jpeg-snoop.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ImpulseAdventure is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

Inc. 5000

  • Website: http://www.inc.com/inc5000
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Inc. 5000 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Indeed

  • Website: http://www.indeed.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Indeed is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an online job searching website that gives job seekers free access to search for a job, post their resumes, and research companies.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Job Search Resources.

Back to Category Index

Index Mundi

  • Website: http://www.indexmundi.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Index Mundi is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Infobel

  • Website: https://www.infobel.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Infobel is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search 164+ million records across 73 countries for companies and individuals. Find places, local service providers, their contact details, reviews, opening hours 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 OSINT > ↑ Phone Number Research.

Back to Category Index

Infogr.am

  • Website: https://infogr.am
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Infogr.am is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

InfoMinder

  • Website: http://www.infominder.com/webminder
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InfoMinder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

infosec reference

  • Website: https://github.com/rmusser01/Infosec_Reference
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Web Security

What it does: infosec reference is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Information Security Reference That Doesn't Suck 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 OSINT > ↑ Related Awesome Lists.

Back to Category Index

Infosniper

  • Website: http://www.infosniper.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Infosniper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

InfoTracer

  • Website: https://infotracer.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InfoTracer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for people. (Searches are paid).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Inkscape

  • Website: https://inkscape.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Inkscape is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

InMobPrefix

  • Website: https://github.com/hstsethi/in-mob-prefix
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InMobPrefix is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Dataset, charts, models about mobile phone numbers prefixes in India along with their respective state, operator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Innocentive

  • Website: http://www.innocentive.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Innocentive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Insecam

  • Website: http://insecam.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Insecam is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Live cameras 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 OSINT > ↑ Video Search and Other Video Tools.

Back to Category Index

Inshorts

  • Website: https://www.inshorts.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Inshorts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Insight

  • Website: https://t.me/ibhld_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Insight is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Shows interests based on subscriptions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Inspire Geoportal

  • Website: http://inspire-geoportal.ec.europa.eu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Inspire Geoportal is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

InstaAnonym

  • Website: https://t.me/instaanonymbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InstaAnonym is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Anonymous Instagram/VK viewer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

InstaBot

  • Website: https://telegram.me/InstaBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InstaBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Downloads Instagram media.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Instagram

  • Website: https://www.instagram.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Instagram is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

instagram_monitor

  • Website: https://github.com/misiektoja/instagram_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: instagram_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Instagram users' activities and profile changes with support for email alerts, CSV logging, showing media in the terminal, anonymous story downloads 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 OSINT > Social Media Tools > ↑ Instagram.

Back to Category Index

InstagramPrivSniffer

  • Website: https://github.com/obitouka/InstagramPrivSniffer
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InstagramPrivSniffer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Views Instagram PRIVATE ACCOUNT'S media without login 😱.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Instagram.

Back to Category Index

Instant Google Street View

  • Website: http://www.instantstreetview.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Instant Google Street View is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

InstantAtlas

  • Website: http://www.instantatlas.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: InstantAtlas is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

IntelHub

  • Website: https://github.com/tomsec8/IntelHub
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IntelHub is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Browser-based open-source OSINT extension. All analysis runs locally (no servers). Features include text profiler, metadata analyzer, site & archive analysis, reverse image search, crypto/telegram analyzers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Intelligence X

  • Website: https://intelx.io/tools
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Intelligence X is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paid OSINT Tool Allowing users to search for information across various sources including the dark web and public data 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

IntellyWeave

  • Website: https://github.com/vericle/intellyweave
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IntellyWeave is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI-powered OSINT platform with GLiNER entity extraction, Mapbox 3D geospatial visualization, and multi-agent archive research across 30+ international archives.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

IntelTechniques

  • Website: https://inteltechniques.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IntelTechniques is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

International Energy Agency Statistics

  • Website: http://www.iea.org/statistics
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: International Energy Agency Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

International Labour Comparisons

  • Website: http://www.bls.gov/fls/chartbook.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: International Labour Comparisons is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

International Trade Center

  • Website: http://www.intracen.org/ByCountry.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: International Trade Center is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Internet Archive

  • Website: https://archive.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Internet Archive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Internet Archive: Open Source Videos

  • Website: https://archive.org/details/opensource_movies
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Internet Archive: Open Source Videos is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Internet Experts

  • Website: http://www.internetexperts.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Internet Experts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

intoDNS

  • Website: http://www.intodns.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: intoDNS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Intrigue

  • Website: http://intrigue.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Intrigue is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Automated OSINT & Attack Surface discovery framework with powerful API, UI and CLI.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

IP 2 Geolocation

  • Website: http://ip2geolocation.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP 2 Geolocation is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

IP 2 Location

  • Website: http://www.ip2location.com/demo.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP 2 Location is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

IP Checking

  • Website: http://www.ipchecking.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP Checking is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

IP Geolocation API DB-IP

  • Website: https://db-ip.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP Geolocation API DB-IP is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Pprovides IP geolocation and intelligence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

IP Location

  • Website: https://www.iplocation.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP Location is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is used for mapping of an IP address or MAC address to the real-world geographic location of an Internet-connected computing or a mobile device.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

IP Location.io

  • Website: https://iplocation.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IP Location.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: IPLocation.io allows you to check the location of an IP for free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

IPFingerprints

  • Website: http://www.ipfingerprints.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IPFingerprints is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is used to find the approximate geographic location of an IP address along with some other useful information including ISP, TimeZone, Area Code, State.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

IPVoid

  • Website: http://www.ipvoid.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: IPVoid is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: IP address toolset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Islegitsite

  • Website: https://www.islegitsite.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Islegitsite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Checks if a website is trustworthy by analyzing its reputation, domain, and security based on public sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Itar-Tass

  • Website: http://www.itar-tass.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Itar-Tass is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

ITP Infotrack

  • Website: https://infotrackpeople.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ITP Infotrack is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: People, vehicle, property lookup.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

ivpaste

  • Website: https://Ivpaste.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ivpaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

iZito

  • Website: http://www.izito.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: iZito is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

Java Infovis Toolkit

  • Website: http://philogb.github.io/jit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Java Infovis Toolkit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Jeffreys Image Metadata Viewer

  • Website: http://exif.regex.info/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Jeffreys Image Metadata Viewer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

JIMPL

  • Website: https://jimpl.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: JIMPL is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Online EXIF data viewer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Analysis.

Back to Category Index

Jobs (Poland)

  • Website: http://www.jobs.pl
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Jobs (Poland) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Jobsite (UK)

  • Website: http://www.jobsite.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Jobsite (UK) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Journal Guide

  • Website: https://www.journalguide.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Journal Guide is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Journal Seek

  • Website: http://journalseek.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Journal Seek is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

JPEGsnoop

  • Website: https://sourceforge.net/projects/jpegsnoop
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: JPEGsnoop is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Analysis.

Back to Category Index

JpGraph

  • Website: http://jpgraph.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: JpGraph is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

jqPlot

  • Website: http://www.jqplot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: jqPlot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A Versatile and Expandable jQuery Plotting Plugin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

jsbin

  • Website: https://Jsbin.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: jsbin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

Judyrecords

  • Website: https://www.judyrecords.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Judyrecords is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free. Nationwide search of 400 million+ United States court cases.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Junar

  • Website: http://junar.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Junar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

justdeleteme

  • Website: http://justdelete.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: justdeleteme is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

justpaste

  • Website: https://Justpaste.it
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: justpaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

  • Website: https://kagi.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kagi Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Liberate your search. Free of ads. Free of surveillance. Your time respected. You are the customer, never the product.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

KartaView

  • Website: https://kartaview.org/map/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: KartaView is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

KartaVision

  • Website: https://kartavision.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: KartaVision is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: search engine for KartaView imagery. It supports natural-language search and search by image.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

Kartograph

  • Website: http://kartograph.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kartograph is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Kaspersky Cyberthreat live Map

  • Website: https://cybermap.kaspersky.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kaspersky Cyberthreat live Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find out if you are under cyber-attack here.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Katbin

  • Website: https://katb.in
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Katbin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Small, lightweight pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

KeePass Password Safe

  • Website: http://keepass.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: KeePass Password Safe is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a free and open-source password manager that uses the most secure encryption algorithms to safegard your passwords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Keyword Discovery

  • Website: http://www.keyworddiscovery.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Keyword Discovery is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

Keyword Spy

  • Website: http://www.keywordspy.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Keyword Spy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

KeywordTool

  • Website: http://keywordtool.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: KeywordTool is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

Klear

  • Website: http://klear.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Klear is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Kloth

  • Website: http://www.kloth.net/services
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kloth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Knoema

  • Website: https://knoema.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Knoema is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Knowledge guide to international company registration

  • Website: http://www.icaew.com/en/library/subject-gateways/business-management/company-administration/knowledge-guide-international-company-registration
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Knowledge guide to international company registration is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

KNOWLEDGENOW

  • Website: https://know.netenrich.com/content/track/threat-actor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: KNOWLEDGENOW is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Trending Threats.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Kompass

  • Website: http://www.kompass.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kompass is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Business directory and search.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Kribrum

  • Website: https://kribrum.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Kribrum is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

LandMatrix

  • Website: http://landmatrix.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LandMatrix is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

lastfm_monitor

  • Website: https://github.com/misiektoja/lastfm_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: lastfm_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Last.fm users' listening activity including detection when user gets online & offline, pauses or resumes playback, all played songs, its duration, skipped songs, with optional auto-play, email alerts, CSV logging, session stats 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 OSINT > ↑ Music Streaming Services.

Back to Category Index

Lastpass

  • Website: https://lastpass.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lastpass is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Latinobarometro

  • Website: http://www.latinobarometro.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Latinobarometro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

lazarusholic

  • Website: https://lazarus.day/actors/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: lazarusholic is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Total 203 threat actors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Lazy Scholar

  • Website: http://www.lazyscholar.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lazy Scholar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Leaflet

  • Website: http://leafletjs.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Leaflet is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: an open-source JavaScript library for mobile-friendly interactive maps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Leak OSINT

  • Website: https://telegram.me/Leak_SSINTbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Leak OSINT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Phone-number leakage check.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

LeakCheck

  • Website: https://leakcheck.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LeakCheck is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Data Breach Search Engine with 7.5B+ entries collected from more than 3000 databases. Search by e-mail, username, keyword, password or corporate domain name.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

LeakRadar

  • Website: https://leakradar.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LeakRadar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Scans for compromised emails and domains in stealer logs, offering proactive breach prevention and real-time alerts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Lenso.ai

  • Website: https://lenso.ai
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lenso.ai is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reverse image search tool with facial recognition, created for finding people, similar images, copies of photos, identical places 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 OSINT > ↑ Image Search.

Back to Category Index

lesma.eu

  • Website: https://lesma.eu/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: lesma.eu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Simple paste app friendly with browser and command line.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Library of Congress: Ask a Librarian

  • Website: http://www.loc.gov/rr/askalib
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Library of Congress: Ask a Librarian is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Library, University of Michigan: Statistics and Datasets

  • Website: http://www.lib.umich.edu/browse/Statistics%20and%20Data%20Sets
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Library, University of Michigan: Statistics and Datasets is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

LibreWolf

  • Website: https://librewolf.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LibreWolf is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Privacy-focused Firefox fork with enhanced security defaults.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Browsers.

Back to Category Index

Licenseplates

  • Website: http://www.worldlicenseplates.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Licenseplates is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

LinEnum

  • Website: https://github.com/rebootuser/LinEnum
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: LinEnum is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Scripted local Linux enumeration and privilege escalation checker useful for auditing a host and during CTF gaming.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Linkedin

  • Website: https://www.linkedin.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Linkedin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Commonly used social-media platform with a focus on professional profiles and recruitment. Spans a wide variety of industries. Very useful for gathering information on what specific individuals are active within an entity.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Major Social Networks.

Back to Category Index

Linkedin Groups

  • Website: http://www.linkedin.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Linkedin Groups is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

LinkedInDumper

  • Website: https://github.com/l4rm4nd/LinkedInDumper
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LinkedInDumper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Script to dump/scrape/extract company employees info from LinkedIn API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ LinkedIn.

Back to Category Index

Linkode(alpha)

  • Website: https://linkode.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Linkode(alpha) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Linkode is the useful pastebin!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

LinkScope Client

  • Website: https://github.com/AccentuSoft/LinkScope_Client
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LinkScope Client is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: LinkScope Client Github repository.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Linkuroius

  • Website: http://linkurio.us
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Linkuroius is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

LIONIC Cyber Threat Map

  • Website: https://www.lionic.com/monitoring/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LIONIC Cyber Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Listify

  • Website: http://listify.okfnlabs.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Listify is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Turn a Google spreadsheet into a beautiful, searchable listing in seconds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Liveuamap

  • Website: https://liveuamap.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Liveuamap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

LocalFocus

  • Website: https://www.localfocus.nl
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: LocalFocus is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Lockbin

  • Website: https://lockbin.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lockbin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

lol_monitor

  • Website: https://github.com/misiektoja/lol_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: lol_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of LoL (League of Legends) players gaming activities including detection when a user starts or finishes a match with support for email alerts, CSV logging, playtime stats 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 OSINT > ↑ Gaming Platforms.

Back to Category Index

Lucidchart

  • Website: https://www.lucidchart.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lucidchart is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: the intelligent diagramming application that brings teams together to make better decisions and build the future.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

  • Website: https://search.lycos.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Lycos Image Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

MagPortal

  • Website: http://www.magportal.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MagPortal is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Maigret OSINT bot

  • Website: https://t.me/osint_maigret_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maigret OSINT bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Username search on 1,366 sites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Mailbox

  • Website: https://mailbox.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mailbox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

MailTester

  • Website: http://mailtester.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MailTester is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: hunt for emails and improve your email deliverability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Mailvelope

  • Website: https://www.mailvelope.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mailvelope is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Majestic

  • Website: https://majestic.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Majestic is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find out who links to your 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

Malpedia

  • Website: https://malpedia.caad.fkie.fraunhofer.de/actors
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Malpedia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Get List of threat actor 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 OSINT > ↑ Threat Actor Search.

Back to Category Index

Maltego

  • Website: https://www.maltego.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maltego is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Maltego is an open source intelligence (OSINT) and graphical link analysis tool for gathering and connecting information for investigative 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 OSINT > ↑ Other Tools.

Back to Category Index

Maltego Telegram

  • Website: https://github.com/vognik/maltego-telegram
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maltego Telegram is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Rich Set of Entities & Transforms for OSINT on Telegram with Maltego.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Mamont

  • Website: https://www.mmnt.ru/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mamont is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Map Maker

  • Website: https://maps.co
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Map Maker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

MapAList

  • Website: http://mapalist.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MapAList is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

MapBox

  • Website: https://www.mapbox.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MapBox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mapchart.net

  • Website: https://mapchart.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mapchart.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

MapChecking

  • Website: https://www.mapchecking.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MapChecking is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Maperitive

  • Website: http://maperitive.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maperitive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

MapHub

  • Website: https://maphub.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MapHub is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mapillary

  • Website: https://www.mapillary.com/app/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mapillary is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

MapJam

  • Website: http://mapjam.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MapJam is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mapline

  • Website: https://mapline.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mapline is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mapquest

  • Website: https://www.mapquest.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mapquest is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mark Monitor WHOIS

  • Website: https://whois-webform.markmonitor.com/whois/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mark Monitor WHOIS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Displays domain registration 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

Master Password

  • Website: http://masterpasswordapp.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Master Password is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Maven

  • Website: http://www.maven.co
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maven is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

MaxMind

  • Website: https://www.maxmind.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MaxMind is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Maxthon

  • Website: http://www.maxthon.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Maxthon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Meawfy

  • Website: https://meawfy.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Meawfy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Advanced Mega.nz File Search Engine. Search and discover files from Mega.nz with our intelligent crawler technology. Access over 9 million indexed files instantly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ File Search.

Back to Category Index

Mention

  • Website: https://en.mention.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mention is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Mergent Intellect

  • Website: http://www.mergentintellect.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mergent Intellect is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Mergent Online

  • Website: http://www.mergentonline.com/login.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mergent Online is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Metacafe

  • Website: http://www.metacafe.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Metacafe is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Metadata Viewer

  • Website: https://kriztalz.sh/metadata-viewer/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Metadata Viewer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Online EXIF data viewer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Analysis.

Back to Category Index

metagoofil

  • Website: https://github.com/laramies/metagoofil
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: metagoofil is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Metadata 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 > Open Sources Intelligence (OSINT) > Metadata harvesting and analysis.

Back to Category Index

Metatube

  • Website: http://www.metatube.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Metatube is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Microsoft Academic

  • Website: http://academic.research.microsoft.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Microsoft Academic is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Million Short

  • Website: https://millionshort.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Million Short is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Minerva OSINT

  • Website: https://minervaosint.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Minerva OSINT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Email search tool that finds and aggregates data on a target email from over a hundred 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: Awesome OSINT > ↑ Email Search / Email Check.

Back to Category Index

MISP Galaxy

  • Website: https://www.misp-galaxy.org/360net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MISP Galaxy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Known or estimated adversary groups as identified by 360.net.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

Mixi (Japan)

  • Website: https://mixi.jp
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mixi (Japan) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

mnp_bot

  • Website: https://t.me/mnp_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: mnp_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Phone operator + region.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Modest Maps

  • Website: http://modestmaps.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Modest Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Mojeek

  • Website: https://www.mojeek.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mojeek is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Mojeek is a growing independent search engine which does not track you.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Monster

  • Website: http://www.monster.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Monster is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Mostly Harmless

  • Website: http://kerrick.github.io/Mostly-Harmless/#features
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mostly Harmless is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Mostly Harmless looks up the page you are currently viewing to see if it has been submitted to reddit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

MotherSearchBot

  • Website: https://t.me/MotherSearchBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MotherSearchBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Google-like Telegram search.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Mozilla HTTP Observatory

  • Website: https://developer.mozilla.org/en-US/observatory
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mozilla HTTP Observatory is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Observatory⁩ enhances web security by analyzing compliance with best security practices.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

MuckRack

  • Website: http://muckrack.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MuckRack is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Extensive database of U.S. government public records obtained through federal and state public records requests. Automated tool that will make public records requests and follow up until records are obtained on your behalf.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Expert Search.

Back to Category Index

Mugshots

  • Website: https://mugshots.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mugshots is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ People Investigations.

Back to Category Index

Mullvad Browser

  • Website: https://mullvad.net/en/browser
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Mullvad Browser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Privacy-focused browser developed in collaboration with Tor 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 OSINT > ↑ Browsers.

Back to Category Index

Multirbl

  • Website: https://multirbl.valli.org/dnsbl-lookup
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Multirbl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: MultiRBL Valli checks if an IP or domain is listed on multiple public RBLs (blacklists) 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

MustBePresent

  • Website: http://mustbepresent.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MustBePresent is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

mxtoolbox

  • Website: https://mxtoolbox.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: mxtoolbox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free online tools to investigate/troubleshoot email server issues.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Myallsearch

  • Website: http://www.myallsearch.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Myallsearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

MyTweetAlerts

  • Website: https://www.mytweetalerts.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: MyTweetAlerts is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A tool to create custom email alerts based on Twitter search.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

n0paste

  • Website: https://n0paste.eu/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: n0paste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paste and share your code online.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Najdi (Slovenia)

  • Website: http://www.najdi.si
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Najdi (Slovenia) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Name Checkr

  • Website: http://www.namecheckr.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Name Checkr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: checks a domain and username across many platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Name Checkup

  • Website: https://namecheckup.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Name Checkup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a search tool that allows you to check the avilability of a givrn username from all over the social media. Inaddition it also sllows you to check the avilability of a given domain name.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Name Chk

  • Website: http://www.namechk.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Name Chk is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Check over 30 domains and more than 90 social media account platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

NameKetchup

  • Website: https://nameketchup.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NameKetchup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: checks domain name and username in popular social media sites and platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

NAPALM FTP Indexer

  • Website: https://www.searchftps.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NAPALM FTP Indexer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ File Search.

Back to Category Index

Nation Master

  • Website: http://www.nationmaster.com/statistics
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Nation Master is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

National Company Registers

  • Website: https://en.wikipedia.org/wiki/List_of_company_registers
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: National Company Registers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

National Speakers Association

  • Website: http://www.nsaspeaker.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: National Speakers Association is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Naukri (India)

  • Website: http://www.naukri.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Naukri (India) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

  • Website: http://www.naver.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Naver (South Korea) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

nekobin

  • Website: https://nekobin.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: nekobin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paste code, save and share the link!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

NerdyData

  • Website: https://nerdydata.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NerdyData is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search engine for source 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 OSINT > ↑ Code Search.

Back to Category Index

NetBootcamp OSINT Tools

  • Website: http://netbootcamp.org/osinttools/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: NetBootcamp OSINT Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Collection of OSINT links and custom Web interfaces to other services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > OSINT Online Resources.

Back to Category Index

Netcraft Site Report

  • Website: http://toolbar.netcraft.com/site_report?url=undefined#last_reboot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Netcraft Site Report is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an online database that will provide you a report with detail information about a particular website and the history associated with it.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Netlas.io

  • Website: https://app.netlas.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Netlas.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

NETSCOUT Cyber Threat Map

  • Website: https://horizon.netscout.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NETSCOUT Cyber Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Real-Time DDoS Attack Map.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Netvibes

  • Website: http://www.netvibes.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Netvibes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

NEUROAUTOSEARCH

  • Website: https://t.me/noblackAuto_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NEUROAUTOSEARCH is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Car DB search + neural 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 OSINT > Social Media Tools > ↑ Telegram.

Back to Category Index

New Paste

  • Website: https://paste1.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: New Paste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: I wanna paste because typing is so boring!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

NGA GEOINT

  • Website: https://github.com/ngageoint
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NGA GEOINT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Ning

  • Website: http://www.ning.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ning is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

NixIntel

  • Website: https://nixintel.info/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NixIntel is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Nixory

  • Website: http://nixory.sourceforge.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Nixory is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Nod

  • Website: http://get-nod.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Nod is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Nodebox

  • Website: https://www.nodebox.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Nodebox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a family of tools gives you the leverage to create generative design the way you want.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

NoPaste

  • Website: https://nopaste.boris.sh/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NoPaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: NoPaste is an open-source website similar to Pastebin where you can store any piece of code, and generate links for easy sharing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

nopaste.net

  • Website: https://nopaste.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: nopaste.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: nopaste.net is a temporary file host, nopaste and clipboard across machines. You can upload files or text and share the link with others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

NoScript

  • Website: https://noscript.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NoScript is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Notes

  • Website: https://notes.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Notes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: fast.easy.short.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

NRC Research Press

  • Website: http://www.nrcresearchpress.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: NRC Research Press is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Oblivion

  • Website: https://github.com/loseys/Oblivion
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Oblivion is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Observable

  • Website: https://observablehq.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Observable is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a modern way to create powerful, performant, polyglot data apps built on open source.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

OCCRP Aleph

  • Website: https://aleph.occrp.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OCCRP Aleph is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

ODCrawler

  • Website: https://odcrawler.xyz/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ODCrawler is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A search engine for open directories. Find millions of publicly available 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 OSINT > ↑ File Search.

Back to Category Index

ODIN

  • Website: https://search.odin.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ODIN is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Used to search for Hosts, CVEs & Exposed Buckets/Files and shows a website is vulnerable or not. 10 Free Searches Per Day.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Odnoklassniki (Russia)

  • Website: http://ok.ru
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Odnoklassniki (Russia) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

OECD Aid Database

  • Website: http://www.oecd.org/dac/stats/data.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OECD Aid Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

OECD Data

  • Website: https://data.oecd.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OECD Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Offliberty

  • Website: http://offliberty.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Offliberty is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that lets you access any online content without a permanent Internet connection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Offline Browsing.

Back to Category Index

Offshore Leak Database

  • Website: https://offshoreleaks.icij.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Offshore Leak Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Document and Slides Search.

Back to Category Index

OffShore.cat

  • Website: https://offshore.cat/vpn
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OffShore.cat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: list of vpns for the privacy conscious.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ VPN Services.

Back to Category Index

OkSearch

  • Website: https://telegram.me/OkSearchBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OkSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search channels, bots, groups by keyword.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

OmeaReader

  • Website: http://www.jetbrains.com/omea/reader
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OmeaReader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

One Look Reverse Dictionary

  • Website: http://www.onelook.com/reverse-dictionary.shtml
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: One Look Reverse Dictionary is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

OneMillionTweetMap

  • Website: http://onemilliontweetmap.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OneMillionTweetMap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Onet.pl (Poland)

  • Website: http://www.onet.pl
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Onet.pl (Poland) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

OnWebChange

  • Website: http://onwebchange.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OnWebChange is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

ONYPHE

  • Website: https://search.onyphe.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ONYPHE is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT engine indexing exposed assets and services across the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Open Access Scientific Journals

  • Website: http://www.pagepress.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Open Access Scientific Journals is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Open DNS

  • Website: https://www.opendns.com/home-internet-security
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Open DNS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Open Grey

  • Website: http://www.opengrey.eu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Open Grey is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Open PGP

  • Website: https://www.enigmail.net/index.php/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Open PGP is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Open Street Map

  • Website: http://www.openstreetmap.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Open Street Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

OpenCorporates

  • Website: https://opencorporates.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenCorporates is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Global search of registered corporate entities and their associated individual officers or investors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

OpenDataUABot

  • Website: https://t.me/OpenDataUABot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenDataUABot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Ukrainian OSINT bot.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

OPENHUNTING.IO

  • Website: https://openhunting.io/threat-library
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OPENHUNTING.IO is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Threat Library Collecting 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: Awesome OSINT > ↑ Threat Actor Search.

Back to Category Index

OpenLayers

  • Website: http://openlayers.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenLayers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A high-performance, feature-packed library for all your mapping needs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

OpenLinkProfiler

  • Website: http://www.openlinkprofiler.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenLinkProfiler is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

OPENLOAD Bot

  • Website: https://t.me/OPENLOADTOPBOT
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OPENLOAD Bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Semi-automated OSINT/vuln scanning 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: Awesome OSINT > Social Media Tools > ↑ Telegram.

Back to Category Index

OpenOwnership Register

  • Website: https://register.openownership.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenOwnership Register is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

OpenRefine

  • Website: https://github.com/OpenRefine
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenRefine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free & open source power tool for working with messy data and improving it.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

OpenSanctions

  • Website: https://www.opensanctions.org/search/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpenSanctions is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Information on sanctions and public office holders.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Opera

  • Website: http://www.opera.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Opera is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

OpinionCrawl

  • Website: http://www.opinioncrawl.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OpinionCrawl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Orange (France)

  • Website: http://www.orange.fr
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Orange (France) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Orbis directory

  • Website: http://orbisdirectory.bvdinfo.com/version-20161014/OrbisDirectory/Companies
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Orbis directory is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Orbit

  • Website: https://github.com/s0md3v/Orbit
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Orbit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Draws relationships between crypto wallets with recursive crawling of transaction history.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Oscobo Search Engine

  • Website: https://oscobo.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Oscobo Search Engine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

OSINT Ambition Publication

  • Website: https://publication.osintambition.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT Ambition Publication is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

OSINT Belarus

  • Website: https://t.me/s/osintby
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT Belarus is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Other Resources.

Back to Category Index

OSINT Dojo

  • Website: https://www.osintdojo.com/resources/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT Dojo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Other Resources.

Back to Category Index

OSINT Framework

  • Website: http://osintframework.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: OSINT Framework is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Collection of various OSINT tools broken out by 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: Awesome Penetration Testing > Open Sources Intelligence (OSINT) > OSINT Online Resources.

Back to Category Index

OSINT Team

  • Website: https://www.osintteam.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT Team is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

OSINT Techniques

  • Website: https://www.osinttechniques.com/blog
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT Techniques is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

OSINT x UCCU Workshop on Open Source Intelligence

  • Website: https://www.slideshare.net/miaoski/osint-x-uccu-workshop-on-open-source-intelligence
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: OSINT x UCCU Workshop on Open Source Intelligence is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > OSINT.

Back to Category Index

OSINT-Steam

  • Website: https://osint-steam.vercel.app/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT-Steam is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An tool that returns public information, such as friends list and possible locations, from Steam profiles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Steam.

Back to Category Index

OSINT-Tool

  • Website: https://www.osint-tool.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT-Tool is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A browser extension that gives you access to a suite of OSINT utilities (Dehashed, Epieos, Domaintools, Exif data, Reverse image search, etc) directly on any webpage you visit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

OSINT.SH

  • Website: https://osint.sh/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINT.SH is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Information Gathering Toolset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

OSINTCurious

  • Website: https://osintcurio.us/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINTCurious is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

OSINTEye

  • Website: https://github.com/atiilla/OsintEye
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OSINTEye is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT Eye: A WPF Desktop Application for GitHub Intelligence, Social Media Reconnaissance, and Subdomain 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

Osintgram

  • Website: https://github.com/Datalux/Osintgram
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Osintgram is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Osintgram offers an interactive shell to perform analysis on Instagram account of any users by its nickname.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Instagram.

Back to Category Index

Osintkit

  • Website: https://t.me/osintkit_check_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Osintkit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Ukrainian lookup: passport, tax ID, email, phone, address, vehicles, Telegram.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

OTS- One Time Secrets

  • Website: https://ots.hackliberty.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: OTS- One Time Secrets is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An encrypted pastebin site. No login needed!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Outwit

  • Website: http://www.outwit.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Outwit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find, grab and organize all kinds of data and media from online sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Overseas Company Registers

  • Website: https://www.gov.uk/government/publications/overseas-registries/overseas-registries
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Overseas Company Registers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Oxford Journals

  • Website: http://www.oxfordjournals.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Oxford Journals is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

paaster

  • Website: https://paaster.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paaster is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paaster is a secure and user-friendly pastebin application that prioritizes privacy and simplicity. With end-to-end encryption and paste history, Paaster ensures that your pasted code remains confidential and accessible.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

PageGlimpse

  • Website: http://www.pageglimpse.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PageGlimpse is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

pagodo

  • Website: https://github.com/opsdisk/pagodo
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: pagodo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Automate Google Hacking Database scraping.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

Palladio

  • Website: http://hdlab.stanford.edu/palladio
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Palladio is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Visualize complex historical data with ease.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Panopticlick

  • Website: https://panopticlick.eff.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Panopticlick is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Parseek (Iran)

  • Website: http://www.parseek.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Parseek (Iran) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

PasswordSearch

  • Website: https://telegram.me/PasswordSearchBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PasswordSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Shows leaked passwords for an email.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

PastBin.net

  • Website: https://pastbin.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PastBin.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Similar to Pastebin website where you can store code/text online for a set period of time and share to anyone anywhere. Search Option Available.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Paste.Cash

  • Website: https://www.paste.cash/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Paste.Cash is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paste.CASH Is a privacy respected and encrypted pastebin hosted by Cash Hosting. Every paste are encrypted using 256 bits AES.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

paste.debian

  • Website: https://Paste.debian.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paste.debian is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

paste.in.ua

  • Website: https://paste.in.ua/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paste.in.ua is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Simple pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

paste.kde

  • Website: https://Paste.kde.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paste.kde is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

Paste.Monster

  • Website: https://paste.monster/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Paste.Monster is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Share your thoughts online. API Available.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Paste.Quest

  • Website: https://pastequest.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Paste.Quest is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Copy and Paste text online to share with anyone anywhere. Use the password option to add a password to the pasted 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: Awesome OSINT > ↑ Pastebins.

Back to Category Index

paste.sh

  • Website: https://paste.sh/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paste.sh is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: This is an encrypted paste site. Simply type or paste code here and share the URL. Saving is Automatic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

paste.ubuntu

  • Website: https://paste.ubuntu.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: paste.ubuntu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Pastebins.

Back to Category Index

Pastebin

  • Website: https://pastebin.pl/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pastebin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Store code/text online for a set period of time and share to anybody on earth.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

  • Website: https://tor.link/paste/new
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pastebin - Tor Link is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Paste text to store or share with others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Pastebin.cz

  • Website: https://www.pastebin.cz/en/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pastebin.cz is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A simple Pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Pastery

  • Website: https://www.pastery.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pastery is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The sweetest pastebin in the world!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

PasteShr

  • Website: https://www.pasteshr.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PasteShr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Store any text online for easy sharing. Search option available!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

PasteSite.Net

  • Website: https://pastesite.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PasteSite.Net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The new generation pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

  • Website: https://oedci.uspto.gov/OEDCI/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Patent Attorneys/Agent Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Official listing of U.S. attorneys qualified to represent individuals in U.S. patent office proceedings.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Expert Search.

Back to Category Index

Paul Hensel’s General Informational Data Page

  • Website: http://www.paulhensel.org/dataintl.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Paul Hensel’s General Informational Data Page is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

PeekYou

  • Website: https://www.peekyou.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PeekYou is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: PeekYou offers the ability to search for people with checks done against more sites. Can check for arrest records as well.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Peepmail

  • Website: http://www.samy.pl/peepmail
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Peepmail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a tool that allows you to discover business email addresses for users, even if their email address may not be publicly available or shared.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Peerblock

  • Website: http://forums.peerblock.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Peerblock is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Penn World Table

  • Website: http://www.rug.nl/research/ggdc/data/pwt/pwt-8.1
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Penn World Table is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Pentest-Tools.com

  • Website: https://pentest-tools.com/information-gathering/google-hacking
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pentest-Tools.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: uses advanced search operators (Google Dorks) to find juicy information about target 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

Perplexity

  • Website: https://www.perplexity.ai
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Perplexity is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI-powered search engine with source citations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Perry Castaneda Library

  • Website: https://www.lib.utexas.edu/maps
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Perry Castaneda Library is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

personal-security-checklist

  • Website: https://github.com/Lissy93/personal-security-checklist
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: personal-security-checklist is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: by @Lissy93.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Related Awesome Lists.

Back to Category Index

Perspective

  • Website: https://github.com/finos/perspective
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Perspective is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: interactive data visualization and analytics component, well-suited for large, streaming and static datasets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Pew Research Center

  • Website: http://www.pewinternet.org/datasets
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pew Research Center is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

PGPKeyAnalyser

  • Website: https://kriztalz.sh/pgp-key-analyser/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PGPKeyAnalyser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Analyse and view the details of a PGP key online without having to download the asc file.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Phind

  • Website: https://www.phind.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Phind is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI search engine optimized for developers and technical questions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Phone Validator

  • Website: https://www.phonevalidator.com/index.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Phone Validator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Pretty accurate phone lookup service, particularly good against Google Voice numbers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

PhoneInfoga

  • Website: https://github.com/sundowndev/PhoneInfoga
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PhoneInfoga is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Advanced information gathering & OSINT framework for phone numbers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

PhotoBucket

  • Website: https://photobucket.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PhotoBucket is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Photon

  • Website: https://github.com/s0md3v/Photon
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Web Security

What it does: Photon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Incredibly fast crawler designed for OSINT 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Pic2Map

  • Website: https://www.pic2map.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pic2Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

PicTriev

  • Website: http://www.pictriev.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PicTriev is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a face search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

Pidgin

  • Website: https://www.pidgin.im
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pidgin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Piktochart

  • Website: https://piktochart.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Piktochart is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

PimEyes

  • Website: https://telegram.me/pimeyesbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PimEyes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Face-search across social 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 OSINT > Social Media Tools > ↑ Telegram.

Back to Category Index

PimEyes

  • Website: https://pimeyes.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PimEyes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: an online face search engine that goes through the Internet to find pictures containing given faces.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

Pingroupie

  • Website: http://pingroupie.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pingroupie is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Pinterest.

Back to Category Index

Pinterest

  • Website: http://www.pinterest.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pinterest is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an image sharing social media service used to easly discover, share and save ideas using visual representation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Major Social Networks.

Back to Category Index

Pinterest Pin Stats

  • Website: https://chromewebstore.google.com/detail/pinterest-pin-stats-sort/mcmkeopcpbfgjlakblglpcccpodbjkel
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pinterest Pin Stats is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Display hidden Pinterest stats for each pin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Pinterest.

Back to Category Index

Pipl

  • Website: https://pipl.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pipl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a provider of identity solutions.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Pixel Block

  • Website: https://chrome.google.com/webstore/detail/pixelblock/jmpmfcjnflbcoidlgapblgpgbilinlem
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pixel Block is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Pixsy

  • Website: https://www.pixsy.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pixsy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Take back control of your images. See where & how your images are being used online!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

Pixxa

  • Website: http://www.pixxa.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pixxa is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Plotly

  • Website: https://plot.ly
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Plotly is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Plunkett Research

  • Website: http://www.plunkettresearchonline.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Plunkett Research is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Polymaps

  • Website: http://polymaps.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Polymaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Population Reference Bureau Data Finder

  • Website: http://www.prb.org/DataFinder.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Population Reference Bureau Data Finder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Preceden

  • Website: https://www.preceden.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Preceden is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Create a Visual Timeline About Any Topic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Infographics and Data Visualization.

Back to Category Index

  • Website: https://predictasearch.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Predicta Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for social accounts with e-mail and phone.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Presearch

  • Website: https://presearch.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Presearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Presearch is a decentralized, community-driven search engine that protects your privacy and rewards you when you search.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Press Reader

  • Website: http://www.pressreader.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Press Reader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Privacy Badger

  • Website: https://www.eff.org/privacybadger
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Privacy Badger is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Privacy.com

  • Website: https://privacy.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Privacy.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Virtual payment cards for online privacy and 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 OSINT > ↑ Privacy and Encryption Tools.

Back to Category Index

Privazer

  • Website: http://privazer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Privazer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

ProfileImageIntel

  • Website: https://profileimageintel.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ProfileImageIntel is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Social media and WhatsApp profile image tool to find when a profile image was uploaded.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Analysis.

Back to Category Index

Proton Mail

  • Website: https://protonmail.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Proton Mail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

PRS Risk Indicators

  • Website: http://www.prsgroup.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PRS Risk Indicators is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

psn_monitor

  • Website: https://github.com/misiektoja/psn_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: psn_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Sony Playstation (PSN) players gaming activities including detection when a user gets online/offline or plays games with support for email alerts, CSV logging, playtime stats 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 OSINT > ↑ Gaming Platforms.

Back to Category Index

PublicWWW

  • Website: https://publicwww.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: PublicWWW is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Code Search.

Back to Category Index

Pullpush

  • Website: https://pullpush.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pullpush is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: PullPush is a service for the indexing and retrieval of content that Reddit users have submitted to Reddit. Helpful for finding deleted/removed posts & comments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Pushshift API

  • Website: https://pushshift.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Pushshift API is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A powerful API that provides access to historical Reddit data, including posts, comments, and metadata for analysis and research—more 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: Awesome OSINT > Social Media Tools > ↑ Reddit.

Back to Category Index

pygreynoise

  • Website: https://github.com/GreyNoise-Intelligence/pygreynoise
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: pygreynoise is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Greynoise Python Library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

QGIS

  • Website: http://qgis.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: QGIS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

QlikView

  • Website: https://www.visualintelligence.co.nz/qlikview
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: QlikView is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Quadrigram

  • Website: http://www.quadrigram.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Quadrigram is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Qualys SSL Check

  • Website: https://www.ssllabs.com/ssltest/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Web Security

What it does: Qualys SSL Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Online service that performs a deep analysis of the configuration of any SSL web server on the public internet. Provided 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

Quantcast

  • Website: https://www.quantcast.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Quantcast is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Qubes OS

  • Website: https://www.qubes-os.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Security, Awesome OSINT, Awesome Cyber Security Tools

What it does: Qubes OS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Qubes OS is a free and open-source security-oriented operating system meant for single-user desktop computing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

  • Website: https://www.quetzal-search.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Quetzal Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Quick Sprout

  • Website: https://www.quicksprout.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Quick Sprout is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

QuickCode

  • Website: https://quickcode.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: QuickCode is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Python and R data analysis environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

QuickMaps

  • Website: https://chrome.google.com/webstore/detail/quick-maps/bgbojmobaekecckmomemopckmeipecij
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: QuickMaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Quora

  • Website: http://www.quora.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Quora is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Qwant

  • Website: http://www.qwant.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Qwant is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: French search engine that relies on Microsoft Bing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Meta Search.

Back to Category Index

Qwant

  • Website: https://www.qwant.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Qwant is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The search engine that respects your privacy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Qzone (China)

  • Website: http://qzone.qq.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Qzone (China) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

Raphael

  • Website: http://dmitrybaranovskiy.github.io/raphael
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Raphael is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

raven

  • Website: https://github.com/0x09AL/raven
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: raven is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: raven is a Linkedin information gathering tool that can be used by pentesters to gather information about an organization employees using Linkedin 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

RAW

  • Website: http://raw.densitydesign.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RAW is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Reacher

  • Website: https://reacher.email
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reacher is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Real-time email verification API, written in Rust, 100% open-source.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

RECAP Archive

  • Website: https://www.courtlistener.com/recap/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RECAP Archive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Public archive of PACER court documents.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Document and Slides Search.

Back to Category Index

Recon-ng

  • Website: https://github.com/lanmaster53/recon-ng
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: Recon-ng is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Recon-ng is a full-featured Web Reconnaissance framework written in Python. Recon-ng has a look and feel similar to 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 > Open Sources Intelligence (OSINT).

Back to Category Index

ReconDog

  • Website: https://github.com/s0md3v/ReconDog
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: ReconDog is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reconnaissance Swiss Army Knife 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

RecruitEm

  • Website: https://recruitin.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RecruitEm is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

REDARCS

  • Website: https://the-eye.eu/redarcs/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: REDARCS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reddit archives 2005-2023.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Reddit

  • Website: https://www.reddit.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

Reddit Archive

  • Website: http://www.redditarchive.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit Archive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Historical archives of reddit posts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Reddit Comment Lookup

  • Website: https://randomtools.io/reddit-comment-search/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit Comment Lookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for reddit comments by reddit username.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

  • Website: https://redditcommentsearch.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit Comment Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Analyze a reddit users by comment history.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Reddit Suite

  • Website: https://chrome.google.com/webstore/detail/reddit-enhancement-suite/kbmfpngjjgdllneeigpgjifpgocmfgmb
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit Suite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Enhances your reddit experience.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

Reddit User Analyser

  • Website: https://atomiks.github.io/reddit-user-analyser/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reddit User Analyser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: reddit user account analyzer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

RedditMetis

  • Website: https://redditmetis.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RedditMetis is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: RedditMetis is a Reddit user analysis tool to see the summary and statistics for a Reddit account, including top posts and user activity etc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

RedirectDetective

  • Website: http://redirectdetective.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RedirectDetective is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Reed (UK)

  • Website: http://www.reed.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reed (UK) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Reeder

  • Website: http://reederapp.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reeder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

RegDateBot

  • Website: https://t.me/regdate_clone_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RegDateBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Registration date by ID/forward.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Remote DNS Lookup

  • Website: https://remote.12dt.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Remote DNS Lookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Rentry

  • Website: https://rentry.co/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Rentry is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Rentry.co is a markdown paste service service with preview, custom urls and editing. Fast, simple and free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Reposearch

  • Website: http://codefinder.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reposearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Code Search.

Back to Category Index

ReseacherID

  • Website: http://www.researcherid.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ReseacherID is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Research Gate

  • Website: http://www.researchgate.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Research Gate is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Resolver

  • Website: https://metaproductsrevolver.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Resolver is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

Reunion

  • Website: http://reunion.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reunion is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: People search. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

Reuters

  • Website: http://www.reuters.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reuters is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Reverse Phone Check

  • Website: https://www.reversephonecheck.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reverse Phone Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Look up names, addresses, phone numbers, or emails and anonymously discover information about yourself, family, friends, or old schoolmates. Powered by infotracer.com.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Reverse Phone Lookup

  • Website: http://www.reversephonelookup.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Reverse Phone Lookup is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Detailed information about phone carrier, region, service provider, and switch 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: Awesome OSINT > ↑ Phone Number Research.

Back to Category Index

RiteTag

  • Website: https://ritetag.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RiteTag is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Rival IQ

  • Website: https://www.rivaliq.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Rival IQ is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Robtex

  • Website: https://www.robtex.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Robtex is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is an IP address and domain name based researching websites that offers multiple services such as Reverse DNS Lookup, Whois, and AS Macros.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Ronin

  • Website: https://ronin-rb.dev
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Ronin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free and Open Source Ruby Toolkit for Security Research and Development, providing many different libraries and commands for a variety of security tasks, such as recon, vulnerability scanning, exploit development, exploitation, post-exploitation, 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 > Multi-paradigm Frameworks.

Back to Category Index

Router Passwords

  • Website: https://www.routerpasswords.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Router Passwords is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Online database of default router passwords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

RSS Feed Reader

  • Website: https://chrome.google.com/webstore/detail/rss-feed-reader/pnjaodmkngahhkoihejjehlcdlnohgmp
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RSS Feed Reader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

RSS Micro

  • Website: http://www.rssmicro.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RSS Micro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

RSS Search Engine

  • Website: http://ctrlq.org/rss
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RSS Search Engine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

RSS Search Hub

  • Website: http://www.rsssearchhub.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RSS Search Hub is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

RSSOwl

  • Website: http://www.rssowl.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: RSSOwl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Safari

  • Website: http://www.apple.com/safari
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Safari is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

SafeNote

  • Website: https://safenote.co/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SafeNote is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: SafeNote is a free web-based service that allows you to share a note or a file with confidentiality. There is no way to spying on you even to a hacker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

SAGE Journals

  • Website: http://online.sagepub.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SAGE Journals is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

SameID

  • Website: http://sameid.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SameID is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

SangMata (beta)

  • Website: https://t.me/SangMata_beta_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SangMata (beta) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Name-change history via /search_id.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

SangMataInfo_bot

  • Website: https://t.me/SangMataInfo_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SangMataInfo_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Username change history.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

SANS OSINT Summit 2021 (Playlist)

  • Website: https://www.youtube.com/playlist?list=PLs4eo9Tja8bj3jJvv42LxOkhc2_ylpS9y
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT, Awesome Threat Detection, Awesome Hacking

What it does: SANS OSINT Summit 2021 (Playlist) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Videos.

Back to Category Index

SAPO (Portugal)

  • Website: http://www.sapo.pt
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SAPO (Portugal) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

SAS Planet

  • Website: http://www.sasgis.org/sasplaneta/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SAS Planet is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Software used to view, download and stitch satellite images.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Satellites Pro

  • Website: https://satellites.pro/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Satellites Pro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

SatIntel

  • Website: https://github.com/ANG13T/SatIntel
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SatIntel is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

SaveYoutubeBot

  • Website: https://t.me/SaveYoutubeBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SaveYoutubeBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Finds and downloads YouTube videos.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Science Publications

  • Website: http://www.thescipub.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Science Publications is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

ScienceDirect

  • Website: http://www.sciencedirect.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ScienceDirect is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

ScienceDomain

  • Website: http://www.sciencedomain.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ScienceDomain is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

SCIRP

  • Website: http://www.scirp.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SCIRP is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Scoot

  • Website: http://www.scoot.co.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Scoot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

Scribble Maps

  • Website: http://scribblemaps.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Scribble Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Scribd

  • Website: http://www.scribd.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Scribd is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Document and Slides Search.

Back to Category Index

Script Safe

  • Website: https://chrome.google.com/webstore/detail/scriptsafe/oiigbmnaadbkfbmpbfijlflahbdbdgdf?hl=en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Script Safe is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

  • Website: https://scrt.link/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: scrt.link is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Share a Secret with a link that only works one time and then self-destructs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Search.ch (Switzerland)

  • Website: http://www.search.ch
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Search.ch (Switzerland) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Search.com

  • Website: https://www.search.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Search.com is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search the Web by searching the best engines from 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 OSINT > ↑ General Search.

Back to Category Index

Search4faces

  • Website: https://search4faces.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Search4faces is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a service for searching people on the Internet by photo.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

Search_firm_bot

  • Website: https://t.me/Search_firm_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Search_firm_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches organizations, banks, postal codes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

SearchBug

  • Website: http://www.searchbug.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchBug is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: People search. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

SearchCode

  • Website: https://searchcode.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchCode is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Help find real world examples of functions, API's and libraries across 10+ sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Code Search.

Back to Category Index

SearchDorks

  • Website: https://kriztalz.sh/search-dorks/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchDorks is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Generate Search Engine (Google, FOFA, Shodan, Censys, ZoomEye) Dorks using AI.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Google Dorks Tools.

Back to Category Index

SearchFiles.de

  • Website: https://searchfiles.de/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchFiles.de is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ File Search.

Back to Category Index

Searchforchats

  • Website: https://telegram.me/searchforchatsbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Searchforchats is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches chats by keywords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

SearchIsBack

  • Website: https://searchisback.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchIsBack is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Facebook.

Back to Category Index

SearchPeopleFREE

  • Website: https://www.searchpeoplefree.com/phone-lookup
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SearchPeopleFREE is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a reverse name, address, email address, or phone lookup that allows you to discover the owner of a phone number or who lives at an address.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Sector035

  • Website: https://sector035.nl/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sector035 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Secure Gateway Live Cyber Threat Map

  • Website: https://securegateway.com/map/v5/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Secure Gateway Live Cyber Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Securesha

  • Website: https://securesha.re
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Securesha is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

security-list

  • Website: https://github.com/zbetcheckin/Security_list
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: security-list is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: by @zbetcheckin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Related Awesome Lists.

Back to Category Index

Seek (Australia)

  • Website: http://www.seek.com.au
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Seek (Australia) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Seekr

  • Website: https://github.com/seekr-osint/seekr
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Seekr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A multi-purpose all in one toolkit for gathering and managing OSINT-Data with a neat web-interface. Can be used for note taking and username checking.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Selfoss

  • Website: http://selfoss.aditu.de
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Selfoss is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

SEMrush

  • Website: https://www.semrush.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SEMrush is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Sentiment140

  • Website: http://www.twittersentiment.appspot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sentiment140 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Sentinel Hub

  • Website: https://www.sentinel-hub.com/explore/sentinelplayground/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sentinel Hub is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

SEO Chat Tools

  • Website: http://tools.seochat.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SEO Chat Tools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

SEOTools for Excel

  • Website: http://seotoolsforexcel.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SEOTools for Excel is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

SerpApi

  • Website: https://serpapi.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SerpApi is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Scrapes Google search and 25+ search engines with ease and retruns a raw JSON. Supports 10 API wrappers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

SerpScan

  • Website: https://github.com/Alaa-abdulridha/SerpScan
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SerpScan is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Powerful PHP script designed to allow you to leverage the power of dorking straight from the comfort of your command line. Analyzes data from Google, Bing, Yahoo, Yandex, and Badiu.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Serpstat

  • Website: https://serpstat.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Serpstat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

SESRIC Basic Social and Economic Indicators

  • Website: http://www.sesric.org/baseind.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SESRIC Basic Social and Economic Indicators is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

SESRIC Databases

  • Website: http://www.sesric.org/databases-index.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SESRIC Databases is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Seznam(Czech Republic)

  • Website: https://seznam.cz
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Seznam(Czech Republic) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Shadowserver

  • Website: https://dashboard.shadowserver.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Shadowserver is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Dashboard with global statistics on cyber threats collected by the Shadowserver Foundation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

Shanti Interactive

  • Website: http://www.viseyes.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Shanti Interactive is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Sherlock

  • Website: https://t.me/Getcontact123qwerty_bot?start=_ref_jGW8Sa_iEmG9V
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sherlock is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Name/phone/email search + vehicle data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Sherlock

  • Website: https://github.com/sherlock-project/sherlock
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sherlock is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for a username in multiple platforms/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: Awesome OSINT > ↑ Username Check.

Back to Category Index

SherlockEye

  • Website: https://sherlockeye.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SherlockEye is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for publicly available information connected to a username, uncovering associated profiles and activities across the web.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

SheSource

  • Website: http://www.shesource.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SheSource is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Shotstars

  • Website: https://github.com/snooppr/shotstars
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Shotstars is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An advanced tool for checking GitHub repositories, with star statistics, including fake star analysis and data visualization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ GitHub.

Back to Category Index

ShtrafKZBot

  • Website: https://t.me/ShtrafKZBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ShtrafKZBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Fines, taxes, penalties; traffic violations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Signal

  • Website: https://signal.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Signal is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: End-to-end encrypted messaging and calls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Silent circle

  • Website: https://www.silentcircle.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Silent circle is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Silobreaker

  • Website: http://www.silobreaker.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Silobreaker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Similar Web

  • Website: https://www.similarweb.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Similar Web is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Compare any website traffic statistics & analytics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

SimilarSites

  • Website: http://www.similarsites.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SimilarSites is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Discover websites that are similar to each other.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Similar Sites Search.

Back to Category Index

SimplyEmail

  • Website: https://github.com/SimplySecurity/SimplyEmail
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: SimplyEmail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Email recon made fast and easy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Email search and analysis tools.

Back to Category Index

SimplyHired

  • Website: http://www.simplyhired.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SimplyHired is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Sintelix

  • Website: https://sintelix.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sintelix is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Sintelix is an open source intelligence (OSINT) and graphical link analysis tool for gathering and connecting information for investigative 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 OSINT > ↑ Other Tools.

Back to Category Index

SitesLike

  • Website: http://www.siteslike.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SitesLike is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find similar websites by 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: Awesome OSINT > ↑ Similar Sites Search.

Back to Category Index

SiteSucker

  • Website: http://ricks-apps.com/osx/sitesucker/index.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SiteSucker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

Skiptracer

  • Website: https://github.com/xillwillx/skiptracer
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Skiptracer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: OSINT scraping framework that utilizes basic Python webscraping (BeautifulSoup) of PII paywall sites to compile passive information on a target on a ramen noodle budget.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Skopenow

  • Website: https://www.skopenow.com/news
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Skopenow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Sleipnir

  • Website: http://www.fenrir-inc.com/jp/sleipnir
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sleipnir is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Sleuth For The Truth

  • Website: http://sleuthforthetruth.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sleuth For The Truth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

SlideShare

  • Website: http://www.slideshare.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SlideShare is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Document and Slides Search.

Back to Category Index

Slimjet

  • Website: http://www.slimjet.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Slimjet is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

SmallSEOTools

  • Website: http://smallseotools.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SmallSEOTools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

SMS Activate

  • Website: https://t.me/PrivatePhoneBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SMS Activate is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Virtual numbers from 50+ countries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

sn0int

  • Website: https://github.com/kpcyrd/sn0int
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: sn0int is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Semi-automatic OSINT framework and package 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: Awesome Penetration Testing > Open Sources Intelligence (OSINT).

Back to Category Index

Sn1per

  • Website: https://github.com/1N3/Sn1per
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Sn1per is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Automated Pentest Recon Scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Snappa

  • Website: https://snappa.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Snappa is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

snippet.host

  • Website: https://snippet.host/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: snippet.host is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Minimal text and code snippet hosting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

snitch

  • Website: https://github.com/Smaash/snitch
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: snitch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Information gathering via dorks.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

Snoop

  • Website: https://github.com/snooppr/snoop/blob/master/README.en.md
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Snoop is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for a nickname on the web (OSINT world).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

Snopes

  • Website: http://www.snopes.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Snopes is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The definitive Internet reference source for urban legends, folklore, myths, rumors, and misinformation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Fact Checking.

Back to Category Index

Snov.io

  • Website: https://snov.io/email-finder
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Snov.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find email addresses on any 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

Social Analyzer

  • Website: https://github.com/qeeqbox/social-analyzer
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Social Analyzer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: API, CLI, and Web App for analyzing and finding a person's profile in 1000 social media \ 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: Awesome OSINT > ↑ Username Check.

Back to Category Index

Social DownORNot

  • Website: http://social.downornot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Social DownORNot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

  • Website: https://blog.sociallinks.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Social Links is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ OSINT Blogs.

Back to Category Index

Social Mapper

  • Website: https://github.com/SpiderLabs/social_mapper
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: Social Mapper is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Social Media Enumeration & Correlation Tool by Jacob Wilkin(Greenwolf) 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Social Searcher

  • Website: http://www.social-searcher.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Social Searcher is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

SocialBakers

  • Website: http://www.socialbakers.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SocialBakers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

SocialBlade

  • Website: http://socialblade.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SocialBlade is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Socialcatfish

  • Website: https://socialcatfish.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Socialcatfish is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Superextensive people search which works worldwide. Searches are done from 200 Billion records.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

SOCRadar LABS

  • Website: https://socradar.io/labs/threat-actor/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SOCRadar LABS is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Know threat actor tactics, techniques, and past activities. Access detailed profiles and track their activities.Keep up with the latest threats and Tactics, Techniques, and Procedures (TTPs).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Actor Search.

Back to Category Index

SoGou (China)

  • Website: http://www.sogou.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SoGou (China) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Soovle

  • Website: http://www.soovle.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Soovle is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

Sourcebot

  • Website: https://www.sourcebot.dev/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sourcebot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Index thousands of repos on your machine and search through them in a fast, powerful, and modern web interface.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Code Search.

Back to Category Index

SourceGraph

  • Website: https://sourcegraph.com/search
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SourceGraph is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search code from millions of open source 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 OSINT > ↑ Code Search.

Back to Category Index

Sources

  • Website: http://www.sources.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sources is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Spacebin

  • Website: https://spaceb.in/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spacebin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Spacebin is a modern Pastebin server implemented in Go and is capable of serving notes, novels, code, or any other form of text.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Spamhaus

  • Website: https://check.spamhaus.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spamhaus is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Lookup Reputation Checker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

SpiderFoot

  • Website: https://github.com/smicallef/spiderfoot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SpiderFoot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: SpiderFoot Github repository.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Spideroak

  • Website: https://spideroak.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spideroak is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

SpiderSuite

  • Website: https://github.com/3nock/SpiderSuite
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SpiderSuite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An advance, cross-platform, GUI web security crawler.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Spike

  • Website: http://www.newswhip.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spike is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Spokeo

  • Website: http://www.spokeo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spokeo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: People search. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

spotify_monitor

  • Website: https://github.com/misiektoja/spotify_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: spotify_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Spotify friends' listening activity including detection when user gets online & offline, played songs, its duration, skipped songs, with optional auto-play, email alerts, CSV logging, session stats 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 OSINT > ↑ Music Streaming Services.

Back to Category Index

spotify_profile_monitor

  • Website: https://github.com/misiektoja/spotify_profile_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: spotify_profile_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Spotify users' activities and profile changes, including playlists, with support for email alerts, CSV logging, showing media in the terminal, detection of profile picture changes 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 OSINT > ↑ Music Streaming Services.

Back to Category Index

Springer

  • Website: http://link.springer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Springer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Spy Dialer

  • Website: http://spydialer.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Spy Dialer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Get the voicemail of a cell phone & owner name lookup.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

SpyFu

  • Website: http://www.spyfu.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SpyFu is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

SpyGGbot

  • Website: https://telegram.me/SpyGGbot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SpyGGbot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: TON balances, NFT owners, Fragment usernames.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Spyse

  • Website: https://spyse.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Hacking

What it does: Spyse is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Data gathering service that collects web info using OSINT. Provided info: IPv4 hosts, domains/whois, ports/banners/protocols, technologies, OS, AS, maintains huge SSL/TLS DB, and more... All the data is stored in its own database allowing get the data without scanning.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Squatm3gator

  • Website: https://github.com/david3107/squatm3gator
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Squatm3gator is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Enumerate available domains generated modifying the original domain name through different cybersquatting techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

SRWare Iron

  • Website: http://www.srware.net/en/software_srware_iron.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SRWare Iron is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

StackExchange

  • Website: http://stackexchange.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: StackExchange is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Startpage

  • Website: https://www.startpage.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Startpage is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The world’s most private search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Statista

  • Website: http://www.statista.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Statista is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

StatsCrop

  • Website: http://www.statscrop.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: StatsCrop is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

StealSeek

  • Website: https://stealseek.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: StealSeek is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Powerful search engine designed to help you find and analyze data breaches.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

Steam-OSINT

  • Website: https://github.com/matiash26/steam-osint
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Steam-OSINT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Open-source OSINT tool for accurate mutual friends analysis on Steam, supporting full friend lists.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Steam.

Back to Category Index

steam_monitor

  • Website: https://github.com/misiektoja/steam_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: steam_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Steam players' gaming activities including detection when a user gets online/offline or plays games with support for email alerts, CSV logging, playtime stats 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 OSINT > ↑ Gaming Platforms.

Back to Category Index

Steganography Online Codec

  • Website: https://www.pelock.com/products/steganography-online-codec
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Steganography Online Codec is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

stored.website

  • Website: https://stored.website
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: stored.website is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web History and Website Capture.

Back to Category Index

Storyful

  • Website: http://storyful.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Storyful is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

StoryMap

  • Website: https://storymap.knightlab.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: StoryMap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

StoryMaps

  • Website: http://storymaps.arcgis.com/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: StoryMaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Sub3 Suite

  • Website: https://github.com/3nock/sub3suite
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sub3 Suite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A research-grade suite of tools for intelligence gathering & target mapping with both active and passive(100+ modules) intelligence gathering 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 OSINT > ↑ Other Tools.

Back to Category Index

SubDomainRadar.io

  • Website: https://subdomainradar.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SubDomainRadar.io is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Fast subdomain finder with multiple search modes and the most extensive data sources, offering real-time notifications.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

subDomainsBrute

  • Website: https://github.com/lijiejie/subDomainsBrute
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: subDomainsBrute is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A simple and fast sub domain brute tool for pentesters 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 > Reconnaissance > Sub Domain Enumeration.

Back to Category Index

Subreddits

  • Website: http://subreddits.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Subreddits is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Discover new subreddits.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

SunCalc

  • Website: https://www.suncalc.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: SunCalc is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Superdesk

  • Website: https://www.superdesk.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Superdesk is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Surfface

  • Website: https://surfface.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Surfface is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: face search and people finder indexing social profiles and public images from social media and the web.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

surfraw

  • Website: https://github.com/kisom/surfraw
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: surfraw is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Fast UNIX command line interface to a variety of popular WWW search engines.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Data Broker and Search Engine Services.

Back to Category Index

Surftg_bot

  • Website: https://t.me/surftg_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Surftg_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searches Telegram messages.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Surveilliance Self Defense

  • Website: https://ssd.eff.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Surveilliance Self Defense is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Swisscows

  • Website: https://swisscows.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Swisscows is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Meta Search.

Back to Category Index

swisscows

  • Website: https://swisscows.com/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: swisscows is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Anonymous search engine, a family-friendly, privacy-focused search engine based in Switzerland.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Focused Search Engines.

Back to Category Index

Sync.ME

  • Website: https://sync.me/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Sync.ME is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a caller ID and spam blocker app.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Tableau

  • Website: http://www.tableausoftware.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tableau is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Tableau

  • Website: http://www.tableau.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tableau is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Tableau Public

  • Website: https://public.tableau.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tableau Public is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Tagboard

  • Website: https://tagboard.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tagboard is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Tagdef

  • Website: https://tagdef.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tagdef is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Tagul

  • Website: https://tagul.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tagul is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Taringa (Latin America)

  • Website: http://www.taringa.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Taringa (Latin America) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

Taylor & Francis Online

  • Website: http://www.tandfonline.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Taylor & Francis Online is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Telegago

  • Website: https://cse.google.com/cse?q=+&cx=006368593537057042503:efxu7xprihg#gsc.tab=0&gsc.q=%20&gsc.page=1
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telegago is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A Google Advanced Search specifically for finding public and private Telegram Channels and Chatrooms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telegram Channel Joiner

  • Website: https://github.com/spmedia/Telegram-Channel-Joiner
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telegram Channel Joiner is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: grow your Free and Premium Telegram accounts easily with this channel joiner script.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telegram channels scraper TeleGraphite

  • Website: https://github.com/hamodywe/telegram-scraper-TeleGraphite
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telegram channels scraper TeleGraphite is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Telegram Scraper & JSON Exporter & telegram channels scraper.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telegram Finder

  • Website: https://www.telegram-finder.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telegram Finder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A tool to find Telegram users by their phone number, linkedin url or email.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telegram Nearby Map

  • Website: https://github.com/tejado/telegram-nearby-map
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telegram Nearby Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Webapp based on OpenStreetMap and the official Telegram library to find the position of nearby users.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telepahty

  • Website: https://github.com/proseltd/Telepathy-Community
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telepahty is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Telepathy is a tool that archives Telegram chats and analyzes communication patterns within the app. By providing insights into user interactions, message frequency, and content trends, Telepathy helps investigators understand the dynamics and relationships within Telegram groups and channels.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Telerecon

  • Website: https://github.com/sockysec/Telerecon
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Telerecon is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A reconnaissance framework for researching and investigating Telegram.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

TeleSearch

  • Website: https://telesearch.me/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TeleSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search and find your desired Telegram channels, groups, bots and games quickly and easily with Telesearch​.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Teleteg

  • Website: https://teleteg.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Teleteg is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The ultimate Telegram search engine. 10 results for free plan.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

TeleTracker

  • Website: https://github.com/tsale/TeleTracker
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TeleTracker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: TeleTracker is a simple set of Python scripts designed for anyone investigating Telegram channels. It helps you send messages quickly and gather useful channel information 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: Awesome OSINT > Social Media Tools > ↑ Telegram.

Back to Category Index

TextBin

  • Website: https://textbin.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TextBin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Secure pastebin where you can paste and store any type of text or code snippets online and share it with your friends.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Textbin-Code

  • Website: https://textbin.online/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Textbin-Code is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: SECURE YOUR 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 OSINT > ↑ Pastebins.

Back to Category Index

Textures.js

  • Website: https://riccardoscalco.github.io/textures
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Textures.js is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

TgramSearch

  • Website: https://tgramsearch.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TgramSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Convenient search for Telegram channels, as well as a structured catalog with over 700000 Telegram channels. Available in 8+ Languages.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

tgworld

  • Website: https://tg.world/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: tgworld is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The Global Search System TG.World will help you find Channels, Groups and Bots in Telegram in any language and for any country in the world!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Thales

  • Website: https://cds.thalesgroup.com/en/cyberthreat/attacks-page
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Thales is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find Threat actor groups in a graphical attack 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 OSINT > ↑ Threat Actor Search.

Back to Category Index

ThatsThem

  • Website: https://thatsthem.com/reverse-email-lookup
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ThatsThem is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reverse Email Lookup.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

The Art of Subdomain Enumeration

  • Website: https://blog.sweepatic.com/art-of-subdomain-enumeration/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: The Art of Subdomain Enumeration is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Sub Domain Enumeration.

Back to Category Index

The Atlas of Economic Complexity

  • Website: http://atlas.cid.harvard.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: The Atlas of Economic Complexity is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

The Data and Story Library

  • Website: http://lib.stat.cmu.edu/DASL
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: The Data and Story Library is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

The most complete guide to finding anyone’s email

  • Website: https://www.blurbiz.io/blog/the-most-complete-guide-to-finding-anyones-email
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: The most complete guide to finding anyone’s email is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > OSINT.

Back to Category Index

The National Archives (UK)

  • Website: http://www.nationalarchives.gov.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: The National Archives (UK) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search UK national archives.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

The Old Reader

  • Website: http://theoldreader.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: The Old Reader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

The Open Syllabus Project

  • Website: http://opensyllabusproject.org/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: The Open Syllabus Project is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

the-endorser

  • Website: https://github.com/eth0izzle/the-endorser
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: the-endorser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool that allows you to draw out relationships between people on LinkedIn via endorsements/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: Awesome OSINT > Social Media Tools > ↑ LinkedIn.

Back to Category Index

theHarvester

  • Website: https://github.com/laramies/theHarvester
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT, Awesome Cyber Security Tools

What it does: theHarvester is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Gather emails, subdomains, hosts, employee names, open ports and banners from different public sources like search engines, PGP key servers and SHODAN computer 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 > Open Sources Intelligence (OSINT) > Metadata harvesting and analysis.

Back to Category Index

These Are the Tools Open Source Researchers Say They Need

  • Website: https://www.bellingcat.com/resources/2022/08/12/these-are-the-tools-open-source-researchers-say-they-need/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: These Are the Tools Open Source Researchers Say They Need is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Results of a survey Bellingcat conducted in February 2022.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Resources.

Back to Category Index

TheWebCo

  • Website: https://thewebco.ai
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TheWebCo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The single source of people intelligence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

Threads

  • Website: https://www.threads.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Threads is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Text-based conversation app from Meta.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Major Social Networks.

Back to Category Index

ThreatsEye Live Cyber Threat Map

  • Website: https://threatseye.io/threats-map
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ThreatsEye Live Cyber Threat Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Real-time visualization of global cyber attacks and threats. Monitor live cyber security incidents, attack origins, targets, and threat categories worldwide.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Live Cyber Threat Maps.

Back to Category Index

Thunderbird

  • Website: https://www.thunderbird.net/en-US/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Thunderbird is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

TIDoS-Framework

  • Website: https://github.com/theInfectedDrake/TIDoS-Framework
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: TIDoS-Framework is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A comprehensive web application audit framework to cover up everything from Reconnaissance and OSINT to Vulnerability Analysis 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 Category Index

Tik-tok

  • Website: https://datanews.github.io/tik-tok
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tik-tok is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Tiki-toki

  • Website: http://www.tiki-toki.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tiki-toki is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Timeflow

  • Website: https://github.com/FlowingMedia/TimeFlow/wiki
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Timeflow is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Timeline

  • Website: http://timeline.knightlab.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Timeline is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Timeline

  • Website: http://www.simile-widgets.org/timeline
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Timeline is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Timetoast

  • Website: http://www.timetoast.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Timetoast is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Tinder

  • Website: https://www.gotinder.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tinder is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

TinEye

  • Website: https://tineye.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TinEye is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Reverse image search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Image Search.

Back to Category Index

tinfoleak

  • Website: https://github.com/vaguileradiaz/tinfoleak
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: tinfoleak is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The most complete open-source tool for Twitter intelligence analysis 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

TinyScan

  • Website: https://www.tiny-scan.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TinyScan is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Another powerful URL scan tool that provides comprehensive information about any given URL. Get insights into IP address, location, screenshots, technology stack, performance metrics, 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

Toofr

  • Website: https://www.toofr.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Toofr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find Anyone’s Email Address in Seconds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Topix

  • Website: http://www.topix.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Topix is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News.

Back to Category Index

Tor Browser

  • Website: https://www.torproject.org/projects/torbrowser.html.en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tor Browser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tor is a free software that prevents people from learning your location or browsing habits by letting you communicate anonymously on the Internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Browsers.

Back to Category Index

Torch

  • Website: http://www.torchbrowser.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Torch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

TorrentFreak List of VPNs

  • Website: https://torrentfreak.com/vpn-services-anonymous-review-2017-170304/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TorrentFreak List of VPNs is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ VPN Services.

Back to Category Index

TOsint

  • Website: https://github.com/drego85/tosint
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TOsint is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tosint (Telegram OSINT) is a powerful tool designed to extract valuable information from Telegram bots and channels. It serves as an essential resource for security researchers, investigators, and anyone interested in gathering insights from various Telegram entities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

Toutatis

  • Website: https://github.com/megadose/toutatis
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Toutatis is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: a tool that allows you to extract information from instagrams accounts such as s, phone numbers 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 OSINT > Social Media Tools > ↑ Instagram.

Back to Category Index

Trace

  • Website: https://trace.manus.space
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Trace is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Real-time OSINT platform to search usernames, emails, phone numbers, and full names across 600+ platforms with breach detection and AI risk scoring.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

TracerouteVisualizer

  • Website: https://kriztalz.sh/traceroute-visualizer/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TracerouteVisualizer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: An online tool that displays your mtr / traceroute / flyingroutes output on a map for visual 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

Trading Economics

  • Website: http://www.tradingeconomics.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Trading Economics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Transparency.org Corruption Perception Index

  • Website: http://www.transparency.org/cpi2015
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Transparency.org Corruption Perception Index is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Trends24

  • Website: http://trends24.in
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Trends24 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

TRExpertWitness

  • Website: https://trexpertwitness.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TRExpertWitness is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

Trooclick

  • Website: http://trooclick.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Trooclick is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ News Digest and Discovery Tools.

Back to Category Index

Truecaller

  • Website: https://truecaller.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Truecaller is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Global reverse phone number search.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Tubuep

  • Website: https://github.com/bibanon/tubeup
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tubuep is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Downloads online videos via yt-dlp, then reuploads them to the Internet Archive for preservation. Note: if you would like to archive comments too, you need to install version 0.0.33 and use the --get-comments flag, however you will still have the new yt-dlp fixes and features, but existing tubeup bugs cannot be fixed, unless you do manual work.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Tumblr

  • Website: https://www.tumblr.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tumblr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

  • Website: http://www.tumblr.com/search
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Tumblr Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Tumblr.

Back to Category Index

TuriBot

  • Website: https://t.me/TuriBot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TuriBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Resolves username from Telegram ID.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

TutPaste

  • Website: https://tutpaste.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TutPaste is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Welcome to our fast and free online paste tool. Paste and share your text or code snippets with anyone, anywhere, no registration 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: Awesome OSINT > ↑ Pastebins.

Back to Category Index

TwChat

  • Website: http://twchat.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TwChat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

TweetMap

  • Website: http://mapd.csail.mit.edu/tweetmap
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TweetMap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

TweetMap

  • Website: http://worldmap.harvard.edu/tweetmap
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: TweetMap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Twilio

  • Website: https://www.twilio.com/docs/lookup/v2-api
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twilio is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Look up a phone numbers carrier type, location, etc. Twilio offers free accounts that come with credits you can use with their API. Each lookup is only ~$0.01-$0.02 typically on US and CAN numbers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Phone Number Research.

Back to Category Index

Twingly

  • Website: http://www.twingly.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twingly is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Blog Search.

Back to Category Index

Twitter

  • Website: https://twitter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twitter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

  • Website: https://twitter.com/search-advanced?lang=en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twitter Advanced Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Twitter Audit

  • Website: https://www.twitteraudit.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twitter Audit is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Twitter Chat Schedule

  • Website: http://tweetreports.com/twitter-chat-schedule
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twitter Chat Schedule is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

  • Website: http://search.twitter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Twitter Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ Twitter.

Back to Category Index

Ubersuggest

  • Website: http://ubersuggest.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ubersuggest is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

uBlock Origin

  • Website: https://github.com/gorhill/uBlock
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: uBlock Origin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

UCBrowser

  • Website: http://www.ucweb.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UCBrowser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

UN COMTRADE Database

  • Website: http://comtrade.un.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UN COMTRADE Database is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UN Data

  • Website: http://data.un.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UN Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Unamer

  • Website: https://telegram.me/unamer_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Unamer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Username ownership history.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

UNCTAD Country Fact Sheets

  • Website: http://unctad.org/en/Pages/DIAE/World%20Investment%20Report/Country-Fact-Sheets.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNCTAD Country Fact Sheets is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UNCTAD Investment Country Profiles

  • Website: http://unctad.org/en/Pages/Publications/Investment-country-profiles.aspx
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNCTAD Investment Country Profiles is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UNCTAD STAT

  • Website: http://unctadstat.unctad.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNCTAD STAT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UNDPs Human Development Index

  • Website: http://hdr.undp.org/en/data
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNDPs Human Development Index is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UNECE

  • Website: http://w3.unece.org/PXWeb/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNECE is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

UNESCO Institute for Statistics

  • Website: http://uis.unesco.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNESCO Institute for Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Unfurl

  • Website: https://dfir.blog/unfurl/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Unfurl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Unfurl analyzes and breaks down URLs into useful forensic components for digital investigation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

UniCourt

  • Website: https://unicourt.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UniCourt is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Limited free searches, premium data upsell. Nationwide search of 100 million+ United States court cases.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

UNIDO Statistical Databases

  • Website: http://www.unido.org/resources/statistics/statistical-databases.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNIDO Statistical Databases is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Universal Scammer List

  • Website: https://universalscammerlist.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Universal Scammer List is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: This acts as the website-portion for the subreddit /r/universalscammerlist. That subreddit, in conjuction with this website and a reddit bot, manages a list of malicious reddit accounts and minimizes the damage they can deal. This list is referred to as the "USL" for short.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Reddit.

Back to Category Index

UNStats Social Indicators

  • Website: http://unstats.un.org/unsd/demographic/products/socind
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UNStats Social Indicators is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Upsala Conflict Data Program

  • Website: http://www.pcr.uu.se/research/UCDP
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Upsala Conflict Data Program is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

urlDNA

  • Website: https://urldna.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: urlDNA is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Unleash website insights! urldna.io analyzes url, monitors brands and track phishing sites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

URLVoid

  • Website: http://www.urlvoid.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: URLVoid is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Analyzes a website through multiple blacklist engines and online reputation tools to facilitate the detection of fraudulent and malicious 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

US Data and Statistics

  • Website: https://www.usa.gov/statistics
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: US Data and Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

User Searcher

  • Website: https://www.user-searcher.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: User Searcher is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: User-Searcher is a powerful and free tool to help you search username in 2000+ 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: Awesome OSINT > ↑ Username Check.

Back to Category Index

user-scanner

  • Website: https://github.com/kaifcodec/user-scanner.git
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: user-scanner is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Takes an email, scan on various popular sites, games and retrieve info if the email is registered there or not.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

username_to_id_bot

  • Website: https://t.me/username_to_id_bot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: username_to_id_bot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Returns user/chat/channel/bot ID.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

USGS (EarthExplorer)

  • Website: https://earthexplorer.usgs.gov/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: USGS (EarthExplorer) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

UsInfoBot

  • Website: https://t.me/usinfobot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UsInfoBot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Resolves username from ID (inline).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Social Media Tools > ↑ Telegram.

Back to Category Index

UVRX

  • Website: http://www.uvrx.com/social.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: UVRX is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Validin

  • Website: https://app.validin.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Validin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Website and API to search current and historical DNS records for free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Vault

  • Website: http://www.vault.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vault is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Well-known ranking of largest United States Corporations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Company Research.

Back to Category Index

vaultbin

  • Website: https://vaultb.in/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: vaultbin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Vaultbin is a blazingly fast and secure alternative to Pastebin and Hastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

vcsmap

  • Website: https://github.com/melvinsh/vcsmap
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: vcsmap is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Plugin-based tool to scan public version control systems for sensitive 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: Awesome Penetration Testing > Open Sources Intelligence (OSINT) > Source code repository searching tools.

Back to Category Index

Venacus

  • Website: https://venacus.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Venacus is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search for your data breaches and get notified when your data is compromised.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Data Breach Search Engines.

Back to Category Index

Venngage

  • Website: https://venngage.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Venngage is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Veoh

  • Website: http://www.veoh.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Veoh is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

Verify Email

  • Website: http://verify-email.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Verify Email is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The fastest and most accurate email verification 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 OSINT > ↑ Email Search / Email Check.

Back to Category Index

Verisign

  • Website: http://dnssec-debugger.verisignlabs.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Verisign is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

versionista

  • Website: http://versionista.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: versionista is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Verybin

  • Website: https://www.verybin.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Verybin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Anonymous and encrypted pastebin. Data is encrypted/decrypted in the browser using 256 bits AES and no IP address logged.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

VHostScan

  • Website: https://github.com/codingo/VHostScan
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: VHostScan is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A virtual host scanner that performs reverse lookups, can be used with pivot tools, detect catch-all scenarios, aliases and dynamic default pages.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

ViaMichelin

  • Website: http://www.viamichelin.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ViaMichelin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Video Stabilization Methods

  • Website: https://github.com/yaochih/awesome-video-stabilization
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Video Stabilization Methods is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

View in Google Earth

  • Website: http://www.mgmaps.com/kml/#view
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: View in Google Earth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

ViewDNS.info

  • Website: http://viewdns.info
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ViewDNS.info is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Vimeo

  • Website: https://vimeo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vimeo is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

VirusTotal domain information

  • Website: https://www.virustotal.com/en/documentation/searching/#getting-domain-information
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Web Security

What it does: VirusTotal domain information is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Searching for domain information 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 > Reconnaissance > Sub Domain Enumeration.

Back to Category Index

Vis.js

  • Website: http://visjs.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vis.js is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Visme

  • Website: http://www.visme.co
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Visme is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Visualize Free

  • Website: http://visualizefree.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Visualize Free is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Visualize.me

  • Website: http://vizualize.me
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Visualize.me is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

visually

  • Website: http://create.visual.ly
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: visually is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

visualping

  • Website: https://visualping.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: visualping is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Vivaldi

  • Website: https://vivaldi.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vivaldi is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Powerful, Private and Personal Web Browser.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Browsers.

Back to Category Index

Vizala

  • Website: https://vizala.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vizala is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

  • Website: http://vk.com/communities
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VK Community Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

  • Website: http://vk.com/people
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VK People Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

VK.watch

  • Website: https://vk.watch/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VK.watch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

VK5

  • Website: http://vk5.city4me.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VK5 is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

VKontakte

  • Website: https://vk.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VKontakte is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

VoilaNorbert

  • Website: https://www.voilanorbert.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VoilaNorbert is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find anyone's contact information for lead research or talent acquisition.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Email Search / Email Check.

Back to Category Index

Vortex

  • Website: http://www.dotmatics.com/products/vortex
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Vortex is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Voter Records

  • Website: https://voterrecords.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Voter Records is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Free political research tool to study more than 100 Million US voter records.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

VPN Comparison by That One Privacy Guy

  • Website: https://thatoneprivacysite.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: VPN Comparison by That One Privacy Guy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a summary list of top best VPN services.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ VPN Services.

Back to Category Index

w3snoop

  • Website: http://webboar.com.w3snoop.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: w3snoop is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a website that gives you a free and comprehensive report about a specific 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

wafw00f

  • Website: https://github.com/EnableSecurity/wafw00f
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: wafw00f is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Identifies and fingerprints Web Application Firewall (WAF) products.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

Walla (Israel)

  • Website: http://www.walla.co.il
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Walla (Israel) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Wappalyzer

  • Website: https://www.wappalyzer.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: Wappalyzer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Detect web technologies including CMS, frameworks, analytics, and servers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

Waterfox

  • Website: https://www.waterfox.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Waterfox is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Fast and Private Web Browser. Get privacy out of the box with Waterfox.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Browsers.

Back to Category Index

WATools

  • Website: https://watools.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WATools is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Real-Time Search, Social Media Search, and General Social Media Tools.

Back to Category Index

Wayback Machine

  • Website: http://archive.org/web/web.php
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wayback Machine is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Explore the history of 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 OSINT > ↑ Web History and Website Capture.

Back to Category Index

Wayback Machine Archiver

  • Website: https://github.com/jsvine/waybackpack
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wayback Machine Archiver is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web History and Website Capture.

Back to Category Index

waybackpy

  • Website: https://github.com/akamhy/waybackpy
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: waybackpy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Python package & CLI tool that interfaces the Wayback Machine APIs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Web History and Website Capture.

Back to Category Index

Waybackurls

  • Website: https://github.com/tomnomnom/waybackurls
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Waybackurls is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Fetch all URLs known by the Wayback Machine for 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 OSINT > ↑ Other Tools.

Back to Category Index

Web-Check

  • Website: https://web-check.as93.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Web-Check is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: All-in-one tool for viewing website and server meta data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

WebAssistant

  • Website: http://www.proxy-offline-browser.com/download.html
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WebAssistant is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

WebMeUp

  • Website: http://webmeup.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WebMeUp is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is the Web's freshest and fastest growing backlink index, and the primary source of backlink data for SEO PowerSuite.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

WebReader

  • Website: http://www.getwebreader.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WebReader is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Webscore

  • Website: https://garvit835.github.io/WebScore/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Webscore is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Enter a website URL to check its legitimacy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Webscout

  • Website: https://webscout.io/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Webscout is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A Swiss Army knife for scaled intelligence and metadata on IP addresses and domains.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

webscreenshot

  • Website: https://github.com/maaaaz/webscreenshot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: webscreenshot is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Simple script to take screenshots of websites from a list of sites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

Website Informer

  • Website: http://website.informer.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Website Informer is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Website Ripper Copier

  • Website: http://www.tensons.com/products/websiterippercopier
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Website Ripper Copier is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Offline Browsing.

Back to Category Index

WebSite Watcher

  • Website: http://www.aignes.com/index.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WebSite Watcher is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

WebsiteTechMiner.py

  • Website: https://github.com/cybersader/WebsiteTechMiner-py
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WebsiteTechMiner.py is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: automates gathering website profiling data into a CSV from the "BuiltWith" or "Wappalyzer" API for tech stack information, technographic data, website reports, website tech lookups, website architecture lookups, etc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Weibo (China)

  • Website: http://weibo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Weibo (China) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

WhatBreach

  • Website: https://github.com/Ekultek/WhatBreach
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: WhatBreach is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Search email addresses and discover all known breaches that this email has been seen in, and download the breached database if it is publicly available.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Email search and analysis tools.

Back to Category Index

WhatIsMyIPAddress

  • Website: http://whatismyipaddress.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WhatIsMyIPAddress is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

WhatsMyName

  • Website: https://whatsmyname.app/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WhatsMyName is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: check for usernames across many different platforms.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Username Check.

Back to Category Index

WhatWaf

  • Website: https://github.com/Ekultek/WhatWaf
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: WhatWaf is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Detect and bypass web application firewalls and protection 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

WhatWeb

  • Website: https://github.com/urbanadventurer/WhatWeb
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome Cyber Security Tools

What it does: WhatWeb is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Website fingerprinting tool to identify web technologies.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Web application and resource analysis tools.

Back to Category Index

White Pages (US)

  • Website: http://www.whitepages.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: White Pages (US) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: People search. Limited free info, premium data upsell.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ People Investigations.

Back to Category Index

WHO Data

  • Website: http://www.who.int/gho/en
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WHO Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

Who.is

  • Website: https://who.is/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Who.is is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Domain whois 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: Awesome OSINT > ↑ Domain and IP Research.

Back to Category Index

Whois Arin Online

  • Website: https://whois.arin.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Whois Arin Online is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: is a web service for Whois data contained within ARIN's registration 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 OSINT > ↑ Domain and IP Research.

Back to Category Index

WhoIsHostingThis

  • Website: http://www.whoishostingthis.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WhoIsHostingThis is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

WhoisMind

  • Website: http://www.whoismind.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WhoisMind is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Whoisology

  • Website: https://whoisology.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Whoisology is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

WhoIsRequest

  • Website: http://whoisrequest.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WhoIsRequest is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

Wickr

  • Website: https://wickr.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wickr is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

WiGLE.net

  • Website: https://wigle.net/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing, Awesome OSINT

What it does: WiGLE.net is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Wi-fi "wardriving" database. Contains a global map containing crowdsourced information on the location, name, and other properties of wi-fi networks. Software available to download to contribute data to the public infoset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > OSINT Online Resources.

Back to Category Index

Wikimapia

  • Website: http://wikimapia.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wikimapia is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Wiley

  • Website: http://eu.wiley.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wiley is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

Winds

  • Website: http://winds.getstream.io
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Winds is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Web Monitoring.

Back to Category Index

Windy

  • Website: https://www.windy.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Windy is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

WIPO

  • Website: https://www3.wipo.int/branddb/en/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WIPO is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Wolfram Alpha

  • Website: https://www.wolframalpha.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wolfram Alpha is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Wolfram Alpha is a computational knowledge engine (answer engine) developed by Wolfram Alpha. It will compute expert-level answers using Wolfram’s breakthrough.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Word Tracker

  • Website: https://www.wordtracker.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Word Tracker is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

World Bank Data

  • Website: http://data.worldbank.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Bank Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

World Bank Data

  • Website: http://datatopics.worldbank.org/consumption/home
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Bank Data is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

World Bank Doing Business

  • Website: http://www.doingbusiness.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Bank Doing Business is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

World Bank Enterprise Surveys

  • Website: http://www.enterprisesurveys.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Bank Enterprise Surveys is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

World Bank Investing Across Borders

  • Website: http://iab.worldbank.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Bank Investing Across Borders is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

World Digital Library

  • Website: http://www.wdl.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Digital Library is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

World Integrated Trade Solution

  • Website: http://wits.worldbank.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: World Integrated Trade Solution is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

WorldMap Harvard

  • Website: http://worldmap.harvard.edu
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WorldMap Harvard is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Worldwide OSINT Tools Map

  • Website: https://cipher387.github.io/osintmap/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Worldwide OSINT Tools Map is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: A global map of databases and OSINT sources by applicable location.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

WorldWideScience.org

  • Website: http://worldwidescience.org
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WorldWideScience.org is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

WOT

  • Website: https://www.mywot.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WOT is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Wpscan

  • Website: https://wpscan.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Wpscan is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Scan your WordPress site and get an instant report on its 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 OSINT > ↑ Speciality Search Engines.

Back to Category Index

Write.as

  • Website: https://write.as/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Write.as is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Type words, put them on the internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

WTO Statistics

  • Website: https://www.wto.org/english/res_e/statis_e/statis_e.htm
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: WTO Statistics is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Data and Statistics.

Back to Category Index

xbox_monitor

  • Website: https://github.com/misiektoja/xbox_monitor
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: xbox_monitor is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Tool for real-time tracking of Xbox Live players gaming activities including detection when a user gets online/offline or plays games with support for email alerts, CSV logging, playtime stats 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 OSINT > ↑ Gaming Platforms.

Back to Category Index

Xing

  • Website: https://www.xing.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Xing is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Major Social Networks.

Back to Category Index

Xing

  • Website: http://www.xing.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Xing is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

Yahoo Answers

  • Website: http://answers.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo Answers is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Yahoo Groups

  • Website: https://groups.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo Groups is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Forums and Discussion Boards Search.

Back to Category Index

  • Website: https://images.search.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo Image Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Yahoo Maps

  • Website: https://maps.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo Maps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

  • Website: http://video.search.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo Video Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

  • Website: https://www.yahoo.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yahoo! Search is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: The search engine that helps you find exactly what you're looking for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

Yandex (Russia)

  • Website: http://www.yandex.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yandex (Russia) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

Yandex Browser

  • Website: https://browser.yandex.com/desktop/main
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yandex Browser is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Browsers.

Back to Category Index

Yandex Images

  • Website: https://www.yandex.com/images
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yandex Images is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Image Search.

Back to Category Index

Yandex Wordstat

  • Website: https://wordstat.yandex.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Yandex Wordstat is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Keywords Discovery and Research.

Back to Category Index

Yar

  • Website: https://github.com/Furduhlutur/yar
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome Penetration Testing

What it does: Yar is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Clone git repositories to search through the whole commit history in order of commit time for secrets, tokens, or passwords.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Source code repository searching tools.

Back to Category Index

YOU

  • Website: https://you.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: YOU is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: AI search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ General Search.

Back to Category Index

You Get Signal

  • Website: http://www.yougetsignal.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: You Get Signal is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Domain and IP Research.

Back to Category Index

YouControl

  • Website: https://youcontrol.com.ua/en/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: YouControl is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Company Research.

Back to Category Index

YouTube

  • Website: https://www.youtube.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: YouTube is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

YouTube Geofind

  • Website: https://mattw.io/youtube-geofind/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: YouTube Geofind is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

YouTube Metadata

  • Website: https://mattw.io/youtube-metadata/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: YouTube Metadata is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

yt-dlp

  • Website: https://github.com/yt-dlp/yt-dlp/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: yt-dlp is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Downloads videos from almost any online platform, along with information, thumbnails, subtitles, descriptions, and comments (comments only on a select few sites like Youtube and a few small sites). If a site is not supported, or a useful or crucial piece of metadata, including comments, is missing, create an issue.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Video Search and Other Video Tools.

Back to Category Index

ZabaSearch

  • Website: https://www.zabasearch.com/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZabaSearch is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ People Investigations.

Back to Category Index

Zanran

  • Website: http://zanran.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zanran is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Speciality Search Engines.

Back to Category Index

Zapmeta

  • Website: http://www.zapmeta.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zapmeta is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Visual Search and Clustering Search Engines.

Back to Category Index

Zarebin (Iran)

  • Website: http://zarebin.ir
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zarebin (Iran) is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Main National Search Engines.

Back to Category Index

ZBin

  • Website: https://zbin.dev/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZBin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Private & Secure Pastebin.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Zeemaps

  • Website: https://www.zeemaps.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zeemaps is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Zen

  • Website: https://github.com/s0md3v/Zen
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zen is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: Find email addresses of Github users urls and other data effortlessly.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

ZeroBin

  • Website: https://sebsauvage.net/paste/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZeroBin is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: ZeroBin is a minimalist, opensource online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

Zetoc

  • Website: http://zetoc.jisc.ac.uk
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zetoc is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Academic Resources and Grey Literature.

Back to Category Index

ZingChart

  • Website: http://www.zingchart.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZingChart is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Infographics and Data Visualization.

Back to Category Index

Zintro

  • Website: https://www.zintro.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zintro is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Expert Search.

Back to Category Index

ZipRecruiter

  • Website: https://www.ziprecruiter.com
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZipRecruiter is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Job Search Resources.

Back to Category Index

ZMail

  • Website: http://zmail.sourceforge.net
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: ZMail is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 Category Index

Zoom Earth

  • Website: https://zoom.earth/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Zoom Earth is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

Дезертир

  • Website: http://vk.com/app3046467
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Дезертир is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > Social Media Tools > ↑ VKontakte.

Back to Category Index

Ответы

  • Website: https://otvet.mail.ru/
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Ответы is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. 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 > ↑ Q&A Sites.

Back to Category Index

Фари

  • Website: https://telegram.me/faribybot
  • Model: Open Source
  • Category: OSINT & Reconnaissance
  • Source Lists: Awesome OSINT

What it does: Фари is used in osint & reconnaissance programs to support asset discovery, external exposure mapping, and intelligence collection. Source summaries describe it as: VIN-history lookup from getcar.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 OSINT > Social Media Tools > ↑ Telegram.

Back to Category Index

OT / ICS / IoT Security

This category contains 5 documented tools. It focuses on capabilities used for asset visibility, protocol-aware detection, and resilience for cyber-physical systems. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

A Modbus/TCP Fuzzer for testing internetworked industrial systems, 2015

  • Website: https://doi.org/10.1109/ETFA.2015.7301400
  • Model: Open Source
  • Category: OT / ICS / IoT Security
  • Source Lists: Awesome Fuzzing

What it does: A Modbus/TCP Fuzzer for testing internetworked industrial systems, 2015 is used in ot / ics / iot security programs to support asset visibility, protocol-aware detection, and resilience for cyber-physical systems. 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 > The others.

Back to Category Index

DIANE: Identifying Fuzzing Triggers in Apps to Generate Under-constrained Inputs for IoT Devices, 2021

  • Website: https://conand.me/publications/redini-diane-2021.pdf
  • Model: Open Source
  • Category: OT / ICS / IoT Security
  • Source Lists: Awesome Fuzzing

What it does: DIANE: Identifying Fuzzing Triggers in Apps to Generate Under-constrained Inputs for IoT Devices, 2021 is used in ot / ics / iot security programs to support asset visibility, protocol-aware detection, and resilience for cyber-physical systems. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

ICSFuzz: Manipulating I/Os and Repurposing Binary Code to Enable Instrumented Fuzzing in ICS Control Applications, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/tychalas
  • Model: Open Source
  • Category: OT / ICS / IoT Security
  • Source Lists: Awesome Fuzzing

What it does: ICSFuzz: Manipulating I/Os and Repurposing Binary Code to Enable Instrumented Fuzzing in ICS Control Applications, 2021 is used in ot / ics / iot security programs to support asset visibility, protocol-aware detection, and resilience for cyber-physical systems. 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 > USENIX Security.

Back to Category Index

Industrial Control System Security

  • Website: https://github.com/hslatman/awesome-industrial-control-system-security
  • Model: Open Source
  • Category: OT / ICS / IoT Security
  • Source Lists: Awesome Malware Analysis

What it does: Industrial Control System Security is used in ot / ics / iot security programs to support asset visibility, protocol-aware detection, and resilience for cyber-physical systems. 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: Related Awesome Lists.

Back to Category Index

SNIPUZZ: Black-box Fuzzing of IoT Firmware via Message Snippet Inference, 2021

  • Website: https://arxiv.org/pdf/2105.05445.pdf
  • Model: Open Source
  • Category: OT / ICS / IoT Security
  • Source Lists: Awesome Fuzzing

What it does: SNIPUZZ: Black-box Fuzzing of IoT Firmware via Message Snippet Inference, 2021 is used in ot / ics / iot security programs to support asset visibility, protocol-aware detection, and resilience for cyber-physical systems. 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 Category Index

Penetration Testing & Red Team

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.

Open category-focused page

"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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

.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 Category Index

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 Category Index

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 Category Index

@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 Category Index

@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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

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 Category Index

Perimeter / Zero Trust Security

This category contains 7 documented tools. It focuses on capabilities used for policy-based access control, segmentation, and egress monitoring. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

acra

  • Website: https://github.com/cossacklabs/acra
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Security, Awesome Web Security

What it does: acra is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Database security suite: proxy for data protection with transparent "on the fly" data encryption, data masking and tokenization, SQL firewall (SQL injections prevention), intrusion detection 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 Web Security > Tools > Preventing.

Back to Category Index

IPsec VPN Server Auto Setup Scripts

  • Website: https://github.com/hwdsl2/setup-ipsec-vpn
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: IPsec VPN Server Auto Setup Scripts is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Scripts to build your own IPsec VPN server, with IPsec/L2TP, Cisco IPsec and IKEv2.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

LuLu

  • Website: https://objective-see.com/products/lulu.html
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: LuLu is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Free macOS firewall.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > macOS-based defenses.

Back to Category Index

OWASP ZAP

  • Website: https://www.owasp.org/index.php/Projects/OWASP_Zed_Attack_Proxy_Project
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome CTF

What it does: OWASP ZAP is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Intercepting proxy to replay, debug, and fuzz HTTP requests and responses.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Web.

Back to Category Index

Tailscale

  • Website: https://tailscale.com/
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Tailscale is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Managed freemium mesh VPN service built on top of WireGuard.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

Threat Hunting Techniques - AV, Proxy, DNS and HTTP Logs

  • Website: https://www.cyberhuntz.com/2016/08/threat-hunting-techniques-av-proxy-dns.html
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Threat Detection

What it does: Threat Hunting Techniques - AV, Proxy, DNS and HTTP Logs is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. 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 > Resources.

Back to Category Index

WireGuard

  • Website: https://www.wireguard.com/
  • Model: Open Source
  • Category: Perimeter / Zero Trust Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: WireGuard is used in perimeter / zero trust security programs to support policy-based access control, segmentation, and egress monitoring. Source summaries describe it as: Extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Transport-layer defenses > Overlay and Virtual Private Networks (VPNs).

Back to Category Index

SIEM & Log Management

This category contains 54 documented tools. It focuses on capabilities used for centralized event collection, correlation logic, detection tuning, and structured triage. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Android SmartTVs Vulnerability Discovery via Log-Guided Fuzzing, 2021

  • Website: https://www.usenix.org/conference/usenixsecurity21/presentation/aafer
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Fuzzing

What it does: Android SmartTVs Vulnerability Discovery via Log-Guided Fuzzing, 2021 is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. 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 > USENIX Security.

Back to Category Index

AppCompatProcessor

  • Website: https://github.com/mbevilacqua/appcompatprocessor
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: AppCompatProcessor is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: AppCompatProcessor has been designed to extract additional value from enterprise-wide AppCompat / AmCache data beyond the classic stacking and grepping techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

APT Hunter

  • Website: https://github.com/ahmedkhlief/APT-Hunter
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: APT Hunter is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: APT-Hunter is Threat Hunting tool for windows event logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Bifrozt

  • Website: http://sourceforge.net/projects/bifrozt/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: Bifrozt is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Bifrozt is a NAT device with a DHCP server that is usually deployed with one NIC connected directly to the Internet and one NIC connected to the internal network. What differentiates Bifrozt from other standard NAT devices is its ability to work as a transparent SSHv2 proxy between an attacker and your honeypot. If you deployed an SSH server on Bifrozt’s internal network it would log all the interaction to a TTY file in plain text that could be viewed later and capture a copy of any files that were downloaded. You would not have to install any additional software, compile any kernel modules or use a specific version or type of operating system on the internal SSH server for this to work. It will limit outbound traffic to a set number of ports and will start to drop outbound packets on these ports when certain limits are exceeded.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Chainsaw

  • Website: https://github.com/countercept/chainsaw
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Chainsaw is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Chainsaw provides a powerful ‘first-response’ capability to quickly identify threats within Windows event logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

CitrixHoneypot

  • Website: https://github.com/MalwareTech/CitrixHoneypot
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Honeypots

What it does: CitrixHoneypot is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Detect and log CVE-2019-19781 scan and exploitation attempts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Event Log Explorer

  • Website: https://eventlogxp.com/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Event Log Explorer is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Tool developed to quickly analyze log files and other data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Event Log Observer

  • Website: https://lizard-labs.com/event_log_observer.aspx
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Event Log Observer is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: View, analyze and monitor events recorded in Microsoft Windows event logs with this GUI 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 Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Fail2Ban

  • Website: http://www.fail2ban.org/wiki/index.php/Main_Page
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: Fail2Ban is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Scans log files and takes action on IPs that show malicious 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 Security > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

FIR

  • Website: https://github.com/certsocietegenerale/FIR
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Incident Response, Awesome Cybersecurity Blue Team

What it does: FIR is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Cybersecurity incident management platform designed with agility and speed in mind. It allows for easy creation, tracking, and reporting of cybersecurity incidents and is useful for CSIRTs, CERTs and SOCs alike.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > IR management consoles.

Back to Category Index

Hayabusa

  • Website: https://github.com/Yamato-Security/hayabusa
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Hayabusa is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Hayabusa is a Windows event log fast forensics timeline generator and threat hunting tool created by the Yamato Security group in Japan.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Highlighter

  • Website: https://www.fireeye.com/services/freeware/highlighter.html
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Highlighter is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Free Tool available from Fire/Mandiant that will depict log/text file that can highlight areas on the graphic, that corresponded to a key word or phrase. Good for time lining an infection and what was done post compromise.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Timeline Tools.

Back to Category Index

httpry

  • Website: http://dumpsterventures.com/jason/httpry/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: httpry is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: httpry is a specialized packet sniffer designed for displaying and logging HTTP traffic. It is not intended to perform analysis itself, but to capture, parse, and log the traffic for later analysis. It can be run in real-time displaying the traffic as it is parsed, or as a daemon process that logs to an output file. It is written to be as lightweight and flexible as possible, so that it can be easily adaptable to different 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 Security > Network > Monitoring / Logging.

Back to Category Index

HUDINX

  • Website: https://github.com/Cryptix720/HUDINX
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Honeypots

What it does: HUDINX is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Tiny interaction SSH honeypot engineered in Python to log brute force attacks and, most importantly, the entire shell interaction performed by the attacker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

justniffer

  • Website: http://justniffer.sourceforge.net/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: justniffer is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Justniffer is a network protocol analyzer that captures network traffic and produces logs in a customized way, can emulate Apache web server log files, track response times and extract all "intercepted" files from the HTTP traffic.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

Kaspersky CyberTrace

  • Website: https://support.kaspersky.com/13850
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Kaspersky CyberTrace is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Threat intelligence fusion and analysis tool that integrates threat data feeds with SIEM solutions. Users can immediately leverage threat intelligence for security monitoring and incident report (IR) activities in the workflow of their existing security 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 Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Kippo

  • Website: https://github.com/desaster/kippo
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Honeypots

What it does: Kippo is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Kippo is a medium interaction SSH honeypot designed to log brute force attacks and, most importantly, the entire shell interaction performed by the attacker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Honey Pot / Honey Net.

Back to Category Index

Kippo2MySQL

  • Website: https://bruteforcelab.com/kippo2mysql
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Honeypots

What it does: Kippo2MySQL is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Extracts some very basic stats from Kippo’s text-based log files and inserts them in a MySQL 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: Contents > Honeypots.

Back to Category Index

LastActivityView

  • Website: https://www.nirsoft.net/utils/computer_activity_view.html
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Forensics

What it does: LastActivityView is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: LastActivityView by Nirsoftis a tool for Windows operating system that collects information from various sources on a running system, and displays a log of actions made by the user and events occurred on this computer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Windows Artifacts.

Back to Category Index

Log Parser Lizard

  • Website: https://lizard-labs.com/log_parser_lizard.aspx
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Log Parser Lizard is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Execute SQL queries against structured log data: server logs, Windows Events, file system, Active Directory, log4net logs, comma/tab separated text, XML or JSON files. Also provides a GUI to Microsoft LogParser 2.2 with powerful UI elements: syntax editor, data grid, chart, pivot table, dashboard, query manager 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 Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

LogAnon

  • Website: http://code.google.com/archive/p/loganon/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Honeypots

What it does: LogAnon is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Log anonymization library that helps having anonymous logs consistent between logs and network captures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Logdissect

  • Website: https://github.com/dogoncouch/logdissect
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Incident Response

What it does: Logdissect is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: CLI utility and Python API for analyzing log files and other data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

LogESP

  • Website: https://github.com/dogoncouch/LogESP
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: LogESP is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Open Source SIEM (Security Information and Event Management 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 Security > Network > Security Information & Event Management.

Back to Category Index

LogonTracer

  • Website: https://github.com/JPCERTCC/LogonTracer
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response, Awesome Cybersecurity Blue Team, Awesome Forensics

What it does: LogonTracer is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Tool to investigate malicious Windows logon by visualizing and analyzing Windows event log.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Logpasta

  • Website: https://logpasta.com/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome OSINT

What it does: Logpasta is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Simple, secure log paste service. Command line mode based.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Pastebins.

Back to Category Index

LogSlash

  • Website: https://github.com/FoxIO-LLC/LogSlash
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Threat Detection

What it does: LogSlash is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A standard for reducing log volume without sacrificing analytical capability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

LongTail Log Analysis @ Marist College

  • Website: http://longtail.it.marist.edu/honey/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Honeypots

What it does: LongTail Log Analysis @ Marist College is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Analyzed SSH honeypot logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Lorg

  • Website: https://github.com/jensvoid/lorg
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: Lorg is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Tool for advanced HTTPD logfile security analysis and forensics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

OpenFPC

  • Website: http://www.openfpc.org
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: OpenFPC is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: OpenFPC is a set of tools that combine to provide a lightweight full-packet network traffic recorder & buffering system. It's design goal is to allow non-expert users to deploy a distributed network traffic recorder on COTS hardware while integrating into existing alert and log management 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 Security > Network > Full Packet Capture / Forensic.

Back to Category Index

OSSEC

  • Website: https://ossec.github.io/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome OSINT

What it does: OSSEC is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Comprehensive Open Source HIDS. Not for the faint of heart. Takes a bit to get your head around how it works. Performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response. It runs on most operating systems, including Linux, MacOS, Solaris, HP-UX, AIX and Windows. Plenty of reasonable documentation. Sweet spot is medium to large deployments.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

OSSIM

  • Website: https://www.alienvault.com/open-threat-exchange/projects
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: OSSIM is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Single-server open source SIEM platform featuring asset discovery, asset inventorying, behavioral monitoring, and event correlation, driven by AlienVault Open Threat Exchange (OTX).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Security Information and Event Management (SIEM).

Back to Category Index

passivedns

  • Website: https://github.com/gamelinux/passivedns
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Penetration Testing

What it does: passivedns is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A tool to collect DNS records passively to aid Incident handling, Network Security Monitoring (NSM) and general digital forensics. PassiveDNS sniffs traffic from an interface or reads a pcap-file and outputs the DNS-server answers to a log file. PassiveDNS can cache/aggregate duplicate DNS answers in-memory, limiting the amount of data in the logfile without loosing the essens in the DNS answer.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network Tools > Network Reconnaissance Tools.

Back to Category Index

Prelude

  • Website: https://www.prelude-siem.org/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: Prelude is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Prelude is a Universal "Security Information & Event Management" (SIEM) system. Prelude collects, normalizes, sorts, aggregates, correlates and reports all security-related events independently of the product brand or license giving rise to such events; Prelude is "agentless".

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Security Information and Event Management (SIEM).

Back to Category Index

Public Security Log Sharing Site

  • Website: http://log-sharing.dreamhosters.com
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Threat Detection

What it does: Public Security Log Sharing Site is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. 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 > Dataset.

Back to Category Index

sagan

  • Website: http://sagan.quadrantsec.com/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: sagan is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Sagan uses a 'Snort like' engine and rules to analyze logs (syslog/event log/snmptrap/netflow/etc).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

Security Onion

  • Website: http://blog.securityonion.net/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: Security Onion is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Security Onion is a Linux distro for intrusion detection, network security monitoring, and log management. It's based on Ubuntu and contains Snort, Suricata, Zeek, OSSEC, Sguil, Squert, Snorby, ELSA, Xplico, NetworkMiner, and many other security tools. The easy-to-use Setup wizard allows you to build an army of distributed sensors for your enterprise in minutes!.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

Security Onion

  • Website: https://securityonionsolutions.com/
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Security Onion is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Free and open source GNU/Linux distribution for intrusion detection, enterprise security monitoring, and log management.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Operating System distributions.

Back to Category Index

SIEM

  • Website: https://www.gartner.com/en/information-technology/glossary/security-information-and-event-management-siem
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome SOC

What it does: SIEM is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

Sigma

  • Website: https://github.com/SigmaHQ/sigma
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Sigma is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Generic signature format for SIEM systems already containing an extensive ruleset.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Sigma

  • Website: https://github.com/Neo23x0/sigma
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Sigma is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Generic signature format for SIEM systems, offering an open signature format that allows you to describe relevant log events in a straightforward manner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

Sigma2KQL

  • Website: https://github.com/Khadinxc/Sigma2KQL
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: Sigma2KQL is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A repository of all SIGMA rules converted to KQL that runs on a weekly schedule to update the repository and align with the up to date version of the SIGMA rules repository.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

Sigma2SPL

  • Website: https://github.com/Khadinxc/Sigma2SPL
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: Sigma2SPL is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A repository of all SIGMA rules converted to SPL that runs on a weekly schedule to update the repository and align with the up to date version of the SIGMA rules repository.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > Monitoring / Logging.

Back to Category Index

SpoofSpotter

  • Website: https://github.com/NetSPI/SpoofSpotter
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: SpoofSpotter is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Catch spoofed NetBIOS Name Service (NBNS) responses and alert to an email or log file.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Security monitoring > Network Security Monitoring (NSM).

Back to Category Index

sshwatch

  • Website: https://github.com/marshyski/sshwatch
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Security

What it does: sshwatch is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: IPS for SSH similar to DenyHosts written in Python. It also can gather information about attacker during the attack in a log.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Network > IDS / IPS / Host IDS / Host IPS.

Back to Category Index

State of SIEM market 2025

  • Website: https://go.crowdstrike.com/rs/281-OBQ-266/images/Whitepaper2025StateofSIEMMarketCribl.pdf?version=0
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome SOC

What it does: State of SIEM market 2025 is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

StreamAlert

  • Website: https://github.com/airbnb/streamalert
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: StreamAlert is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A serverless, realtime data analysis framework which empowers you to ingest, analyze, and alert on data from any environment, using datasources and alerting logic you define.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

Synthetic Adversarial Log Objects (SALO)

  • Website: https://github.com/splunk/salo
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Threat Detection

What it does: Synthetic Adversarial Log Objects (SALO) is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A framework for the generation of log events without the need for infrastructure or actions to initiate the event that causes a log event.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Sysmon

  • Website: https://docs.microsoft.com/en-us/sysinternals/downloads/sysmon
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Threat Detection

What it does: Sysmon is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A Windows system service and device driver that monitors and logs system activity to the Windows event log.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Endpoint Monitoring.

Back to Category Index

SysmonSearch

  • Website: https://github.com/JPCERTCC/SysmonSearch
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: SysmonSearch is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: SysmonSearch makes Windows event log analysis more effective and less time consuming by aggregation of event logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

Uncoder

  • Website: https://uncoder.io
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Threat Detection

What it does: Uncoder is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: An online translator for SIEM saved searches, filters, queries, API requests, correlation and Sigma rules.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Untitled Goose Tool

  • Website: https://github.com/cisagov/untitledgoosetool
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Untitled Goose Tool is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Assists incident response teams by exporting cloud artifacts from Azure/AzureAD/M365 environments in order to run a full investigation despite lacking in logs ingested by a SIEM.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Incident Response tools > Evidence collection.

Back to Category Index

WELA

  • Website: https://github.com/Yamato-Security/WELA
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response

What it does: WELA is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Windows Event Log Analyzer aims to be the Swiss Army knife for Windows event logs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

WMI Monitor

  • Website: https://github.com/realparisi/WMI_Monitor
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: WMI Monitor is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: Log newly created WMI consumers and processes to the Windows Application event log.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Windows-based defenses.

Back to Category Index

Zircolite

  • Website: https://github.com/wagga40/Zircolite
  • Model: Open Source
  • Category: SIEM & Log Management
  • Source Lists: Awesome Incident Response, Awesome SOC

What it does: Zircolite is used in siem & log management programs to support centralized event collection, correlation logic, detection tuning, and structured triage. Source summaries describe it as: A standalone and fast SIGMA-based detection tool for EVTX or JSON.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Log Analysis Tools.

Back to Category Index

SOAR & Automation

This category contains 43 documented tools. It focuses on capabilities used for incident playbook execution, enrichment automation, and response task orchestration. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

autosecure

  • Website: https://github.com/vincentkoc/autosecure
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cyber Security Tools

What it does: autosecure is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Threat-feed IP block automation for Linux and macOS firewalls.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Threat Intelligence.

Back to Category Index

Ansible Lockdown

  • Website: https://ansiblelockdown.io/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Ansible Lockdown is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Curated collection of information security themed Ansible roles that are both vetted and actively maintained.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

automation

  • Website: https://megamorf.gitlab.io/2020/07/19/automating-the-windows-sandbox/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome SOC

What it does: automation is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Catalyst

  • Website: https://github.com/SecurityBrewery/catalyst
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response, Awesome Forensics

What it does: Catalyst is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A free SOAR system that helps to automate alert handling and incident response processes.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

censys-python

  • Website: https://github.com/censys/censys-python
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: censys-python is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Python wrapper to the Censys REST API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

Clevis

  • Website: https://github.com/latchset/clevis
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Clevis is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Plugable framework for automated decryption, often used as a Tang client.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

CORTEX XSOAR

  • Website: https://www.paloaltonetworks.com/cortex/xsoar
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response

What it does: CORTEX XSOAR is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Paloalto security orchestration, automation and response platform with full Incident lifecycle management and many integrations to enhance automations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

DATA

  • Website: https://github.com/hadojae/DATA
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: DATA is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Credential phish analysis and automation tool that can accept suspected phishing URLs directly or trigger on observed network traffic containing such a URL.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

Decker

  • Website: https://github.com/stevenaldinger/decker
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Penetration Testing

What it does: Decker is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Penetration testing orchestration and automation framework, which allows writing declarative, reusable configurations capable of ingesting variables and using outputs of tools it has run as inputs to others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Dev-Sec.io

  • Website: https://dev-sec.io/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Dev-Sec.io is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Server hardening framework providing Ansible, Chef, and Puppet implementations of various baseline security configurations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

Dispatch

  • Website: https://github.com/Netflix/dispatch
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Threat Detection

What it does: Dispatch is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: An open-source crisis management orchestration 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 > Tools.

Back to Category Index

dorks

  • Website: https://github.com/USSCltd/dorks
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Penetration Testing

What it does: dorks is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Google hack database automation 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 > Open Sources Intelligence (OSINT) > Dorking tools.

Back to Category Index

ElastAlert

  • Website: https://github.com/Yelp/elastalert
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Threat Detection

What it does: ElastAlert is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A framework for alerting on anomalies, spikes, or other patterns of interest from data in Elasticsearch.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

Falcon Orchestrator

  • Website: https://github.com/CrowdStrike/falcon-orchestrator
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response

What it does: Falcon Orchestrator is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Extendable Windows-based application that provides workflow automation, case management and security response functionality.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > All-In-One Tools.

Back to Category Index

ForensicMiner

  • Website: https://github.com/securityjoes/ForensicMiner
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Forensics

What it does: ForensicMiner is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A PowerShell-based DFIR automation tool, for artifact and evidence collection on Windows 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 Forensics > Tools > Acquisition.

Back to Category Index

IntelMQ

  • Website: https://github.com/certtools/intelmq/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Security, Awesome Forensics

What it does: IntelMQ is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: IntelMQ is a solution for CERTs for collecting and processing security feeds, pastebins, tweets using a message queue protocol. It's a community driven initiative called IHAP (Incident Handling Automation Project) which was conceptually designed by European CERTs during several InfoSec events. Its main goal is to give to incident responders an easy way to collect & process threat intelligence thus improving the incident handling processes of CERTs. .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

libcrafter

  • Website: https://github.com/pellegre/libcrafter
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: libcrafter is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: High level C++ network packet sniffing and crafting library.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

LinkScope

  • Website: https://accentusoft.com/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome OSINT

What it does: LinkScope is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: LinkScope is an open source intelligence (OSINT) graphical link analysis tool and automation platform for gathering and connecting information for investigative 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 OSINT > ↑ Other Tools.

Back to Category Index

Market Guide for Security Orchestration, Automation and Response Solutions

  • Website: https://fr.scribd.com/document/619736260/Gartner-Market-Guide-for-Security-Orchestration-Automation
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome SOC

What it does: Market Guide for Security Orchestration, Automation and Response Solutions is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Password Manager Resources

  • Website: https://github.com/apple/password-manager-resources
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Password Manager Resources is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Collaborative, crowd-sourced data and code to make password management better.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

peepdf

  • Website: https://eternal-todo.com/tools/peepdf-pdf-analysis-tool
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: peepdf is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Python tool to explore PDF files in order to find out if the file can be harmful or not.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

PINCE

  • Website: https://github.com/korcankaraokcu/PINCE
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome CTF

What it does: PINCE is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: GDB front-end/reverse engineering tool, focused on game-hacking and automation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Reversing.

Back to Category Index

Posh-VirusTotal

  • Website: https://github.com/darkoperator/Posh-VirusTotal
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Posh-VirusTotal is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: PowerShell interface to VirusTotal.com APIs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

Pyba

  • Website: https://github.com/fauvidoTechnologies/PyBrowserAutomation/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome OSINT

What it does: Pyba is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A browser automation framework which requires low-code to search the web and perform OSINT using DFS and BFS modes, ideal for exploratory 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 OSINT > ↑ Other Tools.

Back to Category Index

PyREBox

  • Website: https://talosintelligence.com/pyrebox
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: PyREBox is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Python-scriptable reverse engineering sandbox, based on QEMU.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

python-dshield

  • Website: https://github.com/rshipp/python-dshield
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: python-dshield is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Pythonic interface to the Internet Storm Center/DShield API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention > Code libraries and bindings.

Back to Category Index

python-stix2

  • Website: https://github.com/oasis-open/cti-python-stix2
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: python-stix2 is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Python APIs for serializing and de-serializing Structured Threat Information eXpression (STIX) JSON content, plus higher-level APIs for common 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 Cybersecurity Blue Team > Automation and Convention > Code libraries and bindings.

Back to Category Index

Red Team Automation (RTA)

  • Website: https://github.com/endgameinc/RTA
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response, Awesome Threat Detection

What it does: Red Team Automation (RTA) is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: RTA provides a framework of scripts designed to allow blue teams to test their detection capabilities against malicious tradecraft, modeled after MITRE ATT&CK.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Adversary Emulation.

Back to Category Index

Rudder

  • Website: http://www.rudder-project.org/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Security

What it does: Rudder is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Rudder is an easy to use, web-driven, role-based solution for IT Infrastructure Automation & Compliance. Automate common system administration tasks (installation, configuration); Enforce configuration over time (configuring once is good, ensuring that configuration is valid and automatically fixing it is better); Inventory of all managed nodes; Web interface to configure and manage nodes and their configuration; Compliance reporting, by configuration and/or by node.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Endpoint > Configuration Management.

Back to Category Index

Security orchestration for dummies

  • Website: https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/cortex-xsoar/Security-Orchestration-For-Dummies-Demisto-Special-Edition.pdf
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome SOC

What it does: Security orchestration for dummies is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Shuffle

  • Website: https://github.com/frikky/Shuffle
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response

What it does: Shuffle is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A general purpose security automation platform focused on accessibility.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

Shuffle

  • Website: https://shuffler.io/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Shuffle is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Graphical generalized workflow (automation) builder for IT professionals and blue 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 Cybersecurity Blue Team > Automation and Convention > Security Orchestration, Automation, and Response (SOAR).

Back to Category Index

Shuffle

  • Website: https://github.com/Shuffle/Shuffle
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Threat Detection

What it does: Shuffle is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: A general purpose security automation 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: Awesome Threat Detection and Hunting > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

SOAR

  • Website: https://soar.earth/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome OSINT

What it does: SOAR is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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 > ↑ Geospatial Research and Mapping Tools.

Back to Category Index

SOAR

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/soar.md
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome SOC

What it does: SOAR is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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: Table of Content.

Back to Category Index

SOAR Data quadrant awards

  • Website: https://swimlane.com/resources/reports/soar-quadrant/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome SOC

What it does: SOAR Data quadrant awards is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

Spiderfoot

  • Website: http://www.spiderfoot.net/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: Spiderfoot is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Multi-source OSINT automation tool with a Web UI and report visualizations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

SpiderFoot

  • Website: https://www.spiderfoot.net
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome OSINT

What it does: SpiderFoot is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: SpiderFoot is an open source intelligence (OSINT) automation platform with over 200 modules for threat intelligence, attack surface monitoring, security assessments and asset 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 OSINT > ↑ Other Tools.

Back to Category Index

Sublime

  • Website: https://github.com/sublime-security/sublime-platform
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Threat Detection

What it does: Sublime is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: An open platform for detection, response, and threat hunting in email environments. Sublime lets you write advanced detections as code to alert and remediate threats like phishing in real-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 Threat Detection and Hunting > Tools > Detection, Alerting and Automation Platforms.

Back to Category Index

VolatilityBot

  • Website: https://github.com/mkorman90/VolatilityBot
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response

What it does: VolatilityBot is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Automation tool for researchers cuts all the guesswork and manual tasks out of the binary extraction phase, or to help the investigator in the first steps of performing a memory analysis investigation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Memory Analysis Tools.

Back to Category Index

Watchtower

  • Website: https://containrrr.dev/watchtower/
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Watchtower is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Container-based solution for automating Docker container base image updates, providing an unattended upgrade experience.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Automation and Convention.

Back to Category Index

XRay

  • Website: https://github.com/evilsocket/xray
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Penetration Testing, Awesome Web Security

What it does: XRay is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: XRay is a tool for recon, mapping and OSINT gathering from public networks 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

Zenduty

  • Website: https://www.zenduty.com
  • Model: Open Source
  • Category: SOAR & Automation
  • Source Lists: Awesome Incident Response

What it does: Zenduty is used in soar & automation programs to support incident playbook execution, enrichment automation, and response task orchestration. Source summaries describe it as: Zenduty is a novel incident management platform providing end-to-end incident alerting, on-call management and response orchestration, giving teams greater control and automation over the incident management lifecycle.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Incident Response > IR Tools Collection > Incident Management.

Back to Category Index

SOC Operations

This category contains 182 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

"While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack... initial investigations suggest that an error in the implementation of our defences amplified the impact of the attack rather than mitigating it"

  • Website: https://www.bbc.com/news/articles/c903e793w74o
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: "While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack... initial investigations suggest that an error in the implementation of our defences amplified the impact of the attack rather than mitigating it" is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

11 strategies for a world-class SOC

  • Website: https://www.mitre.org/publications/technical-papers/11-strategies-world-class-cybersecurity-operations-center
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: 11 strategies for a world-class SOC is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

18 critical security controls

  • Website: https://www.cisecurity.org/controls/cis-controls-list
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: 18 critical security controls is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

2024 SOC survey

  • Website: https://swimlane.com/wp-content/uploads/SANS-SOC-Survey_2024.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: 2024 SOC survey is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

365Inspect

  • Website: https://github.com/soteria-security/365Inspect
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: 365Inspect is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

AD decoy acounts

  • Website: https://medium.com/securonix-tech-blog/detecting-ldap-enumeration-and-bloodhound-s-sharphound-collector-using-active-directory-decoys-dfc840f2f644
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: AD decoy acounts is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > SOC sensors, nice to have.

Back to Category Index

AD post-compromise checklist

  • Website: https://www.pwndefend.com/2021/09/15/post-compromise-active-directory-checklist/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: AD post-compromise checklist is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

ADRecon

  • Website: https://github.com/tomwechsler/Active_Directory_Advanced_Threat_Hunting/blob/main/Different_hunting_methods/In-depth_investigation_active_directory.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ADRecon is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

ADTrapper

  • Website: https://github.com/MHaggis/ADTrapper
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ADTrapper is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

AIL Framework

  • Website: https://github.com/CIRCL/AIL-framework
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: AIL Framework is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

alerts

  • Website: https://www.us-cert.gov/ncas/alerts.xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: alerts is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

All stories

  • Website: https://www.darkreading.com/rss.xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: All stories is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Analyzing MITRE ATT&CK evaluations 2023

  • Website: https://explore.bitdefender.com/epp-nurture-2023_2/blog-mitre-attck-evaluations-2023?cid=emm%7Cb%7Chubspot%7Cnrt-epp-2023&utm_campaign=nurture-epp-2023&utm_medium=email&_hsmi=280552612&utm_content=280552612&utm_source=hs_automation
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Analyzing MITRE ATT&CK evaluations 2023 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Antimalware check SOP

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/sop_malware_critical_controls.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Antimalware check SOP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

ATT&CK: Getting started

  • Website: https://attack.mitre.org/resources/getting-started/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ATT&CK: Getting started is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Baseline Cyber Security Requirements for AI Models and Systems

  • Website: https://www.etsi.org/deliver/etsi_en/304200_304299/304223/02.01.01_60/en_304223v020101p.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Baseline Cyber Security Requirements for AI Models and Systems is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

BEATS agents

  • Website: https://www.elastic.co/beats/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: BEATS agents is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Best practices for AD disaster recovery

  • Website: https://www.quest.com/webcast-ondemandt/best-practices-for-active-directory-disaster-recovery/?param=L4qcdiH1R46lWbN5Jxs%2fNN0Qky57LDYQTnsyaoWVqKYZTocd3n1RpFTyQegqps0MbW7yx4UWSKyVRVyz%2bwo0XRB2%2fXpFzrMZeOA%2fne%2f4Fm3oH5YJAnFCP%2fnRqs9Rq%2fRD0VTXvdBaojCx5J46htyILvanM5FhOVa7MCGDGYBcq6925YtpmANy9OA1%2fjdtlDrp
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Best practices for AD disaster recovery is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

BloodHound Community

  • Website: https://github.com/SpecterOps/BloodHound
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: BloodHound Community is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Blue Team Notes

  • Website: https://github.com/Purp1eW0lf/Blue-Team-Notes
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Blue Team Notes is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

BlueCoat Edge SWG

  • Website: https://www.broadcom.com/products/cybersecurity/network/web-protection/proxy-sg-and-advanced-secure-gateway
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: BlueCoat Edge SWG is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Building a SOC

  • Website: https://www.first.org/resources/guides/Factsheet_Building_a_SOC_start_small.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Building a SOC is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

Building a SOC

  • Website: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Building a SOC is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

Business Impact Assessment

  • Website: https://bia.cisecurity.org/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Business Impact Assessment is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Canary.tools

  • Website: https://canary.tools/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Canary.tools is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

Cat-Scale

  • Website: https://labs.withsecure.com/tools/cat-scale-linux-incident-response-collection
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Cat-Scale is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

CERT-FR

  • Website: https://www.cert.ssi.gouv.fr/avis/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CERT-FR is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

CERT-in-a-box

  • Website: https://www.first.org/resources/guides/cert-in-a-box.zip
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CERT-in-a-box is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a CERT/CSIRT.

Back to Category Index

CERT-US

  • Website: https://www.cisa.gov/uscert/ncas/alerts
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CERT-US is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Chapril

  • Website: https://drop.chapril.org/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Chapril is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

CIS

  • Website: https://www.cisecurity.org/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CIS is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Harden SOC/CSIRT environment.

Back to Category Index

CIS benchmarks

  • Website: https://www.cisecurity.org/cis-benchmarks/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CIS benchmarks is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT achitecture of a SOC > Disconnect (as much as possible) SOC from monitored environment > Endpoints hardening:.

Back to Category Index

CISA Thorium

  • Website: https://github.com/cisagov/thorium?tab=readme-ov-file
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CISA Thorium is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

clean-up script

  • Website: https://github.com/simeononsecurity/Windows-Optimize-Harden-Debloat
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: clean-up script is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Harden SOC/CSIRT environment.

Back to Category Index

CloudFlare

  • Website: https://www.cloudflare.com/plans/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CloudFlare is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

command line reference

  • Website: https://cmd.ms/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: command line reference is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Community Yara rules

  • Website: https://github.com/Neo23x0/signature-base
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Community Yara rules is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Compromise assessment methodology

  • Website: https://evrenbey.medium.com/compromise-assessment-methodology-820910efb6a4
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Compromise assessment methodology is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Crowdsec

  • Website: https://www.crowdsec.net/product/crowdsec-security-engine
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Crowdsec is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

CrowdStrike

  • Website: https://www.crowdstrike.com/blog/feed
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CrowdStrike is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

CSIRT Services Framework

  • Website: https://www.first.org/standards/frameworks/csirts/csirt_services_framework_v2.1
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CSIRT Services Framework is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a CERT/CSIRT.

Back to Category Index

CSIRT, SOC, ISAC and PSIRT definitions

  • Website: https://www.linkedin.com/pulse/csirt-soc-isac-psirt-definitions-vilius-benetis
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CSIRT, SOC, ISAC and PSIRT definitions is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

CTI Framework

  • Website: https://www.cert.europa.eu/publications/threat-intelligence/cyber-threat-intelligence-framework/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CTI Framework is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

CTI's repo

  • Website: https://github.com/chronicle/GCTI/tree/main/YARA
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CTI's repo is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Yara rules for Cobalt Strike and others.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

CVSS v4 specs

  • Website: https://www.first.org/cvss/v4-0/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CVSS v4 specs is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Cyber Defense Incident Responder role

  • Website: https://www.cisa.gov/cyber-defense-incident-responder
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Cyber Defense Incident Responder role is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Cyber Threat readiness report 2023

  • Website: https://swimlane.com/wp-content/uploads/Cyber-Threat-Readiness-Report-2023.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Cyber Threat readiness report 2023 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

CyberChef

  • Website: https://github.com/NextronSystems/CyberChef
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CyberChef is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

CyberSecurity

  • Website: https://medium.com/feed/tag/cybersecurity
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: CyberSecurity is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Cybersecurity business value benchmark

  • Website: https://emtemp.gcom.cloud/ngw/globalassets/en/doc/documents/775537-gartner-cybersecurity-business-value-benchmark-1st-generation.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Cybersecurity business value benchmark is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Databreach reports

  • Website: https://www.verizon.com/business/resources/reports/dbir/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Databreach reports is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Detection engineering

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/detection_engineering.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Detection engineering is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Table of Content.

Back to Category Index

DeTTECT

  • Website: https://github.com/rabobank-cdc/DeTTECT
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: DeTTECT is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

Diaries

  • Website: https://isc.sans.edu/diary/0
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Diaries is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Digital Defense Report

  • Website: https://www.microsoft.com/en-us/corporate-responsibility/cybersecurity/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Digital Defense Report is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

EBIOS RM methodology

  • Website: https://www.ssi.gouv.fr/guide/ebios-risk-manager-the-method/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: EBIOS RM methodology is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

EMCO Remote installer

  • Website: https://emcosoftware.com/remote-installer
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: EMCO Remote installer is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

FastIR

  • Website: https://github.com/OWNsecurity/fastir_artifacts
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: FastIR is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

FireEye Flare-VM

  • Website: https://github.com/mandiant/flare-vm
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: FireEye Flare-VM is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: framework to automate security tools installation on analysts workstations;.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

forest is the AD security boundary

  • Website: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/gathering-information-about-your-active-directory-deployment
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: forest is the AD security boundary is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: , for isolation purposes, in case of a global enterprise's IT compromise.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Harden SOC/CSIRT environment.

Back to Category Index

Forrester wave for SSE

  • Website: https://www.netskope.com/wp-content/uploads/2024/03/forrester-wave-sse-solutions-diagram-1340x1640-1.png
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Forrester wave for SSE is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Fundamental concepts

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/soc_basics.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Fundamental concepts is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Table of Content.

Back to Category Index

Gartner magic quadrant

  • Website: https://www.bitdefender.com/en-us/business/campaign/2025-gartner-magic-quadrant-for-epp-the-only-visionary
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner magic quadrant is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

Gartner magic quadrant

  • Website: https://www.gartner.com/doc/reprints?id=1-2IYCQ1TR&ct=241001&st=sb
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner magic quadrant is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Gartner magic quadrant

  • Website: https://www.sentinelone.com/lp/gartnermq/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner magic quadrant is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: , , and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Gartner magic quadrant

  • Website: https://www.netskope.com/wp-content/uploads/2025/05/2025-05-SSE-MQ-site-1040x1094-1-768x808.png
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner magic quadrant is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Gartner reviews and ratings

  • Website: https://www.gartner.com/reviews/market/email-security
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner reviews and ratings is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Gartner reviews and ratings

  • Website: https://www.gartner.com/reviews/market/data-loss-prevention
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gartner reviews and ratings is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

Gatewatcher

  • Website: https://www.gatewatcher.com/en/our-solutions/trackwatch/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gatewatcher is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

GDPR cybersecurity implications (in French)

  • Website: https://atelier-rgpd.cnil.fr/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: GDPR cybersecurity implications (in French) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Gigamon

  • Website: https://www.gigamon.com/products/access-traffic/network-taps.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Gigamon is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

GitLab

  • Website: https://about.gitlab.com/handbook/engineering/security/security-operations/sirt/sec-incident-response.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: GitLab is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

Good practice for incident management

  • Website: https://www.enisa.europa.eu/publications/good-practice-guide-for-incident-management
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Good practice for incident management is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a CERT/CSIRT.

Back to Category Index

hardening tool

  • Website: https://apps.microsoft.com/detail/9p7ggfl7dx57
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: hardening tool is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Harden SOC/CSIRT environment.

Back to Category Index

How to be compliant with NIS2?

  • Website: https://securenvoy.com/blog/how-to-be-compliant-with-new-nis-directive/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: How to be compliant with NIS2? is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

how to mange FP in a SOC?

  • Website: https://www.idna.fr/2018/11/06/comment-gerer-les-faux-positifs-dans-un-soc/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: how to mange FP in a SOC? is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: , in FR.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

How to set-up a CSIRT and SOC

  • Website: https://www.enisa.europa.eu/publications/how-to-set-up-csirt-and-soc/at_download/fullReport
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: How to set-up a CSIRT and SOC is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

How will NIS2 impact your organization?

  • Website: https://www.linkedin.com/pulse/how-eu-directive-nis2-impact-your-organization-anders-fleinert-larsen%3FtrackingId=Vq3GCGlOTXe1u0dllhn9MA%253D%253D/?_l=fr_FR
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: How will NIS2 impact your organization? is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

IBM Resilient

  • Website: https://www.ibm.com/qradar/security-qradar-soar?utm_content=SRCWW&p1=Search&p4=43700068028974608&p5=e&gclid=Cj0KCQjw9ZGYBhCEARIsAEUXITW2yUqAfNqWNeYXyENeUAoqLxV543LT0n2oYhYxEQ47Yjm7NfYTFHAaAtwpEALw_wcB&gclsrc=aw.ds
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: IBM Resilient is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

image

  • Website: https://user-images.githubusercontent.com/16035152/202517740-812091b6-ff31-49cd-941e-3f6e4b4d140c.png
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: image is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Harden SOC/CSIRT environment.

Back to Category Index

ImmuniWeb

  • Website: https://www.immuniweb.com/websec/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ImmuniWeb is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Intrinsec (in French)

  • Website: https://www.intrinsec.com/monitoring-cyber/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Intrinsec (in French) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

ISO 27035 Practical value for CSIRT and SOCs

  • Website: https://www.first.org/resources/papers/conf2023/FIRSTCON23-TLPCLEAR-Benetis-ISO-27035-practical-value-for-CSIRTs-and-SOCs.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ISO 27035 Practical value for CSIRT and SOCs is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

Isolate Tier 0 assets with group policy

  • Website: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/initially-isolate-tier-0-assets-with-group-policy-to-start/ba-p/1184934
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Isolate Tier 0 assets with group policy is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Krebs on security

  • Website: https://krebsonsecurity.com/feed/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Krebs on security is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

latest Forrester Wave about MTD

  • Website: https://reprint.forrester.com/reports/the-forrester-wave-tm-mobile-threat-defense-solutions-q3-2024-fd48faab/index.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: latest Forrester Wave about MTD is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Licensing maps, eg. for Defender

  • Website: https://m365maps.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Licensing maps, eg. for Defender is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Nice to read.

Back to Category Index

LinkedIn Information Security Community group

  • Website: https://www.linkedin.com/groups/38412/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: LinkedIn Information Security Community group is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

List of trusted cybersecurity services providers

  • Website: https://www.enisa.europa.eu/sites/default/files/2025-07/EU%20Cybersecurity%20Reserve%20companies.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: List of trusted cybersecurity services providers is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Management

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/management.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Management is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Table of Content.

Back to Category Index

Mappings explorer

  • Website: https://center-for-threat-informed-defense.github.io/mappings-explorer/external/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Mappings explorer is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Michel De Crevoisier's Git

  • Website: https://github.com/mdecrevoisier/SIGMA-detection-rules
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Michel De Crevoisier's Git is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Microsoft Defender

  • Website: https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-windows?view=o365-worldwide
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft Defender is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Microsoft Defender for Office365

  • Website: https://www.microsoft.com/en-us/security/business/siem-and-xdr/microsoft-defender-office-365
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft Defender for Office365 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Microsoft Developer virtual machines

  • Website: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft Developer virtual machines is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Harden SOC/CSIRT environment.

Back to Category Index

Microsoft Intune

  • Website: https://docs.microsoft.com/en-us/mem/intune/fundamentals/what-is-intune
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft Intune is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

Microsoft MCAS

  • Website: https://www.microsoft.com/en-us/security/business/siem-and-xdr/microsoft-defender-cloud-apps
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft MCAS is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Microsoft Sentinel queries

  • Website: https://github.com/reprise99/Sentinel-Queries
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft Sentinel queries is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Microsoft SharePoint

  • Website: https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Microsoft SharePoint is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: , Wiki (choose the one you prefer, or ).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

Mitre Engenuity Evaluations 2022 review

  • Website: https://www.cybervigilance.uk/post/2022-mitre-att-ck-engenuity-results
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Mitre Engenuity Evaluations 2022 review is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

MMPC

  • Website: https://blogs.technet.microsoft.com/mmpc/feed/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: MMPC is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

MS Sentinel architecture and recommendations for MSSP

  • Website: https://myfabersecurity.com/2023/03/31/sentinel-poc-architecture-and-recommendations-for-mssps-part-1/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: MS Sentinel architecture and recommendations for MSSP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Must read

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/README.md#must-read
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Must read is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Table of Content.

Back to Category Index

NIS2 10 main requirements

  • Website: https://nis2directive.eu/nis2-requirements/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: NIS2 10 main requirements is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

NIS2 technical implementation guidance

  • Website: https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: NIS2 technical implementation guidance is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

NIS2, how to address the security control gaps

  • Website: https://event.on24.com/eventRegistration/console/apollox/mainEvent?simulive=y&eventid=4110743&sessionid=1&username=&partnerref=&format=fhvideo1&mobile=&flashsupportedmobiledevice=&helpcenter=&key=588150776CAE70D7F02ECF2848FF11FA&newConsole=true&nxChe=true&newTabCon=true&consoleEarEventConsole=false&text_language_id=en&playerwidth=748&playerheight=526&eventuserid=600843623&contenttype=A&mediametricsessionid=517006274&mediametricid=5797475&usercd=600843623&mode=launch
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: NIS2, how to address the security control gaps is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Nozomi Guardian

  • Website: https://www.nozominetworks.com/products/guardian/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Nozomi Guardian is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

Olaf Hartong's config

  • Website: https://github.com/olafhartong/sysmon-modular/blob/master/sysmonconfig.xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Olaf Hartong's config is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

OneTimeSecret

  • Website: https://onetimesecret.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: OneTimeSecret is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

OpenIOC format

  • Website: https://github.com/fireeye/OpenIOC_1.1/blob/master/IOC_Terms_Defs.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: OpenIOC format is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

OSINTracker

  • Website: https://app.osintracker.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: OSINTracker is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Other critical tools for a SOC and a CERT/CSIRT.

Back to Category Index

PacketStorm Security

  • Website: https://packetstorm.news/rss/news
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: PacketStorm Security is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

PAW Microsoft

  • Website: https://docs.microsoft.com/en-us/security/compass/privileged-access-devices
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: PAW Microsoft is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

PhishLabs

  • Website: https://www.phishlabs.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: PhishLabs is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > SOC sensors, nice to have.

Back to Category Index

Powershell Hunter

  • Website: https://github.com/MHaggis/PowerShell-Hunter/tree/main
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Powershell Hunter is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

ProofPoint

  • Website: https://www.proofpoint.com/us/rss.xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: ProofPoint is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

PTES

  • Website: http://www.pentest-standard.org/index.php/Main_Page
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: PTES is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Purple Team Assessment

  • Website: https://www.fireeye.fr/content/dam/fireeye-www/regional/fr_FR/services/pdfs/ds-purple-team-assessment.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Purple Team Assessment is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

R 8596, Cybersecurity Framework Profile for Artificial Intelligence

  • Website: https://csrc.nist.gov/pubs/ir/8596/iprd
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: R 8596, Cybersecurity Framework Profile for Artificial Intelligence is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

RACI template (in French)

  • Website: https://github.com/cyberabdou/SOC/blob/77f01ba82c22cb11028cde4a862ae0bea4258378/SOC%20RACI.xlsx
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: RACI template (in French) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Ransomware live feeds

  • Website: https://ransomware.live/rss.xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Ransomware live feeds is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

RedTeam resources

  • Website: https://github.com/J0hnbX/RedTeam-Resources
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: RedTeam resources is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Resources inventory

  • Website: https://inventory.raw.pm/resources.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Resources inventory is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

RFC2350

  • Website: https://www.cert.ssi.gouv.fr/uploads/CERT-FR_RFC2350_EN.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: RFC2350 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: (CERT description).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Nice to read.

Back to Category Index

SaaS attack matrix

  • Website: https://github.com/pushsecurity/saas-attacks#the-saas-attacks-matrix
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SaaS attack matrix is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

SANS SOC survey 2022

  • Website: https://www.splunk.com/en_us/pdfs/resources/whitepaper/sans-soc-survey-2022.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SANS SOC survey 2022 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Schneier on Security

  • Website: http://feeds.feedburner.com/schneier/excerpts
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Schneier on Security is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Secure Web Gateway

  • Website: https://www.gartner.com/en/information-technology/glossary/secure-web-gateway
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Secure Web Gateway is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: ** (SWG) / Security Service Edge:.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Secure your business with 365

  • Website: https://learn.microsoft.com/en-us/microsoft-365/business-premium/secure-your-business-data?view=o365-worldwide
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Secure your business with 365 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

SecureList

  • Website: https://securelist.com/feed/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SecureList is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Security 360

  • Website: https://twitter.com/Shubham_pen/status/1655192003448020993?s=20
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Security 360 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Security advisories

  • Website: https://cert.europa.eu/publications/security-advisories-rss
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Security advisories is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Security incident management according to ISO 27005

  • Website: https://www.linkedin.com/pulse/security-incident-management-according-iso-27035-dipen-das-
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Security incident management according to ISO 27005 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a CERT/CSIRT.

Back to Category Index

Semperis Directory Services Protector

  • Website: https://www.semperis.com/active-directory-security/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Semperis Directory Services Protector is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Semperis Purple Knight

  • Website: https://www.purple-knight.com/fr/?utm_source=gads&utm_medium=paidsearch&utm_campaign=pk_emea&gclid=Cj0KCQjw9ZGYBhCEARIsAEUXITV3yX7Nn6_GR-YVwiOANFvS9wsEQdTyUGHvMMirMzNQEoQ1Q3EQYIMaAjTgEALw_wcB
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Semperis Purple Knight is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: or.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Semperis Purple Knight

  • Website: https://www.purple-knight.com/active-directory-security-tool/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Semperis Purple Knight is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Sentinel data collection scenarios

  • Website: https://learn.microsoft.com/en-us/azure/sentinel/connect-cef-ama#how-collection-works-with-the-common-event-format-cef-via-ama-connector
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Sentinel data collection scenarios is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

SentinelOne

  • Website: https://www.sentinelone.com/blog/active-edr-feature-spotlight/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SentinelOne is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

SIFT Workstation

  • Website: https://www.sans.org/tools/sift-workstation/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SIFT Workstation is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: , or ;.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Sigma HQ (detection rules)

  • Website: https://github.com/SigmaHQ/sigma/tree/master/rules
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Sigma HQ (detection rules) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

SIRP

  • Website: https://d3security.com/blog/whats-the-difference-between-soar-and-sao/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SIRP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

SIRP / SOA / TIP benefits

  • Website: https://threatconnect.com/blog/realizing-the-benefits-of-security-orchestration-automation-and-response-soar/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SIRP / SOA / TIP benefits is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

SOC analyst interview questions

  • Website: https://github.com/LetsDefend/SOC-Interview-Questions
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SOC analyst interview questions is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

SOC model guide

  • Website: https://fr.scribd.com/document/732782046/Gartner-SOC-Model-Guide-2023
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SOC model guide is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

SOC Prime

  • Website: https://tdm.socprime.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SOC Prime is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

SOC-CMM

  • Website: https://www.soc-cmm.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SOC-CMM is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

SOCTOM

  • Website: https://soc-cmm.com/downloads/SOCTOM%20whitepaper.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SOCTOM is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

SP800-53 rev5 (Security and Privacy Controls for Information Systems and Organizations)

  • Website: https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SP800-53 rev5 (Security and Privacy Controls for Information Systems and Organizations) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

SP800-61 rev3, incident handling guide

  • Website: https://csrc.nist.gov/pubs/sp/800/61/r3/ipd
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SP800-61 rev3, incident handling guide is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Splunk Security content (free detection rules for Splunk)

  • Website: https://research.splunk.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Splunk Security content (free detection rules for Splunk) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

State of Security 2023

  • Website: https://www.splunk.com/en_us/pdfs/gated/ebooks/state-of-security-2023.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: State of Security 2023 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > For a SOC.

Back to Category Index

STIX

  • Website: https://oasis-open.github.io/cti-documentation/stix/intro.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: STIX is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

SwimLane

  • Website: https://swimlane.com/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SwimLane is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

SwitchToOpen

  • Website: https://github.com/CyberFlooD/SwitchToOpen
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: SwitchToOpen is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Sysinspector

  • Website: https://www.eset.com/int/support/sysinspector/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Sysinspector is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Sysmon

  • Website: https://learn.microsoft.com/fr-fr/sysinternals/downloads/sysmon
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Sysmon is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

TaHiTI (threat hunting methodology)

  • Website: https://www.betaalvereniging.nl/wp-content/uploads/TaHiTI-Threat-Hunting-Methodology-whitepaper.pdf
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: TaHiTI (threat hunting methodology) is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

TheRecord.media

  • Website: https://therecord.media/subscribe
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: TheRecord.media is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Threat landscape 2025

  • Website: https://www.enisa.europa.eu/publications/enisa-threat-landscape-2025
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Threat landscape 2025 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Threat Matrix for AI-systems

  • Website: https://github.com/mitre/advmlthreatmatrix/blob/master/pages/adversarial-ml-threat-matrix.md#adversarial-ml-threat-matrix
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Threat Matrix for AI-systems is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Threat report

  • Website: https://www.welivesecurity.com/en/eset-research/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Threat report is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Timesketch

  • Website: https://timesketch.org/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Timesketch is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Tiny Check

  • Website: https://github.com/KasperskyLab/TinyCheck
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Tiny Check is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

TIP

  • Website: https://www.ssi.gouv.fr/en/actualite/opencti-the-open-source-solution-for-processing-and-sharing-threat-intelligence-knowledge/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: TIP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

TLP

  • Website: https://www.first.org/tlp/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: TLP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: (intelligence sharing and confidentiality), and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Tools inventory

  • Website: https://inventory.raw.pm/tools.html
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Tools inventory is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Top 0days "in the wild"

  • Website: https://docs.google.com/spreadsheets/d/1lkNJ0uQwbeC1ZTRrxdtuPLCIl7mlUreoKfSIgajnSyY/edit#gid=1746868651
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Top 0days "in the wild" is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

top 10

  • Website: https://expertinsights.com/insights/the-top-dark-web-monitoring-solutions/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: top 10 is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > SOC sensors, nice to have.

Back to Category Index

Turning threat reports into detection insights with AI

  • Website: https://www.microsoft.com/en-us/security/blog/2026/01/29/turning-threat-reports-detection-insights-ai/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Turning threat reports into detection insights with AI is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Upcoming advisories

  • Website: https://www.zerodayinitiative.com/rss/upcoming/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Upcoming advisories is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

V1D1AN's Drawing: architecture of detection

  • Website: https://github.com/V1D1AN/S1EM/wiki/Architecture-guide#the-architecture-of-detection
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: V1D1AN's Drawing: architecture of detection is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Nice to read.

Back to Category Index

Velociraptor

  • Website: https://docs.velociraptor.app/docs/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Velociraptor is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Wazuh at the heart of a SOC architecture for public/critical infrastructures

  • Website: https://medium.com/@ludovic.doamba/wazuh-at-the-heart-of-sovereign-soc-architecture-for-public-and-critical-infrastructures-f0d18562d14b
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Wazuh at the heart of a SOC architecture for public/critical infrastructures is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

We Live Security

  • Website: http://feeds.feedburner.com/eset/blog?format=xml
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: We Live Security is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Web server compromise assessment SOP

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/sop_web_server_compromise_assessment.md
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Web server compromise assessment SOP is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

What is SecOps

  • Website: https://www.sentinelone.com/cybersecurity-101/secops/?utm_content=white-paper&utm_medium=paid-display&utm_source=gdn-paid&utm_campaign=emea-t1-en-g-dsa&utm_term={demo-request}&utm_campaignid=19179764064&gclid=EAIaIQobChMItYzg5amQ_gIV6pBoCR1u0ACxEAAYAiAAEgJ1ofD_BwE
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: What is SecOps is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

Windows 10 and Windows Server 2016 security auditing and monitoring reference

  • Website: https://www.microsoft.com/en-us/download/details.aspx?id=52630
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Windows 10 and Windows Server 2016 security auditing and monitoring reference is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: To go further > Must read.

Back to Category Index

Windows Defender Offline

  • Website: https://support.microsoft.com/en-us/windows/help-protect-my-pc-with-microsoft-defender-offline-9306d528-64bf-4668-5b80-ff533f183d6c
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Windows Defender Offline is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

WSTG

  • Website: https://owasp.org/www-project-web-security-testing-guide/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: WSTG is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Nice to read.

Back to Category Index

Xposed

  • Website: https://www.withsecure.com/en/expertise/podcasts
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Xposed is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: IT/security Watch > Recommended sources.

Back to Category Index

Yara rules repo

  • Website: https://github.com/phbiohazard/Yara
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Yara rules repo is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical tools for CSIRT.

Back to Category Index

Zimperium MTD

  • Website: https://www.zimperium.com/mtd/
  • Model: Open Source
  • Category: SOC Operations
  • Source Lists: Awesome SOC

What it does: Zimperium MTD is used in soc operations programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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: Mission-critical means (tools/sensors) > Critical sensors for a SOC.

Back to Category Index

Secrets & Credential Security

This category contains 9 documented tools. It focuses on capabilities used for secret storage hardening, credential rotation, and key governance. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

0xf.at

  • Website: https://0xf.at/
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Hacking

What it does: 0xf.at is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: a website without logins or ads where you can solve password-riddles (so called hackits).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Web.

Back to Category Index

Hashcat

  • Website: https://hashcat.net/hashcat/
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome CTF, Awesome Forensics

What it does: Hashcat is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: Fast password cracker with GPU support.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Decryption.

Back to Category Index

hnypots-agent)

  • Website: https://github.com/joshrendek/hnypots-agent
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Honeypots

What it does: hnypots-agent) is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: SSH Server in Go that logs username and password combinations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

Keyscope

  • Website: https://github.com/SpectralOps/keyscope
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Security, Awesome Penetration Testing, Awesome Hacking

What it does: Keyscope is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: Keyscope is an extensible key and secret validation for checking active secrets against multiple SaaS vendors built in Rust.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT).

Back to Category Index

Ophcrack

  • Website: http://ophcrack.sourceforge.net/
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome CTF

What it does: Ophcrack is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: Windows password cracker based on rainbow tables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 > Bruteforcers.

Back to Category Index

passbolt

  • Website: https://www.passbolt.com/
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Security

What it does: passbolt is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: The password manager your team was waiting for. Free, open source, extensible, based on OpenPGP.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

passpie

  • Website: https://github.com/marcwebbie/passpie
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Security

What it does: passpie is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: Multiplatform command-line password 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: Awesome Security > Datastores.

Back to Category Index

Safe

  • Website: https://github.com/starkandwayne/safe
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Security

What it does: Safe is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: A Vault CLI that makes reading from and writing to the Vault easier to do.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Vault

  • Website: https://www.vaultproject.io/
  • Model: Open Source
  • Category: Secrets & Credential Security
  • Source Lists: Awesome Security

What it does: Vault is used in secrets & credential security programs to support secret storage hardening, credential rotation, and key governance. Source summaries describe it as: An encrypted datastore secure enough to hold environment and application secrets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Datastores.

Back to Category Index

Security Awareness & Training

This category contains 7 documented tools. It focuses on capabilities used for human risk reduction through behavioral learning and simulation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

BadBlood

  • Website: https://www.secframe.com/badblood/
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: BadBlood is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: Fills a test (non-production) Windows Domain with data that enables security analysts and engineers to practice using tools to gain an understanding and prescribe to securing 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 Cybersecurity Blue Team > Preparedness training and wargaming.

Back to Category Index

Caldera

  • Website: https://caldera.mitre.org/
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Caldera is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: Scalable, automated, and extensible adversary emulation platform developed by MITRE.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Haaukins

  • Website: https://github.com/aau-network-security/haaukins
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome CTF

What it does: Haaukins is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: A Highly Accessible and Automated Virtualization Platform for Security Education.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

HR and training

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/hr_training.md
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome SOC

What it does: HR and training is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. 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: Table of Content.

Back to Category Index

LetsDefend

  • Website: https://letsdefend.io
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome Threat Detection

What it does: LetsDefend is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: Hands-On SOC Analyst Training.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

RedEye

  • Website: https://cisagov.github.io/RedEye/
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: RedEye is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: Analytic tool to assist both Red and Blue teams with visualizing and reporting command and control activities, replay and demonstrate attack paths, and more clearly communicate remediation recommendations to stakeholders.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Post-engagement analysis and reporting.

Back to Category Index

TryHackMe

  • Website: https://tryhackme.com
  • Model: Open Source
  • Category: Security Awareness & Training
  • Source Lists: Awesome Threat Detection, Awesome Hacking

What it does: TryHackMe is used in security awareness & training programs to support human risk reduction through behavioral learning and simulation. Source summaries describe it as: Hands-on cyber security training through real-world scenarios.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Supply Chain Security

This category contains 7 documented tools. It focuses on capabilities used for dependency provenance controls, build pipeline trust, and artifact verification. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Confusion checker

  • Website: https://github.com/sonatype-nexus-community/repo-diff
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Confusion checker is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Script to check if you have artifacts containing the same name between your 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 Cybersecurity Blue Team > DevSecOps > Dependency confusion.

Back to Category Index

Dependency Combobulator

  • Website: https://github.com/apiiro/combobulator
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Dependency Combobulator is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Open source, modular and extensible framework to detect and prevent dependency confusion leakage and potential 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 Cybersecurity Blue Team > DevSecOps > Dependency confusion.

Back to Category Index

Helm GPG (GnuPG) Plugin

  • Website: https://github.com/technosophos/helm-gpg
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Helm GPG (GnuPG) Plugin is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Chart signing and verification with GnuPG for Helm.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Supply chain security.

Back to Category Index

in-toto

  • Website: https://in-toto.io/
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: in-toto is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Framework to secure the integrity of software supply chains.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Supply chain security.

Back to Category Index

Notary

  • Website: https://github.com/theupdateframework/notary
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Notary is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Aims to make the internet more secure by making it easy for people to publish and verify content.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Supply chain security.

Back to Category Index

Preflight

  • Website: https://github.com/spectralops/preflight
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Security

What it does: Preflight is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: helps you verify scripts and executables to mitigate supply chain attacks in your CI and other 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 Security > DevOps.

Back to Category Index

snync

  • Website: https://github.com/snyk-labs/snync
  • Model: Open Source
  • Category: Supply Chain Security
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: snync is used in supply chain security programs to support dependency provenance controls, build pipeline trust, and artifact verification. Source summaries describe it as: Prevent and detect if you're vulnerable to dependency confusion supply chain security 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 Cybersecurity Blue Team > DevSecOps > Dependency confusion.

Back to Category Index

Threat Detection

This category contains 116 documented tools. It focuses on capabilities used for baseline hardening, monitoring integration, and defense-in-depth validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

A Research-Driven process applied to Threat Detection Engineering Inputs

  • Website: https://ateixei.medium.com/a-research-driven-process-applied-to-threat-detection-engineering-inputs-1b7e6fe0412b
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: A Research-Driven process applied to Threat Detection Engineering Inputs is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

A Simple Hunting Maturity Model

  • Website: http://detect-respond.blogspot.com.au/2015/10/a-simple-hunting-maturity-model.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: A Simple Hunting Maturity Model is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Hunting Maturity Model describes five levels of organizational hunting capability, ranging from HMM0 (the least capability) to HMM4 (the most).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

Actionable Detects

  • Website: https://prezi.com/vejpnxkm85ih/actionable-detects-dns-keynote/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Actionable Detects is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Blue Team Tactics.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > DNS.

Back to Category Index

Active Directory Threat Hunting

  • Website: https://adsecurity.org/wp-content/uploads/2017/04/2017-BSidesCharm-DetectingtheElusive-ActiveDirectoryThreatHunting-Final.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Active Directory Threat Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows.

Back to Category Index

adversary_emulation_library

  • Website: https://github.com/center-for-threat-informed-defense/adversary_emulation_library
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: adversary_emulation_library is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: An open library of adversary emulation plans designed to empower organizations to test their defenses based on real-world TTPs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Alerting and Detection Strategies Framework

  • Website: https://github.com/palantir/alerting-detection-strategy-framework
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Alerting and Detection Strategies Framework is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A framework for developing alerting and detection strategies.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

Alerting and Detection Strategy Framework

  • Website: https://medium.com/@palantir/alerting-and-detection-strategy-framework-52dc33722df2
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Alerting and Detection Strategy Framework is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Alexandre Teixeira

  • Website: https://ateixei.medium.com
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Alexandre Teixeira is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Blogs.

Back to Category Index

An Introduction to HTTP fingerprinting

  • Website: https://www.net-square.com/httprint_paper.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: An Introduction to HTTP fingerprinting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Anton Chuvakin

  • Website: https://medium.com/anton-on-security
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Anton Chuvakin is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Blogs.

Back to Category Index

attack_data

  • Website: https://github.com/splunk/attack_data
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: attack_data is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A repository of curated datasets from various 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 Threat Detection and Hunting > Dataset.

Back to Category Index

Boss of the SOC (BOTS) Dataset Version 1

  • Website: https://github.com/splunk/botsv1
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Boss of the SOC (BOTS) Dataset Version 1 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Dataset.

Back to Category Index

Boss of the SOC (BOTS) Dataset Version 2

  • Website: https://github.com/splunk/botsv2
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Boss of the SOC (BOTS) Dataset Version 2 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Dataset.

Back to Category Index

Boss of the SOC (BOTS) Dataset Version 3

  • Website: https://github.com/splunk/botsv3
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Boss of the SOC (BOTS) Dataset Version 3 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Dataset.

Back to Category Index

botconf 2016 Slides

  • Website: https://www.botconf.eu/wp-content/uploads/2016/11/PR12-Sysmon-UELTSCHI.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: botconf 2016 Slides is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources > Windows > Sysmon.

Back to Category Index

Bro-Osquery

  • Website: https://github.com/bro/bro-osquery
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Bro-Osquery is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Bro integration with osquery.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Brosquery

  • Website: https://github.com/jandre/brosquery
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Brosquery is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A module for osquery to load Bro logs into tables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

BZAR

  • Website: https://github.com/mitre-attack/bzar
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: BZAR is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: (Bro/Zeek ATT&CK-based Analytics and Reporting) - A set of Zeek scripts to detect ATT&CK techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

C2 Matrix

  • Website: https://www.thec2matrix.com/matrix
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: C2 Matrix is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Threat Simulation Resources.

Back to Category Index

Capability Abstraction

  • Website: https://posts.specterops.io/capability-abstraction-fbeaeeb26384
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Capability Abstraction is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

CIC Datasets

  • Website: https://www.unb.ca/cic/datasets/index.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: CIC Datasets is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Canadian Institute for Cybersecurity datasets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Dataset.

Back to Category Index

Cyber Kill Chain

  • Website: https://www.lockheedmartin.com/us/what-we-do/aerospace-defense/cyber/cyber-kill-chain.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Cyber Kill Chain is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: It is part of the Intelligence Driven Defense® model for identification and prevention of cyber intrusions activity. The model identifies what the adversaries must complete in order to achieve their objective.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

CyberThreatHunting

  • Website: https://github.com/A3sal0n/CyberThreatHunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: CyberThreatHunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A collection of resources for threat hunters.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources.

Back to Category Index

Darknet Diaries

  • Website: https://darknetdiaries.com
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Darknet Diaries is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: by Andy Greenberg - True stories from the dark side of the Internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Podcasts.

Back to Category Index

Data Science Hunting Funnel

  • Website: http://www.austintaylor.io/network/traffic/threat/data/science/hunting/funnel/machine/learning/domain/expertise/2017/07/11/data-science-hunting-funnel/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Data Science Hunting Funnel is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

data_hacking

  • Website: https://github.com/SuperCowPowers/data_hacking
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: data_hacking is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Examples of using IPython, Pandas, and Scikit Learn to get the most out of your security data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Data Science.

Back to Category Index

Detecting DNS Tunneling

  • Website: https://www.sans.org/reading-room/whitepapers/dns/detecting-dns-tunneling-34152
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Detecting DNS Tunneling is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

Detecting dynamic DNS domains in Splunk

  • Website: https://www.splunk.com/blog/2015/08/04/detecting-dynamic-dns-domains-in-splunk.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Detecting dynamic DNS domains in Splunk is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

Detection Engineering Weekly

  • Website: https://www.detectionengineering.net
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Detection Engineering Weekly is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: by Zack 'techy' Allen.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Newsletters.

Back to Category Index

Detection Spectrum

  • Website: https://posts.specterops.io/detection-spectrum-198a0bfb9302
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Detection Spectrum is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

Detection: Challenging Paradigms

  • Website: https://www.dcppodcast.com/all-episodes
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Detection: Challenging Paradigms is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: by SpecterOps.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Podcasts.

Back to Category Index

DetectionLab

  • Website: https://github.com/clong/DetectionLab/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: DetectionLab is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Vagrant & Packer scripts to build a lab environment complete with security tooling and logging best practices.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

DNS is NOT Boring

  • Website: https://www.first.org/resources/papers/conf2017/DNS-is-NOT-Boring-Using-DNS-to-Expose-and-Thwart-Attacks.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: DNS is NOT Boring is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Using DNS to Expose and Thwart 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 Threat Detection and Hunting > Resources > DNS.

Back to Category Index

Effective TLS Fingerprinting Beyond JA3

  • Website: https://www.ntop.org/ndpi/effective-tls-fingerprinting-beyond-ja3/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Effective TLS Fingerprinting Beyond JA3 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Elastic Detection Rules

  • Website: https://github.com/elastic/detection-rules
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Elastic Detection Rules is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Detection Rules.

Back to Category Index

Empire

  • Website: https://github.com/EmpireProject/Empire
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection, Awesome Cyber Security Tools, Awesome Hacking

What it does: Empire is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A post exploitation framework for powershell and 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 Threat Detection and Hunting > Threat Simulation Tools.

Back to Category Index

EQL

  • Website: https://github.com/endgameinc/eql
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: EQL is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Event Query Language.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

EQLLib

  • Website: https://github.com/endgameinc/eqllib
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: EQLLib is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Event Query Language Analytics Library (eqllib) is a library of event based analytics, written in EQL to detect adversary behaviors identified in MITRE ATT&CK™.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Expert Investigation Guide - Threat Hunting

  • Website: https://github.com/Foundstone/ExpertInvestigationGuides/tree/master/ThreatHunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Expert Investigation Guide - Threat Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Generating Hypotheses for Successful Threat Hunting

  • Website: https://www.sans.org/reading-room/whitepapers/threats/generating-hypotheses-successful-threat-hunting-37172
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Generating Hypotheses for Successful Threat Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

HASSH - a profiling method for SSH Clients and Servers

  • Website: https://engineering.salesforce.com/open-sourcing-hassh-abed3ae5044c
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HASSH - a profiling method for SSH Clients and Servers is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

HASSH @BSides Canberra 2019 - Slides

  • Website: https://github.com/benjeems/Presentations/blob/master/BSides%202019%20%20-%20HASSH%20-%20a%20Profiling%20Method%20for%20SSH%20Clients%20and%20Servers.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HASSH @BSides Canberra 2019 - Slides is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Have I Been Squatted

  • Website: https://haveibeensquatted.com
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Have I Been Squatted is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A fast domain typosquatting detection 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 Threat Detection and Hunting > Tools.

Back to Category Index

HeadPrint: Detecting Anomalous Communications through Header-based Application Fingerprinting

  • Website: https://www.conand.me/publications/bortolameotti-headprint-2020.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HeadPrint: Detecting Anomalous Communications through Header-based Application Fingerprinting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

HellsBells, Let's Hunt PowerShells!

  • Website: https://www.splunk.com/blog/2017/07/06/hellsbells-lets-hunt-powershells.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HellsBells, Let's Hunt PowerShells! is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > PowerShell.

Back to Category Index

HTTP Client Fingerprinting Using SSL Handshake Analysis

  • Website: https://www.ssllabs.com/projects/client-fingerprinting/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HTTP Client Fingerprinting Using SSL Handshake Analysis is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: (source 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 Threat Detection and Hunting > Resources > Fingerprinting.

Back to Category Index

HTTPS traffic analysis and client identification using passive SSL/TLS fingerprinting

  • Website: https://link.springer.com/article/10.1186/s13635-016-0030-7
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: HTTPS traffic analysis and client identification using passive SSL/TLS fingerprinting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Hunt-Detect-Prevent

  • Website: https://github.com/MHaggis/hunt-detect-prevent
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Hunt-Detect-Prevent is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Lists of sources and utilities to hunt, detect and prevent evildoers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources.

Back to Category Index

Hunting for PowerShell Using Heatmaps

  • Website: https://medium.com/@jshlbrd/hunting-for-powershell-using-heatmaps-69b70151fa5d
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Hunting for PowerShell Using Heatmaps is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > PowerShell.

Back to Category Index

Hunting the Known Unknowns (with DNS)

  • Website: https://www.splunk.com/pdfs/events/govsummit/hunting_the_known_unknowns_with_DNS.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Hunting the Known Unknowns (with DNS) is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

Hunting the Known Unknowns (With PowerShell)

  • Website: https://conf.splunk.com/files/2016/slides/hunting-the-known-unknowns-the-powershell-edition.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Hunting the Known Unknowns (With PowerShell) is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > PowerShell.

Back to Category Index

Hunting with Sysmon

  • Website: https://medium.com/@haggis_m/hunting-with-sysmon-38de012e62e6
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Hunting with Sysmon is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

Introducing Event Query Language

  • Website: https://www.elastic.co/blog/introducing-event-query-language
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Introducing Event Query Language is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Introducing the Funnel of Fidelity

  • Website: https://posts.specterops.io/introducing-the-funnel-of-fidelity-b1bb59b04036
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Introducing the Funnel of Fidelity is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

Investigating Windows Endpoints

  • Website: https://training.13cubed.com/investigating-windows-endpoints
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Investigating Windows Endpoints is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: by Richard Davis.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Investigation Scenario

  • Website: https://twitter.com/search?q=%23InvestigationPath%20from%3Achrissanders88&f=live
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Investigation Scenario is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: tweets by Chris Sanders.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources.

Back to Category Index

JPCERT - Detecting Lateral Movement through Tracking Event Logs

  • Website: https://blogs.jpcert.or.jp/en/2017/12/research-report-released-detecting-lateral-movement-through-tracking-event-logs-version-2.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: JPCERT - Detecting Lateral Movement through Tracking Event Logs is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows.

Back to Category Index

Lessons Learned in Detection Engineering

  • Website: https://medium.com/starting-up-security/lessons-learned-in-detection-engineering-304aec709856
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Lessons Learned in Detection Engineering is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A well experienced detection engineer describes in detail his observations, challenges, and recommendations for building an effective threat detection 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: Awesome Threat Detection and Hunting > Resources.

Back to Category Index

MaGMa Use Case Defintion Model

  • Website: https://www.betaalvereniging.nl/wp-content/uploads/FI-ISAC-use-case-framework-verkorte-versie.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MaGMa Use Case Defintion Model is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A business-centric approach for planning and defining threat detection use cases.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

Markov Chain Fingerprinting to Classify Encrypted Traffic

  • Website: https://drakkar.imag.fr/IMG/pdf/1569811033.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Markov Chain Fingerprinting to Classify Encrypted Traffic is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

MITRE ATT&CK

  • Website: https://attack.mitre.org/wiki/Main_Page
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MITRE ATT&CK is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A curated knowledge base and model for cyber adversary behavior, reflecting the various phases of an adversary’s lifecycle and the platforms they are known to target.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

MITRE ATT&CK Navigator

  • Website: https://mitre.github.io/attack-navigator/enterprise/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MITRE ATT&CK Navigator is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: () - The ATT&CK Navigator is designed to provide basic navigation and annotation of ATT&CK matrices, something that people are already doing today in tools like Excel.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

MITRE CAR

  • Website: https://car.mitre.org/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MITRE CAR is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Cyber Analytics Repository is a knowledge base of analytics developed by MITRE based on the Adversary Tactics, Techniques, and Common Knowledge (ATT&CK™) adversary model.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Detection Rules.

Back to Category Index

MITRE Engage

  • Website: https://engage.mitre.org/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MITRE Engage is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A framework for planning and discussing adversary engagement operations that empowers you to engage your adversaries and achieve your cybersecurity goals.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

MITRE's Adversary Emulation Plans

  • Website: https://attack.mitre.org/wiki/Adversary_Emulation_Plans
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: MITRE's Adversary Emulation Plans is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Monitoring macOS hosts with osquery

  • Website: https://blog.kolide.com/monitoring-macos-hosts-with-osquery-ba5dcc83122d
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Monitoring macOS hosts with osquery is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Osquery.

Back to Category Index

Mordor

  • Website: https://github.com/Cyb3rWard0g/mordor
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Mordor is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Pre-recorded security events generated by simulated adversarial techniques in the form of JavaScript Object Notation (JSON) files. The data is categorized by platforms, adversary groups, tactics and techniques defined by the Mitre ATT&CK 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 > Dataset.

Back to Category Index

NIST Cybersecurity Framework

  • Website: https://www.nist.gov/cyberframework
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection, Awesome SOC

What it does: NIST Cybersecurity Framework is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Frameworks.

Back to Category Index

NRD-db

  • Website: https://github.com/StrackVibes/NRD-db
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: NRD-db is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Automatically fetches and stores newly registered domains in a Redis 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 Threat Detection and Hunting > Tools.

Back to Category Index

On Botnets that use DNS for Command and Control

  • Website: http://www.few.vu.nl/~herbertb/papers/feederbot_ec2nd11.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: On Botnets that use DNS for Command and Control is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Research Papers.

Back to Category Index

On TTPs

  • Website: http://ryanstillions.blogspot.com.au/2014/04/on-ttps.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: On TTPs is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Open Cybersecurity Schema Framework (OCSF)

  • Website: https://github.com/ocsf/ocsf-schema
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Open Cybersecurity Schema Framework (OCSF) is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A framework for creating schemas and it also delivers a cybersecurity event schema built with the 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 > Resources > Frameworks.

Back to Category Index

osquery Across the Enterprise

  • Website: https://medium.com/@palantir/osquery-across-the-enterprise-3c3c9d13ec55
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: osquery Across the Enterprise is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Osquery.

Back to Category Index

osquery for Security — Part 1

  • Website: https://medium.com/@clong/osquery-for-security-b66fffdf2daf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: osquery for Security — Part 1 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Osquery.

Back to Category Index

osquery for Security — Part 2

  • Website: https://medium.com/@clong/osquery-for-security-part-2-2e03de4d3721
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: osquery for Security — Part 2 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Advanced osquery functionality, File integrity monitoring, process auditing, 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 Threat Detection and Hunting > Resources > Osquery.

Back to Category Index

OSSEM

  • Website: https://github.com/hunters-forge/OSSEM
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: OSSEM is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: (Open Source Security Events Metadata) - A community-led project that focuses on the documentation and standardization of security event logs from diverse data sources and operating 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 Threat Detection and Hunting > Resources > Frameworks.

Back to Category Index

Part 1,

  • Website: https://www.splunk.com/en_us/blog/security/ci-cd-detection-engineering-splunk-security-content-part-1.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Part 1, is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: - A multipart series describing how detection as code can be successfully deployed in a Splunk environment.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources.

Back to Category Index

Part I (Event ID 7)

  • Website: https://cyberwardog.blogspot.com.au/2017/03/chronicles-of-threat-hunter-hunting-for.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Part I (Event ID 7) is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

Part II (Event ID 10)

  • Website: https://cyberwardog.blogspot.com.au/2017/03/chronicles-of-threat-hunter-hunting-for_22.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Part II (Event ID 10) is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

  • Website: https://isc.sans.edu/forums/diary/Proactive+Malicious+Domain+Search/23065/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Proactive Malicious Domain Search is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

ProcMon for Linux

  • Website: https://github.com/Sysinternals/ProcMon-for-Linux
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: ProcMon for Linux is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Tools.

Back to Category Index

Random Words on Entropy and DNS

  • Website: https://www.splunk.com/blog/2015/10/01/random-words-on-entropy-and-dns.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Random Words on Entropy and DNS is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

RDP Fingerprinting - Profiling RDP Clients with JA3 and RDFP

  • Website: https://medium.com/@0x4d31/rdp-client-fingerprinting-9e7ac219f7f4
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: RDP Fingerprinting - Profiling RDP Clients with JA3 and RDFP is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Revoke-Obfuscation

  • Website: https://github.com/danielbohannon/Revoke-Obfuscation
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Revoke-Obfuscation is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: PowerShell Obfuscation Detection 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 > Tools.

Back to Category Index

Risky Business

  • Website: https://risky.biz
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Risky Business is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: by Patrick Gray.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Podcasts.

Back to Category Index

SecRepo.com

  • Website: https://www.secrepo.com
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: SecRepo.com is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: () - Samples of security related data.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Dataset.

Back to Category Index

Signal the ATT&CK: Part 1

  • Website: https://www.pwc.co.uk/issues/cyber-security-data-privacy/research/signal-att-and-ck-part-1.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Signal the ATT&CK: Part 1 is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Building a real-time threat detection capability with Tanium that focuses on documented adversarial techniques.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Slides

  • Website: https://www.sans.org/cyber-security-summit/archives/file/summit-archive-1492182404.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Slides is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

Splunk Boss of the SOC

  • Website: https://bots.splunk.com/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Splunk Boss of the SOC is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Hands-on workshops and challenges to practice threat hunting using the BOTS and other datasets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Labs.

Back to Category Index

Splunk Detections

  • Website: https://research.splunk.com/detections/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Splunk Detections is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Detection Rules.

Back to Category Index

Splunk Security Content

  • Website: https://github.com/splunk/security_content
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Splunk Security Content is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: Splunk-curated detection content that can easily be used accross many SIEMs (see Uncoder Rule Converter.).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Splunkmon — Taking Sysmon to the Next Level

  • Website: https://www.crypsisgroup.com/wp-content/uploads/2017/07/CG_WhitePaper_Splunkmon_1216-1.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Splunkmon — Taking Sysmon to the Next Level is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

Suspicious Domains Tracking Dashboard

  • Website: https://isc.sans.edu/forums/diary/Suspicious+Domains+Tracking+Dashboard/23046/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Suspicious Domains Tracking Dashboard is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

Syscall Auditing at Scale

  • Website: https://slack.engineering/syscall-auditing-at-scale-e6a3ca8ac1b8
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Syscall Auditing at Scale is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Sysmon Threat Detection Guide

  • Website: https://www.varonis.com/blog/sysmon-threat-detection-guide/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Sysmon Threat Detection Guide is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources > Windows > Sysmon.

Back to Category Index

The Diamond Model of Intrusion Analysis

  • Website: http://www.activeresponse.org/wp-content/uploads/2013/07/diamond.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The Diamond Model of Intrusion Analysis is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Research Papers.

Back to Category Index

The DML Model

  • Website: http://ryanstillions.blogspot.com.au/2014/04/the-dml-model_21.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The DML Model is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The Detection Maturity Level (DML) model is a capability maturity model for referencing ones maturity in detecting cyber 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 Threat Detection and Hunting > Resources > Frameworks.

Back to Category Index

The No Hassle Guide to Event Query Language (EQL) for Threat Hunting

  • Website: https://www.varonis.com/blog/guide-no-hassle-eql-threat-hunting/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The No Hassle Guide to Event Query Language (EQL) for Threat Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Threat Detection and Hunting > Resources.

Back to Category Index

The osquery Extensions Skunkworks Project

  • Website: https://github.com/trailofbits/presentations/tree/master/Osquery%20Extensions
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The osquery Extensions Skunkworks Project is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Osquery.

Back to Category Index

The PARIS Model

  • Website: http://threathunter.guru/blog/the-paris-model/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The PARIS Model is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A model for threat hunting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

The Pyramic of Pain

  • Website: http://detect-respond.blogspot.com.au/2013/03/the-pyramid-of-pain.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The Pyramic of Pain is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The relationship between the types of indicators you might use to detect an adversary's activities and how much pain it will cause them when you are able to deny those indicators to them.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Frameworks.

Back to Category Index

The Sysmon and Threat Hunting Mimikatz wiki for the blue team

  • Website: https://www.peerlyst.com/posts/the-sysmon-and-threat-hunting-mimikatz-wiki-for-the-blue-team-guurhart
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The Sysmon and Threat Hunting Mimikatz wiki for the blue team is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

The ThreatHunting Project

  • Website: https://github.com/ThreatHuntingProject/ThreatHunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The ThreatHunting Project is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A great and threat hunting 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 > Resources.

Back to Category Index

The use of TLS in Censorship Circumvention

  • Website: https://tlsfingerprint.io/static/frolov2019.pdf
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: The use of TLS in Censorship Circumvention is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Threat Hunting

  • Website: https://posts.specterops.io/tagged/threat-hunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Threat Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 Category Index

Threat Hunting with Sysmon: Word Document with Macro

  • Website: http://www.syspanda.com/index.php/2017/10/10/threat-hunting-sysmon-word-document-macro/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Threat Hunting with Sysmon: Word Document with Macro is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows > Sysmon.

Back to Category Index

ThreatHunting

  • Website: https://github.com/olafhartong/ThreatHunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: ThreatHunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A Splunk app mapped to MITRE ATT&CK to guide your threat hunts.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

TLS fingerprinting - Smarter Defending & Stealthier Attacking

  • Website: https://blog.squarelemon.com/tls-fingerprinting/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: TLS fingerprinting - Smarter Defending & Stealthier Attacking is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

TLS Fingerprinting in the Real World

  • Website: https://blogs.cisco.com/security/tls-fingerprinting-in-the-real-world
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: TLS Fingerprinting in the Real World is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

TLS Fingerprinting with JA3 and JA3S

  • Website: https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247362855967
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: TLS Fingerprinting with JA3 and JA3S is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Fingerprinting.

Back to Category Index

Tool Analysis Result Sheet

  • Website: https://jpcertcc.github.io/ToolAnalysisResultSheet/
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Tool Analysis Result Sheet is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows.

Back to Category Index

Tracking Newly Registered Domains

  • Website: https://isc.sans.edu/diary/Tracking+Newly+Registered+Domains/23127
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Tracking Newly Registered Domains is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > DNS.

Back to Category Index

Windows Commands Abused by Attackers

  • Website: http://blog.jpcert.or.jp/.s/2016/01/windows-commands-abused-by-attackers.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Windows Commands Abused by Attackers is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources.

Back to Category Index

Windows Commands Abused by Attackers

  • Website: https://blogs.jpcert.or.jp/en/2016/01/windows-commands-abused-by-attackers.html
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Windows Commands Abused by Attackers is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. 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 > Resources > Windows.

Back to Category Index

Windows Hunting

  • Website: https://github.com/beahunt3r/Windows-Hunting
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: Windows Hunting is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: A collection of Windows hunting queries.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Resources > Windows.

Back to Category Index

YARA

  • Website: https://github.com/virustotal/yara
  • Model: Open Source
  • Category: Threat Detection
  • Source Lists: Awesome Threat Detection

What it does: YARA is used in threat detection programs to support baseline hardening, monitoring integration, and defense-in-depth validation. Source summaries describe it as: The pattern matching swiss knife.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

Threat Intelligence

This category contains 110 documented tools. It focuses on capabilities used for indicator ingestion, adversary tracking, and context enrichment of detections. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Abuse.ch

  • Website: https://abuse.ch
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools

What it does: Abuse.ch is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Provides threat feeds such as ransomware and malware campaign trackers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Threat Intelligence.

Back to Category Index

ExifTool

  • Website: https://exiftool.org
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools, Awesome Forensics

What it does: ExifTool is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Reads, writes, and edits meta information in 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: Malware Analysis > Static Analysis > IOC and Pattern Identification.

Back to Category Index

OpenCTI

  • Website: https://www.opencti.io
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools

What it does: OpenCTI is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Open-source platform for managing cyber threat intelligence knowledge and observables.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Threat Intelligence.

Back to Category Index

Recorded Future

  • Website: https://www.recordedfuture.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools

What it does: Recorded Future is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Commercial threat intelligence platform providing real-time threat analysis and risk scoring.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Threat Intelligence.

Back to Category Index

ThreatConnect

  • Website: https://threatconnect.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools

What it does: ThreatConnect is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Threat intelligence platform combining data aggregation, analytics, and response workflows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Threat Intelligence.

Back to Category Index

zipdump

  • Website: https://github.com/nlitsme/zipdump
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cyber Security Tools

What it does: zipdump is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Analyzes zip files and runs YARA rules.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > IOC and Pattern Identification.

Back to Category Index

abuse.ch

  • Website: https://www.abuse.ch/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: abuse.ch is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: ZeuS Tracker / SpyEye Tracker / Palevo Tracker / Feodo Tracker tracks Command&Control servers (hosts) around the world and provides you a domain- and an IP-blocklist.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

AbuseHelper

  • Website: https://github.com/abusesa/abusehelper
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: AbuseHelper is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: An open-source.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

AlienVault Open Threat Exchange

  • Website: http://www.alienvault.com/open-threat-exchange/dashboard
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: AlienVault Open Threat Exchange is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: AlienVault Open Threat Exchange (OTX), to help you secure your networks from data loss, service disruption and system compromise caused by malicious IP addresses.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

AlienVault Open Threat Exchange

  • Website: https://otx.alienvault.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome OSINT, Awesome Cyber Security Tools

What it does: AlienVault Open Threat Exchange is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Open Threat Exchange is the neighborhood watch of the global intelligence community. It enables private companies, independent security researchers, and government agencies to openly collaborate and share the latest information about emerging threats, attack methods, and malicious actors, promoting greater security across the entire 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: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

AttackerKB

  • Website: https://attackerkb.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: AttackerKB is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free and public crowdsourced vulnerability assessment platform to help prioritize high-risk patch application and combat vulnerability fatigue.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

AutoShun

  • Website: https://www.autoshun.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: AutoShun is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: AutoShun is a Snort plugin that allows you to send your Snort IDS logs to a centralized server that will correlate attacks from your sensor logs with other snort sensors, honeypots, and mail filters from around the world.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Bambenek Consulting Feeds

  • Website: http://osint.bambenekconsulting.com/feeds/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Bambenek Consulting Feeds is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

CAPEC - Common Attack Pattern Enumeration and Classification

  • Website: http://capec.mitre.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: CAPEC - Common Attack Pattern Enumeration and Classification is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

CI Army

  • Website: http://cinsscore.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: CI Army is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Combine

  • Website: https://github.com/mlsecproject/combine
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: Combine is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Gather and combine multiple threat intelligence feed sources into one customizable, standardized CSV-based format.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

Criminal IP

  • Website: https://www.criminalip.io/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: Criminal IP is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Cyber Threat Intelligence Search Engine and Attack Surface Management(ASM) 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: Awesome OSINT > ↑ Speciality Search Engines.

Back to Category Index

Critical Stack- Free Intel Market

  • Website: https://intel.criticalstack.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Critical Stack- Free Intel Market is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Crypto Scam & Crypto Phishing URL Threat Intel Feed

  • Website: https://github.com/spmedia/Crypto-Scam-and-Crypto-Phishing-Threat-Intel-Feed
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: Crypto Scam & Crypto Phishing URL Threat Intel Feed is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A fresh feed of crypto phishing and crypto scam websites. Automatically updated daily.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Cybercrime tracker

  • Website: http://cybercrime-tracker.net/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Cybercrime tracker is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Multiple botnet active tracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

CyberGordon

  • Website: https://cybergordon.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: CyberGordon is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: CyberGordon is a threat intelligence search engine. It leverages 30+ sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

Cyberowl

  • Website: https://github.com/karimhabush/cyberowl
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Cyberowl is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A daily updated summary of the most frequent types of security incidents currently being reported from different sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

CybOX - Cyber Observables eXpression

  • Website: http://cyboxproject.github.io
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: CybOX - Cyber Observables eXpression is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Cymon

  • Website: https://cymon.io/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Cymon is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Threat intelligence tracker, with IP/domain/hash.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

Cyware Threat Intelligence Feeds

  • Website: https://cyware.com/community/ctix-feeds
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Cyware Threat Intelligence Feeds is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Cyware’s Threat Intelligence feeds brings to you the valuable threat data from a wide range of open and trusted sources to deliver a consolidated stream of valuable and actionable threat intelligence. Our threat intel feeds are fully compatible with STIX 1.x and 2.0, giving you the latest information on malicious malware hashes, IPs and domains uncovered across the globe in real-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 Security > Threat Intelligence.

Back to Category Index

DNS-BH

  • Website: http://www.malwaredomains.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: DNS-BH is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: The DNS-BH project creates and maintains a listing of domains that are known to be used to propagate malware and spyware. This project creates the Bind and Windows zone files required to serve fake replies to localhost for any requests to these, thus preventing many spyware installs and reporting.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

Emerging Threats - Open Source

  • Website: http://doc.emergingthreats.net/bin/view/Main/EmergingFAQ
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Emerging Threats - Open Source is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Emerging Threats began 10 years ago as an open source community for collecting Suricata and SNORT® rules, firewall rules, and other IDS rulesets. The open source community still plays an active role in Internet security, with more than 200,000 active users downloading the ruleset daily. The ETOpen Ruleset is open to any user or organization, as long as you follow some basic guidelines. Our ETOpen Ruleset is available for download any 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 Security > Threat Intelligence.

Back to Category Index

ESET's Malware IoCs

  • Website: https://github.com/eset/malware-ioc
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: ESET's Malware IoCs is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Indicators of Compromises (IOCs) derived from ESET's various investigations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence > Threat signature packages and collections.

Back to Category Index

Fidelis Barncat

  • Website: https://www.fidelissecurity.com/resources/fidelis-barncat
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Fidelis Barncat is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Fileintel

  • Website: https://github.com/keithjjones/fileintel
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: Fileintel is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Pull intelligence per file hash.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

FireEye OpenIOCs

  • Website: https://github.com/fireeye/iocs
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security, Awesome Malware Analysis

What it does: FireEye OpenIOCs is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: FireEye Publicly Shared Indicators of Compromise (IOCs).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

FireEye's Red Team Tool Countermeasures

  • Website: https://github.com/fireeye/red_team_tool_countermeasures
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: FireEye's Red Team Tool Countermeasures is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Collection of Snort and YARA rules to detect attacks carried out with FireEye's own Red Team tools, first released after FireEye disclosed a breach in December 2020.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence > Threat signature packages and collections.

Back to Category Index

FireEye's Sunburst Countermeasures

  • Website: https://github.com/fireeye/sunburst_countermeasures
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: FireEye's Sunburst Countermeasures is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Collection of IoC in various languages for detecting backdoored SolarWinds Orion NMS activities and related vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence > Threat signature packages and collections.

Back to Category Index

FireHOL IP Lists

  • Website: https://iplists.firehol.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: FireHOL IP Lists is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Analytics for 350+ IP lists.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Focsec

  • Website: https://focsec.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: Focsec is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Threat Intelligence API that detects if a IP address is associated with a VPN, Proxy, TOR or Bots.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

Forager

  • Website: https://github.com/opensourcesec/Forager
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Forager is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Multi-threaded threat intelligence gathering built with Python3 featuring simple text-based configuration and data storage for ease of use and data portability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

GitGuardian - Public GitHub Monitoring

  • Website: https://www.gitguardian.com/monitor-public-github-for-secrets
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: GitGuardian - Public GitHub Monitoring is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Monitor public GitHub repositories in real time. Detect secrets and sensitive information to prevent hackers from using GitHub as a backdoor to your business.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

GRASSMARLIN

  • Website: https://github.com/nsacyber/GRASSMARLIN
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: GRASSMARLIN is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Provides IP network situational awareness of industrial control systems (ICS) and Supervisory Control and Data Acquisition (SCADA) by passively mapping, accounting for, and reporting on your ICS/SCADA network topology and endpoints.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

Greynoise

  • Website: https://greynoise.io/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: Greynoise is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: "Anti-Threat Intelligence" Greynoise characterizes the background noise of the internet, so the user can focus on what is actually important.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Other Tools.

Back to Category Index

HASSH

  • Website: https://github.com/salesforce/hassh
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: HASSH is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Network fingerprinting standard which can be used to identify specific client and server SSH implementations.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > Network Monitoring > Fingerprinting Tools.

Back to Category Index

HoneyDB

  • Website: https://riskdiscovery.com/honeydb
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: HoneyDB is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Community driven honeypot sensor data collection and aggregation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Hostintel

  • Website: https://github.com/keithjjones/hostintel
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Incident Response

What it does: Hostintel is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Pull intelligence per host.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

hpfeeds

  • Website: https://github.com/rep/hpfeeds
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Honeypots

What it does: hpfeeds is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Lightweight authenticated publish-subscribe protocol.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Infosec - CERT-PA lists

  • Website: https://infosec.cert-pa.it/analyze/statistics.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Infosec - CERT-PA lists is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: ( - - ) - Blocklist service.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

InQuest REPdb

  • Website: https://labs.inquest.net/repdb
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: InQuest REPdb is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Continuous aggregation of IOCs from a variety of open reputation sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Intel Owl

  • Website: https://github.com/intelowlproject/IntelOwl
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Threat Detection

What it does: Intel Owl is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: An Open Source Intelligence, or OSINT solution to get threat intelligence data about a specific file, an IP or a domain from a single API at scale.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

IntelMQ

  • Website: https://www.enisa.europa.eu/topics/csirt-cert-services/community-projects/incident-handling-automation
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: IntelMQ is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

Internet Storm Center

  • Website: https://www.dshield.org/reports.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Internet Storm Center is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: The ISC was created in 2001 following the successful detection, analysis, and widespread warning of the Li0n worm. Today, the ISC provides a free analysis and warning service to thousands of Internet users and organizations, and is actively working with Internet Service Providers to fight back against the most malicious attackers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

Internet Storm Center (DShield)

  • Website: https://isc.sans.edu/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome SOC

What it does: Internet Storm Center (DShield) is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Diary and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

IOC Editor

  • Website: https://www.fireeye.com/services/freeware/ioc-editor.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: IOC Editor is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

ioc_writer

  • Website: https://github.com/mandiant/ioc_writer
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ioc_writer is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Python library for.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

iocextract

  • Website: https://github.com/InQuest/python-iocextract
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: iocextract is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Advanced Indicator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

isMalicious

  • Website: https://ismalicious.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: isMalicious is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Threat intelligence platform aggregating malicious IP and domain data from multiple security feeds with real-time reputation scoring and threat categorization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Domain and IP Research.

Back to Category Index

JA3

  • Website: https://ja3er.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: JA3 is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Extracts SSL/TLS handshake settings for fingerprinting and communicating about a given TLS implementation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence > Fingerprinting.

Back to Category Index

MAEC - Malware Attribute Enumeration and Characterization

  • Website: http://maec.mitre.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: MAEC - Malware Attribute Enumeration and Characterization is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

malc0de

  • Website: http://malc0de.com/database/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: malc0de is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Searchable incident 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

MalPipe

  • Website: https://github.com/silascutler/MalPipe
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: MalPipe is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Malware/IOC ingestion and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

Malware Analysis, Threat Intelligence and Reverse Engineering

  • Website: https://www.slideshare.net/bartblaze/malware-analysis-threat-intelligence-and-reverse-engineering
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Malware Analysis, Threat Intelligence and Reverse Engineering is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 > Other.

Back to Category Index

Malware Domain List

  • Website: http://www.malwaredomainlist.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Malware Domain List is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Search and share.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Malware Information Sharing Platform and Threat Sharing (MISP)

  • Website: https://misp-project.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Malware Information Sharing Platform and Threat Sharing (MISP) is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Open source software solution for collecting, storing, distributing and sharing cyber security indicators.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

MetaDefender Threat Intelligence Feed

  • Website: https://www.opswat.com/developers/threat-intelligence-feed
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: MetaDefender Threat Intelligence Feed is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

MISP

  • Website: https://github.com/MISP/MISP
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: MISP is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Malware Information Sharing.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

MISP - Open Source Threat Intelligence Platform

  • Website: https://www.misp-project.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security, Awesome Cyber Security Tools

What it does: MISP - Open Source Threat Intelligence Platform is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: MISP threat sharing platform is a free and open source software helping information sharing of threat intelligence including cyber security indicators. A threat intelligence platform for gathering, sharing, storing and correlating Indicators of Compromise of targeted attacks, threat intelligence, financial fraud information, vulnerability information or even counter-terrorism information. The MISP project includes software, common libraries (, ), an extensive data model to share new information using and default .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

NSFOCUS

  • Website: https://nti.nsfocus.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Web Security

What it does: NSFOCUS is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: THREAT INTELLIGENCE PORTAL by NSFOCUS GLOBAL.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

onion-lookup

  • Website: https://onion.ail-project.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: onion-lookup is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free online service and API for checking the existence of Tor hidden services (.onion address) and retrieving their associated metadata. onion-lookup relies on an private AIL instance to obtain the metadata.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

OnionScan

  • Website: https://github.com/s-rah/onionscan
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: OnionScan is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free and open source tool for investigating the Dark Web. Its main goal is to help researchers and investigators monitor and track Dark Web sites.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

Open Source Vulnerabilities (OSV)

  • Website: https://osv.dev/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Penetration Testing

What it does: Open Source Vulnerabilities (OSV) is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Vulnerability database and triage infrastructure for open source projects aimed at helping both open source maintainers and consumers of open source.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

OpenIOC

  • Website: https://www.fireeye.com/services/freeware.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: OpenIOC is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Framework for sharing threat intelligence.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

OpenVAS NVT Feed

  • Website: http://www.openvas.org/openvas-nvt-feed.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: OpenVAS NVT Feed is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: The public feed of Network Vulnerability Tests (NVTs). It contains more than 35,000 NVTs (as of April 2014), growing on a daily basis. This feed is configured as the default for OpenVAS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

PhishingSecLists

  • Website: https://github.com/spmedia/PhishingSecLists
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: PhishingSecLists is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: This list is to be used with web scanning tools (Gobuster, ffuf, Burp Suite, DirBuster). These lists are specifically tailored and designed for fuzzing phishing, crypto scam landing pages, and other malicious sketch af websites. You can gain vaulable intel on successful hits.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

PhishStats

  • Website: https://phishstats.info/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome OSINT

What it does: PhishStats is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Phishing Statistics with search for IP, domain and website title.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Domain Analysis.

Back to Category Index

PhishTank

  • Website: http://www.phishtank.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: PhishTank is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: PhishTank is a collaborative clearing house for data and information about phishing on the Internet. Also, PhishTank provides an open API for developers and researchers to integrate anti-phishing data into their applications at no charge.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

Project Honey Pot

  • Website: http://www.projecthoneypot.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Project Honey Pot is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Project Honey Pot is the first and only distributed system for identifying spammers and the spambots they use to scrape addresses from your website. Using the Project Honey Pot system you can install addresses that are custom-tagged to the time and IP address of a visitor to your site. If one of these addresses begins receiving email we not only can tell that the messages are spam, but also the exact moment when the address was harvested and the IP address that gathered it.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

Proofpoint Threat Intelligence

  • Website: https://www.proofpoint.com/us/products/et-intelligence
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Proofpoint Threat Intelligence is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Pulsedive

  • Website: https://pulsedive.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome OSINT

What it does: Pulsedive is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free, community-driven threat intelligence platform collecting IOCs from open-source feeds.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

PyIOCe

  • Website: https://github.com/pidydx/PyIOCe
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: PyIOCe is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A Python OpenIOC 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 Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

Ransomware overview

  • Website: https://docs.google.com/spreadsheets/d/1TWS238xacAto-fLKh1n5uTsdijWdCEsGIM0Y0Hvmc5g/pubhtml
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Ransomware overview is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Redline

  • Website: https://fireeye.market/apps/211364
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Forensics

What it does: Redline is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free endpoint security tool from FireEye.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > IOC Scanner.

Back to Category Index

REScure Threat Intel Feed

  • Website: https://rescure.fruxlabs.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: REScure Threat Intel Feed is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: REScure is an independent threat intelligence project which we undertook to enhance our understanding of distributed systems, their integration, the nature of threat intelligence and how to efficiently collect, store, consume, distribute it.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

RiskIQ

  • Website: https://community.riskiq.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: RiskIQ is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Research, connect, tag and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

SBL / XBL / PBL / DBL / DROP / ROKSO

  • Website: http://www.spamhaus.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: SBL / XBL / PBL / DBL / DROP / ROKSO is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: The Spamhaus Project is an international nonprofit organization whose mission is to track the Internet's spam operations and sources, to provide dependable realtime anti-spam protection for Internet networks, to work with Law Enforcement Agencies to identify and pursue spam and malware gangs worldwide, and to lobby governments for effective anti-spam legislation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

STIX - Structured Threat Information eXpression

  • Website: http://stixproject.github.io
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: STIX - Structured Threat Information eXpression is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

SystemLookup

  • Website: https://www.systemlookup.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: SystemLookup is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: SystemLookup hosts a collection of lists that provide information on.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

TAXII - Trusted Automated eXchange of Indicator Information

  • Website: http://taxiiproject.github.io
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: TAXII - Trusted Automated eXchange of Indicator Information is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

The Coventry Conundrum of Threat Intelligence

  • Website: https://summitroute.com/blog/2015/06/10/the_conventry_conundrum_of_threat_intelligence/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Threat Detection

What it does: The Coventry Conundrum of Threat Intelligence is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 > Resources.

Back to Category Index

THOR Lite

  • Website: https://www.nextron-systems.com/thor-lite/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Forensics

What it does: THOR Lite is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Free IOC and YARA Scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > IOC Scanner.

Back to Category Index

Threat Actor Usernames Scrape

  • Website: https://github.com/spmedia/Threat-Actor-Usernames-Scrape
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: Threat Actor Usernames Scrape is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A collection of fresh intel and 350k+ threat actor usernames scraped from various cybercrime sources & forums.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Threat Intelligence.

Back to Category Index

Threat Bus

  • Website: https://github.com/tenzir/threatbus
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Threat Detection

What it does: Threat Bus is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Threat intelligence dissemination layer to connect security tools through a distributed publish/subscribe message broker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence.

Back to Category Index

Threat Intelligence

  • Website: https://github.com/hslatman/awesome-threat-intelligence
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: Threat Intelligence is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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: Related Awesome Lists.

Back to Category Index

Threat intelligence

  • Website: https://github.com/cyb3rxp/awesome-soc/blob/main/threat_intelligence.md
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome SOC

What it does: Threat intelligence is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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: Mission-critical means (tools/sensors) > Critical tools for a SOC/CSIRT.

Back to Category Index

Threat Jammer

  • Website: https://threatjammer.com
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Threat Jammer is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: REST API service that allows developers, security engineers, and other IT professionals to access curated threat intelligence data from a variety of sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

threataggregator

  • Website: https://github.com/jpsenior/threataggregator
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: threataggregator is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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 Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

ThreatConnect

  • Website: https://threatconnect.com/free/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ThreatConnect is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: TC Open allows you to see and.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

ThreatCrowd

  • Website: https://www.threatcrowd.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Penetration Testing

What it does: ThreatCrowd is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A search engine for threats,.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Data Broker and Search Engine Services.

Back to Category Index

ThreatIngestor

  • Website: https://github.com/InQuest/ThreatIngestor/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team

What it does: ThreatIngestor is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Extendable tool to extract and aggregate IOCs from threat feeds including Twitter, RSS feeds, or other sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

ThreatMiner

  • Website: https://www.threatminer.org/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ThreatMiner is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Data mining portal for threat.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

threatRECON

  • Website: https://threatrecon.co/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: threatRECON is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Search for indicators, up to 1000.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

ThreatShare

  • Website: https://threatshare.io/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ThreatShare is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: C2 panel tracker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

ThreatTracker

  • Website: https://github.com/michael-yip/ThreatTracker
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ThreatTracker is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: A 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 Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

TIQ-test

  • Website: https://github.com/mlsecproject/tiq-test
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: TIQ-test is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Data visualization.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Tools.

Back to Category Index

Tor Bulk Exit List

  • Website: https://metrics.torproject.org/collector.html
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Tor Bulk Exit List is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: CollecTor, your friendly data-collecting service in the Tor network. CollecTor fetches data from various nodes and services in the public Tor network and makes it available to the world. If you're doing research on the Tor network, or if you're developing an application that uses Tor network data, this is your place to start. / /.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat Intelligence.

Back to Category Index

Trust Scan

  • Website: https://github.com/undeadlist/trust-scan
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security

What it does: Trust Scan is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: URL security scanner with WHOIS, SSL, threat intelligence (URLhaus, PhishTank, Spamhaus), and 40+ scam/phishing pattern detection. Includes optional AI analysis via Ollama. ().

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Unfetter

  • Website: https://nsacyber.github.io/unfetter/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: Unfetter is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Identifies defensive gaps in security posture by leveraging Mitre's ATT&CK 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 Cybersecurity Blue Team > Threat intelligence.

Back to Category Index

virustotal

  • Website: https://www.virustotal.com/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Security, Awesome Malware Analysis, Awesome Incident Response, Awesome Honeypots, Awesome Penetration Testing, Awesome OSINT, Awesome Cyber Security Tools

What it does: virustotal is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: VirusTotal, a subsidiary of Google, is a free online service that analyzes files and URLs enabling the identification of viruses, worms, trojans and other kinds of malicious content detected by antivirus engines and website scanners. At the same time, it may be used as a means to detect false positives, i.e. innocuous resources detected as malicious by one or more scanners.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Open Sources Intelligence (OSINT) > Data Broker and Search Engine Services.

Back to Category Index

Visual Threat Intelligence

  • Website: https://www.amazon.fr/Visual-Threat-Intelligence-Illustrated-Researchers/dp/B0C7JCF8XD
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome SOC

What it does: Visual Threat Intelligence is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. 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: Must read > Globally (SOC and CERT/CSIRT).

Back to Category Index

YARA

  • Website: https://github.com/VirusTotal/yara
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Cybersecurity Blue Team, Awesome Cyber Security Tools

What it does: YARA is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Tool aimed at (but not limited to) helping malware researchers to identify and classify malware samples, described as "the pattern matching swiss army knife" for file patterns and signatures.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Malware Analysis > Static Analysis > IOC and Pattern Identification.

Back to Category Index

Yara rules

  • Website: https://github.com/Yara-Rules/rules
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis, Awesome Cybersecurity Blue Team, Awesome SOC

What it does: Yara rules is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Project covering the need for IT security researchers to have a single repository where different Yara signatures are compiled, classified and kept as up to date as possible.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Threat intelligence > Threat signature packages and collections.

Back to Category Index

YARAif

  • Website: https://yaraify.abuse.ch/scan/
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome OSINT

What it does: YARAif is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Collaborative YARA engine providing open threat intelligence through file pattern matching.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > ↑ Speciality Search Engines.

Back to Category Index

YETI

  • Website: https://github.com/yeti-platform/yeti
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: YETI is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: Yeti is a platform meant to organize observables, indicators of compromise, TTPs, and knowledge on threats in a single, unified repository.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

ZeuS Tracker

  • Website: https://zeustracker.abuse.ch/blocklist.php
  • Model: Open Source
  • Category: Threat Intelligence
  • Source Lists: Awesome Malware Analysis

What it does: ZeuS Tracker is used in threat intelligence programs to support indicator ingestion, adversary tracking, and context enrichment of detections. Source summaries describe it as: ZeuS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Awesome Malware Analysis > Open Source Threat Intelligence > Other Resources.

Back to Category Index

Vulnerability Management

This category contains 78 documented tools. It focuses on capabilities used for risk-based vulnerability prioritization and remediation planning. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

Nessus

  • Website: https://www.tenable.com/products/nessus/nessus-professional
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Cyber Security Tools

What it does: Nessus is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Vulnerability scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

A2SV

  • Website: https://github.com/hahwul/a2sv
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: A2SV is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Auto Scanning to SSL Vulnerability 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 > Auditing.

Back to Category Index

Agentic Radar

  • Website: https://github.com/splx-ai/agentic-radar
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Agentic Radar is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Open-source CLI security scanner for agentic AI workflows.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Artemis

  • Website: https://github.com/CERT-Polska/Artemis/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security

What it does: Artemis is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: A modular vulnerability scanner with automatic report generation 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 Security > Web > Scanning / Pentesting.

Back to Category Index

Attacking JavaScript Engines - A case study of JavaScriptCore and CVE-2016-4622

  • Website: http://www.phrack.org/papers/attacking_javascript_engines.html
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Attacking JavaScript Engines - A case study of JavaScriptCore and CVE-2016-4622 is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

AutoSploit

  • Website: https://github.com/NullArray/AutoSploit
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: AutoSploit is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Automated mass exploiter, which collects target by employing the Shodan.io API and programmatically chooses Metasploit exploit modules based on the Shodan query.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Bash Bunny

  • Website: https://www.hak5.org/gear/bash-bunny
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Bash Bunny is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Local exploit delivery tool in the form of a USB thumbdrive in which you write payloads in a DSL called BunnyScript.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Brakeman

  • Website: https://github.com/presidentbeef/brakeman
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Brakeman is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Static analysis security vulnerability scanner for Ruby on Rails 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 > Static Analyzers.

Back to Category Index

BRETT BUERHAUS

  • Website: https://buer.haus/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: BRETT BUERHAUS is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Vulnerability disclosures and rambles on application 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 Web Security > Blogs.

Back to Category Index

Bugtraq (BID)

  • Website: http://www.securityfocus.com/bid/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Bugtraq (BID) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Software security bug identification database compiled from submissions to the SecurityFocus mailing list and other sources, operated by Symantec, Inc.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

China National Vulnerability Database (CNNVD)

  • Website: http://www.cnnvd.org.cn/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: China National Vulnerability Database (CNNVD) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Chinese government-run vulnerability database analoguous to the United States's CVE database hosted by Mitre Corporation.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

CISA Known Vulnerabilities Database (KEV)

  • Website: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing, Awesome SOC

What it does: CISA Known Vulnerabilities Database (KEV) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Vulnerabilities in various systems already known to America's cyber defense agency, the Cybersecurity and Infrastructure Security Agency, to be actively exploited.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Cloud Security Risks (Part 1): Azure CSV Injection Vulnerability

  • Website: https://rhinosecuritylabs.com/azure/cloud-security-risks-part-1-azure-csv-injection-vulnerability/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Cloud Security Risks (Part 1): Azure CSV Injection Vulnerability is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Azure.

Back to Category Index

Common Vulnerabilities and Exposures (CVE)

  • Website: https://cve.mitre.org/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Common Vulnerabilities and Exposures (CVE) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Dictionary of common names (i.e., CVE Identifiers) for publicly known security vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

CSP Scanner

  • Website: https://cspscanner.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Hacking

What it does: CSP Scanner is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Analyze a site's Content-Security-Policy (CSP) to find bypasses and missing directives.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Web > Tools.

Back to Category Index

CVE-2017-2446 or JSC::JSGlobalObject::isHavingABadTime.

  • Website: https://doar-e.github.io/blog/2018/07/14/cve-2017-2446-or-jscjsglobalobjectishavingabadtime/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: CVE-2017-2446 or JSC::JSGlobalObject::isHavingABadTime. is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

CVE-2019-1306: ARE YOU MY INDEX?

  • Website: https://www.thezdi.com/blog/2019/10/23/cve-2019-1306-are-you-my-index
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: CVE-2019-1306: ARE YOU MY INDEX? is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Remote Code Execution.

Back to Category Index

cve-ape

  • Website: https://github.com/baalmor/cve-ape
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security

What it does: cve-ape is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: A non-intrusive CVE scanner for embedding in test and CI environments that can scan package lists and individual packages for existing CVEs via locally stored CVE database. Can also be used as an offline CVE scanner for e.g. OT/ICS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > DevOps.

Back to Category Index

CXSecurity

  • Website: https://cxsecurity.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: CXSecurity is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Archive of published CVE and Bugtraq software vulnerabilities cross-referenced with a Google dork database for discovering the listed vulnerability.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

DefectDojo

  • Website: https://www.defectdojo.org/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: DefectDojo is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Application vulnerability management tool built for DevOps and continuous security integration.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

dirsearch

  • Website: https://github.com/maurosoria/dirsearch
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: dirsearch is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Web path scanner.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Exploit Exercises

  • Website: https://exploit-exercises.lains.space/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome CTF

What it does: Exploit Exercises is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Variety of VMs to learn variety of computer security issues.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Exploit Exercises - Nebula

  • Website: https://exploit-exercises.com/nebula/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Hacking

What it does: Exploit Exercises - Nebula is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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: Wargame > System.

Back to Category Index

Exploit.Education

  • Website: http://exploit.education
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome CTF

What it does: Exploit.Education is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Variety of VMs to learn variety of computer security issues.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, 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 Category Index

Exploiting prototype pollution – RCE in Kibana (CVE-2019-7609)

  • Website: https://research.securitum.com/prototype-pollution-rce-kibana-cve-2019-7609/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Exploiting prototype pollution – RCE in Kibana (CVE-2019-7609) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Prototype Pollution.

Back to Category Index

EXPOSURE: Finding Malicious Domains Using Passive DNS Analysis

  • Website: https://www.cs.ucsb.edu/~chris/research/doc/ndss11_exposure.pdf
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Threat Detection

What it does: EXPOSURE: Finding Malicious Domains Using Passive DNS Analysis is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Resources > Research Papers.

Back to Category Index

fimap

  • Website: https://github.com/kurobeats/fimap
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: fimap is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Find, prepare, audit, exploit and even Google automatically for LFI/RFI 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 > Web Exploitation > Web file inclusion tools.

Back to Category Index

Full-Disclosure

  • Website: http://seclists.org/fulldisclosure/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Full-Disclosure is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Public, vendor-neutral forum for detailed discussion of vulnerabilities, often publishes details before many other sources.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Fuzzing: Brute Force Vulnerability Discovery by Michael Sutton et al., 2007

  • Website: http://www.fuzzing.org/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Fuzzing: Brute Force Vulnerability Discovery by Michael Sutton et al., 2007 is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 Category Index

Fuzzing: Brute Force Vulnerability Discovery, 1st Edition

  • Website: https://www.amazon.com/Fuzzing-Brute-Force-Vulnerability-Discovery/dp/0321446119/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Fuzzing

What it does: Fuzzing: Brute Force Vulnerability Discovery, 1st Edition is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: (2007).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Books.

Back to Category Index

git-scanner

  • Website: https://github.com/HightechSec/git-scanner
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing, Awesome Hacking

What it does: git-scanner is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: A tool for bug hunting or pentesting for targeting websites that have open .git repositories available in public.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

GitHub Advisories

  • Website: https://github.com/advisories/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: GitHub Advisories is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Public vulnerability advisories published by or affecting codebases hosted by GitHub, including open source projects.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

H26Forge

  • Website: https://github.com/h26forge/h26forge
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: H26Forge is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Domain-specific infrastructure for analyzing, generating, and manipulating syntactically correct but semantically spec-non-compliant video 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 > Exploit Development Tools.

Back to Category Index

HOW TO EXPLOIT LIFERAY CVE-2020-7961 : QUICK JOURNEY TO POC

  • Website: https://www.synacktiv.com/en/publications/how-to-exploit-liferay-cve-2020-7961-quick-journey-to-poc.html
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: HOW TO EXPLOIT LIFERAY CVE-2020-7961 : QUICK JOURNEY TO POC is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Deserialization.

Back to Category Index

  • Website: https://pentest-tools.com/blog/exploit-dotnetnuke-cookie-deserialization/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: How to exploit the DotNetNuke Cookie Deserialization is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Deserialization.

Back to Category Index

How we exploited a remote code execution vulnerability in math.js

  • Website: https://capacitorset.github.io/mathjs/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: How we exploited a remote code execution vulnerability in math.js is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Remote Code Execution.

Back to Category Index

HPI-VDB

  • Website: https://hpi-vdb.de/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: HPI-VDB is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Aggregator of cross-referenced software vulnerabilities offering free-of-charge API access, provided by the Hasso-Plattner Institute, Potsdam.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Industrial Exploitation Framework (ISF)

  • Website: https://github.com/dark-lbp/isf
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Industrial Exploitation Framework (ISF) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Metasploit-like exploit framework based on routersploit designed to target Industrial Control Systems (ICS), SCADA devices, PLC firmware, 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 > Industrial Control and SCADA Systems.

Back to Category Index

Inj3ct0r

  • Website: https://www.0day.today/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Inj3ct0r is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Exploit marketplace and vulnerability information aggregator. (.).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Internet of Things Scanner

  • Website: http://iotscanner.bullguard.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Internet of Things Scanner is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Check if your internet-connected devices at home are public on Shodan 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 Category Index

Kadimus

  • Website: https://github.com/P0cL4bs/Kadimus
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Kadimus is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: LFI scan and exploit 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 Category Index

LFISuite

  • Website: https://github.com/D35m0nd142/LFISuite
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: LFISuite is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Automatic LFI scanner and exploiter.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Linux Exploit Suggester

  • Website: https://github.com/PenturaLabs/Linux_Exploit_Suggester
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Linux Exploit Suggester is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Heuristic reporting on potentially viable exploits for a given 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 > GNU/Linux Utilities.

Back to Category Index

Microsoft Security Advisories and Bulletins

  • Website: https://docs.microsoft.com/en-us/security-updates/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Microsoft Security Advisories and Bulletins is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Archive and announcements of security advisories impacting Microsoft software, published by the Microsoft Security Response Center (MSRC).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Mozilla Foundation Security Advisories

  • Website: https://www.mozilla.org/security/advisories/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Mozilla Foundation Security Advisories is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Archive of security advisories impacting Mozilla software, including the Firefox Web Browser.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

National Vulnerability Database (NVD)

  • Website: https://nvd.nist.gov/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: National Vulnerability Database (NVD) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: United States government's National Vulnerability Database provides additional meta-data (CPE, CVSS scoring) of the standard CVE List along with a fine-grained search engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

OpalOPC

  • Website: https://opalopc.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: OpalOPC is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Commercial OPC UA vulnerability assessment tool, sold by Molemmat.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Industrial Control and SCADA Systems.

Back to Category Index

Open Redirect Vulnerability

  • Website: https://s0cket7.com/open-redirect-vulnerability/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Open Redirect Vulnerability is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 Category Index

OWASP Testing Checklist v4

  • Website: https://www.owasp.org/index.php/Testing_Checklist
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security

What it does: OWASP Testing Checklist v4 is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: List of some controls to test during a web vulnerability assessment. Markdown version may be found .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Penetration Testing Framework (PTF)

  • Website: http://www.vulnerabilityassessment.co.uk/Penetration%20Test.html
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Penetration Testing Framework (PTF) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Outline for performing penetration tests compiled as a general framework usable by vulnerability analysts and penetration testers alike.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

PingCastle

  • Website: https://www.pingcastle.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: PingCastle is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Active Directory vulnerability detection and reporting 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 Cybersecurity Blue Team > Windows-based defenses > Active Directory.

Back to Category Index

Pre-authentication XXE vulnerability in the Services Drupal module

  • Website: https://www.synacktiv.com/ressources/synacktiv_drupal_xxe_services.pdf
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Pre-authentication XXE vulnerability in the Services Drupal module is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > XXE.

Back to Category Index

PUSHING WEBKIT'S BUTTONS WITH A MOBILE PWN2OWN EXPLOIT

  • Website: https://www.zerodayinitiative.com/blog/2018/2/12/pushing-webkits-buttons-with-a-mobile-pwn2own-exploit
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: PUSHING WEBKIT'S BUTTONS WITH A MOBILE PWN2OWN EXPLOIT is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

Pwntools

  • Website: https://github.com/Gallopsled/pwntools
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing, Awesome CTF

What it does: Pwntools is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Rapid exploit development framework built for use in CTFs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Exploit Development Tools.

Back to Category Index

Raccoon

  • Website: https://github.com/evyatarmeged/Raccoon
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing, Awesome CTF, Awesome Web Security

What it does: Raccoon is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: High performance offensive security tool for reconnaissance and vulnerability scanning 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 > Reconnaissance > OSINT - Open-Source Intelligence.

Back to Category Index

react2shell-scanner

  • Website: https://github.com/nxgn-kd01/react2shell-scanner
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security

What it does: react2shell-scanner is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Detect CVE-2025-55182 (React2Shell) RCE vulnerability in React Server Components. Scans React 19.x and Next.js projects for critical remote code execution flaws.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

retire.js

  • Website: https://github.com/RetireJS/retire.js
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: retire.js is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Scanner detecting the use of JavaScript libraries with known vulnerabilities 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 > Detecting.

Back to Category Index

SecuriTeam

  • Website: http://www.securiteam.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: SecuriTeam is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Independent source of software vulnerability 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: Awesome Penetration Testing > Vulnerability Databases.

Back to Category Index

shai-hulud-scanner

  • Website: https://github.com/nxgn-kd01/shai-hulud-scanner
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security

What it does: shai-hulud-scanner is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Detect indicators of compromise from the Shai Hulud 2.0 npm supply chain attack that compromised 796+ packages. Performs comprehensive security checks for malicious files, hashes, and patterns.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Singularity of Origin

  • Website: https://github.com/nccgroup/singularity
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Singularity of Origin is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: It includes the necessary components to rebind the IP address of the attack server DNS name to the target machine's IP address and to serve attack payloads to exploit vulnerable software on the target machine 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 > DNS Rebinding.

Back to Category Index

Snyk Vulnerability DB

  • Website: https://snyk.io/vuln/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Snyk Vulnerability DB is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Detailed information and remediation guidance for vulnerabilities known by Snyk.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

TaintScope: A checksum-aware directed fuzzing tool for automatic software vulnerability detection, 2010

  • Website: https://ieeexplore.ieee.org/abstract/document/5504701
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Fuzzing

What it does: TaintScope: A checksum-aware directed fuzzing tool for automatic software vulnerability detection, 2010 is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. 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 > IEEE Symposium on Security and Privacy (IEEE S&P).

Back to Category Index

tfsec

  • Website: https://aquasecurity.github.io/tfsec/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Cybersecurity Blue Team

What it does: tfsec is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Static analysis security scanner for your Terraform code designed to run locally and in CI 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 Category Index

Trend Micro Threat Discovery Appliance - Session Generation Authentication Bypass (CVE-2016-8584)

  • Website: http://blog.malerisch.net/2017/04/trend-micro-threat-discovery-appliance-session-generation-authentication-bypass-cve-2016-8584.html
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: Trend Micro Threat Discovery Appliance - Session Generation Authentication Bypass (CVE-2016-8584) is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Written by and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Evasions > Authentication.

Back to Category Index

Trivy

  • Website: https://github.com/aquasecurity/trivy
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Security, Awesome Cybersecurity Blue Team

What it does: Trivy is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Simple and comprehensive vulnerability scanner for containers and other artifacts, suitable for use in continuous integration 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 Category Index

US-CERT Vulnerability Notes Database

  • Website: https://www.kb.cert.org/vuls/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: US-CERT Vulnerability Notes Database is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Summaries, technical details, remediation information, and lists of vendors affected by software vulnerabilities, aggregated by the United States Computer Emergency Response Team (US-CERT).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

VulDB

  • Website: https://vuldb.com
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: VulDB is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Independent vulnerability database with user community, exploit details, and additional meta data (e.g. CPE, CVSS, CWE).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Vulmon

  • Website: https://vulmon.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Vulmon is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Vulnerability search engine with vulnerability intelligence features that conducts full text searches in its 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 > Vulnerability Databases.

Back to Category Index

Vulnerability as a service: SambaCry

  • Website: https://hub.docker.com/r/vulnerables/cve-2017-7494/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Vulnerability as a service: SambaCry is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: docker pull vulnerables/cve-2017-7494.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Vulnerability Lab

  • Website: https://www.vulnerability-lab.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Vulnerability Lab is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Open forum for security advisories organized by category of exploit target.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Vulners

  • Website: https://vulners.com/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Vulners is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Security database of software vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

WAScan

  • Website: https://github.com/m4ll0k/WAScan
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: WAScan is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Is an open source web application security scanner that uses "black-box" method, created 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 > Scanning.

Back to Category Index

wePWNise

  • Website: https://labs.mwrinfosecurity.com/tools/wepwnise/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: wePWNise is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Generates architecture independent VBA code to be used in Office documents or templates and automates bypassing application control and exploit mitigation 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 > Windows Utilities.

Back to Category Index

Windows Exploit Suggester

  • Website: https://github.com/GDSSecurity/Windows-Exploit-Suggester
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Windows Exploit Suggester is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Detects potential missing patches on the target.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Wordpress Exploit Framework

  • Website: https://github.com/rastating/wordpress-exploit-framework
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Wordpress Exploit Framework is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Ruby framework for developing and using modules which aid in the penetration testing of WordPress powered websites and 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 > Exploit Development Tools.

Back to Category Index

wpscan

  • Website: https://github.com/wpscanteam/wpscan
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Web Security

What it does: wpscan is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: WPScan is a black box WordPress vulnerability scanner 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 > Scanning.

Back to Category Index

WPSploit

  • Website: https://github.com/espreto/wpsploit
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: WPSploit is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Exploit WordPress-powered websites with Metasploit.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Zero Day Initiative

  • Website: http://zerodayinitiative.com/advisories/published/
  • Model: Open Source
  • Category: Vulnerability Management
  • Source Lists: Awesome Penetration Testing

What it does: Zero Day Initiative is used in vulnerability management programs to support risk-based vulnerability prioritization and remediation planning. Source summaries describe it as: Bug bounty program with publicly accessible archive of published security advisories, operated by TippingPoint.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Vulnerability Databases.

Back to Category Index

Web & API Security

This category contains 264 documented tools. It focuses on capabilities used for application-layer threat prevention and request/response validation. Use this section when building shortlists, comparing operational tradeoffs, and mapping controls to detection/response ownership.

Open category-focused page

$36k Google App Engine RCE

  • Website: https://sites.google.com/site/testsitehacking/-36k-google-app-engine-rce
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: $36k Google App Engine RCE is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

$7.5k Google services mix-up

  • Website: https://sites.google.com/site/testsitehacking/-7-5k-Google-services-mix-up
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: $7.5k Google services mix-up is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

0Day Labs

  • Website: http://blog.0daylabs.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: 0Day Labs is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Awesome bug-bounty and challenges 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 Web Security > Blogs.

Back to Category Index

is filtered ?

  • Website: https://twitter.com/strukt93/status/931586377665331200
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: is filtered ? is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

@cure53berlin

  • Website: https://twitter.com/cure53berlin
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @cure53berlin is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: is a German cybersecurity firm.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@filedescriptor

  • Website: https://twitter.com/filedescriptor
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @filedescriptor is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Active penetrator often tweets and writes useful articles.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@garethheyes

  • Website: https://twitter.com/garethheyes
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @garethheyes is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: English web penetrator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@hasegawayosuke

  • Website: https://twitter.com/hasegawayosuke
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @hasegawayosuke is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Japanese javascript security researcher.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@kinugawamasato

  • Website: https://twitter.com/kinugawamasato
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @kinugawamasato is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Japanese web penetrator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@shhnjk

  • Website: https://twitter.com/shhnjk
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @shhnjk is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Web and Browsers Security Researcher.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

@XssPayloads

  • Website: https://twitter.com/XssPayloads
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: @XssPayloads is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: The wonderland of JavaScript unexpected usages, 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 Web Security > Twitter Users.

Back to Category Index

A glimpse into GitHub's Bug Bounty workflow

  • Website: https://githubengineering.com/githubs-bug-bounty-workflow/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: A glimpse into GitHub's Bug Bounty workflow is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

A Methodical Approach to Browser Exploitation

  • Website: https://blog.ret2.io/2018/06/05/pwn2own-2018-exploit-development/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: A Methodical Approach to Browser Exploitation is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by , and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

  • Website: https://www.blackhat.com/docs/us-17/thursday/us-17-Tsai-A-New-Era-Of-SSRF-Exploiting-URL-Parser-In-Trending-Programming-Languages.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: A New Era of SSRF - Exploiting URL Parser in Trending Programming Languages! is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

Advisory: Java/Python FTP Injections Allow for Firewall Bypass

  • Website: http://blog.blindspotsecurity.com/2017/02/advisory-javapython-ftp-injections.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Advisory: Java/Python FTP Injections Allow for Firewall Bypass is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > FTP Injection.

Back to Category Index

Airbnb – When Bypassing JSON Encoding, XSS Filter, WAF, CSP, and Auditor turns into Eight Vulnerabilities

  • Website: https://buer.haus/2017/03/08/airbnb-when-bypassing-json-encoding-xss-filter-waf-csp-and-auditor-turns-into-eight-vulnerabilities/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Airbnb – When Bypassing JSON Encoding, XSS Filter, WAF, CSP, and Auditor turns into Eight Vulnerabilities is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > WAF.

Back to Category Index

alert(1) to win

  • Website: https://alf.nu/alert1
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: alert(1) to win is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Series of XSS challenges - 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 Category Index

All you need to know about SSRF and how may we write tools to do auto-detect

  • Website: https://www.auxy.xyz/web%20security/2017/07/06/all-ssrf-knowledge.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: All you need to know about SSRF and how may we write tools to do auto-detect is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

An example why NAT is NOT security

  • Website: https://0day.work/an-example-why-nat-is-not-security/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: An example why NAT is NOT security is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Another XSS in Google Colaboratory

  • Website: https://blog.bentkowski.info/2018/09/another-xss-in-google-colaboratory.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Another XSS in Google Colaboratory is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

Any protection against dynamic module import?

  • Website: https://github.com/w3c/webappsec-csp/issues/243
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Any protection against dynamic module import? is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

Applied Crypto Hardening

  • Website: https://bettercrypto.org/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Applied Crypto Hardening is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Crypto.

Back to Category Index

ASP.NET resource files (.RESX) and deserialisation issues

  • Website: https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/august/aspnet-resource-files-resx-and-deserialisation-issues/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: ASP.NET resource files (.RESX) and deserialisation issues is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Deserialization.

Back to Category Index

Attacking Private Networks from the Internet with DNS Rebinding

  • Website: https://medium.com/@brannondorsey/attacking-private-networks-from-the-internet-with-dns-rebinding-ea7098a2d325
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Attacking Private Networks from the Internet with DNS Rebinding is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Automating local DTD discovery for XXE exploitation

  • Website: https://www.gosecure.net/blog/2019/07/16/automating-local-dtd-discovery-for-xxe-exploitation
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Automating local DTD discovery for XXE exploitation is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

AWS takeover through SSRF in JavaScript

  • Website: http://10degres.net/aws-takeover-through-ssrf-in-javascript/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: AWS takeover through SSRF in JavaScript is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

BadLibrary

  • Website: https://github.com/SecureSkyTechnology/BadLibrary
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: BadLibrary is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Vulnerable web application for training - 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 Category Index

Be careful what you copy: Invisibly inserting usernames into text with Zero-Width Characters

  • Website: https://medium.com/@umpox/be-careful-what-you-copy-invisibly-inserting-usernames-into-text-with-zero-width-characters-18b4e6f17b66
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Be careful what you copy: Invisibly inserting usernames into text with Zero-Width Characters is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Breaking UC Browser

  • Website: https://habr.com/en/company/drweb/blog/452076/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Breaking UC Browser is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

Broken Browser

  • Website: https://www.brokenbrowser.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Broken Browser is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Fun with Browser Vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

bug-bounty-reference

  • Website: https://github.com/ngalongc/bug-bounty-reference
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: bug-bounty-reference is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: List of bug bounty write-up that is categorized by the bug nature 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 Category Index

bXSS

  • Website: https://github.com/LewisArdern/bXSS
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: bXSS is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: bXSS is a simple Blind XSS application adapted from 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 > Detecting.

Back to Category Index

Bypass Fix of OOB XXE Using Different encoding

  • Website: https://twitter.com/SpiderSec/status/1191375472690528256
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Bypass Fix of OOB XXE Using Different encoding is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > XXE.

Back to Category Index

Bypassing Mobile Browser Security For Fun And Profit

  • Website: https://www.blackhat.com/docs/asia-16/materials/asia-16-Baloch-Bypassing-Browser-Security-Policies-For-Fun-And-Profit-wp.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Bypassing Mobile Browser Security For Fun And Profit is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

Bypassing Web Cache Poisoning Countermeasures

  • Website: https://portswigger.net/blog/bypassing-web-cache-poisoning-countermeasures
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Bypassing Web Cache Poisoning Countermeasures is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Web Cache Poisoning.

Back to Category Index

C.XSS Guide

  • Website: https://excess-xss.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: C.XSS Guide is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Cache poisoning and other dirty tricks

  • Website: https://lab.wallarm.com/cache-poisoning-and-other-dirty-tricks-120468f1053f
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Cache poisoning and other dirty tricks is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Web Cache Poisoning.

Back to Category Index

Call-Flow Aware API Fuzz Testing for Security of Windows Systems, 2008

  • Website: https://www.computer.org/csdl/proceedings/iccsa/2008/3243/00/3243a019-abs.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: Call-Flow Aware API Fuzz Testing for Security of Windows Systems, 2008 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > The others.

Back to Category Index

cefdebug

  • Website: https://github.com/taviso/cefdebug
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: cefdebug is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Minimal code to connect to a CEF debugger 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 > Others.

Back to Category Index

Charles

  • Website: https://www.charlesproxy.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Charles is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Proxy.

Back to Category Index

charsetinspect

  • Website: https://github.com/hack-all-the-things/charsetinspect
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: charsetinspect is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Script that inspects multi-byte character sets looking for characters with specific user-defined properties 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 > Fuzzing.

Back to Category Index

Chronicle Detection Rules

  • Website: https://github.com/chronicle/detection-rules
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Threat Detection

What it does: Chronicle Detection Rules is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Collection of YARA-L 2.0 sample rules for the Chronicle Detection API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Detection Rules.

Back to Category Index

Clickjacking

  • Website: https://www.imperva.com/learn/application-security/clickjacking/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Clickjacking is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Clickjacking.

Back to Category Index

Clickjackings in Google worth 14981.7$

  • Website: https://medium.com/@raushanraj_65039/google-clickjacking-6a04132b918a
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Clickjackings in Google worth 14981.7$ is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Clickjacking.

Back to Category Index

CloudGoat

  • Website: https://github.com/RhinoSecurityLabs/cloudgoat
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: CloudGoat is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Rhino Security Labs' "Vulnerable by Design" AWS infrastructure setup tool - 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 Category Index

Common Azure Security Vulnerabilities and Misconfigurations

  • Website: https://rhinosecuritylabs.com/cloud-security/common-azure-security-vulnerabilities/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Common Azure Security Vulnerabilities and Misconfigurations is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Azure.

Back to Category Index

Cracking Java’s RNG for CSRF - Javax Faces and Why CSRF Token Randomness Matters

  • Website: https://blog.securityevaluators.com/cracking-javas-rng-for-csrf-ea9cacd231d2
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Cracking Java’s RNG for CSRF - Javax Faces and Why CSRF Token Randomness Matters is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF.

Back to Category Index

Cross-Site Scripting – Application Security – Google

  • Website: https://www.google.com/intl/sw/about/appsecurity/learning/xss/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Cross-Site Scripting – Application Security – Google is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Crowdsec WAF

  • Website: https://www.crowdsec.net/solutions/application-security
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome SOC

What it does: Crowdsec WAF is used in web & api security programs to support application-layer threat prevention and request/response validation. 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: To go further > SOC sensors, nice to have.

Back to Category Index

CSP: bypassing form-action with reflected XSS

  • Website: https://labs.detectify.com/2016/04/04/csp-bypassing-form-action-with-reflected-xss/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: CSP: bypassing form-action with reflected XSS is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

Csper

  • Website: https://csper.io
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Csper is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: A set of tools for building/evaluating/monitoring content-security-policy to prevent/detect cross site scripting 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 > Preventing.

Back to Category Index

CSS-Keylogging

  • Website: https://github.com/maxchehab/CSS-Keylogging
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: CSS-Keylogging is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Chrome extension and Express server that exploits keylogging abilities of CSS 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 > Leaking.

Back to Category Index

CSV Injection -> Meterpreter on Pornhub

  • Website: https://news.webamooz.com/wp-content/uploads/bot/offsecmag/147.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: CSV Injection -> Meterpreter on Pornhub is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSV Injection.

Back to Category Index

Curiefense

  • Website: https://github.com/curiefense/curiefense
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: Curiefense is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Curiefense adds a broad set of automated web security tools, including a WAF to Envoy Proxy.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

CyberChef

  • Website: https://github.com/gchq/CyberChef
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: CyberChef is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: The Cyber Swiss Army Knife - a web app for encryption, encoding, compression and data analysis - 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 > Others.

Back to Category Index

Dark Reading

  • Website: https://www.darkreading.com/Default.asp
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Dark Reading is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Connecting The Information Security 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: Awesome Web Security > Forums.

Back to Category Index

dirhunt

  • Website: https://github.com/Nekmo/dirhunt
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: dirhunt is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Web crawler optimized for searching and analyzing the directory structure of a site 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 > Fuzzing.

Back to Category Index

Dnslogger

  • Website: https://wiki.skullsecurity.org/index.php?title=Dnslogger
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Dnslogger is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: DNS Logger 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 > Others.

Back to Category Index

DOM XSS – auth.uber.com

  • Website: http://stamone-bug-bounty.blogspot.tw/2017/10/dom-xss-auth14.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DOM XSS – auth.uber.com is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

domato

  • Website: https://github.com/google/domato
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: domato is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: DOM fuzzer 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 > Fuzzing.

Back to Category Index

Domato Fuzzer's Generation Engine Internals

  • Website: https://www.sigpwn.io/blog/2018/4/14/domato-fuzzers-generation-engine-internals
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Domato Fuzzer's Generation Engine Internals is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

DOMPurify

  • Website: https://github.com/cure53/DOMPurify
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DOMPurify is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG 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 > Preventing.

Back to Category Index

DON'T TRUST THE DOM: BYPASSING XSS MITIGATIONS VIA SCRIPT GADGETS

  • Website: https://www.blackhat.com/docs/us-17/thursday/us-17-Lekies-Dont-Trust-The-DOM-Bypassing-XSS-Mitigations-Via-Script-Gadgets.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DON'T TRUST THE DOM: BYPASSING XSS MITIGATIONS VIA SCRIPT GADGETS is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by , , and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > XSS.

Back to Category Index

DOS File Path Magic Tricks

  • Website: https://medium.com/walmartlabs/dos-file-path-magic-tricks-5eda7a7a85fa
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DOS File Path Magic Tricks is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

dref

  • Website: https://github.com/mwrlabs/dref
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: dref is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: DNS Rebinding Exploitation Framework. Dref does the heavy-lifting for DNS rebinding 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 > DNS Rebinding.

Back to Category Index

DRUPAL 7.X SERVICES MODULE UNSERIALIZE() TO RCE

  • Website: https://www.ambionics.io/blog/drupal-services-module-rce
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DRUPAL 7.X SERVICES MODULE UNSERIALIZE() TO RCE is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

DVCS-Pillage

  • Website: https://github.com/evilpacket/DVCS-Pillage
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: DVCS-Pillage is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Pillage web accessible GIT, HG and BZR repositories 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 > Leaking.

Back to Category Index

ECMAScript 6 from an Attacker's Perspective - Breaking Frameworks, Sandboxes, and everything else

  • Website: http://www.slideshare.net/x00mario/es6-en
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: ECMAScript 6 from an Attacker's Perspective - Breaking Frameworks, Sandboxes, and everything else is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

EQGRP

  • Website: https://github.com/x0rz/EQGRP
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: EQGRP is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Decrypted content of eqgrp-auction-file.tar.xz 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 Category Index

Escape and Evasion Egressing Restricted Networks

  • Website: https://www.optiv.com/blog/escape-and-evasion-egressing-restricted-networks
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Escape and Evasion Egressing Restricted Networks is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Evading CSP with DOM-based dangling markup

  • Website: https://portswigger.net/blog/evading-csp-with-dom-based-dangling-markup
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Evading CSP with DOM-based dangling markup is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

Evil Teacher: Code Injection in Moodle

  • Website: https://blog.ripstech.com/2018/moodle-remote-code-execution/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Evil Teacher: Code Injection in Moodle is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

Evil XML with two encodings

  • Website: https://mohemiv.com/all/evil-xml/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Evil XML with two encodings is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

Exploiting a V8 OOB write.

  • Website: https://halbecaf.com/2017/05/24/exploiting-a-v8-oob-write/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Exploiting a V8 OOB write. is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

Exploiting CSRF on JSON endpoints with Flash and redirects

  • Website: https://blog.appsecco.com/exploiting-csrf-on-json-endpoints-with-flash-and-redirects-681d4ad6b31b
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Exploiting CSRF on JSON endpoints with Flash and redirects is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF.

Back to Category Index

Exploiting Node.js deserialization bug for Remote Code Execution

  • Website: https://opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remote-code-execution/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Exploiting Node.js deserialization bug for Remote Code Execution is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

Exploiting XSS with 20 characters limitation

  • Website: https://jlajara.gitlab.io/posts/2019/11/30/XSS_20_characters.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Exploiting XSS with 20 characters limitation is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

Exploiting XXE with local DTD files

  • Website: https://mohemiv.com/all/exploiting-xxe-with-local-dtd-files/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Exploiting XXE with local DTD files is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

FANS

  • Website: https://github.com/iromise/fans
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: FANS is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: FANS is a fuzzing tool for fuzzing Android native system services. It contains four components: interface collector, interface model extractor, dependency inferer, and fuzzer engine.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > API.

Back to Category Index

File Upload Restrictions Bypass

  • Website: https://www.exploit-db.com/docs/english/45074-file-upload-restrictions-bypass.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: File Upload Restrictions Bypass is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Upload.

Back to Category Index

Forcing XXE Reflection through Server Error Messages

  • Website: https://blog.netspi.com/forcing-xxe-reflection-server-error-messages/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Forcing XXE Reflection through Server Error Messages is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

fuzz.txt

  • Website: https://github.com/Bo0oM/fuzz.txt
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: fuzz.txt is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Potentially dangerous files 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 > Fuzzing.

Back to Category Index

GitHub Enterprise Remote Code Execution

  • Website: http://exablue.de/blog/2017-03-15-github-enterprise-remote-code-execution.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GitHub Enterprise Remote Code Execution is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

GitHub Enterprise SQL Injection

  • Website: http://blog.orange.tw/2017/01/bug-bounty-github-enterprise-sql-injection.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GitHub Enterprise SQL Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

GitHub's CSP journey

  • Website: https://githubengineering.com/githubs-csp-journey/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GitHub's CSP journey is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

GitHub's post-CSP journey

  • Website: https://githubengineering.com/githubs-post-csp-journey/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GitHub's post-CSP journey is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

gitleaks

  • Website: https://github.com/zricethezav/gitleaks
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: gitleaks is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Searches full repo history for secrets and keys 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 > Leaking.

Back to Category Index

GitMiner

  • Website: https://github.com/UnkL4b/GitMiner
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GitMiner is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Tool for advanced mining for content on Github 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 > Leaking.

Back to Category Index

Google VRP and Unicorns

  • Website: https://sites.google.com/site/bughunteruniversity/behind-the-scenes/presentations/google-vrp-and-unicorns
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Google VRP and Unicorns is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

GraphFuzz

  • Website: https://github.com/ForAllSecure/GraphFuzz
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: GraphFuzz is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: GraphFuzz is an experimental framework for building structure-aware, library API fuzzers.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > API.

Back to Category Index

GraphQL NoSQL Injection Through JSON Types

  • Website: http://www.petecorey.com/blog/2017/06/12/graphql-nosql-injection-through-json-types/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: GraphQL NoSQL Injection Through JSON Types is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > NoSQL Injection.

Back to Category Index

GuardRails

  • Website: https://github.com/apps/guardrails
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security, Awesome Web Security

What it does: GuardRails is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: A GitHub App that provides security feedback in Pull 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 Web Security > Tools > Detecting.

Back to Category Index

H5SC

  • Website: https://github.com/cure53/H5SC
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: H5SC is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

HackDig

  • Website: http://en.hackdig.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: HackDig is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Dig high-quality web security articles for hacker.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Forums.

Back to Category Index

Hardcoded secrets, unverified tokens, and other common JWT mistakes

  • Website: https://r2c.dev/blog/2020/hardcoded-secrets-unverified-tokens-and-other-common-jwt-mistakes/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Hardcoded secrets, unverified tokens, and other common JWT mistakes is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > JWT.

Back to Category Index

Honeyλ (HoneyLambda)

  • Website: https://github.com/0x4D31/honeylambda
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Honeypots

What it does: Honeyλ (HoneyLambda) is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Simple, serverless application designed to create and monitor URL honeytokens, on top of AWS Lambda and Amazon API Gateway.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, or defer.

Selection considerations: As an open-source option, teams usually evaluate maintainer activity, release cadence, and community response quality. Related source context: Contents > Honeypots.

Back to Category Index

How do we Stop Spilling the Beans Across Origins?

  • Website: https://docs.google.com/document/d/1cbL-X0kV_tQ5rL8XJ3lXkV-j0pt_CfTu5ZSzYrncPDc/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How do we Stop Spilling the Beans Across Origins? is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

How I Chained 4 vulnerabilities on GitHub Enterprise, From SSRF Execution Chain to RCE!

  • Website: http://blog.orange.tw/2017/07/how-i-chained-4-vulnerabilities-on.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I Chained 4 vulnerabilities on GitHub Enterprise, From SSRF Execution Chain to RCE! is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

How I could have stolen your photos from Google - my first 3 bug bounty writeups

  • Website: https://blog.avatao.com/How-I-could-steal-your-photos-from-Google/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I could have stolen your photos from Google - my first 3 bug bounty writeups is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

How I exploited ACME TLS-SNI-01 issuing Let's Encrypt SSL-certs for any domain using shared hosting

  • Website: https://labs.detectify.com/2018/01/12/how-i-exploited-acme-tls-sni-01-issuing-lets-encrypt-ssl-certs-for-any-domain-using-shared-hosting/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I exploited ACME TLS-SNI-01 issuing Let's Encrypt SSL-certs for any domain using shared hosting is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

How I found a $5,000 Google Maps XSS (by fiddling with Protobuf)

  • Website: https://medium.com/@marin_m/how-i-found-a-5-000-google-maps-xss-by-fiddling-with-protobuf-963ee0d9caff#.u50nrzhas
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I found a $5,000 Google Maps XSS (by fiddling with Protobuf) is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

How I got my first big bounty payout with Tesla

  • Website: https://medium.com/heck-the-packet/how-i-got-my-first-big-bounty-payout-with-tesla-8d28b520162d
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I got my first big bounty payout with Tesla is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

How I hacked Google’s bug tracking system itself for $15,600 in bounties

  • Website: https://medium.com/free-code-camp/messing-with-the-google-buganizer-system-for-15-600-in-bounties-58f86cc9f9a5
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How I hacked Google’s bug tracking system itself for $15,600 in bounties is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Others.

Back to Category Index

How to bypass libinjection in many WAF/NGWAF

  • Website: https://medium.com/@d0znpp/how-to-bypass-libinjection-in-many-waf-ngwaf-1e2513453c0f
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How to bypass libinjection in many WAF/NGWAF is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > WAF.

Back to Category Index

How to Hunt Bugs in SAML; a Methodology - Part I

  • Website: https://epi052.gitlab.io/notes-to-self/blog/2019-03-07-how-to-test-saml-a-methodology/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How to Hunt Bugs in SAML; a Methodology - Part I is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Security Assertion Markup Language (SAML).

Back to Category Index

How to Hunt Bugs in SAML; a Methodology - Part II

  • Website: https://epi052.gitlab.io/notes-to-self/blog/2019-03-13-how-to-test-saml-a-methodology-part-two/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How to Hunt Bugs in SAML; a Methodology - Part II is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Security Assertion Markup Language (SAML).

Back to Category Index

How to Hunt Bugs in SAML; a Methodology - Part III

  • Website: https://epi052.gitlab.io/notes-to-self/blog/2019-03-16-how-to-test-saml-a-methodology-part-three/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How to Hunt Bugs in SAML; a Methodology - Part III is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Security Assertion Markup Language (SAML).

Back to Category Index

How we abused Slack's TURN servers to gain access to internal services

  • Website: https://www.rtcsec.com/2020/04/01-slack-webrtc-turn-compromise/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: How we abused Slack's TURN servers to gain access to internal services is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

HQL : Hyperinsane Query Language (or how to access the whole SQL API within a HQL injection ?)

  • Website: https://www.synacktiv.com/ressources/hql2sql_sstic_2015_en.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: HQL : Hyperinsane Query Language (or how to access the whole SQL API within a HQL injection ?) is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ORM Injection.

Back to Category Index

HQL for pentesters

  • Website: http://blog.h3xstream.com/2014/02/hql-for-pentesters.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: HQL for pentesters is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ORM Injection.

Back to Category Index

HTTPLeaks

  • Website: https://github.com/cure53/HTTPLeaks
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: HTTPLeaks is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: All possible ways, a website can leak HTTP requests 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 > Leaking.

Back to Category Index

Hunting for Web Shells

  • Website: https://www.tenable.com/blog/hunting-for-web-shells
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Hunting for Web Shells is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

IE11 Information disclosure - local file detection

  • Website: https://www.facebook.com/ExploitWareLabs/photos/a.361854183878462.84544.338832389513975/1378579648872572/?type=3&theater
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: IE11 Information disclosure - local file detection is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by James Lee.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

If HttpOnly You Could Still CSRF… Of CORS you can!

  • Website: https://medium.com/@_graphx/if-httponly-you-could-still-csrf-of-cors-you-can-5d7ee2c7443
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: If HttpOnly You Could Still CSRF… Of CORS you can! is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF.

Back to Category Index

Implications of Loading .NET Assemblies

  • Website: https://threatvector.cylance.com/en_us/home/implications-of-loading-net-assemblies.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Implications of Loading .NET Assemblies is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Inducing DNS Leaks in Onion Web Services

  • Website: https://github.com/epidemics-scepticism/writing/blob/master/onion-dns-leaks.md
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Inducing DNS Leaks in Onion Web Services is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Others.

Back to Category Index

Infosec Newbie

  • Website: https://www.sneakymonkey.net/2017/04/23/infosec-newbie/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Infosec Newbie is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Digests.

Back to Category Index

Introduction to OAuth 2.0 and OpenID Connect

  • Website: https://pragmaticwebsecurity.com/courses/introduction-oauth-oidc.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Introduction to OAuth 2.0 and OpenID Connect is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > OAuth.

Back to Category Index

Introduction to Web Application Security

  • Website: https://www.slideshare.net/nragupathy/introduction-to-web-application-security-blackhoodie-us-2018
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Introduction to Web Application Security is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by , and .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Invoke-ATTACKAPI

  • Website: https://github.com/Cyb3rWard0g/Invoke-ATTACKAPI
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Threat Detection

What it does: Invoke-ATTACKAPI is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: A PowerShell script to interact with the MITRE ATT&CK Framework via its own API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools.

Back to Category Index

IPObfuscator

  • Website: https://github.com/OsandaMalith/IPObfuscator
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: IPObfuscator is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Simple tool to convert the IP to a DWORD IP 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 > Fuzzing.

Back to Category Index

ironbee

  • Website: https://github.com/ironbee/ironbee
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: ironbee is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: IronBee is an open source project to build a universal web application security sensor. IronBee as a framework for developing a system for securing web applications - a framework for building a web application firewall (WAF).

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

I’m harvesting credit card numbers and passwords from your site. Here’s how.

  • Website: https://hackernoon.com/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: I’m harvesting credit card numbers and passwords from your site. Here’s how. is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

James Kettle

  • Website: http://albinowax.skeletonscribe.net/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: James Kettle is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Head of Research at .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

JavaScript MVC and Templating Frameworks

  • Website: http://www.slideshare.net/x00mario/jsmvcomfg-to-sternly-look-at-javascript-mvc-and-templating-frameworks
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: JavaScript MVC and Templating Frameworks is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > JSMVC.

Back to Category Index

JoomlaScan

  • Website: https://github.com/drego85/JoomlaScan
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: JoomlaScan is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Free software to find the components installed in Joomla CMS, built out of the ashes of Joomscan 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 > Scanning.

Back to Category Index

js-vuln-db

  • Website: https://github.com/tunz/js-vuln-db
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: js-vuln-db is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Collection of JavaScript engine CVEs with PoCs 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 > PoCs > Database.

Back to Category Index

js-xss

  • Website: https://github.com/leizongmin/js-xss
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: js-xss is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Sanitize untrusted HTML (to prevent XSS) with a configuration specified by a Whitelist 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 > Preventing.

Back to Category Index

JSON hijacking for the modern web

  • Website: http://blog.portswigger.net/2016/11/json-hijacking-for-modern-web.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: JSON hijacking for the modern web is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

Large-scale analysis of style injection by relative path overwrite

  • Website: https://blog.acolyer.org/2018/05/28/large-scale-analysis-of-style-injection-by-relative-path-overwrite/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Large-scale analysis of style injection by relative path overwrite is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Relative Path Overwrite.

Back to Category Index

leavesongs

  • Website: https://www.leavesongs.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: leavesongs is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: China's talented web penetrator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

LinkFinder

  • Website: https://github.com/GerbenJavado/LinkFinder
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: LinkFinder is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Python script that finds endpoints in JavaScript files 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 > Leaking.

Back to Category Index

List of bug bounty writeups

  • Website: https://pentester.land/list-of-bug-bounty-writeups.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: List of bug bounty writeups is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Look Mom, I don't use Shellcode - Browser Exploitation Case Study for Internet Explorer 11

  • Website: https://labs.bluefrostsecurity.de/files/Look_Mom_I_Dont_Use_Shellcode-WP.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Look Mom, I don't use Shellcode - Browser Exploitation Case Study for Internet Explorer 11 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

Making a Blind SQL Injection a little less blind

  • Website: https://medium.com/@tomnomnom/making-a-blind-sql-injection-a-little-less-blind-428dcb614ba8
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Making a Blind SQL Injection a little less blind is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

MINER

  • Website: https://github.com/puppet-meteor/MINER
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: MINER is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: MINER is a REST API fuzzer that utilizes three data-driven designs working together to guide the sequence generation, improve the request generation quality, and capture the unique errors caused by incorrect parameter usage.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > API.

Back to Category Index

Minerva

  • Website: https://github.com/ChijinZ/Minerva
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: Minerva is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Minerva is a browser fuzzer augmented by API mod-ref relations, aiming to synthesize highly-relevant browser API invocations in each test 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 > Tools > API.

Back to Category Index

Misadventures in AWS

  • Website: https://labs.f-secure.com/blog/misadventures-in-aws
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Misadventures in AWS is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by Christian Demko.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

ModSecurity

  • Website: http://www.modsecurity.org/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: ModSecurity is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: ModSecurity is a toolkit for real-time web application monitoring, logging, and access control.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

MySQL Error Based SQL Injection Using EXP

  • Website: https://www.exploit-db.com/docs/english/37953-mysql-error-based-sql-injection-using-exp.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: MySQL Error Based SQL Injection Using EXP is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

n0tr00t

  • Website: https://www.n0tr00t.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: n0tr00t is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: ~# n0tr00t Security 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 Web Security > Blogs.

Back to Category Index

nano

  • Website: https://github.com/s0md3v/nano
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: nano is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Family of code golfed PHP shells 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 > Webshell.

Back to Category Index

NAXSI

  • Website: https://github.com/nbs-system/naxsi
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: NAXSI is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: NAXSI is an open-source, high performance, low rules maintenance WAF for NGINX, NAXSI means Nginx Anti Xss & Sql Injection.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

Neat tricks to bypass CSRF-protection

  • Website: https://zhuanlan.zhihu.com/p/32716181
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Neat tricks to bypass CSRF-protection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF.

Back to Category Index

Neatly bypassing CSP

  • Website: https://lab.wallarm.com/how-to-trick-csp-in-letting-you-run-whatever-you-want-73cb5ff428aa
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Neatly bypassing CSP is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

notes

  • Website: https://github.com/ChALkeR/notes
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: notes is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Some public notes 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 Category Index

ntlm_challenger

  • Website: https://github.com/b17zr/ntlm_challenger
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: ntlm_challenger is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Parse NTLM over HTTP challenge messages 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 > Others.

Back to Category Index

Official Rails Security Guide

  • Website: http://guides.rubyonrails.org/security.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Official Rails Security Guide is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Rails.

Back to Category Index

open-appsec

  • Website: https://github.com/openappsec/openappsec
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: open-appsec is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: open-appsec is an open source machine-learning security engine that preemptively and automatically prevents threats against Web Application & APIs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

OpenRASP

  • Website: https://github.com/baidu/openrasp
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security, Awesome Web Security

What it does: OpenRASP is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: An open source RASP solution actively maintained by Baidu Inc. With context-aware detection algorithm the project achieved nearly no false positives. And less than 3% performance reduction is observed under heavy server load.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Runtime Application Self-Protection.

Back to Category Index

OpnSec

  • Website: https://opnsec.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: OpnSec is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Open Mind 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 Web Security > Blogs.

Back to Category Index

Orange

  • Website: http://blog.orange.tw/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Orange is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Taiwan's talented web penetrator.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

ORM Injection

  • Website: https://www.slideshare.net/simone.onofri/orm-injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: ORM Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ORM Injection.

Back to Category Index

ORM2Pwn: Exploiting injections in Hibernate ORM

  • Website: https://www.slideshare.net/0ang3el/orm2pwn-exploiting-injections-in-hibernate-orm
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: ORM2Pwn: Exploiting injections in Hibernate ORM is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ORM Injection.

Back to Category Index

OWASP ZAP Node API

  • Website: https://github.com/zaproxy/zap-api-nodejs
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: OWASP ZAP Node API is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Leverage the OWASP Zed Attack Proxy (ZAP) within your NodeJS applications with this official API.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Development.

Back to Category Index

PayloadsAllTheThings - Command Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Command%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - Command Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

PayloadsAllTheThings - CSRF Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/CSRF%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - CSRF Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF - Cross-Site Request Forgery.

Back to Category Index

PayloadsAllTheThings - CSV Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/CSV%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - CSV Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSV Injection.

Back to Category Index

PayloadsAllTheThings - Open Redirect

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Open%20Redirect
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - Open Redirect is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

PayloadsAllTheThings - SAML Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/SAML%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - SAML Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Security Assertion Markup Language (SAML).

Back to Category Index

PayloadsAllTheThings - Server-Side Request Forgery

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Server%20Side%20Request%20Forgery
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - Server-Side Request Forgery is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF - Server-Side Request Forgery.

Back to Category Index

PayloadsAllTheThings - SQL Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/SQL%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - SQL Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

PayloadsAllTheThings - Upload Insecure Files

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Upload%20Insecure%20Files
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - Upload Insecure Files is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Upload.

Back to Category Index

PayloadsAllTheThings - XSS Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/XSS%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - XSS Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

PayloadsAllTheThings - XXE Injection

  • Website: https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/XXE%20Injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PayloadsAllTheThings - XXE Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by various contributors.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

Phishing with Unicode Domains

  • Website: https://www.xudongz.com/blog/2017/idn-phishing/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Phishing with Unicode Domains is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > URL.

Back to Category Index

PHP SSRF Techniques

  • Website: https://medium.com/secjuice/php-ssrf-techniques-9d422cb28d51
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: PHP SSRF Techniques is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

Piercing the Veil: Server Side Request Forgery to NIPRNet access

  • Website: https://medium.com/bugbountywriteup/piercing-the-veil-server-side-request-forgery-to-niprnet-access-c358fd5e249a
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Piercing the Veil: Server Side Request Forgery to NIPRNet access is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

Poor RichFaces

  • Website: https://codewhitesec.blogspot.com/2018/05/poor-richfaces.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Poor RichFaces is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Remote Code Execution.

Back to Category Index

Portswigger Web Security Academy

  • Website: https://portswigger.net/web-security
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Portswigger Web Security Academy is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Free trainings and labs - 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 Category Index

Potential command injection in resolv.rb

  • Website: https://github.com/ruby/ruby/pull/1777
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Potential command injection in resolv.rb is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Practical introduction to SSL/TLS

  • Website: https://github.com/Hakky54/mutual-tls-ssl
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Practical introduction to SSL/TLS is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Practical Web Cache Poisoning

  • Website: https://portswigger.net/blog/practical-web-cache-poisoning
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Practical Web Cache Poisoning is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Cache Poisoning.

Back to Category Index

Prototype pollution attack in NodeJS application

  • Website: https://github.com/HoLyVieR/prototype-pollution-nsec18/blob/master/paper/JavaScript_prototype_pollution_attack_in_NodeJS.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Prototype pollution attack in NodeJS application is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Prototype Pollution.

Back to Category Index

prowler

  • Website: https://github.com/Alfresco/prowler
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: prowler is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Tool for AWS security assessment, auditing and hardening 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 > Auditing.

Back to Category Index

pwngitmanager

  • Website: https://github.com/allyshka/pwngitmanager
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: pwngitmanager is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Git manager for pentesters 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 > Leaking.

Back to Category Index

Query parameter reordering causes redirect page to render unsafe URL

  • Website: https://hackerone.com/reports/293689
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Query parameter reordering causes redirect page to render unsafe URL is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

Rails Security - First part

  • Website: https://hackmd.io/s/SkuTVw5O-
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Rails Security - First part is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Rails.

Back to Category Index

Rails SQL Injection

  • Website: https://rails-sqli.org
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Rails SQL Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Rails.

Back to Category Index

Real-world JS - 1

  • Website: https://blog.p6.is/Real-World-JS-1/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Real-world JS - 1 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Prototype Pollution.

Back to Category Index

Reddit

  • Website: https://www.reddit.com/r/websecurity/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Reddit is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Web Security > Community.

Back to Category Index

repo-supervisor

  • Website: https://github.com/auth0/repo-supervisor
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: repo-supervisor is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Scan your code for security misconfiguration, search for passwords and secrets.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Detecting.

Back to Category Index

REST-ler: Automatic Intelligent REST API Fuzzing, 2018

  • Website: https://arxiv.org/abs/1806.09739
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: REST-ler: Automatic Intelligent REST API Fuzzing, 2018 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ArXiv (Fuzzing with Artificial Intelligence & Machine Learning).

Back to Category Index

RestTestGen

  • Website: https://github.com/SeUniVr/RestTestGen
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Fuzzing

What it does: RestTestGen is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: RestTestGen is a robust tool and framework designed for automated black-box testing of RESTful web APIs.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Tools > API.

Back to Category Index

reverse-shell

  • Website: https://github.com/lukechilds/reverse-shell
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: reverse-shell is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Reverse Shell as a Service 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 > Webshell.

Back to Category Index

Reverse-Shell-Manager

  • Website: https://github.com/WangYihang/Reverse-Shell-Manager
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Reverse-Shell-Manager is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Reverse Shell Manager via Terminal .

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Webshell.

Back to Category Index

RIPS Technologies

  • Website: https://blog.ripstech.com/tags/security/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: RIPS Technologies is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Write-ups for PHP vulnerabilities.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

Scrutiny

  • Website: https://datarift.blogspot.tw/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Scrutiny is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Internet Security through Web Browsers by Dhiraj Mishra.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Blogs.

Back to Category Index

SELinux Game

  • Website: http://selinuxgame.org/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SELinux Game is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Learn SELinux by doing. Solve Puzzles, show skillz - 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 Category Index

Sending arbitrary IPC messages via overriding Function.prototype.apply

  • Website: https://hackerone.com/reports/188086
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Sending arbitrary IPC messages via overriding Function.prototype.apply is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

Sergey Bobrov

  • Website: http://blog.blackfan.ru/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Sergey Bobrov is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Web Security > Tricks > URL.

Back to Category Index

Setting arbitrary request headers in Chromium via CRLF injection

  • Website: https://blog.bentkowski.info/2018/06/setting-arbitrary-request-headers-in.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Setting arbitrary request headers in Chromium via CRLF injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

slurp

  • Website: https://github.com/hehnope/slurp
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: slurp is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Evaluate the security of S3 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 > Auditing.

Back to Category Index

SMTP over XXE − how to send emails using Java's XML parser

  • Website: https://shiftordie.de/blog/2017/02/18/smtp-over-xxe/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SMTP over XXE − how to send emails using Java's XML parser is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > FTP Injection.

Back to Category Index

snallygaster

  • Website: https://github.com/hannob/snallygaster
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: snallygaster is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Tool to scan for secret files on HTTP servers 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 > Leaking.

Back to Category Index

Some Problems Of URLs

  • Website: https://noncombatant.org/2017/11/07/problems-of-urls/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Some Problems Of URLs is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > URL.

Back to Category Index

Some Tricks From My Secret Group

  • Website: https://www.leavesongs.com/SHARE/some-tricks-from-my-secret-group.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Some Tricks From My Secret Group is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Others.

Back to Category Index

Some-PoC-oR-ExP

  • Website: https://github.com/coffeehb/Some-PoC-oR-ExP
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Some-PoC-oR-ExP is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: 各种漏洞poc、Exp的收集或编写 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 > PoCs > Database.

Back to Category Index

SOP bypass / UXSS – Stealing Credentials Pretty Fast (Edge)

  • Website: https://www.brokenbrowser.com/sop-bypass-uxss-stealing-credentials-pretty-fast/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SOP bypass / UXSS – Stealing Credentials Pretty Fast (Edge) is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

SPLOITUS

  • Website: https://sploitus.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SPLOITUS is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Exploits & Tools Search Engine 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 > PoCs > Database.

Back to Category Index

SQL INJECTION AND POSTGRES - AN ADVENTURE TO EVENTUAL RCE

  • Website: https://pulsesecurity.co.nz/articles/postgres-sqli
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SQL INJECTION AND POSTGRES - AN ADVENTURE TO EVENTUAL RCE is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

SQL injection in an UPDATE query - a bug bounty story!

  • Website: http://zombiehelp54.blogspot.jp/2017/02/sql-injection-in-update-query-bug.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SQL injection in an UPDATE query - a bug bounty story! is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

SQL Injection Pocket Reference

  • Website: https://websec.ca/kb/sql_injection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SQL Injection Pocket Reference is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

SQL Injection Wiki

  • Website: https://sqlwiki.netspi.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SQL Injection Wiki is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

sql_firewall

  • Website: https://github.com/uptimejp/sql_firewall
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Security

What it does: sql_firewall is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: SQL Firewall Extension for PostgreSQL.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Web Application Firewall.

Back to Category Index

sqlchop

  • Website: https://sqlchop.chaitin.cn/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: sqlchop is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: SQL injection detection engine 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 > Detecting.

Back to Category Index

SSD Advisory – Chrome Turbofan Remote Code Execution

  • Website: https://blogs.securiteam.com/index.php/archives/3379
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SSD Advisory – Chrome Turbofan Remote Code Execution is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

SSRF in Exchange leads to ROOT access in all instances

  • Website: https://hackerone.com/reports/341876
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SSRF in Exchange leads to ROOT access in all instances is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: A $25k bounty for SSRF leading to ROOT Access in all instances 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 > SSRF.

Back to Category Index

SSRF in https://imgur.com/vidgif/url

  • Website: https://hackerone.com/reports/115748
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SSRF in https://imgur.com/vidgif/url is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

SSRF Tips

  • Website: http://blog.safebuff.com/2016/07/03/SSRF-Tips/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: SSRF Tips is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > SSRF.

Back to Category Index

Stack Overflow

  • Website: http://stackoverflow.com/questions/tagged/security
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Stack Overflow is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Web Security > Community.

Back to Category Index

Stealing CSRF tokens with CSS injection (without iFrames)

  • Website: https://github.com/dxa4481/cssInjection
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Stealing CSRF tokens with CSS injection (without iFrames) is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF.

Back to Category Index

Stored XSS, and SSRF in Google using the Dataset Publishing Language

  • Website: https://s1gnalcha0s.github.io/dspl/2018/03/07/Stored-XSS-and-SSRF-Google.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Stored XSS, and SSRF in Google using the Dataset Publishing Language is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Others.

Back to Category Index

Take Advantage of Out-of-Scope Domains in Bug Bounty Programs

  • Website: https://ahussam.me/Take-Advantage-of-Out-of-Scope-Domains-in-Bug-Bounty/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Take Advantage of Out-of-Scope Domains in Bug Bounty Programs is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

The Absurdly Underestimated Dangers of CSV Injection

  • Website: http://georgemauer.net/2017/10/07/csv-injection.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Absurdly Underestimated Dangers of CSV Injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSV Injection.

Back to Category Index

THE BIG BAD WOLF - XSS AND MAINTAINING ACCESS

  • Website: http://www.paulosyibelo.com/2018/06/the-big-bad-wolf-xss-and-maintaining.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: THE BIG BAD WOLF - XSS AND MAINTAINING ACCESS is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

The bug bounty program that changed my life

  • Website: http://10degres.net/the-bug-bounty-program-that-changed-my-life/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The bug bounty program that changed my life is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

The Bug Hunters Methodology v2.1

  • Website: https://docs.google.com/presentation/d/1VpRT8dFyTaFpQa9jhehtmGaC7TqQniMSYbUdlHN6VrY/edit?usp=sharing
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Bug Hunters Methodology v2.1 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

  • Website: https://speakerdeck.com/filedescriptor/the-cookie-monster-in-your-browsers
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Cookie Monster in Your Browsers is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

The Daily Swig - Web security digest

  • Website: https://portswigger.net/daily-swig
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Daily Swig - Web security digest is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Digests.

Back to Category Index

The Definitive Security Data Science and Machine Learning Guide

  • Website: http://www.covert.io/the-definitive-security-datascience-and-machinelearning-guide/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Definitive Security Data Science and Machine Learning Guide is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by JASON TROS.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

The inception bar: a new phishing method

  • Website: https://jameshfisher.com/2019/04/27/the-inception-bar-a-new-phishing-method/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The inception bar: a new phishing method is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

The Magic of Learning

  • Website: https://bitvijays.github.io/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Magic of Learning is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Digests.

Back to Category Index

The Register

  • Website: http://www.theregister.co.uk/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The Register is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Biting the hand that feeds IT.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > Forums.

Back to Category Index

The world of Site Isolation and compromised renderer

  • Website: https://speakerdeck.com/shhnjk/the-world-of-site-isolation-and-compromised-renderer
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: The world of Site Isolation and compromised renderer is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index

Three roads lead to Rome

  • Website: http://blogs.360.cn/360safe/2016/11/29/three-roads-lead-to-rome-2/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Three roads lead to Rome is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Backend (core of Browser implementation, and often refers to C or C++ part).

Back to Category Index

TWITTER XSS + CSP BYPASS

  • Website: http://www.paulosyibelo.com/2017/05/twitter-xss-csp-bypass.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: TWITTER XSS + CSP BYPASS is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > CSP.

Back to Category Index

  • Website: http://zhchbin.github.io/2017/08/30/Uber-XSS-via-Cookie/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Uber XSS via Cookie is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

Unicode Domains are bad and you should feel bad for supporting them

  • Website: https://www.vgrsec.com/post20170219.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Unicode Domains are bad and you should feel bad for supporting them is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > URL.

Back to Category Index

Upgrade self XSS to Exploitable XSS an 3 Ways Technic

  • Website: https://www.hahwul.com/2019/11/upgrade-self-xss-to-exploitable-xss.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Upgrade self XSS to Exploitable XSS an 3 Ways Technic is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

uxss-db

  • Website: https://github.com/Metnew/uxss-db
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: uxss-db is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Collection of UXSS CVEs with PoCs 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 > PoCs > Database.

Back to Category Index

VWGen

  • Website: https://github.com/qazbnm456/VWGen
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: VWGen is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Vulnerable Web applications 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 > Code Generating.

Back to Category Index

WCTF2019: Gyotaku The Flag

  • Website: https://westerns.tokyo/wctf2019-gtf/wctf2019-gtf-slides.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: WCTF2019: Gyotaku The Flag is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

Web Application Firewall (WAF) Evasion Techniques

  • Website: https://medium.com/secjuice/waf-evasion-techniques-718026d693d8
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Web Application Firewall (WAF) Evasion Techniques is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > WAF.

Back to Category Index

Web Application Firewall (WAF) Evasion Techniques #2

  • Website: https://medium.com/secjuice/web-application-firewall-waf-evasion-techniques-2-125995f3e7b0
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Web Application Firewall (WAF) Evasion Techniques #2 is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Evasions > WAF.

Back to Category Index

Web Application Security Zone by Netsparker

  • Website: https://www.netsparker.com/blog/web-security/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Web Application Security Zone by Netsparker is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Digests.

Back to Category Index

webshell

  • Website: https://github.com/tennc/webshell
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: webshell is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: This is a webshell open source project 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 > Webshell.

Back to Category Index

Webshell-Sniper

  • Website: https://github.com/WangYihang/Webshell-Sniper
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Webshell-Sniper is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Manage your website via terminal 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 > Webshell.

Back to Category Index

wfuzz

  • Website: https://github.com/xmendez/wfuzz
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: wfuzz is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Web application bruteforcer 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 > Fuzzing.

Back to Category Index

What is a Side-Channel Attack ?

  • Website: https://www.csoonline.com/article/3388647/what-is-a-side-channel-attack-how-these-end-runs-around-encryption-put-everyone-at-risk.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: What is a Side-Channel Attack ? is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Crypto.

Back to Category Index

What is going on with OAuth 2.0? And why you should not use it for authentication.

  • Website: https://medium.com/securing/what-is-going-on-with-oauth-2-0-and-why-you-should-not-use-it-for-authentication-5f47597b2611
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: What is going on with OAuth 2.0? And why you should not use it for authentication. is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > OAuth.

Back to Category Index

What You Didn't Know About XML External Entities Attacks

  • Website: https://2013.appsecusa.org/2013/wp-content/uploads/2013/12/WhatYouDidntKnowAboutXXEAttacks.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: What You Didn't Know About XML External Entities Attacks is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

Whonow DNS Server

  • Website: https://github.com/brannondorsey/whonow
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Whonow DNS Server is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: A malicious DNS server for executing DNS Rebinding attacks on the fly 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 > DNS Rebinding.

Back to Category Index

Why mail() is dangerous in PHP

  • Website: https://blog.ripstech.com/2017/why-mail-is-dangerous-in-php/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Why mail() is dangerous in PHP is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Webmail.

Back to Category Index

Wiping Out CSRF

  • Website: https://medium.com/@jrozner/wiping-out-csrf-ded97ae7e83f
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Wiping Out CSRF is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > CSRF - Cross-Site Request Forgery.

Back to Category Index

X-Frame-Options: All about Clickjacking?

  • Website: https://github.com/cure53/Publications/blob/master/xfo-clickjacking.pdf?raw=true
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: X-Frame-Options: All about Clickjacking? is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Clickjacking.

Back to Category Index

XML external entity (XXE) injection

  • Website: https://portswigger.net/web-security/xxe
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XML external entity (XXE) injection is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

XML Out-Of-Band Data Retrieval

  • Website: https://media.blackhat.com/eu-13/briefings/Osipov/bh-eu-13-XML-data-osipov-slides.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XML Out-Of-Band Data Retrieval is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by Timur Yunusov and Alexey Osipov.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 > FTP Injection.

Back to Category Index

XML Schema, DTD, and Entity Attacks

  • Website: https://www.vsecurity.com/download/publications/XMLDTDEntityAttacks.pdf
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XML Schema, DTD, and Entity Attacks is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by and Omar Al Ibrahim.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

XSS Challenges

  • Website: http://xss-quiz.int21h.jp/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS Challenges is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Series of XSS challenges - Written by yamagata21.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

XSS game

  • Website: https://xss-game.appspot.com/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS game is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Google XSS Challenge - Written by Google.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

XSS in Google Colaboratory + CSP bypass

  • Website: https://blog.bentkowski.info/2018/06/xss-in-google-colaboratory-csp-bypass.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS in Google Colaboratory + CSP bypass is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

XSS via a spoofed React element

  • Website: http://danlec.com/blog/xss-via-a-spoofed-react-element
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS via a spoofed React element is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > ReactJS.

Back to Category Index

XSS without HTML: Client-Side Template Injection with AngularJS

  • Website: http://blog.portswigger.net/2016/01/xss-without-html-client-side-template.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS without HTML: Client-Side Template Injection with AngularJS is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > AngularJS.

Back to Category Index

XSS without parentheses and semi-colons

  • Website: https://portswigger.net/blog/xss-without-parentheses-and-semi-colons
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS without parentheses and semi-colons is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

XSS-Auditor — the protector of unprotected and the deceiver of protected.

  • Website: https://medium.com/bugbountywriteup/xss-auditor-the-protector-of-unprotected-f900a5e15b7b
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS-Auditor — the protector of unprotected and the deceiver of protected. is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XSS.

Back to Category Index

XSS.png

  • Website: https://github.com/LucaBongiorni/XSS.png
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XSS.png is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Written by @jackmasa.

Operational value: Security teams commonly use this capability to improve consistency between detection, investigation, and response decisions, especially when alerts, evidence collection, and triage ownership are distributed across multiple teams.

Typical deployment pattern: Implementations usually start with scoped pilot coverage, baseline logging/telemetry validation, and explicit runbook mapping so analysts understand when to escalate, contain, 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 Category Index

xsschop

  • Website: https://xsschop.chaitin.cn/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: xsschop is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: XSS detection engine 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 > Detecting.

Back to Category Index

XXE

  • Website: https://phonexicum.github.io/infosec/xxe.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XXE is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 Category Index

XXE in WeChat Pay Sdk ( WeChat leave a backdoor on merchant websites)

  • Website: http://seclists.org/fulldisclosure/2018/Jul/3
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XXE in WeChat Pay Sdk ( WeChat leave a backdoor on merchant websites) is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

XXE OOB exploitation at Java 1.7+

  • Website: http://lab.onsec.ru/2014/06/xxe-oob-exploitation-at-java-17.html
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XXE OOB exploitation at Java 1.7+ is used in web & api security programs to support application-layer threat prevention and request/response validation. Source summaries describe it as: Exfiltration using FTP protocol - 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 > FTP Injection.

Back to Category Index

XXE OOB extracting via HTTP+FTP using single opened port

  • Website: https://skavans.ru/en/2017/12/02/xxe-oob-extracting-via-httpftp-using-single-opened-port/
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: XXE OOB extracting via HTTP+FTP using single opened port is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > XXE.

Back to Category Index

Zen Rails Security Checklist

  • Website: https://github.com/brunofacca/zen-rails-security-checklist
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Zen Rails Security Checklist is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Rails.

Back to Category Index

Особенности Safari в client-side атаках

  • Website: https://bo0om.ru/safari-client-side
  • Model: Open Source
  • Category: Web & API Security
  • Source Lists: Awesome Web Security

What it does: Особенности Safari в client-side атаках is used in web & api security programs to support application-layer threat prevention and request/response validation. 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 > Browser Exploitation > Frontend (like SOP bypass, URL spoofing, and something like that).

Back to Category Index