Penetration Testing/Web App & API Testing
Web Application & API Penetration Testing

Web application penetration testing for apps, APIs and SaaS

Manual testing of your web apps, APIs and multi-tenant SaaS for broken access control, business logic flaws, injection and tenant leakage. Every finding comes with a reproducible proof of concept and a fix your engineers can ship.

  • Authorization tested by hand across every role and tenant
  • REST, GraphQL and SOAP APIs, including endpoints the app doesn’t show
  • Mapped to OWASP Top 10:2025 and OWASP API Security Top 10 2023
  • Real-time findings on the PTaaS platform, with JIRA integration
The credentials behind every engagement
CREST-accredited for penetration testingISO/IEC 27001 certifiedSOC 2 Type 2 attested
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026
Penetration Testing Solution of the Year2026 CyberSecurity Breakthrough Awards

Reviewed by Omair Manzoor, Founder & CEO, ioSENTRIX · Updated

Key terms: What is IDOR? · What is SSRF?

Trusted by security teams at
See it in action

Could another customer read your customers' data?

An automated scan reported no issues. A tester changed one ID in an API request and got another tenant's invoice back.

REQUEST · signed in as user AGET /api/v1/invoices/10421043Authorization: Bearer eyJhbGci… (user A)APIserverAUTOMATED SCAN✓ No issues foundioSENTRIX TESTERtesting…ioSENTRIX TESTER✗ 200 OK: another tenant's invoiceBroken object level authorizationOWASP API1:2023 · CWE-639

What happens in the test

Illustrative example.

  1. The scan runs with one user session and finds nothing.
  2. The tester signs in as user A and requests invoice 1043, which belongs to tenant B.
  3. The API returns it: broken object level authorization (OWASP API1:2023, CWE-639).
  4. The fix is an ownership check on every API call, and the retest confirms it.
Multi-tenant SaaS

One changed ID. Another customer's data.

We sign in as two different customers and try to cross the line between them: in your API, headers, search and exports.

Swipe to see the full exhibit →

Every tenant is one ID away

Multi-tenant flaws hide in IDs, headers, search and exports, not on the login page.

We test as two customers

We sign in as separate tenants and try to read, change and export each other's data.

Isolation proven, not assumed

Each leak comes with a fix, and we retest until every path returns 403.

Read this exhibit as text
  1. We sign in to a multi-tenant SaaS app as one customer, tenant 2041, and test whether that account can reach other customers' data.
  2. Changing the organization ID in an API request returns another tenant's invoices. This is broken object level authorization, OWASP API1.
  3. Setting an X-Tenant-ID header to another tenant's ID is accepted, because the API trusts the header instead of the session.
  4. A shared search index returns records from a third tenant.
  5. Export files use predictable IDs, so another tenant's customer list can be downloaded.
  6. After the fixes, the same four requests return 403 Forbidden, and each account can read only its own tenant. Findings map to the OWASP API Security Top 10 and OWASP ASVS.

Source: ioSENTRIX web and API testing methodology; OWASP API Security Top 10 (2023). Illustrative example with fictional tenants, not client data.

The short answer

What is web application penetration testing?

Web application penetration testing is a hands-on security test of a web application and the APIs behind it. Testers attack authentication, authorization, business logic, input handling and configuration the way a real attacker would, and prove each exploitable weakness with a reproducible proof of concept and a fix.

API penetration testing applies the same method to the endpoints your apps, partners and integrations call directly, where many access-control flaws hide. For SaaS products, testing adds tenant isolation: proving one customer cannot reach another’s data. Findings map to the OWASP Top 10:2025 and the OWASP API Security Top 10 2023.

At ioSENTRIX, web application and API penetration testing is carried out by hand by certified testers at a CREST-accredited firm, and every fix gets a free retest.

You need a web app pentest if

  • An enterprise customer or auditor asked for a third-party pentest report
  • You are launching a product, a major feature or a public API
  • Your SaaS serves many customers from shared infrastructure
  • You changed authentication, roles or payment flows
What we test

Four areas, tested by hand

Scope follows your application. Most web application and API penetration tests cover these four areas.

Area 1

Web application

The browser-facing app, tested like an attacker with an account.

  • Authentication and session handling
  • Access control across roles
  • Injection and cross-site scripting
  • Business logic and workflow abuse
Area 2

APIs

The endpoints behind your app and the ones partners call directly.

  • Object and property-level authorization
  • REST, GraphQL and SOAP
  • Rate limits and resource abuse
  • Server-side request forgery
Area 3

Multi-tenant SaaS

Proof that one customer cannot reach another.

  • Cross-tenant data access
  • Tenant ID tampering
  • Shared storage and cache leakage
  • Admin and support tooling
Area 4

Configuration and supply chain

What surrounds the code.

  • Security headers and TLS
  • Third-party scripts and dependencies
  • Exposed debug and admin endpoints
  • Error handling and information leakage
