Manual, authenticated testing of your web application and API by a U.S. based tester with 10+ years of penetration testing experience and 20+ certifications. You receive a clear report your developers can act on and an Letter of Attestation your customers and auditors will accept.
Get a Free Quote | Request a Sample Report
Quotes are usually sent within a few hours. Testing can usually start within 2 to 3 weeks.
Who Needs a Web Application Penetration Test?
Most of our clients come to us for one of three reasons:
- A customer of our client asked for proof of a pen test. A security questionnaire or contract requires a recent third-party penetration test before a deal can close.
- An audit is coming. You are working toward SOC 2, ISO 27001, PCI DSS, or HIPAA and need independent testing as evidence.
- It is time. Your annual test is due, or you have released major changes since the last one.
If this is your first penetration test, that is common. We will walk you through scoping in one short conversation.
What We Test
We test your application the way a real attacker would, with valid user accounts and a focus on the flaws that automated scanners cannot find.
- Authentication and session handling: login, password reset, multi-factor authentication, and session management
- Access control: whether one user can reach another user's or another customer's data, and whether a standard user can gain admin privileges
- Input handling: injection, cross-site scripting, server-side request forgery, and file upload flaws
- Business logic: ways to misuse your application's own features, such as bypassing payment or approval steps
- API: the endpoints behind your application, including those the user interface does not expose
- Configuration: exposed components, security headers, and information leakage
- AI / LLM application security: prompt injection, jailbreaks, model manipulation, sensitive data leakage, unintended actions, manipulation of AI-generated responses, and abuse of AI-powered features
Our testing follows the OWASP Web Security Testing Guide and covers the OWASP Top 10. Our team also builds its own tools, including Burp Suite extensions, to test more thoroughly in the time available.
Manual Testing, Not an Automated Scan
Penetration tests cannot be automated. An "automated" pen test is often another name for a vulnerability scan, and many customers and auditors will not accept one.
Every Central InfoSec penetration test is driven by manual testing. Scanning tools may support the work but they never replace it. The most serious web application vulnerabilities we find, such as one customer being able to read another customer's data, are found by a person and not by a tool.
Who Performs Your Test
You will know exactly who is testing your application when you receive your quote.
- Your lead tester has 10+ years of penetration testing experience
- Your lead tester holds 20+ certifications, including CRTO, OSCP, OSWP, GPEN, GWAPT, GCPN, GMOB, PNPT, PWPP, PWPA, CEH, and PenTest+
- Central InfoSec testers are all based in the U.S.
Our Process
- 1. Scoping. Complete our short contact form so we understand your application, user roles, and goals.
- 2. Quote. You receive a quote within 1 business day, with testing options, who your tester will be, sample reporting output, example finding writeups, and our methodology.
- 3. Kickoff. You provide test accounts and a point of contact. We confirm testing dates and rules of engagement.
- 4. Testing. We perform hands-on manual testing for the hours scoped to your project. If we find a critical vulnerability, we tell you right away with ad-hoc reporting and a debrief if needed.
- 5. Reporting. You receive your Executive Summary Report, Technical Details Report, Spreadsheet of Findings, and Letter of Attestation.
- 6. Debrief. We walk your team through the findings if needed.
- 7. Retest (optional). After you fix the findings, we verify each fix, and update your report to indicate which findings were confirmed to be fixed.
Timeline
- Form submitted to quote: 1 business day (usually only a few hours)
- Signed quote to testing start: 2 to 3 weeks
- Lite and Basic projects: one to two weeks
- Standard and Advanced projects: two to three weeks
- Retest after your fixes: within 30 days
Have a deadline from a customer or auditor? Tell us the date and we will tell you whether we can meet it. We offer expedited scheduling for urgent deadlines, including working nights and weekends.
What You Receive
One or two PDF reports are not enough. Every Central InfoSec penetration test includes four deliverables:
- Executive Summary Report for senior management and executive leadership
- Technical Details Report for the teams who will fix the findings
- Spreadsheet of Findings for tracking remediation efforts
- Letter of Attestation for your customers and auditors
Executive Summary Report
Written for senior management and executive leadership. It covers the project purpose, the scope, our methodology, a summary of your overall security posture, how your posture compares to similar organizations, your key security strengths, key areas for improvement, statistics on the findings, and strategic approaches to fixing core issues.
- Project Information
- Executive Summary
- Testing Methodology
- Testing Summary
- Summary Opinion
Technical Details Report
Written for remediation teams and technical staff who need specific information to resolve vulnerabilities. It contains everything in the Executive Summary Report, plus:
- Attack Narrative (if applicable)
- Technical Details of Findings and Recommendations
- Appendices, including testing details, scope, live hosts, and a custom severity matrix
Spreadsheet of Findings
Many companies only provide PDF reports, which are hard to copy, paste, and track findings from. We create an additional spreadsheet so your team can track and remediate findings easily.
If you do not have a tracking system, you can use the spreadsheet as one. Assign each finding to an employee or team, and use the prefilled status values to update progress. The date is tracked automatically each time a status changes.
Letter of Attestation
If a customer or auditor asked for proof of a penetration test, this is usually the document they want. The Letter of Attestation is written for your customers who need proof that security testing was performed. It does not include detailed or sensitive information, so you can share it without revealing the findings in your full report.
What Makes Our Reports Different
Over the years, clients have given us numerous compliments about our reports. Here is why:
- High-quality reporting with high-quality screenshots
- PDF reports and a spreadsheet of the findings for easier remediation tracking
- Detailed recommendations, with references for many findings
- Specific findings instead of grouped findings, so you know exactly what to fix
Example 1:
Many companies provide generic findings with generic recommendations, that leave their clients confused and with extra work to determine what actually needs to be fixed. Central InfoSec strives to provide detailed recommendations with references. Compare the two examples below.
A generic finding from another company
This finding does not say which header is missing, and the list even includes deprecated headers. Clients are left to work it out themselves.
Finding: Missing HTTP Headers
Description: One or more of the following HTTP headers are missing: Strict-Transport Security, Content Security Policy, X Frame Options, X Content Type Options, Cross Origin Opener Policy, or Referrer Policy.
Recommendation: Add any of the missing HTTP headers if they are not currently present. You need to manually review your server configuration to determine which are missing from the list above.
A detailed finding from Central InfoSec
Not every recommendation includes references or this level of detail, but this is the standard we aim for.
Finding: HTTP Security Response Header Missing (Cross Origin Opener Policy)
Description: The HTTP response header "Cross-Origin-Opener-Policy" (COOP) is missing. COOP ensures a top-level document does not share a browsing context group with cross-origin documents. COOP will process-isolate your document, and potential attackers cannot access your global object if they were to open it in a popup, preventing a set of cross-origin attacks dubbed XS-Leaks. If a cross-origin document with COOP is opened in a new window, the opening document will not have a reference to it, and the window.opener property of the new window will be null. This allows you to have more control over references to a window than rel=noopener, which only affects outgoing navigations.
Recommendation: Add the missing HTTP response header. Additional details are noted below.
Below is an example of isolating the browsing context exclusively to same-origin documents.
• Cross-Origin-Opener-Policy: same-origin
Example Syntax:
• Cross-Origin-Opener-Policy: unsafe-none
• Cross-Origin-Opener-Policy: same-origin-allow-popups
• Cross-Origin-Opener-Policy: same-origin
Example Syntax Directives:
• unsafe-none: This default value allows the document to be added to its opener's browsing context group unless the opener itself has a COOP of same-origin or same-origin-allow-popups.
• same-origin-allow-popups: Retains references to newly opened windows or tabs that either do not set COOP or that opt out of isolation by setting a COOP of unsafe-none.
• same-origin: Isolates the browsing context exclusively to same-origin documents. Cross-origin documents are not loaded in the same browsing context.
References:
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
• https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html
Example 2:
Many companies group findings together to save time on reporting. That leaves their clients confused and with extra work to determine what actually needs to be fixed. Central InfoSec strives to provide specific findings with actionable recommendations. Compare the two examples below.
Multiple findings groups together from another company with a generic recommendation
Grouped Findings:
• API Issues
Grouped Recommendation:
• Use better API controls
Individual findings for every API issue from Central InfoSec
Individual Findings:
• API Broken Access Control (API Does Not Require Key)
• API Broken Function Level Authorization (BFLA)
• API Broken Object Level Authorization (BOLA)
• API Broken Object Property Level Authorization (BOPLA)
• Lack of API Protections (No API Rate Limiting)
• Swagger API Documentation Exposed
• Unauthenticated API Endpoint Exposed
• Weak API Keys (Brute Forced API Key)
Individual Recommendations:
• Each finding includes their own description, screenshot, recommendation, and other details
Retesting
After your developers fix the findings, we retest each one and mark it as resolved or still open. You receive an updated report that reflects which findings were fixed.
A retest is optional, and it is worth considering if you plan to share your results. A customer's security team that sees open findings will ask whether they were fixed. The retest gives you the answer in writing. Retests can be requested within 1 year of your report.
Testing Options and Pricing
Every quote includes multiple service tiers so you can choose the testing that fits your budget, timeline, and required depth. All four deliverables are included with every tier.
- Lite Pen Test: essential testing to identify the most common vulnerabilities. A cost-effective starting point when you need quick visibility on a limited budget.
- Basic Pen Test: a balance between Lite and Standard. Budget-friendly testing focused on vulnerabilities that are easiest for an attacker to exploit.
- Standard Pen Test (recommended): the recommended starting point for most projects, with a balance of budget and hours designed for optimal project success.
- Advanced Pen Test: extensive testing with added hours for hard-to-exploit vulnerabilities and complex issues such as business logic flaws. Best for larger projects and enterprises that want the deepest review.
Which tier is right for you? Smaller companies, startups, and teams with an MVP that have never had a pen test usually choose Lite, Basic, or Standard. Mid-sized organizations and larger enterprises usually choose Standard or Advanced.
Lite and Basic tests average 10 to 40 hours of work over about one to two weeks. They may sample targets and vulnerabilities to give you a practical starting point without the length or expense of a full-scale assessment. Standard and Advanced tests typically involve 40 to 150 hours of in-depth, hands-on work over two to three weeks.
All testing is time-boxed and performed on a best-effort basis, focused on identifying your greatest areas of risk within the timeframe scoped.
Most web application penetration tests cost between $5,000 and $30,000, depending on the size of the application, number of roles being tested, the depth of testing, and other factors. Your quote is a fixed price for the scope described.
Frequently Asked Questions
How much does a web application penetration test cost?
Most tests cost between $5,000 and $30,000. Price depends mainly on the hours of testing, which are driven by the size of your application, the number of API endpoints, the number of user roles, the depth of testing, and other factors. Quotes may include Lite and Basic tiers for tighter budgets.
How long does the pen test take?
Lite and Basic projects usually take about one to two weeks. Standard and Advanced projects usually take two to three weeks.
How soon can you start?
We can usually start within 2 to 3 weeks of a signed Statement of Work.
Do you test production or staging?
Either. A staging environment that mirrors production is ideal because it removes any risk to live data. Many clients test in production, and we plan the testing with you to avoid disruption.
Will testing disrupt our application or users?
Disruption is rare. Our testing is manual and controlled, and we do not perform denial-of-service attacks. We agree on rules of engagement with you before testing starts.
What do you need from us before testing starts?
The URLs in scope, test accounts for each user role, and a point of contact who can answer questions during the test. That is usually all.
What is the difference between authenticated and unauthenticated testing?
Unauthenticated testing looks at what an outsider can reach without logging in. Authenticated testing uses valid accounts to test what a logged-in user can do, which is where most serious web application vulnerabilities are found. Authenticated testing typically uses one or two test accounts per role.
Will the report satisfy our SOC 2 auditor or our customer's security team?
Yes. Our reports and Letter of Attestation are written to be used as evidence for audits and customer security reviews. If your customer or auditor has specific requirements, send them to us and we will confirm before you sign.
Can we share the report with our customers?
Yes. Most clients share the Letter of Attestation and Executive Summary Report, and share the Technical Details Report only under NDA.
Do you retest after we fix the findings?
Yes. Retesting is available as an option with every test. We verify each fix and update your report to indicate which findings were confirmed to be fixed.
What is the difference between the Lite, Basic, Standard, and Advanced tiers?
Hours of testing. Lite and Basic have fewer hours, so we focus on the most common and most easily exploited vulnerabilities and may sample targets instead of testing every one. Standard gives the tester time for a full hands-on assessment. Advanced includes extensive testing with added hours for hard-to-exploit vulnerabilities and complex issues such as business logic flaws. You receive the same four deliverables with every tier.
Will you sign an NDA?
Yes, we will sign an MSA, NDA, and SOW before the first engagement starts. Future engagements only require a new SOW to be signed. We are also happy to sign your NDA before you share any details about your application.
Trusted Penetration Testing Company
Central InfoSec named Best Boutique Penetration Testing Company by the Global 100 Awards.
Get a Web Application Pen Test Quote
Tell us about your application and we will send you a free customized quote usually within a few hours. Your quote includes testing options, sample reporting output, example finding writeups, our methodology, and the qualifications of your lead tester.
Not sure what you need? Send us the question your customer or auditor asked, and we will tell you what will satisfy it.



