PJPT study materials
PJPT study resources

PJPT study plan

PJPT · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Reconnaissance and Information Gathering & Legal Documentation and Report Writing

  • Map the seven exam domains into a personal tracker and mark the four heaviest (1, 2, 4, 5) as priority blocks

  • Configure a lab (two Linux VMs, one Windows VM, one intentionally vulnerable web app) and verify connectivity and snapshots

  • Execute passive OSINT against a practice target: WHOIS, DNS records, certificate transparency, and search-engine dorking

  • Draft a rules-of-engagement and scope template covering authorization, time window, excluded hosts, and emergency contact

  • Write a one-page engagement kickoff memo for a fictional client using that template

Your checkpoint

A lab build sheet plus a completed fictional scope/authorization document and OSINT notes for one practice domain

Week 2

Reconnaissance and Information Gathering & Scanning and Enumeration

  • Perform active reconnaissance: zone transfer attempts, subdomain brute force, and virtual host discovery against the practice target

  • Run host discovery and full TCP/UDP port scans, then compare service detection results between two scanners

  • Capture and document every open port with service, version, and confidence level

  • Build a reusable recon checklist that separates passive from active steps

  • Time-box a full recon pass and record how long each stage took

Your checkpoint

A consolidated recon and port-scan report for the practice target with a timed checklist

Week 3

Scanning and Enumeration

  • Enumerate SMB, SSH, HTTP, and DNS services and record banners, shares, users, and versions

  • Use directory and file brute forcing against the web app and classify findings by severity

  • Identify at least three plausible entry points and rank them by likelihood and impact

  • Document enumeration output in a structured findings table with evidence screenshots

  • Practice writing a finding in the standard format: title, description, evidence, impact, remediation

Your checkpoint

An enumeration findings table with at least five entries, each written in full finding format

Week 4

Exploitation Basics

  • Exploit at least two known-vulnerable services in the lab and capture proof of access

  • Perform password attacks: online brute force against a lab service and offline cracking of a captured hash

  • Demonstrate a public exploit against the practice web app and explain each step of the chain

  • Practice shell stabilization and basic post-exploitation enumeration on a compromised host

  • Write a proof-of-concept section for each successful exploit with reproduction steps

Your checkpoint

Two documented proof-of-concept write-ups with captured evidence and a reproduction checklist

Week 5

Active Directory Penetration Testing

  • Stand up a small Active Directory lab with a domain controller and two member hosts

  • Enumerate the domain: users, groups, computers, trusts, and share permissions using built-in and community tools

  • Execute and document at least two credential-access techniques against the lab domain

  • Perform a lateral movement step and record the exact commands and resulting access

  • Map each AD technique used to a detection opportunity a defender could implement

Your checkpoint

An AD attack-path diagram from initial foothold to domain compromise, with commands and detection notes

Week 6

Active Directory Penetration Testing & Web Application Penetration Testing

  • Attempt at least one domain privilege escalation path and document the outcome whether or not it succeeds

  • Test the practice web app for injection, broken access control, and authentication flaws

  • Test for cross-site scripting and file upload weaknesses and record payloads and results

  • Prioritize web findings by exploitability and business impact rather than scanner severity alone

  • Write remediation guidance for each web finding that a developer could act on directly

Your checkpoint

A web application findings section with at least four vulnerabilities, payloads, and developer-ready remediation

Week 7

Wireless Attacks & Web Application Penetration Testing

  • Set up a wireless lab with a monitor-mode adapter and capture a handshake from your own access point

  • Crack the captured handshake and document the wordlist and time required

  • Identify and explain at least three wireless attack categories and the controls that mitigate each

  • Review all prior findings and consolidate them into a single severity-ranked register

  • Re-test two earlier findings after applying the documented fix to confirm remediation

Your checkpoint

A wireless lab write-up plus a consolidated, severity-ranked findings register for the whole engagement

Week 8

Legal Documentation and Report Writing

  • Assemble a full penetration test report: executive summary, scope, methodology, findings, and appendices

  • Write an executive summary in plain language with no jargon and a clear risk narrative

  • Apply a consistent severity rating method and justify each rating in one sentence

  • Perform a peer-style self-review against a report quality checklist and fix every gap

  • Prepare a ten-minute verbal debrief script summarizing the top three risks and recommended actions

Your checkpoint

A complete practice penetration test report with executive summary, rated findings, and debrief script

Milestones

Week 2: Lab is fully operational and you can complete a timed recon and port-scan pass on the practice target without referring to notes

Week 4: You hold documented proof of access on at least two distinct services and can explain each exploit step aloud

Week 6: You have reached domain compromise or a documented dead end in the AD lab, and at least four web findings are written in full format

Week 8: A complete report passes your own quality checklist with every finding rated, evidenced, and paired with remediation