Methodology

How we test: example test cases

A sample of the manual test cases in a typical web application and API penetration test. Your scope decides the full list.

A01:2025

Broken access control across roles

Signed in as a low-privilege user, we call admin functions and change object IDs to reach data and actions we should not.

API3:2023

Object property-level authorization

We add fields such as role or price to requests, and check responses for properties the user should never see.

API6:2023

Business flow abuse

We script flows such as sign-up, coupon redemption or checkout to test whether they can be abused at scale.

SAAS-01

Cross-tenant access

With accounts in two tenants, we swap tenant identifiers, tokens and object IDs to reach the other tenant’s data.

A05:2025

Injection

We test inputs, headers and API parameters for SQL, NoSQL, command and template injection, and for cross-site scripting.

API7:2023

Server-side request forgery

We test URL and webhook inputs for requests that reach internal services or cloud metadata endpoints.

Sample finding

What a finding looks like in our report

An illustrative example in our report format. Not client data.

Finding 01 · IllustrativeCritical

Changing one header lets a tenant admin read another tenant’s users

OWASP Top 10:2025 A01 Broken Access Control · OWASP API Security Top 10 2023 API1:2023 Broken Object Level Authorization

What we found

The SaaS app read the tenant ID from a request header set by the front end, and the API trusted it without checking it against the signed-in user’s session. By changing the header, a tester signed in as an admin of one tenant listed the users, roles and email addresses of another tenant.

Impact

Any customer admin can read other customers’ user accounts and role assignments.

How to fix it

Derive the tenant from the authenticated session on the server, never from client input. Apply a tenant filter in the data layer for every query, and add automated tests that request another tenant’s objects.

What you get

What you get from every web app pentest

Not a scanner export. Proven attacks and fixes your engineers can act on.

1

Findings with proof, ranked by exploitability

Each finding has a severity, the requests that reproduce it and remediation guidance your developers can act on.

2

Mapped to OWASP

Every finding mapped to the OWASP Top 10:2025 and, for APIs, the OWASP API Security Top 10 2023, ready for auditors and enterprise security reviews.

3

Walkthrough, then retesting

The tester who found each issue walks your engineers through it, and retesting confirms the fix.

ioSENTRIX sample penetration test report cover

See how we write findings before you talk to us

A redacted sample penetration test report (web application): finding write-ups, proof-of-concept evidence and remediation. No form required.

Download the sample report (PDF) →
Verified reviews

What security leaders say about working with us

★★★★★
“Unlike other providers, Omair and his team truly dive deep into our infrastructure, delivering findings that go well beyond the surface level. Communication is direct and seamless.”
Jesus B.
Cybersecurity Manager, Banking
Verified G2 review ↗
★★★★★
“We were impressed with ioSENTRIX’s ability to independently validate the security of our customer-facing product.”
Zeehasham R.
Data Scientist, Security Operations · Fortune 500 insurer
Verified Clutch review ↗
★★★★★
“The team at ioSENTRIX is professional and highly skilled at their craft.”
Awwab A.
SVP, Chief Information Security Officer
Verified G2 review ↗
How it works

How a web application penetration test works

Four steps, so you know what happens and what you get.

01

Scope

We review the app, APIs, roles and tenants, and reply with scope, timeline and a fixed quote.

Under an hour
02

Setup

You provide test accounts for each role, API documentation if you have it and a staging environment.

Before any work
03

Manual testing

Testers work through the app and APIs, with findings shared in real time and synced to JIRA.

Days to weeks, by scope
04

Report and retest

A report mapped to OWASP, a walkthrough with your engineers and retesting once fixes land.

At close
Reply in under an hour → fixed quote in writing → manual testing with real-time findings → report, walkthrough and retest
How we compare

Not a DAST scan. Not a checklist.

What a web application penetration test covers compared with the usual alternatives.

ioSENTRIX web app pentest
DAST scanner
Bug bounty program
Access control and tenancy
Tested by hand across roles and tenants
Not tested reliably
Depends on who takes part
Business logic
Tested against how your app is meant to work
Not tested
Sometimes, if a researcher looks
Coverage
The agreed scope, tested end to end
Pages and parameters the crawler finds
Whatever researchers choose to test
Evidence
Reproducible proof of concept and a fix
Findings to triage, with false positives
Individual reports of varying depth
Audit-ready report
Yes, mapped to OWASP
Scan export
Not usually
Scope and price

What affects the scope and price of a web app pentest

Web application and API penetration tests are priced on effort. These are the decisions that move the quote.

What moves the quote

  1. 01How many apps, pages and API endpoints are in scope
  2. 02How many user roles and tenants need testing
  3. 03REST, GraphQL or SOAP, and whether API documentation exists
  4. 04Black-box testing, or access to source code and architecture
  5. 05Staging or production, and any testing windows
  6. 06Retesting, report format and any timebox to fit a budget
