Free tool
Penetration testing RFP and scope builder
Answer a few questions and get a ready-to-send penetration testing RFP and scope, plus a price band from Invadel's published starting prices. Free, and no email required.
Example: web application and API, staging, 3 roles, SOC 2, start within 2 weeks
Your RFP and scope
PENETRATION TESTING RFP AND SCOPE 1. Objective Engage an independent penetration testing provider to find exploitable vulnerabilities in the assets below, show their business impact, and confirm the fixes with a retest. The report will be used as evidence for SOC 2. 2. In-scope assets - Web application: authenticated testing of access control and business logic across 3 user roles or tenants. - API: every documented endpoint (REST, GraphQL or SOAP), tested as each of the 3 user roles or tenants. Environment: Staging, a production-like copy with test data only. Target start: Within 2 weeks. 3. Testing standard Testing follows the Penetration Testing Execution Standard (PTES), plus the OWASP Web Security Testing Guide (WSTG) for the web application, the OWASP API Security Top 10 for the API. 4. Required deliverables - An executive summary for leadership. - A technical report with reproduction steps, evidence and a severity rating for every finding. - An attestation letter for auditors and customers, with findings mapped to SOC 2. - A free retest of remediated findings, with an updated report. 5. Rules of engagement - Written authorization from the asset owner before testing starts. - Agreed testing windows and a named emergency contact on both sides. - No denial-of-service or destructive testing without written approval. - Test accounts for each role; test data only, never real customer data. - Critical findings reported immediately, not held for the final report. - The testers' source IP addresses shared before testing starts. 6. Questions every vendor must answer - Who will do the testing, by name, and are they your employees or subcontractors? - Is any part of the work crowdsourced, offshored or fully automated? - Is a retest included, how many rounds, and for how long after the report? - Is the price fixed in writing for this scope, or billed hourly or by credits? - What does the report include, and can we see a redacted sample? - How soon can testing start, and how long will it take? 7. Response requested A fixed price for the scope above, the named testers, the proposed timeline and a sample report.
Estimated price band
Estimate from Invadel's published starting prices, read from the pricing page on .
| Test | Starting price |
|---|---|
| Web application penetration test | from $5,200 |
| API penetration test | from $4,000 |
| Total | from $9,200 |
Starting prices are for the smallest size of each test. More roles, endpoints or IP addresses move a test into a larger tier, and the exact price is fixed in writing once the scope is agreed. See the pricing page or refine it in the cost calculator.
How this estimate is built
Every figure comes from the starting prices Invadel publishes on its pricing page, read on : web application from $5,200, API from $4,000, mobile (iOS and Android) from $6,000, external network from $4,200, internal network from $6,000, cloud from $6,800, wireless from $3,800, phishing from $3,600, red team from $12,500. The builder adds the starting price of each test you select and shows the sum as a "from" total. It does not guess at size, so the band is the floor of what the work costs with us.
The RFP itself is vendor-neutral. It states the objective, lists the assets you picked, names the testing standard (PTES, plus the OWASP guide for each application type), sets the deliverables every provider should match and the rules of engagement, and ends with the questions that separate one quote from another.
Worked example
A SaaS company preparing for a SOC 2 audit selects its web application and the API behind it, tested on staging with 3 user roles. The band is the web application test from $5,200 plus the API test from $4,000: from $9,200 in total, with a free retest of fixed findings included in both. With three roles, the web application test usually lands in the medium tier, so the written price will likely sit above that floor.
FAQ
Questions about the builder
01Is the price band a quote?
No. It adds up Invadel's published starting prices for the tests you picked, so it is the lowest the work can cost with us. The exact price is fixed in writing once we see your scope, with no sales call needed: send it through the scoping form.
02Can I send this RFP to other vendors?
Yes. The document is vendor-neutral: paste it into an email or a procurement portal and send the same scope to every provider, so the quotes compare like for like. The vendor questions in section 6 explain most of the gaps between two prices.
03Why does the number of user roles matter?
Each role or tenant is tested against the others, so the access-control work grows with the count. On our pricing page, a small web application test fits one or two user roles; several roles with an admin panel is the medium tier. That is why the starting price is a floor, not a forecast.
04Does Invadel store what I enter?
No. The builder runs in your browser and asks for no email or contact details. Nothing you choose is sent to us unless you decide to send the scope through the scoping form.
Cite this: Invadel, "Penetration Testing RFP & Scope Builder", https://invadel.com/tools/pentest-rfp-builder/, prices as of .