• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

Free RFP template | Security Testing

Penetration Testing RFP

A comprehensive RFP template for procuring penetration testing services. Includes scope definitions, evaluation criteria, deliverables checklist, and vendor comparison matrix.
Penetration tester
Pages
9
Sections
11
Fill-in fields
37
Scored criteria
5

What is inside

11 sections, ready to fill in

Each section opens with a short note on why it matters, followed by the wording and fill-in fields you complete before issuing.

  1. 01

    Executive Summary & Project Background

    State plainly who you are, what you want tested, and why now. Vendors price risk and ambiguity; a clear driver produces a sharper, cheaper bid.

  2. 02

    Scope of Work

    Define scope precisely. The single biggest cause of disputed penetration testing invoices is scope stated in adjectives rather than counts.

  3. 03

    Testing Methodology Requirements

    Require a named methodology. It is how you compare bids that otherwise all claim to be thorough.

  4. 04

    Deliverables & Reporting Standards

    Specify the report, because the report is the product. Ask for a sample, a redacted real report tells you more than any capability statement.

  5. 05

    Timeline & Milestones

    Set dates. Vendors with genuine capacity will commit; those without will hedge.

  6. 06

    Vendor Qualifications & Certifications

    Ask about the people who will actually do the work, not the company’s aggregate credentials.

  7. 07

    Evaluation Criteria & Scoring Matrix

    Published weightings for every criterion, scored on a 1 to 5 scale, so bidders know exactly how they will be judged.

  8. 08

    Pricing Structure & Budget Parameters

    Require a fixed price against the stated scope, plus a rate card for anything beyond it. This is what makes bids comparable.

  9. 09

    Compliance & Legal Requirements

    Set the legal frame before testing starts. Authorisation gaps are the most common serious problem in penetration testing engagements.

  10. 10

    Sample Vendor Questions

    Include these verbatim. The answers separate specialists from resellers.

  11. 11

    Submission Instructions

    How, when and to whom to submit, the response format, and the single point of contact for clarification questions.

When to use the Penetration Testing RFP

A penetration testing RFP is the right tool when you need an independent test of your defences and want bids you can actually compare. Most organizations issue one because a framework or a customer asks for it: PCI DSS requires internal and external penetration testing at least once every 12 months and after significant changes, SOC 2 auditors and enterprise customers routinely ask for a recent third-party test, and cyber insurers increasingly ask whether one was done.

The hard part is not finding testers; it is getting quotes that describe the same work. One firm prices an automated scan with a branded report, another prices a week of manual testing by an experienced consultant, and both call it a penetration test. A tight scope and a fixed set of questions are what turn those into comparable proposals.

What to put in scope

Bidders can only price what you describe. Cover each of these in the scope section of the template.
  • Every target in writing: external IP ranges and hostnames, internal network segments, web applications (with URLs and the number of user roles), APIs (with documentation or a collection file), wireless networks and cloud accounts
  • The test type for each target: black box, grey box with credentials, or white box with source code or architecture diagrams
  • For applications, the authenticated roles to test and whether testing should include business logic and authorization between tenants or accounts
  • Segmentation testing, if you rely on network segmentation to reduce PCI DSS scope, stated as a separate line item
  • Testing windows, blackout periods, systems that must not be touched, and whether production or a staging copy will be tested
  • Social engineering (phishing, phone pretexting, physical entry) only if you want it, listed separately so it can be priced and approved on its own
  • Retesting of fixed findings, and the period in which a retest is included

Evaluation criteria

Score every response against the same criteria, agreed before the first proposal arrives.

Methodology and depth of manual testing

How much of the engagement is hands-on testing versus tool output, and which published methodology it follows. This deserves the heaviest weight because it is what you are paying for.

Tester experience and named team

Who will actually do the work, their recent experience with your kind of target, and recognised practical qualifications such as OSCP, OSWE, GPEN or CREST registrations. Weight this nearly as high as methodology.

Report quality

Ask for a redacted sample. A good report has a short executive summary, findings with clear reproduction steps and evidence, risk ratings with reasoning, and fixes your engineers can apply.

Retest and support terms

Whether retesting is included, how long the window is, and whether testers will answer remediation questions after delivery.