Read: Web application penetration testing: OWASP Top 10 in practice →

What we need from you to start

  • URLs and API documentation, such as an OpenAPI file or Postman collection
  • Test accounts for each role, across at least two tenants for SaaS
  • A staging environment that mirrors production
  • Rate limits, payment sandboxes or areas that are off limits
  • A technical contact for questions during testing
Scope my web app test
Track record

Numbers you can check

Ratings you can verify on G2 and Clutch.

G2
4.9 / 5
on G2 from 12 verified reviews
Clutch
5.0 / 5
on Clutch, Premier Verified
CREST-accredited for penetration testing
2017
founded; CREST-accredited, ISO 27001 certified, SOC 2 Type 2 attested
Independently verified

Credentials held by the firm

Every engagement runs inside a company whose methods and own security are checked by outside bodies.

CREST-accredited for penetration testing

CREST-accredited for penetration testing

CREST assesses the firm's testing methodology, quality assurance and handling of client data.

View our CREST listing →
SOC 2 Type 2 attested

SOC 2 Type 2 attested

An independent auditor tested our own security controls over time.

Request the SOC 2 report →
ISO/IEC 27001 certified

ISO/IEC 27001 certified

Our information security management system is certified to ISO/IEC 27001.

View in our trust center →
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026

Recognized independently

Penetration Testing Solution of the Year, 2026 CyberSecurity Breakthrough Awards. G2 High Performer, Fall 2026.

Founded in 2017.

Our commitments

What you can count on

Four promises we make on every testing engagement.

  • Free retest of every fixOnce your team fixes a finding, we test it again at no extra cost and update the report.
  • A fixed priceThe quote you sign is what you pay. The price only changes if you change the scope.
  • A report your auditor acceptsIf your auditor has questions about the report, we answer them and update it until it is accepted.
  • A reply in under an hourSend the form and we reply within an hour during US business hours.
For your buying team

Everything your reviewers will ask for

Security, finance and procurement each need something different. Forward this page, or pull what each reviewer needs.

For security

Sample report

See exactly what you get: findings, proof of concept, fixes and retest results.

Download the sample report (PDF) →
For vendor risk

Trust center

Our SOC 2 Type 2 report and security documentation for your vendor review.

Open the trust center →
For procurement

Procurement pack

Master services agreement, sample statement of work, certificate of insurance and W-9.

Request the procurement pack →
For your team

Share this page

Send the link to the people who need to sign off.

Who you work with

Who does the work

Senior security engineers do the hands-on work and write up the results, so the person who found an issue explains it to your team.

Certified engineers

Each engineer holds one or more of OSCP, OSWE, OSCE, CISSP, CISA or AWS security certifications.

Accredited firm

ioSENTRIX is CREST-accredited for penetration testing, ISO/IEC 27001 certified and SOC 2 Type 2 attested.

Since 2017

Founded in 2017, with security work for Fortune 100, financial services, insurance and SaaS companies.

Ready to see what your app and APIs expose?

We reply in under an hour · no sales pitch

Scope my web app test
Standards

Frameworks we test and map to

◆OWASP Top 10:2025◆OWASP API Security Top 10 2023◆OWASP WSTG v4.2◆OWASP ASVS 5.0◆PTES◆PCI DSS v4.0.1 Requirement 11.4
FAQ

Frequently asked questions

How long does a web app pentest take?

A typical web application penetration test takes 1–2 weeks, depending on scope: the number of applications, APIs, user roles and tenants. We reply in under an hour during US business hours; scope, a timeline and a fixed quote follow the scoping call, and findings appear on the PTaaS platform as they are confirmed.

Do you test APIs without a front end?

Yes. We test REST, GraphQL and SOAP APIs directly, using your OpenAPI file, Postman collection or captured traffic. API-only tests are mapped to the OWASP API Security Top 10 2023.

What is SaaS penetration testing?

SaaS penetration testing is a web app and API test with extra focus on multi-tenancy: whether one customer can reach another’s data, settings or users. It also covers admin and support tools, integrations and single sign-on. Read what SaaS penetration testing involves.

Do you need our source code?

No. Black-box testing shows what an outside attacker sees. Access to code or architecture lets testers go deeper in the same time, and you can pair the test with secure code review.

Can we use the report for SOC 2 or PCI DSS?

The report documents scope, method and every finding with its fix, the evidence SOC 2 auditors and enterprise customers usually ask for. For PCI DSS, it can support the penetration testing that Requirement 11.4 calls for. See SOC 2 penetration testing requirements.

Ready when you are

Test your app and APIs before an attacker does

Tell us about your app, APIs and tenants. We reply in under an hour during US business hours, and a senior engineer follows with scope, timeline and a fixed quote.

A reply in under an hour · Fixed quote in writing before work starts · Your details are never shared