Skip to content
BCTI
All posts

How to prepare for your first penetration test

A practical checklist to get the most value from a pentest: scope, rules of engagement, logistics and what to do with the report.

Published: 2 min read

Also available in: Català · Español

A penetration test is an investment. A little preparation on your side makes the difference between a report full of surprises and one that genuinely moves your security forward. This is the checklist we share with clients before every first engagement.

1. Define what you want to learn

Start with the question, not the technique. Good objectives look like:

  • “Can an external attacker reach customer data through our web platform?”
  • “If a laptop is compromised, how far can the attacker get inside our network?”
  • “Does our new mobile app protect user accounts properly?”

Clear objectives drive the scope, the test type and how results are prioritised.

2. Agree on the scope in writing

The scope lists exactly what may be tested, and what may not. We usually capture it in a short document like this one:

engagement: web-platform-2026
type: grey-box web application test
in_scope:
  - https://app.example.com
  - https://api.example.com/v2
out_of_scope:
  - third-party payment provider
  - denial-of-service techniques
accounts:
  - role: standard user   # two of each, to test access between users
  - role: administrator
window: Mon to Fri, 08:00 to 20:00 CET
emergency_contact: on-call engineer, +376 …

If something belongs to a third party (cloud provider, SaaS, hosting company), check their testing policy: some require prior notification.

3. Prepare the logistics

Most delays in a pentest come from logistics, not technology. Before the start date, make sure that:

  • Test accounts exist for every role in scope, ideally two per role, so testers can check whether one user can access another’s data.
  • Network access is ready: VPN credentials, IP allow-listing or an on-site connection for internal tests.
  • Backups of the systems in scope are recent and verified.
  • Your team knows the test is happening, especially whoever monitors alerts, unless detection is precisely what you want to measure.
  • A single point of contact is available during the testing window.

4. Decide how much information to share

  • Black-box: testers receive almost nothing, like a real outsider. Realistic, but much of the time goes on discovery.
  • Grey-box: testers get accounts and basic documentation. This is the best value for most organisations.
  • White-box: testers also get source code or architecture details. The most thorough option.

5. Plan for the report before you receive it

The report is where the value is. Block time to review it with your team, assign an owner to every finding and agree on remediation deadlines by severity. Then schedule the retest, so you can confirm that the fixes actually work.

The short version

Clear objectives, a written scope, ready-to-use accounts, an available contact and a plan for the results. With those five things in place, your first penetration test will be smooth and far more useful.

How exposed are you, really?

Tell us about your protocol or your environment and we will propose an engagement tailored to it.

Talk to us