Web application penetration testing
Web application penetration testing that goes past the scanner
Manual, authenticated testing of your app and APIs, with a retest included.
BlueRadius provides web application penetration testing for SaaS platforms, customer portals and internal business applications. Our testers log in as your users, work through every role, and look for the access-control and business-logic flaws that automated scanners miss, then show your developers exactly how to fix them.
You get a report your customers, auditors and insurers will accept, findings your engineers can reproduce, and a retest once the fixes ship.
When companies need a web app pen test
- An enterprise customer's security review asks for a recent third-party penetration test report.
- A SOC 2 audit where the auditor expects evidence of independent testing.
- PCI DSS requires application-layer testing of the systems in your cardholder data environment.
- A major release: a new product, a rebuilt authentication system, a move to multi-tenant, or a new public API.
- A cyber insurance renewal asking when your applications were last tested.
What we test
Authentication and session management
Login, password reset, multi-factor authentication, single sign-on and session handling. We look for ways to bypass MFA, take over accounts through reset flows, reuse or predict session tokens, and stay logged in after a password change.
Authorization and access control
The most common serious finding in modern applications. We test whether a user can read or change another user's data by altering an ID (insecure direct object references), whether a standard user can reach admin functions, and whether customer data stays separated in multi-tenant SaaS.
Business logic
Flaws that only make sense in the context of your application: skipping a payment step, applying a credit twice, approving your own request, or manipulating prices and quantities. No scanner finds these, which is why we spend time understanding how the application is meant to work before we try to break it.
Input handling and injection
Cross-site scripting, SQL and NoSQL injection, server-side request forgery, file upload abuse, template injection and deserialization flaws, tested by hand where the scanner results are inconclusive.
APIs behind the application
Modern front ends are mostly API calls, and the API is often less protected than the screen in front of it. We test the REST or GraphQL endpoints your application uses, including the ones the interface never calls, against the OWASP API Security Top 10.
Configuration and dependencies
Security headers, TLS, cookie flags, exposed debug endpoints, verbose errors and known vulnerable libraries. These are usually lower severity, so we group them rather than let them crowd the important findings.
How an engagement runs
- Scoping. We agree the application, environments, roles, APIs and testing window, and who will read the report.
- Walkthrough. A short session with someone who knows the product, so we understand the workflows that matter.
- Testing. Automated discovery to cover the surface, then manual testing for the flaws that need judgment. Critical findings are reported to you the same day rather than held for the report.
- Reporting. An executive summary, plus each finding with severity, the steps to reproduce it, evidence and a fix your developers can apply.
- Retest. Once fixes are deployed, we verify them and issue an updated report.
Related testing
Web applications rarely fail alone. Many clients pair this test with an external penetration test of the infrastructure the application runs on, or with a broader vulnerability assessment. If the application includes LLM features or AI agents, add an AI penetration test. If the test is for a compliance program, our SOC 2 and PCI DSS consultants can make sure the report answers the requirement, and a virtual CISO can own the remediation plan afterward.
Frequently asked questions
What is web application penetration testing?
A hands-on security test of a web application by a tester acting as an attacker. It looks for weaknesses in authentication, authorization, input handling, session management and business logic, tries to exploit them, and shows what an attacker could reach: other customers' data, admin functions, or the systems behind the app.
How is it different from a vulnerability scan?
A scanner sends known payloads and flags responses that look vulnerable. It is good at missing headers and known library flaws and poor at anything that needs an understanding of your app, such as one customer reading another customer's records by changing an ID, or a discount applied twice by replaying a request. Those logic and access-control flaws are where most serious web app findings come from, and they need a human tester.
Do you test as a logged-in user?
Yes, and we recommend it. Most of an application sits behind the login, and the most damaging flaws are usually about what one role can do that it should not. We ask for test accounts for each role, ideally in two separate tenants for multi-tenant SaaS, so we can test whether data stays separated.
Can you test in production?
We prefer a staging environment that matches production, especially for tests that create or change data. If production is the only option, we agree rules of engagement, avoid destructive actions, and coordinate timing with your team.
What standard do you test against?
We use the OWASP Web Security Testing Guide as the methodology and the OWASP Application Security Verification Standard (ASVS) for coverage, with the OWASP Top 10 as the common language in the report. For APIs we also cover the OWASP API Security Top 10.
Is retesting included?
Yes. Once your developers have fixed the findings, we retest them and issue an updated report showing what was resolved. Many customers and auditors want to see the retest, not just the original findings.
Will the report satisfy our customer, auditor or PCI requirement?
That is the point of scoping it properly. We confirm up front who will read the report: an enterprise customer's security team, a SOC 2 auditor, a cyber insurer or a PCI assessor. PCI DSS requires application-layer penetration testing at least once every 12 months and after significant changes, and we make sure the scope and report cover what your assessor will look for.
Scope your web application pen test
Send us the application, the number of user roles, any APIs in scope and who needs to see the report, and we will come back with a scope and a quote. Book a 30-minute scoping call, or see our full range of penetration testing services.