easyMultiple Select
Penetration Test Rules of Engagement
A penetration tester is planning an engagement. Which of the following rules of engagement should be defined before testing begins? (Select TWO.)
Quick Answer
The correct answers are the scope of systems to be tested and emergency contact procedures, as these are essential elements of penetration test rules of engagement. The scope defines the authorized IP ranges, hostnames, and network segments, preventing unauthorized access and ensuring legal compliance, while emergency contact procedures specify who to notify if an incident like an unintended outage or security alert occurs during testing, protecting the tester from legal or operational repercussions. On the CISSP exam, this concept tests your understanding of the formal RoE document required before any penetration test begins, often appearing in domain 6 (Security Assessment and Testing) with a common trap being to confuse operational constraints like time windows with these foundational legal and safety elements. A useful memory tip is to think of RoE as the “start and stop” rules: scope tells you where you can start, and emergency contacts tell you when to stop and call for help.
⚠ Common exam trap
Many candidates confuse 'Rules of Engagement' with a detailed test plan or contract, leading them to select options like 'exact exploits' (A) or 'compensation' (D), which are operational or financial details, not the high-level boundaries that define what is allowed and how to handle emergencies.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Emergency contact procedures
Option B (Emergency contact procedures) is correct because rules of engagement must establish who to contact and how to halt testing immediately if a critical system outage or unintended impact occurs, ensuring safety and rapid escalation. Option C (The scope of systems to be tested) is correct because ROE must explicitly define in-scope and out-of-scope IP ranges, domains, and assets to prevent unauthorized testing and legal exposure. Option A is not required in the ROE because specific exploits are chosen during execution based on findings, not pre-defined in the engagement contract. Option D is irrelevant to ROE since compensation is a business/contractual matter, not a testing boundary or safety control. Option E is inappropriate because naming specific employees to target is not a standard ROE element and could raise ethical or legal concerns; targeting is defined by scope, not individuals.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The exact exploits to be used
Why it's wrong here
Naming exact exploits prescribes the tester's methods, which rules of engagement deliberately leave to professional judgement; scope, timing, targets and authorisation are agreed instead. Specifying tooling would be right only where the client restricts particular techniques, such as prohibiting denial-of-service or social engineering, not as a general requirement.
- ✓
Emergency contact procedures
Why this is correct
Emergency contact procedures establish whom the tester and client notify if testing causes an outage, data loss or law-enforcement involvement, and how to halt the engagement. Defining these before testing begins ensures rapid escalation and containment, which is why they are a mandatory rules-of-engagement element.
- ✓
The scope of systems to be tested
Why this is correct
The scope of systems to be tested defines the exact IP ranges, applications, domains and environments authorised for exploitation. Without it, testers risk touching out-of-scope production assets or third-party infrastructure, creating legal exposure and invalidating the engagement's authorisation.
- ✗
The tester's personal compensation
Why it's wrong here
The tester's personal compensation is a commercial contract term between the testing firm and its client, not a rule of engagement governing how testing is conducted. Rules of engagement cover scope, timing, authorised techniques, escalation contacts and emergency stop conditions. Compensation belongs in the statement of work.
- ✗
The names of employees to be targeted
Why it's wrong here
Naming individual employees to be targeted is a target list, not a rule of engagement; the agreed scope defines in-scope systems, IP ranges and domains, with social engineering permitted or excluded as a category. Employee names would be relevant only for a separately authorised social-engineering campaign.
Go deeper
Related to this question
About these practice questions
This CISSP question is part of Courseiva's 816-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on CISSP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An organization is planning a penetration test of its internal network. Which TWO of the following are essential elements to include in the test scope and rules of engagement?
easy- A.List of specific exploitation tools to be used.
- ✓ B.Time windows when testing is permitted (e.g., after business hours).
- C.Schedule for automated vulnerability scanning of all external systems.
- ✓ D.List of IP addresses and systems authorized for testing.
- E.Detailed plan for exploiting client-side vulnerabilities.
Why B: The rules of engagement (ROE) and scope define the boundaries of the penetration test. Essential elements include authorized time windows (option B) to minimize business disruption and ensure testing occurs during agreed-upon periods, and a list of authorized IP addresses and systems (option D) to clearly define the target scope and avoid legal issues. Option A (list of specific tools) is not necessarily required in the scope; tools can be agreed upon but are not essential. Option C (vulnerability scanning schedule) is a separate activity and not part of penetration test scope. Option E (detailed client-side exploitation plan) is too specific and not a required element of the overall scope.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CISSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISSP exam.