← Back to all products

Penetration Testing Toolkit

$49

Automated security testing scripts, vulnerability scanners, report templates, and methodology checklists.

📁 28 files
MarkdownShellJSONPythonYAMLAWS

📄 Product Preview

Try the interactive reader and demo tools below, or get the full product with all content unlocked.

📖 Interactive Reader (Free Preview) ⚙ Try Demo Tools 📦 Download Free Sample

📁 File Structure 28 files

penetration-testing-toolkit/ ├── LICENSE ├── README.md ├── docs/ │ ├── cvss-v3.1-scoring-guide.md │ ├── engagement-checklist.md │ ├── methodology.md │ ├── reporting-guide.md │ └── rules-of-engagement.md ├── examples/ │ ├── findings.example.json │ ├── sample-report.md │ └── scope.example.yaml ├── free-sample.zip ├── guide/ │ ├── 01-engagement-methodology.md │ ├── 02-scoping-checklist.md │ ├── 03-vulnerability-scoring.md │ ├── 04-reporting-findings.md │ └── 05-sample-report.md ├── index.html ├── scripts/ │ └── preflight_scope_check.sh ├── src/ │ ├── cvss.py │ ├── report_generator.py │ ├── scope_guard.py │ └── wrappers/ │ ├── common.py │ ├── nikto_wrapper.py │ ├── nmap_wrapper.py │ └── testssl_wrapper.py └── templates/ ├── findings-template.md ├── report-template.md └── rules-of-engagement-template.md

📖 Documentation Preview README excerpt

Penetration Testing Toolkit (Defensive / Professional)

A complete, authorization-first workflow for running professional security

assessments of systems you own or are contractually permitted to test. It

gives you the methodology, the safety guardrails, the scoring, and the reporting

to do the job like a consultancy — without shipping a single weaponized payload.

This toolkit is deliberately defensive. It contains **no exploits, no malware,

and no attack code**. What it provides instead:

  • A five-phase methodology (pre-engagement → recon → scan → analyze → report).
  • Scope-enforcing, dry-run-by-default wrappers around standard tools (nmap,

nikto, testssl.sh) that refuse to touch anything outside your written scope.

  • A correct, standalone CVSS v3.1 calculator so every finding is scored

consistently.

  • A report generator that turns a findings file into a clean Markdown report.
  • Ready-to-fill Rules of Engagement, findings, and report templates.
  • Engagement checklists that gate each phase.

Everything runs on Python 3.10+ standard library only — no pip install.

Table of Contents

1. [Who this is for](#who-this-is-for)

2. [The defensive promise](#the-defensive-promise)

3. [What's included](#whats-included)

4. [Quick start](#quick-start)

5. [The five-phase workflow](#the-five-phase-workflow)

6. [File-by-file guide](#file-by-file-guide)

7. [Safety & legal](#safety--legal)

8. [FAQ](#faq)

9. [License](#license)

10. [Support](#support)

Who this is for

  • Security engineers / consultants who want a repeatable, professional process.
  • Blue teams validating their own estate before an adversary does.
  • Engineering leads who need to commission or interpret a pentest.
  • Learners building disciplined, ethical testing habits with real artifacts.

Assumes comfort with the command line and basic networking. No prior offensive-

security experience required.

The defensive promise

This kit is safe to keep in a corporate repo. By design:

  • No exploit code ships here. Validation of findings is manual and minimal.
  • Scope is enforced in code. The wrappers call a scope guard

(src/scope_guard.py) and refuse to run against any target not listed in

your authorized scope file. "Deny wins."

  • Dry-run is the default. Wrappers print the exact command they would run

and exit, until you pass both --run and --i-am-authorized.

... continues with setup instructions, usage examples, and more.

📄 Code Sample .sh preview

scripts/preflight_scope_check.sh#!/usr/bin/env bash # # preflight_scope_check.sh — final guardrail before any active testing. # # Confirms a target is authorized by the engagement scope file BEFORE you point a # tool at it. It delegates to the authoritative Python scope guard # (src/scope_guard.py) for correct CIDR/host logic, and falls back to a literal # membership check if Python is unavailable. # # Defensive use only. A "blocked" result means: do not test that target. # # Usage: # ./preflight_scope_check.sh <target> <scope-file> # ./preflight_scope_check.sh 203.0.113.10 ../examples/scope.example.yaml # # Exit codes: 0 = in scope, 3 = out of scope / blocked, 2 = usage/scope error. set -euo pipefail SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" SRC_DIR="$(cd "${SCRIPT_DIR}/../src" && pwd 2>/dev/null || echo "")" usage() { echo "usage: $(basename "$0") <target> <scope-file>" >&2 exit 2 } if [[ $# -ne 2 ]]; then usage fi TARGET="$1" SCOPE_FILE="$2" if [[ ! -f "${SCOPE_FILE}" ]]; then echo "error: scope file not found: ${SCOPE_FILE}" >&2 exit 2 fi # Preferred path: authoritative check via the Python scope guard (handles CIDRs,
Buy Now — $49 Back to Products