Lesson 3.73: Managing a penetration test
A penetration test is only as useful as its management: a clear scope and rules of engagement before it starts, someone watching during the test window, and afterwards a triage that turns a long report into fixes, followed by a retest that proves the fixes work. In the lab you're the client-side owner of Northwind's external test: you check the scope, catch a finding against a system the testers were not allowed to touch, triage the in-scope findings, match one with an existing ticket, read the retest results and write the summary.
17 min
You will learn to
- Explain scope and rules of engagement
- Detect out-of-scope testing
- Triage findings by severity and exploitation
- Match findings with existing vulnerability records
- Use retest evidence to close findings
Key terms
- Scope
- The systems, addresses and techniques the testers may use.
- Rules of engagement
- How the test runs: window, contacts, forbidden actions, when to report immediately.
- Triage
- Sorting findings into what to fix first.
- Retest
- The testers verifying that fixes work, with evidence.
- Out-of-scope finding
- A result against a target that wasn't authorised.
← Joiners, movers and leavers · All lessons · ICT concentration risk and exit plans →