Penetration testing for when automated tools are not enough.
Experienced security engineers test your web applications, APIs, mobile apps and networks the way a real attacker would. We validate every critical finding by hand, chain weaknesses into real impact, and hand your developers remediation they can ship.
Existing client? Request a test in the client portal.
Web application penetration testing, done by people.
A penetration test is a manual, time-boxed security assessment where an experienced tester attacks your application the way a real attacker would. Unlike an automated vulnerability scan, a pentest chains individual weaknesses together (authentication gaps, broken access control, business-logic flaws) to prove genuine, exploitable impact. That depth is what automated scanners cannot reach, and it is what your customers and auditors want to see.
We combine automated security technology with human expertise. Automation, including our own product OnScanner, provides breadth: every endpoint, header and dependency checked quickly. Our engineers provide depth: the judgment to see how three low-severity issues become one critical one.
When you can share source access, we go further with manual secure code review of your highest-risk features: injection sinks, unsafe deserialization, broken authorization logic, insecure cryptography and hardcoded secrets. Dynamic testing shows what an attacker can reach; code review shows the root cause and every other place the same mistake repeats.
What we test.
Scoped to your environment and risk, priced per engagement, no surprise add-ons.
Web applications
Single-page and server-rendered apps, authenticated and unauthenticated, against the OWASP Top 10 and beyond.
APIs
REST and GraphQL: authorization on every object and function, mass assignment, rate limits and data exposure.
Mobile applications
iOS and Android apps and the backends they talk to, including local storage, transport and client-side trust.
Networks
External and internal network testing: exposed services, misconfigurations and paths to sensitive systems.
Business logic
Workflows, pricing, roles and multi-step processes, where the flaws that cost real money usually hide.
Vulnerability chaining
Individually minor issues combined into realistic attack paths that show true impact.
Manual validation and proof of concept
Every critical finding reproduced by hand, with a proof-of-concept so there is no debate about whether it is real.
Secure code review
Grey-box or white-box review of high-risk code paths, with findings referenced to file and line.
Retesting and remediation validation
After you fix, we verify the fix and issue a remediation letter. Included in every engagement.
A five-phase engagement.
-
Scope and threat model
Asset inventory, rules of engagement and attack-surface mapping, under mutual NDA.
-
Active testing
Engineers chain authentication, authorization and business-logic weaknesses like real adversaries.
-
Evidence
Critical findings reproduced with proof-of-exploit. Only verified issues reach your team.
-
Report and remediation
Executive summary, technical findings and line-by-line fixes, ready for a sprint.
-
Retest and sign-off
Fixes verified before the report is closed, at no extra cost.
What you get.
One set of artifacts that works for your engineers, your leadership, your customers and your auditors.
- Executive summary for leadership
- Technical findings scored with CVSS and CWE
- Proof-of-exploit for every critical finding
- Line-by-line remediation guidance
- Code-level findings with file and line references (white-box)
- Retest report and remediation letter
- Attestation letter to share with customers
Penetration testing FAQ.
How much does a penetration test cost?
Penetration testing is priced per engagement based on scope, the size and complexity of the application, and the depth of testing required. A focused web application or API test is typically a few days of effort; a broad, multi-target engagement is larger. You get a fixed quote before any work starts, with the retest included, so there are no surprise costs.
Do I need a penetration test for SOC 2 or ISO 27001?
A penetration test is not strictly mandatory for a SOC 2 report, but most auditors and enterprise customers expect one as evidence that your security controls work in practice. ISO 27001 likewise expects technical testing of controls. Our report is built for both your engineers and your auditor, and because we also offer compliance consulting, the evidence maps directly to your controls.
Do you offer secure code review?
Yes. Alongside black-box and authenticated testing, we offer manual secure code review when you can share source access. An engineer reads the code behind your highest-risk features to find issues that are hard to trigger from outside, such as injection sinks, unsafe deserialization, broken authorization logic, insecure cryptography and hardcoded secrets. It is scoped as a grey-box or white-box engagement in your quote.
What is the difference between a scan and a penetration test?
An automated scan, such as one run with OnScanner, is fast and broad and finds known issues continuously. A penetration test is a manual engagement where a human tester chains weaknesses together to demonstrate real, exploitable impact, including business-logic flaws scanners cannot detect. Most teams run both.
What do I receive at the end?
An executive summary for leadership, a technical report with CVSS and CWE scoring and proof-of-exploit for every critical finding, line-by-line remediation guidance, and an attestation letter to share with customers. After you fix the issues we retest and issue a remediation letter at no extra cost.
Find out what an attacker would find.
Share your scope and we will reply within one business day with questions or a fixed quote.