Checklist
Penetration Test Preparation Checklist
To prepare for a penetration test, write down the scope and an exclude list, get signed authorization from every system owner, check your cloud providers' testing rules, confirm backups restore, and exchange a contact sheet with halt criteria. Agree how critical findings reach you, and plan the retest that proves your fixes work.
- Write down why you are testing and what decision the report will support, such as a client requirement, an insurer question or a new application.
- List every in-scope system by IP range, hostname, URL, application and cloud account or tenant.
- Write an exclude list of systems the testers must not touch, by IP address and system name.
- State the allowed and prohibited activities, the testing hours, and how testers must handle any sensitive data they reach.Now
- Get written authorization, signed by someone with authority over every in-scope system, before testing starts.
- Get written consent from any hosting provider, IT provider or other party that runs part of the in-scope network.
+ 13 more items
Preview. Tick the items as you go below.
The checklist
Questions
Questions
Do we need AWS or Microsoft approval before a penetration test?
Usually not. AWS allows testing of the services on its permitted list without prior approval, but needs a Simulated Events form at least two weeks ahead for tests such as simulated phishing or command and control. Microsoft has not required pre-approval for Azure testing since June 15, 2017, but testers must follow its rules of engagement.
What should a penetration test authorization letter include?
The systems in scope and the exclude list, the allowed and prohibited activities, the testing dates and hours, who is doing the testing, and a signature from someone with authority over the systems. NIST also suggests a short memo testers can show staff, with a point of contact. If a third party hosts part of the network, get its written consent too.
Can a penetration test break our systems?
It can, which is why preparation matters. NIST notes there is always a chance of accidental or unexpected complications and recommends an incident response plan be in place during testing. Confirm backups restore, agree testing hours and halt criteria, and keep fragile systems on the exclude list or test them in a maintenance window.
Should we tell our security team or MDR provider about the test?
Decide deliberately. An announced test avoids wasted investigations; an unannounced one also tests detection. Either way, NIST says to identify the testers' source IP addresses, and for an unannounced test to agree in advance how detected test activity is handled, so it does not trigger breach reporting to outside parties.
How long after a penetration test should we retest?
Retest once your fixes are in, using the same test cases, because NIST notes a fix can only be verified by repeating the original test. Every Cyberphore penetration test includes one free retest of fixed findings within 90 days, and reports are delivered within 5 business days.
Sources
- Technical Guide to Information Security Testing and Assessment (SP 800-115). National Institute of Standards and Technology, 2008-09.
- CIS Critical Security Control 18: Penetration Testing. Center for Internet Security, 2021-10-28.
- Penetration testing. Microsoft Learn, 2026-07-24.
- Penetration Testing. Amazon Web Services, undated, read November 21, 2026.
- Microsoft Security Testing Rules of Engagement. Microsoft Security Response Center, undated, read November 21, 2026.
- Cloud Security FAQ. Google Cloud, undated, read November 21, 2026.
- Baseline cyber security controls for small and medium organizations. Canadian Centre for Cyber Security, 2020-02-18.
More checklists: all checklists · Penetration testing cost in Canada · Vulnerability management · talk to us