Cybersecurity
Preparing for Penetration Testing: A Checklist for IT Teams
A stalled penetration test is usually caused not by the testers but by incomplete preparation. This checklist helps IT teams prepare permissions, access, environment, and communication channels before day one.
SEO and Content Specialist
5 min read Reviewed by Legia Cybersecurity Team
Short answer: before penetration testing begins, prepare seven things: a written scope, a permission letter signed by the system owner, test accounts for each user role, a decision on the environment (production or a copy), verified backups, emergency contacts on both sides, and a designated report recipient. If the system runs in the cloud, also check the provider’s testing terms.
A test delayed on day one because test accounts have not been created or the permission letter has not been signed is a common occurrence. Every day of delay pushes back the report, the fixes, and the retest. The checklist below helps the IT team prepare everything before testing starts.
1. A written scope
The scope answers the question “what may be tested and what may not”. At a minimum it contains:
- The addresses to be tested: domains, subdomains, and APIs, listed in full. Avoid “the entire system”.
- What is excluded: for example third-party payment services or systems owned by other vendors.
- The method: black box, grey box, or white box. The considerations are covered in the article Black Box, Grey Box, or White Box?.
- The schedule and testing hours, including whether testing may run during working hours.
- Prohibited types of testing, especially testing that aims to make the system unavailable.
2. A permission letter from the system owner
Security testing without written permission from the system owner can be considered illegal access. The permission letter contains the scope, schedule, and limits, and is signed by a party with authority over the system. If the website is managed by a vendor or hosted by another party, make sure they know the schedule and do not block the testing as a real attack, or agree together if the blocking is itself something you want to test.
3. Test accounts for every role
In the grey box method, testers need an account for every role being tested, for example a regular user, an operator, and an admin. Preparation to do:
- Create accounts dedicated to testing, do not lend out employee accounts.
- Prepare at least two accounts per role, so that access flaws between users of the same role can be tested.
- Fill the accounts with enough sample data, for example a few orders or documents, so the flows can be run.
- Disable or adjust two-step authentication for test accounts if needed, or arrange for the tester to receive the code.
- Record all test accounts so they can be deleted after testing is finished.
4. Production or a copy environment
Testing in the production environment gives the most realistic picture, but carries the risk of disruption and of test data mixing with real data. A copy environment (staging) is safer, as long as its version matches production. Consider:
- Does the copy use the same code version and configuration as production?
- Does the copy contain real personal data? If so, treat it with the same safeguards as production.
- If production is tested, is there a time window with low traffic?
5. Backups and monitoring
Before testing, make sure the latest backup exists and can be restored, especially if the testing touches file upload features, forms, or the database. Inform the monitoring team and the hosting provider so that a spike in activity does not trigger panic. Some companies actually want to see whether their monitoring detects the testing; if so, agree on who is told.
6. Emergency contacts and communication channels
Designate one emergency contact on your side and ask for one from the testers. Your emergency contact must be able to stop the testing if a disruption occurs, and the testers must be able to report high-risk findings immediately without waiting for the final report. Also agree on the channel to use, preferably an encrypted one.
7. Cloud provider permissions and terms
Cloud providers have their own terms on security testing:
| Provider | General terms (as of October 2026) |
|---|---|
| AWS | No prior approval needed for services listed as permitted; other services and some types of testing need approval |
| Microsoft Azure | No prior approval needed since 2017, but you must comply with the Microsoft Rules of Engagement; DoS testing is prohibited |
| Google Cloud | No notification needed, but you must comply with the terms of service and the acceptable use policy |
Shared hosting and local providers often have different rules. Check their terms, and if in doubt, ask directly before testing is scheduled.
8. The report recipient
A penetration testing report contains details of flaws that could be abused. Designate the recipient from the start, for example the technical lead and one person in management, and agree on how it will be delivered. Also line up who will fix the findings, so the retest schedule can be estimated. How to read the report is covered in How to Read a Penetration Testing Report.
Summary checklist
| Preparation | Owner | Done |
|---|---|---|
| Written scope, agreed | IT team and testers | ☐ |
| Permission letter signed by the system owner | Management | ☐ |
| Vendors and hosting informed | IT team | ☐ |
| Test accounts per role with sample data | IT team | ☐ |
| Testing environment decided | IT team | ☐ |
| Latest backup verified | IT team | ☐ |
| Emergency contacts on both sides | IT team and testers | ☐ |
| Cloud provider terms checked | IT team and testers | ☐ |
| Report recipient designated | Management | ☐ |
How Legia does it
In the Penetration Testing service for websites and web applications, the first stage is setting the scope and permissions: targets, method, schedule, and limits, including arranging cloud provider permission when needed. Testing begins only after the permission letter is signed and an emergency contact is designated. High-risk findings are reported immediately, the report is delivered over an encrypted channel only to the recipient you designate, and a retest after fixes is included.
Frequently asked questions
How long does this preparation usually take?
If the asset list and the authorized parties are already clear, preparation can be done in a few working days. What most often takes time is signing the permission letter and coordinating with vendors or hosting.
Does the development team need to stop releasing during testing?
Ideally the code being tested does not change during the testing period, so that findings can be reproduced. If a release cannot be postponed, tell the testers the schedule.
Do employees need to be informed?
For website testing, only the parties involved. For social engineering simulations such as phishing, the rules are different and separate written approval from leadership is needed.


