Bitzu

CPSA ยท Engagements, law and reporting

Penetration test lifecycle

Why clients commission tests, the stages from kickoff to closure, debrief and retest.

Key points

  • A client orders a test to find weaknesses first, meet a requirement or check a change.
  • Flow: scoping and contract, kickoff, testing with records kept.
  • Urgent issues are raised as they appear.
  • Then: final report, debrief, optional retest, closure (data returned or destroyed, access removed).

Practice questions

Single choice

Which activity normally comes last in a penetration test engagement?

  1. Kickoff meeting
  2. Closure of the engagement
  3. Final report delivery
  4. Scoping call
Show answer

Answer: B. Closure of the engagement

Closure (removing access, returning or destroying client data) follows the report, debrief and any retest. Report delivery is a late step but not the final one.

Select all that apply

Which are valid reasons for a client to commission a penetration test?

  1. Evidence of security for a customer or regulator
  2. Replacing the need for patching
  3. Finding weaknesses before a real attacker does
  4. Guaranteeing that no breach can ever occur
  5. Removing the need for monitoring
Show answer

Answer: A. Evidence of security for a customer or regulator, C. Finding weaknesses before a real attacker does

A test gives assurance and finds weaknesses at a point in time. It cannot replace patching or monitoring, and it cannot guarantee no breach.

True or false

A clean penetration test report proves the system cannot be compromised.

Show answer

Answer: False

A test samples the system within a scope and time window. It shows what was found, not that nothing exists.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More CPSA topics in this module