How a penetration test actually runs
The engagement is five steps, and the first two happen before anyone touches a system.
- Scoping: agree what will be tested and what will not
- Signed agreement and written rules of engagement: targets, window, permitted techniques, contacts
- Testing: inside the written scope, stopping at proof of impact
- Report: every finding ranked by severity, with remediation steps
- Retest: once fixes are in, confirm they hold
What a tester is looking for
Not a list of known bugs; that is a scanner's job. A tester is looking for the path. Individually minor findings that combine into something serious are the characteristic output of a real test.
A verbose error page discloses a username format. A password policy allows a weak password. A management interface is reachable from a subnet it should not be. None of those is critical alone. Together they are an account, and the report says so.
Why exploitation stops at proof of impact
Once a tester has demonstrated they can reach something, continuing adds risk to you and no information to the report. The point is established.
So a tester who gains database access documents the access and stops. They do not exfiltrate the table. The report proves the exposure without creating the incident it was hired to prevent.
What you should expect to receive
A written report, not a tool export. Every finding ranked by severity, remediation steps for each one, and one retest once your fixes are deployed.
If a vendor's deliverable is a scanner PDF with their logo on it, you bought a scan. The judgment applied to the output is the thing you are paying for.

