Call Contact Us

Web Application and API Penetration Testing

Hands-on web application and API testing by U.S.-only, certified testers.

Testers sign in as the user roles in the agreed scope and try what each role should never do: read another customer's records, approve their own refund, call an administrator's function. Every finding is confirmed by hand and mapped to MITRE ATT&CK and NIST 800-53, and after you patch, InfoSight reconfirms the fix within 24 hours.

What web application and API penetration testing is

NIST's glossary carries a definition written for applications (from SP 800-95): testers target individual binary components or the application as a whole to determine whether vulnerabilities can be exploited to compromise the application. NIST SP 800-115 adds what matters to a buyer: most tests look for combinations of vulnerabilities that together give more access than any single one could.

How it differs from a vulnerability scanner

OWASP describes web application vulnerability scanners as automated tools that scan applications, normally from the outside, for flaws such as cross-site scripting, SQL injection, command injection, path traversal and insecure server configuration. They are frequently called DAST tools (dynamic application security testing).

  • A scan (DAST) sends known attack patterns to the inputs it discovers. It is fast and worth running on a regular cadence, including before releases, but it generally lacks a tester's understanding of your business rules and of who may do what.
  • A penetration test may use the same scanners, then goes further: testers sign in as each role, discard false alarms, and exploit and chain what is real to show what an attacker could reach. In NIST SP 800-53's words, penetration testing goes beyond automated vulnerability scanning.

What a web application penetration test covers

Drawn from the testing categories of the OWASP Web Security Testing Guide, with how a test typically checks each:

Authentication and sessions

How users sign in, reset passwords and stay signed in.

Typical checks: default and weak credentials, lockout and MFA bypass, reset-flow flaws, and session tokens that can be stolen, replayed or never expire.

Access control across roles

Whether each role sees and does only what it should.

Typical checks: signing in as every role and requesting other users' records and admin functions, including by changing IDs.

Input handling and injection

Whether anything a user types or sends can become a command.

Typical checks: SQL and command injection, cross-site scripting and template injection, with hand-crafted payloads that get past filters and web application firewalls.

Business-logic flaws

A shop checks that every coupon is genuine but never notices one coupon used ten times on the same order. Each step is valid; the abuse is in the sequence.

Typical checks: replaying, reordering and racing workflow steps, such as a refund requested twice at once, a skipped approval or a price changed between cart and checkout.

File handling

Uploads, downloads and files stored on the server.

Typical checks: unexpected and malicious file uploads, path traversal outside the web root, and exposed backups or .git folders.

Client-side issues

Code that runs in the visitor's browser.

Typical checks: DOM-based cross-site scripting, open redirects, clickjacking, loose cross-origin (CORS) rules and sensitive data left in browser storage.

What an API penetration test covers

APIs are the endpoints your web front end, mobile app and partners call, and attackers call them directly. A test covers the API styles in the agreed scope; most applications expose REST APIs, and some GraphQL (flexible queries, usually through a single endpoint). InfoSight maps API findings to the OWASP API Top 10, now in its 2023 edition. Six of its ten entries, in plain words:

API1:2023 Broken Object Level Authorization (BOLA)

The API checks that you are signed in, not that the record is yours: a coat check that hands over whichever coat matches the number you call out. Change invoice 1001 to 1002 in a request and you are reading someone else's invoice.

Typical checks: accounts for each role, comparing what each may and may not reach when requesting other users' objects by ID, across the endpoints in scope that take one.

API2:2023 Broken Authentication

Weak handling of sign-in, tokens or keys lets an attacker act as someone else.

Typical checks: token signing, expiry and revocation, OAuth and OpenID Connect scopes, and brute-force limits on login and reset endpoints.

API3:2023 Broken Object Property Level Authorization

The API returns fields a user should not see, or saves fields a user should not set. That second half is mass assignment: add a role or a price to an ordinary update and the server accepts it.

Typical checks: comparing what each role can read and write, field by field.

API4:2023 Unrestricted Resource Consumption

