Study guide

2.1 Scope, Rules of Engagement, and Agreements

CompTIA PenTest+ PT0-003

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current PT0-003 Exam Facts 1.2 Format, PBQs, Scoring, and Retake Policy 1.3 Recertification, CEUs, and Career Fit

2 Pre-Engagement Planning

2.1 Scope, Rules of Engagement, and Agreements 2.2 Target Selection and Assessment Types 2.3 Shared Responsibility, Legal Authorization, and Ethics

3 Collaboration, Frameworks, and Threat Modeling

3.1 Collaboration, Escalation, and Stakeholder Communication 3.2 Testing Frameworks and Methodologies 3.3 Threat Modeling: STRIDE, DREAD, and OCTAVE

4 Reporting and Remediation

4.1 Penetration Test Report Components 4.2 Findings Analysis and Remediation Recommendations

5 Information Gathering

5.1 Active vs Passive Reconnaissance 5.2 OSINT Sources and Techniques 5.3 DNS, Certificate Transparency, and Search Engine Enumeration 5.4 Network Recon, Protocol Scanning, Sniffing, and Banner Grabbing

6 Enumeration Techniques

6.1 OS Fingerprinting, Service Discovery, and Host Discovery 6.2 DNS, Directory, Share, and Account Enumeration 6.3 Secrets, Permissions, and Wireless Enumeration 6.4 WAF Enumeration, Web Crawling, and Attack Path Mapping

7 Recon Scripting and Tools

7.1 Modifying Bash, Python, and PowerShell for Recon 7.2 Recon and Enumeration Tools

8 Vulnerability Scan Types

8.1 Network, Host, Authenticated, and Wireless Scans 8.2 SAST, DAST, IAST, SCA, IaC, and Mobile Scans 8.3 Container, Secrets, and ICS Vulnerability Assessment 8.4 Core Vulnerability Scanners (Nessus, OpenVAS, Nikto)

9 Scan Analysis and Physical Security

9.1 Specialized Discovery Tools 9.2 Validating Scan, Recon, and Enumeration Results 9.3 Public Exploit Selection and Scripted Validation 9.4 Physical Security Concepts for PenTests

10 Attack Prioritization and Preparation

10.1 Target Prioritization: CVSS, CVE, CWE, and EPSS 10.2 Exploit Selection, Customization, and Attack Documentation

11 Network Attacks

11.1 On-Path, VLAN Hopping, Relay, and Multihomed Hosts 11.2 Default Credentials, Misconfigured Services, Packet Crafting, and Certificate Services

12 Authentication Attacks

12.1 Pass-the-Hash, Pass-the-Ticket, Pass-the-Token, and Kerberos Attacks 12.2 Password Attacks, MFA Fatigue, LDAP Injection, OIDC, and SAML

13 Host-Based Attacks

13.1 Privilege Escalation and Credential Dumping 13.2 Process Injection, Security Bypass, and Host Attack Tools

14 Web Application Attacks

14.1 SQL, Command, XSS, and SSTI Injection 14.2 CSRF, SSRF, Deserialization, IDOR, and Directory Traversal 14.3 LFI/RFI, Web Shells, API Abuse, JWT, and Session Hijacking

15 Cloud Attacks

15.1 IAM Misconfiguration, Metadata Service, and Exposed Storage 15.2 Container Escape, Supply Chain, and Cloud Attack Tools

16 Wireless and Social Engineering

16.1 Wireless Attacks and Tools 16.2 Phishing, Spearphishing, Whaling, Vishing, and Smishing 16.3 Physical Social Engineering and SE Tools

17 Specialized Systems

17.1 Mobile Attacks and AI Prompt/Model Attacks 17.2 OT/ICS, NFC, RFID, and Bluetooth Attacks

18 Attack Scripting and BAS

18.1 PowerShell, Python, and Bash Attack Automation 18.2 Breach and Attack Simulation (Caldera, Infection Monkey, Atomic Red Team)

19 Persistence

19.1 Scheduled Tasks, Services, Accounts, and Shells 19.2 C2, Backdoors, Rootkits, and Security-Control Tampering

20 Lateral Movement

20.1 Pivoting, Relays, and Additional Credential Capture 20.2 Remote Services: SMB, RDP, WinRM, WMI, SSH, and Others 20.3 Lateral Movement Tools and LOLbins

21 Exfiltration and Cleanup

21.1 Staging and Exfiltration 21.2 Cleanup, Restoration, and Artifact Preservation

2.1 Scope, Rules of Engagement, and Agreements

Key Takeaways Explain This Topic AI

PT0-003 Domain 1 (Engagement Management) is 13% of the exam; a scan against the wrong CIDR, outside the testing window, or without written permission is unauthorized access, not a finding.

Scope is limited by privacy and security regulations, frameworks, and standards (for example HIPAA, GDPR, PCI DSS, ISO 27001, NIST) even when a client wants everything tested.

Rules of engagement must document exclusions, the escalation process (including an emergency stop), and the testing window before any scan or exploit starts.

An MSA (master agreement) sets the ongoing commercial relationship; a statement of work defines this engagement's targets, deliverables, and timeline.

An NDA protects confidential data learned during the test but does not authorize attacking systems; provider terms of service can still forbid a test the customer signed.

Last updated: August 2026

Pre-engagement work is the unglamorous part of CompTIA PenTest+ Domain 1, and it is also where engagements and careers die. Engagement Management is 13 percent of PT0-003. Objective 1.1 asks you to summarize pre-engagement activities because a technically perfect exploit against the wrong network, at the wrong hour, or without written permission is not a finding — it is unauthorized access. Treat scope , rules of engagement (RoE) , and agreements as the control plane of the test. They decide what is legal before any scanner process starts.

Scope definition: privacy and security constraints

