Break it before they do
Web Application
Penetration Testing
We test your web applications and APIs the way an attacker with an account would, logging in as each role and trying to reach data and actions that belong to someone else. Automated scanning covers breadth. Manual testing finds the access control and business logic flaws that scanners miss.
Logged in as every role
What every role
should never reach.
Testing follows the OWASP Web Security Testing Guide, with coverage measured against OWASP ASVS at the level you choose. We work in Burp Suite with test accounts for every role, and every finding is reproduced by hand with a request you can replay.
Phase 01 · Scope & roles
Agree the app, the roles and the environment.
A scope listing every in scope URL, API and user role, with test accounts for each.
- Staging or production, chosen with your hosting provider's rules in mind.
- Two accounts per role so we can test one user against another.
- API specifications or Postman collections, if you have them.
Phase 02 · Mapping
Map every page, endpoint and parameter.
An application map showing functions, inputs and the trust decisions behind them.
- Crawling and manual browsing as each role.
- Undocumented API endpoints found in the client code.
- The OWASP ASVS checks selected for the level you need.
Phase 03 · Access control
Try to reach what belongs to someone else.
Proof of every place one user or customer can read or change another's data.
- Insecure direct object references across every ID the app exposes.
- Vertical escalation from user to admin functions.
- Tenant isolation tested in apps that serve many customers.
Phase 04 · Input & logic
Feed it what the developers did not expect.
Confirmed injection, session and logic flaws, each with a request you can replay.
- SQL, command and template injection testing.
- Session handling, token storage and authentication flows.
- Business logic abuse such as altered prices or skipped approval steps.
Phase 05 · Report & readout
Hand developers fixes they can ship.
A report mapped to OWASP ASVS, with a retest option once fixes land.
- Each finding with steps to reproduce and a code level fix.
- Severity rated with CVSS and adjusted for your context.
- A readout with the practitioner who tested the app.
Agree the app, the roles and the environment.
A scope listing every in scope URL, API and user role, with test accounts for each.
- Staging or production, chosen with your hosting provider's rules in mind.
- Two accounts per role so we can test one user against another.
- API specifications or Postman collections, if you have them.
Map every page, endpoint and parameter.
An application map showing functions, inputs and the trust decisions behind them.
- Crawling and manual browsing as each role.
- Undocumented API endpoints found in the client code.
- The OWASP ASVS checks selected for the level you need.
Try to reach what belongs to someone else.
Proof of every place one user or customer can read or change another's data.
- Insecure direct object references across every ID the app exposes.
- Vertical escalation from user to admin functions.
- Tenant isolation tested in apps that serve many customers.
Feed it what the developers did not expect.
Confirmed injection, session and logic flaws, each with a request you can replay.
- SQL, command and template injection testing.
- Session handling, token storage and authentication flows.
- Business logic abuse such as altered prices or skipped approval steps.
Hand developers fixes they can ship.
A report mapped to OWASP ASVS, with a retest option once fixes land.
- Each finding with steps to reproduce and a code level fix.
- Severity rated with CVSS and adjusted for your context.
- A readout with the practitioner who tested the app.
Key benefits
Find the flaw a scanner cannot see.
Broken access control and business logic flaws need a person who understands what the app is for. That is where a senior tester spends the time, after automation covers the routine checks.
Results map to OWASP ASVS, so a customer security questionnaire or a SOC 2 Type II auditor gets an answer in the standard terms they already use.
Every finding comes with steps to reproduce, a replayable request and a fix written for your stack. Developers spend their time fixing, not decoding a report.
What you get
What lands on
your desk.
Three handoffs, written for the developers who fix and the leaders who answer customer questions.
The document
The report
Executive summary, scope by role and endpoint, ASVS coverage, and findings by severity with steps to reproduce, evidence and a specific fix written for your stack.
The working file
The findings tracker
One row per issue with severity, endpoint, CWE, status and an owner, ready to import into Jira or whatever your developers use to plan their work.
The conversation
The readout
A working session with the practitioner who tested the app and the developers who will fix it. We walk the findings in priority order and talk through the fixes.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Practical questions
Before the
first request.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
Staging, when it matches production closely. If it does not, we can test production with care: no destructive actions, request rates agreed in advance, and test accounts that keep real customer data out of reach.
Yes. APIs behind your web app and standalone APIs are both in scope when listed. An OpenAPI specification or a Postman collection helps, but we can also map endpoints from the client and its traffic.
Not for a standard test. Access to source turns it into a full knowledge test and lets us confirm root causes faster. If code quality is the real question, a secure code review is the better fit.
Yes, and more. The OWASP Top 10 is an awareness list, not a test standard. We follow the OWASP WSTG for method and report coverage against OWASP ASVS, which goes much further.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