Nothing caps how often or how heavily the API can be called, so an attacker can slow it or run up costs, such as text messages billed per request.

Typical checks: probing rate limits, page sizes and batched queries with controlled bursts inside the agreed test window.

API5:2023 Broken Function Level Authorization

An ordinary user can call an administrator's function, often by guessing its URL or switching the request method.

Typical checks: calling the admin endpoints in scope, documented and discovered, from each lower role, including a GET switched to a DELETE.

API9:2023 Improper Inventory Management

Old versions, test hosts and undocumented endpoints stay reachable after the team has moved on.

Typical checks: comparing the OpenAPI (Swagger) or GraphQL schema with what the API actually answers, and hunting for deprecated versions and debug endpoints.

The other four entries (sensitive business flows, server-side request forgery, security misconfiguration and unsafe use of third-party APIs) come into scope where your architecture calls for them. The full service pages go deeper: Web Application Testing and the API Security Assessment.

The yardsticks: OWASP and NIST

None of these is a law: the OWASP documents are voluntary community standards, guides and awareness lists, and NIST's guide binds only where a law or contract adopts it. A test measures your application against them; it certifies nothing.

How InfoSight runs a web application and API test

InfoSight's baseline methodology runs in five phases: discovery, reconnaissance, vulnerability identification, testing and analysis, and reporting. The first sets how much the testers know going in: black box, gray box or white box.

Gray-box, authenticated testing is the choice when access between users or tenants must be tested, because testing whether one customer can reach another's records normally needs at least two authenticated accounts. Testing with accounts needs test accounts for each role in scope, two in the same role where one customer's access to another's data is tested, plus any API credentials the scope needs.

How a web application or API test is scoped

Scope sets the effort. Gather these before the first call:

Bring them to the scoping call, and we leave with what we need to propose a scope and a price. The ranges security vendors publish put web application and API penetration tests at about $5,000 to $30,000, with the number of user roles, pages and endpoints setting where a test falls. Those are published market ranges, not InfoSight prices or a quote; see what a penetration test costs for the detail.

Scope your application test

Book a zero-cost 15-minute scoping call and instantly receive a preliminary scan report to share with stakeholders and executives.

Prefer the phone? Call 305.828.1003.

What you receive

Rules and audits that bear on application testing

Which rules apply depends on the data you hold and who regulates you. A test report is evidence for them where its scope, method and timing match what the rule asks for; it is not a certification or an attestation. An application test on its own can contribute the application-layer part of PCI DSS 11.4.1 when it is scoped to the cardholder data environment, but it is not the internal and external network testing 11.4 also requires; a network test is scoped separately.

PCI DSS (Requirement 11.4)

Entities in PCI DSS scope must run internal and external penetration tests at least once every 12 months and after any significant infrastructure or application upgrade or change, using a qualified tester who is organizationally independent. Exploitable findings must be corrected and the test repeated to verify the fix. PCI DSS is a payment-industry standard enforced through card brands and acquirers, not a statute.

FTC Safeguards Rule (16 CFR 314.4(d)(2))

Financial institutions under the FTC's jurisdiction, such as mortgage lenders and brokers, finance companies and tax preparation firms, must either run effective continuous monitoring (or other systems that detect vulnerability-creating changes on an ongoing basis) or conduct annual penetration testing, scoped each year by their risk assessment, plus vulnerability assessments at least every six months, after material changes, and whenever there are circumstances they know or have reason to know may have a material impact on their security program. Whether a customer portal is in that scope is a risk-assessment decision. Institutions that hold customer information on fewer than 5,000 consumers are excepted from that testing requirement (16 CFR 314.6).

NYDFS Cybersecurity Regulation (23 NYCRR 500.5(a)(1))

Entities that operate under, or are required to operate under, a license, registration, charter, certificate, permit, accreditation or similar authorization under New York's Banking, Insurance or Financial Services Law must, at a minimum, have a qualified internal or external party conduct penetration testing of their information systems from both inside and outside the systems' boundaries at least annually, under written vulnerability-management policies and procedures based on their risk assessment. Smaller covered entities that meet one of the size tests in 23 NYCRR 500.19(a) are exempt from this requirement.

