
Web Application Pentest
Authorisation and business logic first, then the OWASP classes. The flaws that cost money have no scanner signature.
Vulnerability assessment and penetration testing
Vulnerability assessment and penetration testing across web and mobile apps, APIs, networks, AI, industrial systems and IoT. Each asset scoped, tested and reported on its own.

Read the left column in your own words and take the row that matches. If two match, you need two engagements, and we would rather say that now.
| Service | Answers | Typical duration |
|---|---|---|
| Web Application Pentest | Can somebody abuse our web application to reach data or money that is not theirs? | 1 to 3 weeks |
| API Pentest | Does our API enforce who owns what, or does it trust whatever the client sends? | 1 to 3 weeks |
| Mobile App Pentest | What does a stolen phone, or a decompiled build, give an attacker? | 2 to 3 weeks |
| Infrastructure Pentest | What is exposed to the internet, and how far does one position inside reach? | 1 to 3 weeks |
| AI & LLM Pentest | Can our model be talked into calling a tool or returning data it should not? | 2 to 3 weeks |
| OT / ICS Pentest | Could somebody get from corporate IT to the process, and does segmentation hold? | 3 to 5 weeks |
| IoT Pentest | What does physical possession of one of our devices give an attacker? | 3 to 4 weeks |
Each page carries what is in scope, what we review, the testing approaches, the process and a full FAQ.

Authorisation and business logic first, then the OWASP classes. The flaws that cost money have no scanner signature.

Object and function level authorisation, tokens, rate limits and open banking flows. Tested directly, not through the interface.

iOS and Android on real devices, local storage, pinning, and the backend where most of the risk actually is.

External exposure and internal blast radius, including Active Directory paths and whether segmentation holds.

Prompt injection direct and indirect, tool abuse, agent blast radius and the application underneath.

SCADA and control networks, scoped so availability is never the thing at risk. Boundary first.

Firmware, hardware interfaces, radio and the cloud behind the device, tested as one product.
The same six phases, the same reporting standard and the same operator bar, whichever asset is being tested. That is what makes two reports a year apart comparable, and what lets a regulator read them side by side.
Testing is not the deliverable. The evidence chain is: the scope rationale, the authorisation, findings with named owners, the remediation record and proof of retest.
We reply with a scope, a timeline and a quote, under NDA.