Web Application Pentest Readiness Check
Fifteen yes/no questions that measure how ready your web application and APIs are for a penetration test, based on OWASP practice.
- 15 questions
- ± 6 minutes
What this questionnaire covers
Questions are grouped by area. Open any area to see its questions before you start.
How the score is read
The score is the percentage of yes answers across all questions, mapped to one of these three levels.
- 0–39%
Not Test-ready
Basic scope and controls are not ready. Testing is still possible, but findings will be dominated by fundamentals. Tidy the inventory, access control and dependency patching first.
- 40–74%
Partially Ready
Your application is ready to be tested with some caveats. Complete the lowest-scoring areas so testing focuses on the real weaknesses.
- 75–100%
Test-ready
Your application is ready for effective penetration testing. Next: agree the scope, rules of engagement and schedule.
Application scope and readiness5 questions
- Is the inventory of web applications, subdomains and public API endpoints complete and current?
- Is a production-like staging environment or an agreed production testing window available?
- Can per-role test accounts (regular user, admin, unauthenticated) be provided for grey-box or white-box testing?
- Is architecture documentation (data flow, third-party integrations, technology stack) available?
- Is there a code freeze or change window during testing so results are not skewed by new releases?
Application security controls5 questions
- Is input validation and output encoding applied consistently to prevent injection (SQL injection, XSS)?
- Do authentication and session management (password policy, MFA, session timeout, token expiry) follow best practice?
- Does authorisation control check access rights on the server for every object and endpoint, not just hide them in the UI?
- Is SAST/DAST or a security code review run before release?
- Are third-party dependencies (libraries, frameworks) scanned for vulnerabilities regularly?
Follow-up5 questions
- Are public applications protected by a WAF or an API gateway with equivalent protection?
- Are application logs (auth, errors, access to sensitive data) collected and monitored?
- Is sensitive data encrypted in transit (current TLS) and at rest?
- Have findings from previous pentests been remediated and re-verified (retest)?
- Does every security finding have an owner and a tracked status in one register until closed?
Frequently asked questions
What standard is web application pentesting based on?
The OWASP Testing Guide and OWASP ASVS for methodology, with the OWASP Top 10 as the primary risk classification reference.
How long does a web application test take?
Usually 1 to 2 weeks for a small-to-medium application, depending on the number of pages, user roles and API endpoints covered.
What is the difference between black-box, grey-box and white-box testing?
Black-box has no access, simulating an outside attacker. Grey-box uses limited test accounts to find authorisation flaws. White-box has source code access for the deepest analysis.
Are mobile applications covered by this questionnaire?
No, this questionnaire focuses on web applications and APIs. For Android/iOS mobile app testing, see our Security Assessment services page.
Plan the web application test with our team
Web application and API pentests by an OSCP-certified team following the OWASP Testing Guide, with CVSS v3.1 reporting and a free retest.