SOC 2 and customer security reviews

If a SOC 2 auditor, a customer contract or a security questionnaire asks for a recent application penetration test, scope and timing follow from that request.

Why InfoSight?

tick image

Expert-Validated, Not Tool-Generated

Certified assessors (CISSP, OSCP, CEH) manually chain and confirm every finding: real exposure, not scanner noise.

tick image

25+ Years of Cybersecurity Experience in Regulated Industries

Since 1998, protecting finance, healthcare, energy, and government clients, with the compliance context to prove it.

tick image

IT + OT Coverage

One team assesses data center, cloud, and industrial (SCADA/ICS/IoT) environments under a single methodology. U.S.-based cybersecurity analysts supported by advanced technology.

tick image

Compliance-Mapped Evidence

Every finding maps to the framework that matters to you: NIST, HIPAA, PCI DSS, FFIEC, IEC 62443, or OWASP.

tick image

Findings Tracked in Mitigator®

Results don't die in a PDF. Track remediation status and exposure trends long after the engagement ends.

tick image

Board-Ready Reporting

Executive summaries for leadership, reproduction steps for engineers, delivered from the same engagement.

Related testing: the penetration testing services overview covers every test type, external network penetration testing the internet-facing systems around your application, and AI penetration testing chatbots, copilots and agents. See also the mobile app security assessment, secure code review, AD and Entra ID testing, social engineering and physical testing, red, blue and purple team testing and vulnerability assessments.

InfoSight is based in Miami Lakes, Florida, and serves clients nationwide; application and API testing can be performed remotely wherever you operate. Local pages: Miami, Atlanta and Dallas-Fort Worth.

Web application and API testing questions buyers ask

It depends on the pages, roles and endpoints in scope, so the schedule is set during scoping. Vendors that publish time estimates put a web application test at about 5 to 10 testing days (more for a complex application with many user roles) and an API test at about 3 to 6 days.

It depends on the rule that applies to you. PCI DSS sets internal and external tests at least every 12 months and after significant changes; the FTC Safeguards Rule calls for an annual test unless you run effective continuous monitoring or other ongoing vulnerability-detection systems; NYDFS Part 500 requires one at least annually for covered entities that are not exempt; HIPAA requires a periodic evaluation without naming a test (a January 2025 proposal would require a penetration test at least every 12 months and vulnerability scans at least every six months; as of October 2026 it is not final). Major releases, acquisitions and cloud migrations are common reasons to test in between, as a matter of risk rather than rule; outside those rules, your risk assessment and your rate of change set the cadence.

Not for a black-box or gray-box test, which works against the running application as an attacker would. Source code, or comparable internal detail such as architecture and configuration, makes it a white-box test; reviewing the code itself is a separate service, secure code review, which blends automated static analysis with deep manual inspection.

Either. InfoSight's web application testing works in development, QA or production; staging is the safer choice when it mirrors production closely, and a production test needs written authorization, agreed exclusions and a way to pause it. Testing stays inside a scope you approve up front, against systems you designate, with every action documented.

Yes. The API a mobile app calls is tested like any other API. For the app itself, the mobile app security assessment maps data flows and backend APIs and tests on rooted Android and jailbroken iPhones, not just emulators.

Within limits. Testing targets your configuration, data and user access, within the vendor's written testing rules and your contract.

Your assessment is run exclusively by U.S.-cleared, certified penetration testers, with no offshore outsourcing, which supports data sovereignty. Test accounts and credentials are shared through a channel agreed at scoping.

Findings move into the Mitigator® portal, where your team tracks remediation status and exposure trends long after the engagement ends. After you patch, click Retest and InfoSight reconfirms the fix within 24 hours.

Ready to Breach Your Own Defenses?

Book a zero-cost 15-minute scoping call and instantly receive a preliminary scan report to share with stakeholders and executives.

No spam—one expert follow‑up, guaranteed.

Want to Receive our Newsletter?

Stay informed of the latest cyber trends.