PENETRATION TESTING
What a penetration test actually covers
A penetration test is not a scan. Here is what gets tested, how, and what you should expect to receive.
Airintha Team · Engineering and security
5 min read

01A test is not a scan
A vulnerability scan runs automated checks and lists what it matches. A penetration test is done by people who try to chain weaknesses together the way an attacker would, so the result shows what is actually exploitable and why it matters.
02What gets tested
- Web applications: login, sessions, input handling, access control and business logic.
- APIs: whether one user can reach another user's objects, what happens with extra fields, and what is rate limited.
- Cloud setup: roles and permissions, public storage, network boundaries and leaked secrets.
- Login systems: SSO, MFA, password reset and token lifetime.
03What goes into the scope
Before testing starts, the targets, the allowed methods and the dates are written down. Anything outside that list is not touched. A clear scope protects both sides: you know what was tested, and the tester knows what is off limits.
04What the report should contain
- Each finding with the steps to reproduce it.
- The impact, in plain language.
- A recommended fix.
- Findings ordered by how an attacker would use them.
05What a test does not give you
A test shows the state of a system at one point in time. It is not a compliance certificate and it does not replace secure development. The strongest result comes when findings feed back into how the software is built.


