Web Application Penetration Testing
A hands-on test of your website, customer portal or web app, done the way a real attacker would approach it.
What it is
Automated scanners catch the obvious problems. A manual test finds the ones that matter: one customer seeing another customer's data, a checkout that can be tricked, a password reset that can be abused, or an admin feature that anyone can reach.
We follow the OWASP Web Security Testing Guide and cover your APIs as well as the pages people see. Testing can be done with or without login details, and we agree the scope and dates with you in writing first.
What we test
- Authentication, sessions and password reset flows
- Access control between users, roles and organisations
- Injection flaws, cross-site scripting and unsafe file uploads
- Business logic, such as pricing, discounts and approval steps
- APIs, following the OWASP API Security Top 10
- Configuration, error handling and exposed sensitive data
What you get
- A summary for decision makers and full technical detail for developers
- Proof for each finding and clear steps to fix it
- A walkthrough call, and a retest once you've made the fixes
- A letter confirming the test, which customers and auditors often ask for
Common questions
How long does a test take?
Most small and medium business applications take between three and ten days of testing, depending on size. You'll know the exact length and price before we start.
Do we need a test environment?
It's best, but not required. We can test a live application during agreed windows with care taken not to disrupt users or data.