Manual penetration testing for web apps and APIs
Scope and price are fixed in writing before we start. You get a report your customers' security team can read, and one retest to confirm the fixes.
Invoices of other customers can be read and changed
Missing object-level authorisation in the invoices API
Request, signed in as a user of organisation A
GET /api/v2/invoices/48213 HTTP/1.1 Host: app.example.test Authorization: Bearer <token of a user in organisation A>
Response
HTTP/1.1 200 OK
Content-Type: application/json
{"id": 48213, "organisation": "B", "total": "12480.00", ...}
The same invoice accepts a PUT request from this user and is changed.
- Impact
- Any signed-in user can read and alter every customer's invoices by counting through invoice numbers.
- Fix
- Check that the invoice belongs to the caller's organisation on every read and write. Add non-sequential identifiers as a second layer.
- Retest
- Fixed Both requests now return 404 for invoices of another organisation.
What we test
Testing is done by hand, with tools in support. A scanner run is not a penetration test and we do not sell one as such.
- Web applications
- Authentication, authorisation between roles and between customers, business logic, injection, file handling and session management, following the OWASP Web Security Testing Guide.
- APIs
- REST and GraphQL interfaces tested against the OWASP API Security Top 10, with most of the time spent on object-level and function-level authorisation.
- Mobile apps Quoted separately
- iOS and Android applications and the back-end services they talk to, following the OWASP Mobile Application Security Testing Guide.
- Detection check Optional, after a test
- We replay selected attack steps and check with your team whether your SIEM or EDR recorded them and raised an alert. You get a list of what was seen, what was missed and which detection rules to add.
Two fixed scopes
Most first tests fit one of these. The retest and the letter of attestation are part of the price, not extras.
| Included | Single application | Application and API |
|---|---|---|
| Covers | One web application or one API, one user role | One web application with its API, two to three user roles |
| Testing time | About 5 days | About 7 to 8 days |
| Report in English with a management summary | Included | Included |
| Letter of attestation to share with your customers | Included | Included |
| One retest within 30 days of the report | Included | Included |
| Walk-through call with your developers | Included | Included |
| Price | Fixed, quoted in writing after the scoping call | Fixed, quoted in writing after the scoping call |
Anything larger or different, such as more roles, several applications, mobile apps or internal networks, is quoted by testing days. VAT, travel and testing outside working hours are listed separately in the quote.
How an engagement runs
Six steps, in this order. Testing never starts before step three is signed.
-
Scoping call
Thirty minutes. You show us the application and tell us who is asking for the test and by when.
-
Fixed quote
Scope, testing days, dates and price, in writing.
-
Written authorisation
A service contract, an NDA, rules of engagement and an authorisation letter signed by someone entitled to approve testing of the systems in scope. Where we may come across personal data, a data processing agreement as well.
-
Testing
Inside the agreed window and against the agreed targets only. A critical finding is reported to you as soon as it is confirmed, not held back for the report.
-
Report and walk-through
Every finding comes with evidence, impact, a CVSS score and a specific fix. We go through it on a call with the people who will do the fixing.
-
Retest and attestation
Once you have fixed the findings, we test them again, record the result against each one and issue a letter of attestation you can pass to customers and auditors.
Who does the testing
Your test is performed by our lead tester, who also runs your scoping call.
- More than five years of penetration testing across web applications, APIs, mobile apps and internal networks.
- Acknowledged in the security halls of fame of Microsoft, PayPal, the U.S. Department of Defense, Dell, ASUS, T-Mobile, HubSpot and Visma for vulnerabilities reported to them.
- eCPPT certified by INE Security. OWASP member.
- Background in detection engineering and incident response with Splunk, IBM QRadar and CrowdStrike Falcon.
Before you sign anything you receive the tester's name, CV and links to the public acknowledgements, under NDA. A sanitised sample report is available on request.
For partners
Security consultancies, ISO 27001 and NIS2 advisers, auditors and IT service providers.
When your client needs a penetration test and you do not run one in-house, or your own testers are booked, we take on the technical testing. The report can carry your brand or ours.
We sign a non-solicitation clause before the first engagement. Your client stays your client, and we speak to them only as you direct.
We work and report in English. You keep the client relationship in your own language.
Request a scoping call
Tell us what the application does, who is asking you for the test and your deadline. We reply with times for a thirty-minute call.
Please do not send credentials, source code or details of live vulnerabilities by email. We agree a secure channel on the call.