Skip to content
Cyberphore

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.

Preview. Tick the items as you go below.

The checklist

Scope and rules
  1. Why it matters: NIST's rules of engagement template starts with the purpose of the test. CIS Control 18 frames testing as simulating an attacker's objectives, so the goal shapes what the testers try to reach.

    Source: National Institute of Standards and Technology; Center for Internet Security

  2. Why it matters: NIST says the plan should identify the systems and networks authorized for testing, for example by IP addresses or address ranges.

    Source: National Institute of Standards and Technology

  3. Why it matters: NIST recommends naming systems that are not authorized for testing, at a minimum by IP address and preferably also by system name.

    Source: National Institute of Standards and Technology

  4. Why it matters: NIST says the plan should state prohibited activities in a way that leaves no room for interpretation, and answer how sensitive data will be handled.

    Source: National Institute of Standards and Technology

Authorization
  1. Why it matters: NIST notes that signing the assessment plan shows all parties approve it. Microsoft requires third-party testers to have explicit written authorization from the resource owner, documented before testing begins.

    Source: National Institute of Standards and Technology; Microsoft Learn

  2. Why it matters: NIST says that when you do not control part of the network, the owner of that network usually must also consent in writing.

    Source: National Institute of Standards and Technology

  3. Why it matters: NIST suggests a short memorandum describing allowed activities, authorized systems and a point of contact, which testers can present as proof they are permitted.

    Source: National Institute of Standards and Technology

  4. Why it matters: Microsoft says that if testing is flagged as abuse, you respond with the customer authorization and a description of the in-scope activity, and keeping those documents to hand shortens the process.

    Source: Microsoft Learn

Cloud provider rules
  1. Why it matters: AWS allows testing of listed services without prior approval and says customers testing other services must work with AWS Support or their account representative.

    Source: Amazon Web Services

  2. Why it matters: AWS lists these as prohibited activities and requires Simulated Events requests at least two weeks before the start date.

    Source: Amazon Web Services

  3. Why it matters: Microsoft no longer requires pre-approval for Azure testing, but testers must comply with its unified rules of engagement, which list these as prohibited.

    Source: Microsoft Learn; Microsoft Security Response Center

  4. Why it matters: Google says you do not need to notify it before testing, but you must follow its Acceptable Use Policy and Terms of Service and affect only your own projects.

    Source: Google Cloud

  5. Why it matters: Microsoft's rules say to stop immediately and notify MSRC if you access data you have no rights to. AWS asks customers to contact AWS Security immediately about issues in its services.

    Source: Microsoft Security Response Center; Amazon Web Services

Backups, monitoring and contacts
  1. Why it matters: NIST notes there is always a chance of accidental complications during testing. The Cyber Centre's baseline controls say recovery mechanisms should effectively restore systems from backups.

    Source: National Institute of Standards and Technology; Canadian Centre for Cyber Security

  2. Why it matters: NIST recommends an established incident response plan during testing, criteria for halting, and that testers stop on systems involved in a real incident while you respond.

    Source: National Institute of Standards and Technology

  3. Why it matters: NIST says testers' IP addresses should be identified so administrators can tell testing from real attacks, and that unannounced tests need a plan so detections do not trigger external breach reporting.

    Source: National Institute of Standards and Technology

  4. Why it matters: NIST's template calls for a table of points of contact including the incident response team, and says critical high-impact vulnerabilities should be reported as soon as they are found.

    Source: National Institute of Standards and Technology

Fix and retest
  1. Why it matters: NIST describes a mitigation step where actions are implemented and then verified, so findings need someone accountable for each one.

    Source: National Institute of Standards and Technology

  2. Why it matters: NIST says retesting validates that mitigations were completed, and that testers can verify a fix only if they repeat the original test.

    Source: National Institute of Standards and Technology

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

  1. Technical Guide to Information Security Testing and Assessment (SP 800-115). National Institute of Standards and Technology, 2008-09.
  2. CIS Critical Security Control 18: Penetration Testing. Center for Internet Security, 2021-10-28.
  3. Penetration testing. Microsoft Learn, 2026-07-24.
  4. Penetration Testing. Amazon Web Services, undated, read November 21, 2026.
  5. Microsoft Security Testing Rules of Engagement. Microsoft Security Response Center, undated, read November 21, 2026.
  6. Cloud Security FAQ. Google Cloud, undated, read November 21, 2026.
  7. 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

Book free assessment