Web Pentest — Authorized web pentest: recon, proof-based exploits, report
Web Pentest — Authorized web pentest: recon, proof-based exploits, report
Start with meaning, then move to detail.
This lesson explains Web Pentest — Authorized web pentest: recon, proof-based exploits, report as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, ⚠️ Hard Guardrails — Read Before Every Engagement, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Web Pentest — Authorized web pentest: recon, proof-based exploits, report without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Authorized web pentest: recon, proof-based exploits, report
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03⚠️ Hard Guardrails — Read Before Every Engagement
Read this after the foundation, then connect it to the previous step.
- 04Phase 0: Engagement Setup
Read this after the foundation, then connect it to the previous step.
- 05Phase 1: Pre-Recon (Code Analysis, optional)
Read this after the foundation, then connect it to the previous step.
- 06Phase 2: Recon (Live, Read-Only)
Read this after the foundation, then connect it to the previous step.
- 07Phase 3: Vulnerability Analysis
Read this after the foundation, then connect it to the previous step.
- 08Phase 4: Exploitation (Proof-Based, Conditional)
Read this after the foundation, then connect it to the previous step.
- 09Phase 5: Reporting
Read this after the foundation, then connect it to the previous step.
- 10When to Stop
Finish here to verify the result and special cases.
Copy only after you understand the effect.
ENGAGEMENT=engagement-$(date +%Y%m%d-%H%M%S)
mkdir -p "$ENGAGEMENT"/{evidence,findings,reports}
cd "$ENGAGEMENT"localhost
127.0.0.1
staging.example.com
192.168.1.0/24 # internal lab only, with operator OKnmap -sT -T3 --top-ports 100 -oN evidence/nmap.txt $TARGETRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.