Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
securityskills/pentest-engagement-methodologyWeb and bug bounty

pentest-engagement-methodology

⁨Execute an authorized penetration test end-to-end, from scoping and rules of engagement through reconnaissance, exploitation, post-exploitation, and reporting. Use when planning or running an offensive security engagement.⁩

v2026.8.26-b2b6b523 installs+3 in 7 days0 Starssynced 19 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install securityskills/pentest-engagement-methodology

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
BYjwF30Tob…i4h+5vBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package1d4743ef…cd2229dc
1d4743ef0153…6f8bcd2229dc1 file · ⁦1.4 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/securityskills/skills/tree/main/pentest/methodology/pentest-engagement-methodology@b2b6b52

Work through a structured, repeatable methodology for authorized penetration tests.

When to Use

  • You are planning or executing a penetration test with written authorization
  • You need to ensure coverage and consistency across an engagement
  • You are preparing deliverables for a client or internal stakeholder

Hard Rules

  1. Never test without written authorization. Verify the scope statement, rules of engagement (RoE), and emergency contacts before touching anything.
  2. Stay in scope. Check every IP, domain, and URL against the scope document before testing. If unsure, ask — do not guess.
  3. No destructive actions unless explicitly authorized: no DoS, no data destruction, no production brute-force lockouts.

Phases

1. Scoping and Planning

  • Capture in-scope assets, out-of-scope assets, testing windows, and escalation paths
  • Identify the engagement type: black/grey/white box
  • Agree on evidence-handling and data-destruction requirements
  • Prepare the test plan and get sign-off

2. Reconnaissance

  • Passive first: certificate transparency, DNS records, public code, job postings
  • Active second: port scanning, service fingerprinting, subdomain enumeration
  • Build an asset inventory with owner notes and observed technologies

3. Vulnerability Analysis

  • Map the attack surface to likely vulnerability classes per technology
  • Manual verification of every finding — scanners produce noise; you produce evidence
  • Rank candidate findings by exploitability and business impact

4. Exploitation

  • Use the least invasive proof that proves the finding (POC > payload)
  • Document: request, response, tool, version, and timestamp for every exploit attempt
  • Stop and escalate to the client if you reach a critical system boundary

5. Post-Exploitation

  • Demonstrate impact: what data or access the foothold yields
  • Attempt privilege escalation and lateral movement only within RoE
  • Clean up: remove shells, scripts, and artifacts; record what was created where

6. Reporting

  • Executive summary: business risk in plain language
  • Findings: title, severity (CVSS), affected assets, reproduction steps, evidence, remediation advice
  • Retest criteria and positive observations

Output Format

Deliver: test plan, asset inventory, findings report with evidence, cleanup log, and a debrief agenda.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLicense · No license found

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.8.26-b2b6b52Nov 13, 2026b2b6b521d4743efSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login