Price and commercial terms

Compare price only between proposals that pass the criteria above. A cheaper bid that drops manual testing is a different product, not a discount.

As a starting point, weight methodology and team experience together at roughly half of the total score, report quality and retest terms next, and price last. Adjust the split to your own priorities before you open any response, and record the weights in the RFP so bidders know how they will be judged.

The template's scoring matrix, ready to use

These are the starting weights published in the download. Adjust them, score up to three bidders and compare weighted totals as responses come in.

Scoring matrix

Score each bidder from 1 to 5. Totals are weighted and shown out of 100.

CriterionWeight
Technical methodology and depth
%
Team qualifications and named tester experience
%
Report quality, judged on the submitted sample
%
Price
%
Timeline fit and availability
%
Weighted total100%
60
60
60

Questions to ask every bidder

Ask the same questions of every vendor and require written answers, so responses can be compared line by line.
  • Which methodology do you follow (for example PTES, the OWASP Web Security Testing Guide or NIST SP 800-115), and how do you adapt it to our targets?
  • Roughly what share of the testing days is manual work, and which automated tools do you run?
  • Who are the named testers, what are their qualifications, and will the same people do the work and the retest?
  • Is any part of the work subcontracted? If so, to whom and under what confidentiality terms?
  • How do you rate findings (for example CVSS plus business context), and can we see a redacted sample report?
  • What is your process if you find a critical vulnerability or evidence of a prior compromise during testing?
  • How do you protect our data during and after the test, and when is it destroyed?
  • What does the rules of engagement document cover, and who signs the authorization to test?
  • Is a retest included, within what period, and does it produce an updated report or a letter?

Red flags in a response

Any one of these is worth a follow-up question. Several together usually mean the bidder is not the right fit.

The proposal reads like a scan

Very short timelines for large scopes, a tool list in place of a method, or a sample report full of scanner plugin output usually means little manual testing.

No named testers

If the bidder cannot tell you who will test, or the people in the proposal are sales staff, you have no way to judge experience.

No rules of engagement or written authorization

Testing without signed authorization and agreed boundaries puts you and the tester at legal and operational risk. A professional firm insists on both.

Guaranteed findings or a pass

No tester can promise a clean result or a fixed number of findings. Offers to "certify" your security after one test are a warning sign.

How to run this RFP

  1. Build the target inventory

    List every system in scope with owners, environments and access details. Most scoping disputes start with an incomplete inventory.
  2. Hold a scoping call or Q and A window

    Give all bidders the same chance to ask questions, and share every answer with every bidder.
  3. Score against fixed criteria

    Have at least two people score independently, then compare. Review sample reports side by side.
  4. Agree rules of engagement

    Before kickoff, sign the authorization, confirm windows, emergency contacts and stop conditions, and tell your hosting or cloud provider if their terms require it.
  5. Plan remediation and retest

    Book engineering time for fixes before the report lands, so the retest happens inside the included window.

Penetration Testing RFP: Frequently Asked Questions

How detailed should the scope be in a penetration testing RFP?

Detailed enough that two bidders would price the same work. Give counts and examples: number of external IPs, application URLs, user roles, API endpoints and internal subnets. Vague scopes produce quotes that cannot be compared.

Should we ask for a fixed price or a day rate?

A fixed price against a clear scope is easier to compare and to approve. Ask bidders to state the number of testing days behind the price so you can see how much effort each one is offering.

Do we need to tell our cloud provider before a test?

Check your provider's current policy. Major cloud platforms allow customers to test their own resources within published rules, and some activities such as denial of service testing are restricted. Put the requirement to follow those rules in the RFP.

Is a vulnerability scan the same as a penetration test?

No. A scan identifies known weaknesses automatically. A penetration test has a person try to exploit and chain weaknesses to show real impact. Both are useful, but they should be priced and judged separately.

How often should we run this RFP?

Many organizations test annually and after major changes, which matches PCI DSS expectations. Some rotate providers every few years to get a fresh perspective; others keep a provider for continuity and ask for different testers.

Need help with vendor selection?

Our team can help you tighten the scope, review vendor responses against your criteria and prepare questions for shortlist interviews.