Web app testing that finds what scanners miss.
We test your app by hand, the way a real user and a real attacker would, against the rules your app is supposed to follow.
What we test.
Scanners find reflected XSS. They do not find the workflow that lets a standard user approve their own invoice. We test authentication, authorization, and business logic by hand, against your application's actual rules, because that is where the expensive bugs live.
01
Authentication and session management
We test sign-up, login, password reset and sessions for ways into someone else's account.
02
Broken access control and IDOR
We check whether one user can see or change another user's data just by changing a number.
03
Injection and deserialization flaws
We try to slip commands into forms and requests, like SQL injection, so the app does what it should not.
04
Business logic and workflow abuse
We look for ways to break your app's own rules, like approving your own invoice or skipping a payment.
05
Multi-tenant isolation testing
If many customers share your app, we make sure one can never reach another's data.
06
Client-side and supply chain risks
We check what runs in the browser, including scripts you load from other companies.
What we look for first.
These are the problems that turn up again and again in this kind of system. We check for them first, then go wherever your setup leads.
One user seeing another's data
Changing an ID in a link or request shows someone else's records.
Roles that do too much
A basic user can reach admin pages or actions.
Weak password reset
Reset links that can be guessed, reused or sent to the wrong person.
Checks that can be skipped
Rules checked in the browser but not on the server, so they can be bypassed.
How the test runs.
- 1
Agree on scope
We list the app, its user roles and the test accounts we need, and pick a testing window.
- 2
Learn how it works
We use the app like a real customer first, so we know the rules it is meant to follow.
- 3
Test by hand
We try to break each rule, role by role. Tools help with the basics. People do the real testing.
- 4
Report and retest
Every finding comes with proof, the risk in plain English and how to fix it. With the Complete package, we test again after your fixes.
What we need from you
- A test copy of the app, or a safe time to test the real one
- A test account for each user role
- The features that matter most to you
- A contact we can reach during testing
Getting this for an audit?
Every finding is tied to the rule it affects. See what auditors look for:
Everything your auditor will ask for.
One fixed price covers all of it.
One price, locked when you sign.
We confirm the scope with you first. After you sign, the bill never grows.
- What we test
- Website and API
- Start
- Within 1 week
- Retest
- In one price
- Surprise bills
- Never
The letter your auditor asks for.
Signed at the end of the Complete package, ready to send to whoever asked you for a pentest.
We test again until it is fixed.
With the Complete package, retests are part of the price. Not a second bill.
- Admin page open to the internetFixed
- Old software with known holesFixed
- Weak password rulesFixed
Big problems reach you the same day.
Not three weeks later in a report.
Real people do the testing.
Senior testers check every finding by hand. A scanner is where we start, not where we stop.
- OSCP
- OSCE
- GPEN
- GWAPT
- CISSP
- CISA
- CEH
- CRTO
- AWS Security
- Azure Security
A report you can actually read.
Plain English, with the fixes that matter most at the top.
Web app pentest questions, answered.
01Is this the same as an OWASP Top 10 scan?
No. We cover the OWASP Top 10, but by hand, and we go further into the rules of your own app, which no scanner knows.
02Should you test our live app or a test copy?
Either works. A test copy is safer, as long as it matches the live app closely. We decide together on the scope call.
03Do you test with logins?
Yes. We test with an account for each role, because most serious problems only show up after you log in.
04Do you test our API too?
We test the parts of your API the app calls. A full API test covers every endpoint, including ones no screen uses, and is its own service.
05How long does it take?
We can start within a week. Most tests then take one to three weeks, depending on size. If you have an audit date, tell us on the scope call and we will plan around it.
Other kinds of test.
Your proposal is 90 seconds away.
Type your website. Scope, timeline and a fixed price, in about 90 seconds. Free, and no sales call.
By getting a proposal, you agree to our Terms and Privacy Policy.
- No surprise bills
- Start within 1 week
- Retest and attestation letter in one price
Rather talk to a person? Book a call