Planning for Penetration Testers
Planning is the legal and technical preparation that comes before any test traffic is sent. It fixes the scope, the rules of engagement, testing windows and emergency contacts in a signed document, and it prepares a lab with Kali Linux, virtual machines and note-taking tools. Without written authorisation, testing is not penetration testing.
Stage: Engagement Basics · Part of the Penetration Tester roadmap · Last reviewed 19 November 2026
What to learn in Planning
- Define in-scope and out-of-scope assets in a statement of work
- Write rules of engagement covering timing, techniques and contacts
- Set up a Kali Linux lab with isolated vulnerable target machines
- Organise notes and evidence capture for each finding as you go
- Explain the difference between black box, grey box and white box testing
Planning interview questions
What should rules of engagement include in a penetration test?
They list the approved targets and IP ranges, allowed and forbidden techniques such as denial of service or social engineering, testing hours, how sensitive data is handled, and who to call if something breaks. The client signs them before any testing begins.
What is the difference between a vulnerability scan and a penetration test?
A vulnerability scan is automated and lists possible weaknesses. A penetration test adds human judgement: testers confirm that issues are real, chain them together, show business impact by exploiting them safely, and report on what an attacker could actually achieve.
Where Planning fits in the Penetration Tester roadmap
Planning belongs to the Engagement Basics stage (intermediate level), which takes about 38 hours. Plan the test.
Other units in this stage
Back to the full Penetration Tester roadmap