The short answer
A good penetration test starts with scope: which apps, APIs, mobile apps and cloud accounts, which user roles, and what "success" means for an attacker. Choose grey box testing for most products, insist on a report with evidence and clear fixes, fix critical and high findings first, and get a retest to prove it.
Types of penetration test
| Test type | What it covers | Good for |
|---|---|---|
| Web application | Login, sessions, access control, input handling, business logic | SaaS, portals, eCommerce |
| API | Authentication, authorization per object, rate limits, data exposure | Public and partner APIs, mobile back ends |
| Mobile app | App storage, certificate pinning, API calls, reverse engineering | iOS and Android apps |
| Cloud configuration | IAM, storage, network exposure, logging, secrets | AWS, Azure, Google Cloud |
| External network | Internet-facing hosts and services | Every company |
| Internal network | Lateral movement, Active Directory | Offices, hybrid estates |
How to scope a test: 6 steps
1. Start from the business risk
What would hurt most: customer data leaking between tenants, payment fraud, account takeover? Write two or three attacker goals.
2. List assets precisely
URLs, API base paths and versions, mobile app builds, cloud account IDs, and anything out of scope, such as third-party services you don't own.
3. Define user roles
Provide test accounts for each role, such as admin, standard user and tenant A and B, so testers can check access control between them.
4. Choose the approach
Grey box for most products; add code review for high-risk features. Agree testing windows and whether production or staging is used.
5. Agree rules of engagement
Contacts, emergency stop process, testing hours, data handling and whether denial-of-service tests are allowed.
6. Plan the retest
Book a retest window two to six weeks after the report so fixes are verified while details are fresh.
How to read the report and prioritize
- Read the executive summary for overall risk and the headline issues.
- Fix by risk, not by count: critical and high first, especially access-control flaws and anything exposing customer data.
- Look for patterns: five findings with one root cause, such as missing authorization checks, need one design fix.
- Assign owners and dates in your issue tracker.
- Retest and record the closure letter as evidence for SOC 2, ISO 27001 or PCI DSS.
How Zuroth helps
- Penetration testing from $499 one-time, depending on scope and overall functionality: web, API, mobile and cloud.
- Clear reports with evidence, business impact and fix guidance your developers can use.
- Retests and closure letters for auditors and enterprise customers.
- Vulnerability and patch management to keep issues from coming back.
Next step: use the cost estimator or book a free scoping call.
Related reading
- Security & Compliance services
- SOC 2 vs ISO 27001
- PCI DSS scope reduction
- Penetration testing (VAPT)
- Vulnerability & patch management
Frequently asked questions
What is the difference between a vulnerability scan and a penetration test?
A vulnerability scan is automated and finds known weaknesses across many systems quickly. A penetration test is performed by skilled testers who chain weaknesses together, test business logic and prove real impact. Scans should run continuously; penetration tests usually run yearly and after major changes.
Should a penetration test be black box or grey box?
For most companies, grey box gives the best value: testers get user accounts, documentation and sometimes code access, so they spend time finding real issues instead of guessing. Black box simulates an outsider with no knowledge and suits external perimeter tests or specific red-team goals.
How often should we run a penetration test?
At least once a year and after significant changes such as a new product, major release, architecture change or cloud migration. PCI DSS requires yearly tests and segmentation testing; SOC 2 and ISO 27001 auditors and enterprise buyers usually expect a yearly test.
What should a good penetration test report include?
An executive summary, scope and method, each finding with severity, evidence, reproduction steps, business impact and clear fix guidance, plus a list of what was tested and not tested. A retest letter confirming fixes is useful for auditors and customers.
How much does a penetration test cost?
With Zuroth, penetration tests start from $499 one-time. The final price depends on scope and overall functionality: the number of applications, user roles, API endpoints and environments, plus whether mobile or cloud testing and a retest are included. You get a fixed quote before testing starts.