• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

Checklist · Security Testing

Penetration Test Preparation Checklist

Everything to settle before a penetration test starts, so the days you pay for are spent testing.
Penetration Test Preparation Checklist cover photograph

Written for

IT managers preparing for a test

Time needed

1 to 2 hours

Items

29 across 5 areas

Most wasted time in a penetration test is lost in the first two days: missing credentials, unclear scope, a firewall that blocks the testers, a system owner who was never told. Preparation fixes that.

Complete this checklist with your provider before the start date.

0 of 29 in place (0%)

01

Scope and objectives

Agree what is being tested and why.

02

Rules of engagement

How the test will be run.

03

Access and logistics

What the testers need on day one.

04

Internal readiness

Avoid surprises inside your own organization.

05

Reporting and follow-up

Decide now what you need at the end.

How to get the most from this list

  1. 01

    Tick only what you can prove

    If you could not show an auditor or your board the evidence today, leave it unticked. A lower honest score is more useful than a high hopeful one.

  2. 02

    Give every gap an owner

    For each unticked item, name one person and one date. Gaps without an owner are the ones still open next year.

  3. 03

    Re-run it every quarter

    Your environment changes faster than policy. Repeat the list each quarter and after any major change, and compare the scores.

Gaps we see most often

  • Scope taken from an old asset list
  • No test accounts ready on the first morning
  • No retest, so nobody confirms the fixes worked

Take it with you

Download the checklist as a PDF

A designed 6-page version with tick boxes, the common gaps and the questions people ask. Useful for a team review or as audit evidence.

Want a second pair of eyes?

Bring your completed list to a risk review. We will check the items that matter most for your environment, confirm the evidence and turn the gaps into a short, prioritized plan.

Request a risk review

Common questions

How far ahead should we prepare?

Two to four weeks is comfortable. Third-party permissions and test accounts are what usually take longest.

Should we tell our security team?

It depends on the objective. Announce it if you are testing systems. Keep it limited to a few people if you are also testing detection and response.

Is testing production safe?

It is common and usually safe with agreed rules, testing windows and stop conditions. Fragile or safety-related systems are handled separately.