Customize this training

Get a certificate — $15$5

CompTIA PenTest+ (PT0-003) Exam Prep

CompTIA PenTest+ (PT0-003) Exam Prep

Prepare for PenTest+ PT0-003: revise the five official domains, from scoping and reconnaissance to attacks, lateral movement and reporting, then test yourself on original scenario questions.

What you will learn

  • Summarise the exam format and the pre-engagement activities that make a penetration test authorised, scoped and legal.
  • Compare testing frameworks and explain how to communicate, report and recommend remediation.
  • Apply passive and active reconnaissance, enumeration and basic scripting to map a target.
  • Perform vulnerability discovery, validate results and prioritise findings using CVSS, EPSS and business context.
  • Select and explain network, credential and wireless attacks and the controls that stop them.
  • Select and explain host, web, API, cloud, social engineering and physical attacks and their mitigations.
  • Describe post-exploitation, persistence, lateral movement, exfiltration and cleanup within the rules of engagement.

Modules

  1. Exam facts and pre-engagement activities
  2. Frameworks, communication, reporting and remediation
  3. Reconnaissance and enumeration
  4. Vulnerability discovery and analysis
  5. Network, credential and wireless attacks
  6. Host, web, cloud and social engineering attacks
  7. Post-exploitation, lateral movement and cleanup

Course facts

Level
Exam preparation
Estimated study time
about 2 hours
Final assessment
50 questions · Pass mark 70%
Available in
English
Price
Free. Optional verifiable certificate: $5
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

Security analysts, junior penetration testers, SOC and network staff, and IT professionals preparing for CompTIA PenTest+ PT0-003.

Prerequisites

Solid networking basics (TCP/IP, DNS, common ports), Windows and Linux command-line use, and Security+ level knowledge. CompTIA recommends 3 to 4 years of hands-on penetration testing experience and Network+ and Security+ or equivalent; this is a recommendation, not an entry requirement. Practise only in a lab you own or are authorised to use.

Course content

1. Exam facts and pre-engagement activities

CompTIA PenTest+ validates the skills of a working penetration tester: plan an engagement, find and analyse weaknesses, attack them safely, move through a network, and report in a way the client can act on. This course covers the current version, PT0-003.

FactPT0-003 (confirmed on comptia.org)
Launch / previous version retired17 December 2024 / 17 June 2025 (PT0-002)
QuestionsMaximum of 90, multiple choice and performance-based
Time165 minutes
Passing score750 on a scale of 100 to 900
Recommended experience3 to 4 years in a penetration testing role, plus Network+ and Security+ or equivalent knowledge

The five domains and their weights drive how this course is built:

  1. Engagement Management (13%) — scoping, rules of engagement, frameworks, communication, reporting.
  2. Reconnaissance and Enumeration (21%) — OSINT, scanning, enumeration, reading and modifying scripts.
  3. Vulnerability Discovery and Analysis (17%) — scanners, validation, prioritisation, specialised systems.
  4. Attacks and Exploits (35%) — network, authentication, host, web, cloud, wireless, social engineering, automation.
  5. Post-exploitation and Lateral Movement (14%) — persistence, pivoting, exfiltration, cleanup.

Performance-based questions (PBQs) put you in a simulated task, for example reading scan output, fixing a script or ordering the steps of an attack. They appear at the start of the exam. A common approach is to flag a long PBQ, answer the multiple-choice questions, and return to it.

2. Frameworks, communication, reporting and remediation

A methodology gives your test structure and gives the client confidence that it was complete. The exam asks you to match each framework to its purpose.

FrameworkWhat it is used for
PTES (Penetration Testing Execution Standard)End-to-end phases: pre-engagement, intelligence gathering, threat modelling, vulnerability analysis, exploitation, post-exploitation, reporting
NIST SP 800-115US technical guide to security testing: planning, discovery, attack, reporting
OSSTMMISECOM manual that measures operational security; a metrics-based approach
OWASP Top 10 and WSTGWeb application risk categories and the Web Security Testing Guide
OWASP MASVSMobile application security verification standard
MITRE ATT&CKKnowledge base of adversary tactics and techniques; used to plan, label and report actions
CRESTAccreditation body and testing standards for providers and testers
Purdue ModelReference architecture for industrial control system networks, in levels

Threat modelling helps decide where to focus. STRIDE classifies threats (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege). DREAD scores them (damage, reproducibility, exploitability, affected users, discoverability). OCTAVE is an organisation-level risk method.

Match the target to the framework.

3. Reconnaissance and enumeration

Recon builds the map. Passive reconnaissance collects information without sending traffic to the target's systems, so it cannot be detected by the target. Active reconnaissance touches the target and can be logged.

SourceWhat you learnTypical tools
WHOIS and registriesRegistrar, contacts, name servers, IP ownershipwhois, regional registry sites
DNS recordsHosts, mail servers, SPF, subdomainsdig, nslookup, dnsrecon
Certificate transparencySubdomains from issued certificatescrt.sh, Censys
Internet scan databasesExposed services and banners, without touching the hostShodan, Censys
Search engines and archivesDocuments, login pages, old versionsGoogle dorks, Wayback Machine
Code and paste sitesLeaked keys and credentialsGitHub search, secret scanners
People and jobsEmployees, technologies, email formatsLinkedIn, job ads, theHarvester, Maltego, recon-ng

Passive sources the exam expects you to know.

Examples of dorks: site:example.com filetype:pdf finds public documents, and inurl:admin hunts for login pages. Document metadata (author names, software versions, internal paths) can be read with tools such as exiftool.

A DNS zone transfer (AXFR) request to a misconfigured name server returns the whole zone. Because it queries the target's server, it is active, and it should be in scope.

4. Vulnerability discovery and analysis

Scanners find candidates. The tester decides which are real. Know which kind of scan answers which question.

Scan typeWhat it examinesExamples
Network vulnerability scanHosts and services for known flaws and misconfigurationsNessus, OpenVAS, Nuclei
Credentialed (authenticated)Patch levels and settings from inside the host; fewer false positivesNessus with an SSH or Windows account
Non-credentialedThe outsider's view of exposed servicesDefault external scan
DASTA running web app, tested from outsideOWASP ZAP, Burp Suite scanner, Nikto
SASTSource code, without running itSemgrep, SonarQube
SCAThird-party libraries and their known flawsOWASP Dependency-Check
Container and IaC scanImages, Dockerfiles, Terraform and cloud templatesTrivy, Grype, Checkov
Secrets scanKeys and passwords in repositoriesgitleaks, truffleHog

Validation. Every result is one of four kinds. A true positive is a real flaw reported. A false positive is reported but not real, so it wastes time and trust. A false negative is a real flaw the scan missed, which is the dangerous one. A true negative is correctly absent.

5. Network, credential and wireless attacks

Network attacks exploit trust that protocols assume. Know the attack, its precondition and the control that stops it.

AttackHow it worksDefence
ARP spoofing (on-path)Forged ARP replies put the attacker between a host and its gatewayDynamic ARP inspection, static entries, encryption end to end
LLMNR / NBT-NS poisoningAttacker answers name queries that DNS could not resolve and captures NetNTLM hashes (Responder)Disable LLMNR and NBT-NS, DNS hygiene
SMB / NTLM relayCaptured authentication is forwarded to another server (ntlmrelayx)SMB signing, disable NTLM, EPA
VLAN hoppingSwitch spoofing (trunk negotiation) or double tagging reaches another VLANDisable DTP, set ports to access mode, change native VLAN
DNS poisoningFalse records cached by a resolverDNSSEC, randomised ports and IDs
Denial of serviceExhaust bandwidth, state or CPURate limiting, scrubbing; usually out of scope for tests
NAC bypassMAC spoofing of an allowed device, such as a printer802.1X with certificates, profiling
Default and weak credentialsAdmin panels, SNMP "public", Telnet devicesCredential change on deployment, inventory

6. Host, web, cloud and social engineering attacks

With a low-privilege foothold, the next goal is usually more privilege. Enumerate first, then pick the weakness that fits.

PlatformCommon escalation pathsEnumeration help
WindowsUnquoted service paths, weak service or folder permissions, AlwaysInstallElevated, DLL hijacking, token impersonation (SeImpersonatePrivilege, the "Potato" family), stored credentials, unpatched kernelwhoami /priv, WinPEAS, PowerUp, Seatbelt
LinuxSUID binaries, sudo rights (sudo -l and GTFOBins), writable cron jobs or scripts, capabilities, PATH hijacking, weak file permissions, kernel exploitsid, find / -perm -4000, LinPEAS

Each path has a cause and a fix. An unquoted service path is fixed by quoting it and restricting folder write access. A dangerous SUID binary is removed from the SUID list. A sudo rule that allows a shell-capable program is narrowed to exact commands.

  1. Who and where — user, groups, privileges, OS version, patches.
  2. What runs — services, scheduled tasks, cron, installed software.
  3. What is writable — files, folders and registry keys that privileged processes use.
  4. What is stored — credentials in files, history, configuration and memory.
  5. Choose the least disruptive route — avoid kernel exploits on production when a configuration flaw works.

7. Post-exploitation, lateral movement and cleanup

After access, a tester asks three questions: where am I, what can I reach, and what proves impact? Everything stays inside the RoE.

  1. Situational awareness — whoami, hostname, ipconfig or ip a, net user, id, uname -a, running processes, installed security tools.
  2. Privilege review — groups, token privileges, local admin rights.
  3. Credential discovery — configuration files, shell history, browser stores, the SAM database, NTDS.dit on domain controllers, /etc/shadow, memory (LSASS).
  4. Domain mapping — BloodHound and SharpHound, PowerView or ldapsearch show attack paths in Active Directory.
  5. Persistence, only when the RoE allows it — to keep access across reboots.
Persistence methodPlatform
Scheduled task, new service, registry Run key, startup folder, WMI event subscriptionWindows
Cron job, systemd service, authorized_keys, shell profile scriptsLinux
New local or domain account, web shell, forged Kerberos ticketsBoth

Because every persistence mechanism leaves something to clean up, keep a timestamped log of what you create, where and under which account. Use clearly named test accounts and tell the client what they are.

Four habits after the first shell.

The full lesson continues in the interactive course on this page.

Sources and references

Unofficial practice course. Not affiliated with, endorsed by or sponsored by CompTIA. CompTIA PenTest+ is a trademark of its owner. Check the current exam outline on CompTIA’s website before you book. The content is for authorised security testing and exam preparation only; testing systems without written permission is illegal.

All courses · Cybersecurity and IT — Free courses, certificate $5 | AMAADOR ACADEMY