Scope answers two questions: what may we touch, and under which constraints? PT0-003 groups the first inputs as regulations, frameworks, and standards covering privacy and security . Those clauses are not decoration in a SoW appendix. They can forbid techniques, forbid data retention, require extra approvals, or force synthetic test accounts instead of production identities.

Privacy constraints govern personal data: names, email addresses, government IDs, account numbers, health records, precise location, and cardholder data. A hospital that wants its patient portal tested is still bounded by HIPAA: minimum-necessary access, a business associate agreement if testers will see electronic protected health information (ePHI), and a hard answer to whether production records may be copied into a laptop notes folder. A European SaaS tenant may be subject to GDPR, under which a screenshot of a users table is personal-data processing, not just a pretty evidence file. Consumer brands may sit under CCPA/CPRA-style rules that limit how long you keep resident data. Payment environments pull in PCI DSS duties to protect account data while still showing that the cardholder data environment was tested.

Security constraints govern how systems must be protected and how testing itself is controlled. ISO/IEC 27001 and SOC 2 Type II programs often require independent testing of named controls and a paper trail of authorization. The NIST Cybersecurity Framework and CIS Controls give the client a language to map findings. NIST SP 800-115 describes technical testing techniques and is the sort of how-we-test standard a mature RoE will cite. PCI DSS, FedRAMP, and similar programs can prohibit denial-of-service, require notice to a cloud provider, or restrict tests that could affect other tenants.

Exam trap: a vice president cannot waive a statute. If the client says to ignore GDPR because this is only a lab, you document the legal constraint, reduce collection, anonymize, or decline. Scope is the intersection of what the client wants and what the law and third-party contracts allow.

Rules of engagement: exclusions, escalation, and testing window

CompTIA's PT0-003 RoE bullets are exclusions , escalation process , and testing window . Inclusions still must be written — never infer them from a marketing site — but exam items and incident reports hammer those three named controls.

Exclusions are assets, people, or techniques you must not touch. Common exclusions include a third-party payment processor, a production database cluster, industrial control or medical devices, ISP-managed routers, a partner VPN, executive laptops, and a ban on phishing customers or partner help desks. Exclusions exist because someone else owns the system, because availability is too fragile, or because a regulator forbids the method. If the SoW authorizes 10.4.0.0/16 and excludes the payment processor, a processor interface that happens to live inside that CIDR is still out of scope. The prefix is a candidate set; the exclusion list is a veto.

Escalation process is who you call, on what channel, and what you stop doing when the test collides with reality. Triggers include a crashed host, a suspected ransomware foothold already in production, possible illegal content, a defender launching incident response against you, or a third party opening an abuse ticket. RoE should name a 24/7 client owner, a tester emergency contact, an out-of-band path that does not depend on the network you might have just broken, and an emergency stop that pauses all scanning and exploitation. Live-fire escalation is not the same as the later written report workflow; this is the brake during the window.

Testing window is the approved clock, including timezone. A realistic contract is Saturday 01:00–05:00 local time so batch jobs, backups, and on-call staff are predictable. A Nessus job still sending probes at 05:30 is out of scope in time even when every IP is in scope in space. If the work must overrun, you stop, escalate, and obtain a written window extension. A sleepy sysadmin typing sure in chat is not an amendment.

RoE should also state data handling (encrypted evidence stores, screenshot redaction, retention and purge dates), whether the test is overt or covert, scan-intensity limits, and whether production credentials may be used. Those clauses support the three official bullets; they do not replace them.

Agreement types: NDA, MSA, SoW, and ToS

PT0-003 lists four agreement types. Memorize what each one does and, just as often, what it does not do. CompTIA's objectives PDF labels the commercial umbrella a master agreement (MSA) ; industry language usually says master service agreement.

Agreement What it typically governs What it does not do

Non-disclosure agreement (NDA) Confidentiality of architecture, credentials, findings, and customer data learned during the work Authorize scanning or exploitation; list CIDR ranges; replace RoE

Master service agreement / master agreement (MSA) Ongoing commercial relationship: rates, invoicing, insurance, limitation of liability, intellectual property, dispute venue Define this week's targets, exclusions, or testing window

Statement of work (SoW) This engagement: objectives, in-scope assets, exclusions, deliverables, timeline, staffing, and usually a pointer to RoE Override a cloud provider's terms of service or a missing authorization letter

Terms of service (ToS) A platform, cloud, or SaaS provider's posted rules for how its service may be used and tested A customer's signature on a SoW cannot legalize a test the provider forbids

Practical order: NDA so you can talk, MSA so you are a vendor, SoW so this test has a scope, RoE so operators have rules, provider ToS checks for every cloud or SaaS target, and a written authorization letter so defenders and law enforcement can see permission. If the SoW and a hallway request conflict, the written SoW wins until it is amended in writing.

Worked scenario: Saturday SaaS window

A SaaS client's SoW lists 10.4.0.0/16 plus app.example.com , excludes the payment processor and the production database cluster, and sets testing to 01:00–05:00 local Saturday.

At 02:10 Nessus, pointed at 10.4.0.0/16 , starts hitting an IP that the asset inventory and reverse DNS identify as the payment processor. Stop. CIDR membership does not cancel an exclusion. Scanning a processor can disrupt cardholder systems owned by a company that never signed your SoW, and it can become an unauthorized-access event against that third party.

At 05:30 a tester is still working app.example.com because a session is almost a shell. Stop. The window closed. Continuing is out-of-scope testing even against an in-scope URL. Escalate, record the stop time, and request a written extension if the client still wants the chain completed.

Wrong target and wrong time are the two highest-frequency pre-engagement failures on the exam and in after-action reports. Documents first; packets second.

Loading diagram... Pre-engagement documents before testing starts