PENETRATION TESTING
How to prepare for your first penetration test
A little preparation makes a test faster and the report more useful. Here is a short checklist.
Airintha Team · Engineering and security
4 min read

A penetration test goes better when the tester can spend time attacking instead of waiting for access. Preparation is mostly agreeing things in writing and gathering a few details.
01Decide what is in scope
- The applications, APIs and environments to test.
- Anything that must not be touched, such as production payments.
- The dates, and who to contact during testing.
02Prefer a staging environment
Test against an environment that matches production but holds no real customer data where you can. It lets the tester try destructive actions without risk to real users.
03Prepare test accounts
Provide accounts for each role, for example customer, support and admin. Many serious issues only appear when one role tries to act as another.
04Share what you already know
- An architecture sketch, even a rough one.
- Known weak spots you already worry about.
- Earlier findings or past incidents.
05Plan for the fixes
Reserve engineering time after the report. A finding that sits unfixed is not a result. Agree who owns each fix and when it will be reviewed.

