Prerequisites Basic computer literacy and a willingness to document experiments.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Written permission and rules of engagement Asset scope, exclusions and test windows Safe test intensity and communication Evidence handling and reporting ethics Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Rules-of-engagement template OWASP WSTG Test notebook
Hands-on exercise Create a test plan for a deliberately vulnerable local application and define exclusions. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project An assessment plan with scope, contacts, timing and rollback. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria No activity occurs outside the explicitly approved lab. Evidence must be reproducible and tied to Penetration Testing.
Next: Lab networking and target inventory
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Virtual network isolation and snapshots Service discovery concepts Asset inventory and technology identification Baseline traffic and logs Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools VirtualBox/VMware Nmap in a lab Wireshark
Hands-on exercise Inventory only the deliberately vulnerable lab target and compare observed services to its documentation. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A lab asset map and baseline service inventory. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria The target is locally owned/training-only and inventory is reproducible. Evidence must be reproducible and tied to Penetration Testing.
Next: Web protocols and application mapping
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn HTTP methods, headers, cookies and sessions Authentication and authorisation boundaries Input validation and trust boundaries API routes and application architecture Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Browser devtools Burp Suite Community OWASP ZAP
Hands-on exercise Map routes and trust boundaries in a local training app without attacking external systems. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project An application flow diagram and test-case catalogue. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Each test case maps to an in-scope feature and risk hypothesis. Evidence must be reproducible and tied to Penetration Testing.
Next: Common vulnerability classes and safe validation
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Access-control and IDOR concepts Injection and output encoding SSRF, file handling and deserialization concepts CSRF, session and authentication failures Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools OWASP Juice Shop PortSwigger Web Security Academy OWASP ZAP
Hands-on exercise Complete selected authorised labs and write both reproduction notes and remediation. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A lab findings portfolio with evidence and secure fixes. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Findings are reproducible in the training target and include remediation. Evidence must be reproducible and tied to Penetration Testing.
Next: Controlled tooling and evidence quality
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Manual validation before scanner output False-positive verification Rate limits and safe request handling Screenshots, redaction and evidence identifiers Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Burp Suite ZAP Markdown report template
Hands-on exercise Validate one scanner finding manually against a local lab and document uncertainty. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A quality-assured finding record with redacted evidence. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria No finding is reported without manual validation and scope reference. Evidence must be reproducible and tied to Penetration Testing.
Next: Risk assessment and remediation
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn CVSS as one input, not the whole decision Exploitability and compensating controls Root cause and secure design fixes Retest plan and residual risk Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools CVSS calculator OWASP ASVS Issue tracker
Hands-on exercise Write a remediation plan for a lab finding and retest the fixed code. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A risk-ranked report with retest evidence. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Severity has a rationale and fixes are independently verified. Evidence must be reproducible and tied to Penetration Testing.
Next: Professional reporting and debrief
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Executive summary and technical detail Scope and methodology disclosure Limitations and positive controls Confidentiality and secure report handover Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Report template OWASP reporting guidance
Hands-on exercise Present a short debrief based on lab-only findings and answer remediation questions. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A complete assessment report and management summary. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria The report is accurate, scoped, actionable and protects sensitive details. Evidence must be reproducible and tied to Penetration Testing.
Next: Capstone: authorised security assessment
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Scope approval and lab setup Mapping and controlled validation Evidence and risk ranking Remediation and retest Penetration Testing specialization: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools OWASP Juice Shop Burp or ZAP OWASP WSTG
Hands-on exercise Perform the full engagement only against the local training application and verify fixes. Context for this route: Penetration testing: focus on scope, rules of engagement, asset mapping, controlled validation, evidence and remediation reporting. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A complete portfolio assessment with rules of engagement, findings, fixes and retest results. The outcome must directly demonstrate Penetration Testing, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria All actions stay in scope and the report distinguishes verified findings from assumptions. Evidence must be reproducible and tied to Penetration Testing.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete