Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Web applications · REST and GraphQL APIs

Web Application & API Penetration Testing

Senior testers attack your web applications and APIs the way a real attacker would, to find broken access control, authentication flaws, injection and business logic errors before anyone else does.

  • OWASP Top 10 and beyond
  • Authenticated and unauthenticated
  • Business logic tested by hand
Sample findings · Web and API testSample
CRITICALAny customer's orders readable through the APIBroken object level authorisation on /api/orders/{id}
HIGHStandard users can call admin endpointsRole checks happen only in the front end
HIGHDiscount code can be applied many timesBusiness logic flaw in the checkout
MEDIUMSession tokens survive a password changeStolen sessions stay valid
Each finding with evidence, a risk rating and a fixSample findings

In one sentence

What is web application and API penetration testing?

Web application and API penetration testing is a hands-on security test in which testers attack your web applications and the APIs behind them, to find the weaknesses an attacker could exploit to reach data or take over accounts.

Scanners find known issues. Our testers also find what scanners miss: broken access control between users and roles, business logic flaws and chained weaknesses, mapped to the OWASP Top 10 and beyond.

When to test

  • Before launching a new application or API
  • After major changes to login, payments or permissions
  • At least once a year, or as your compliance requires
  • When a client asks for independent evidence

Scope

What we test

Every area an attacker would probe, in your web front end and the APIs behind it.

Authentication and sessions

Login, password reset, multi-factor authentication, single sign-on, session handling and token lifetimes.

  • Login
  • MFA
  • Tokens

Access control

Whether users can reach other users' data or functions above their role, including insecure direct object references.

  • Authorisation
  • IDOR
  • Roles

Injection and input handling

SQL and command injection, cross-site scripting, server-side request forgery and unsafe file uploads.

  • SQL injection
  • XSS
  • SSRF

Business logic

Workflow and payment abuse that no scanner finds: skipped steps, repeated discounts, race conditions.

  • Workflows
  • Payments
  • Race conditions

API-specific weaknesses

REST and GraphQL APIs: excessive data exposure, mass assignment, missing rate limits and undocumented endpoints.

  • REST
  • GraphQL
  • Rate limits

Configuration

TLS, security headers, CORS, error handling and exposed debug or admin interfaces.

  • TLS
  • Headers
  • CORS

Approach

Testing approaches based on access

Choose how much you share with us. More context means deeper coverage in the same time.

No prior knowledge

Black box

We attack the application as an outside user would, finding what is reachable without an account.

Accounts and some context

Grey box

With test accounts for each role, we test access control and business logic in depth. This is what most clients choose.

Full access

White box

With source code or API specifications, we combine live testing with a review of how security is implemented.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Findings mapped to the frameworks your developers and auditors know.

  • OWASP Top 10
  • OWASP API Security Top 10
  • CREST guidance
  • PCI DSS
  • NIST SP 800-53

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

What does a web application penetration test include?
Testing of authentication, sessions, access control, input handling, business logic and configuration for the applications in your agreed scope, with every finding reported with evidence, a risk rating and a fix.
Can you test an API without a front end?
Yes. Share the API documentation, an OpenAPI specification or a collection of example requests, plus test credentials, and we test the API directly.
Do you test as a logged-in user?
Yes, and we recommend it. Most serious findings, such as one customer reading another's data, only appear with accounts for each role.
Should we test production or staging?
Either can work. Staging avoids any impact on real users if it matches production closely; production gives the most realistic result. We agree this with you during scoping.
How long does it take?
It depends on the size and complexity of the application. We confirm the effort and dates in your statement of work before testing begins.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal. Request a retest for any finding there once it is fixed.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.