Skip to main content

Free 30-min security demo Book Now

RFP checklist for application security testing tools

55 vendor-neutral questions for a SAST, DAST and mobile testing tender, grouped the way evaluation teams score them. Free to copy into your own documents.

How to use it

Send the same questions to every vendor and ask for written answers, then verify the three that matter most in a proof of concept: whether the product really runs inside your network without internet access, what makes the price change during the term, and how many of the findings on your own code your developers would actually fix.

Weight the groups to your situation. Regulated and public-sector teams usually weight deployment and reporting highest. Product teams weight workflow and scan speed.

1. Deployment and data location

  1. Where does analysis run: in the vendor's cloud, in our network, or both?
  2. Can the complete product, including the console and database, run inside our network with no internet access?
  3. How is the licence activated and renewed on a server that has no internet access?
  4. How are detection updates delivered to a disconnected installation, how often, and how do we verify them before import?
  5. Does source code, compiled code, findings or usage data leave our environment at any point? List every outbound connection.
  6. Which hosting regions are available for the cloud service, and can we choose the region?
  7. What infrastructure do we need to operate (servers, cluster, database), and how many administration hours per month do customers of our size report?
  8. How long does a first installation take until the first completed scan?

2. Static analysis (SAST)

  1. Which languages and frameworks in our stack are supported, and at what depth (data-flow analysis or pattern rules)?
  2. Does the scanner need a compiled build, or can it analyse source directly?
  3. How long does a full scan of 500,000 lines take, and is incremental scanning available?
  4. What evidence does each finding carry (data-flow trace, file and line, rule reference)?
  5. How are false positives marked, and do those decisions survive rescans and code movement?
  6. Can we add or tune rules, and who maintains the rule content?
  7. How are hard-coded secrets and unsafe configuration files handled?

3. Dynamic and API testing (DAST)

  1. Which sign-in methods are supported for authenticated scans (form login, single sign-on, multi-factor steps, tokens)?
  2. How are single-page applications crawled?
  3. Can we import OpenAPI, GraphQL schemas and Postman collections?
  4. Which checks rely on an external callback service, and how do they work in a closed network?
  5. Where is request and response evidence stored, and for how long?
  6. Can scans be limited by time window, request rate and scope to protect production systems?
  7. Does the product test applications that use large language models, and for which issue classes?

4. Mobile applications (MAST)

  1. Can compiled Android (APK, AAB) and iOS (IPA) applications be analysed without source code?
  2. Which standard are mobile findings mapped to (for example the OWASP Mobile Top 10)?
  3. Are embedded secrets, insecure storage and weak cryptography reported with their location in the binary?
  4. Is the mobile testing part of the same licence and console?

5. Open-source components and supply chain

  1. Which package ecosystems are covered, and how often is the vulnerability data refreshed?
  2. Can the product produce and import a software bill of materials (CycloneDX, SPDX)?
  3. Are licence obligations reported next to vulnerabilities?
  4. Is there analysis of packages for unwanted behaviour, beyond known vulnerability lists?
  5. How does vulnerability data reach a disconnected installation?

6. Workflow and integrations

  1. Which source control and CI systems are supported out of the box, and is there a documented REST API?
  2. Can a build be stopped on policy (for example new critical findings only)?
  3. Which IDE plugins exist, and do they need a server connection?
  4. Which ticketing systems are supported, and is synchronisation two-way?
  5. Is single sign-on (SAML or OIDC) available, with role-based access by team and project?
  6. Is the interface available in the languages our teams and auditors use, including right-to-left languages?
  7. Is there an integration for AI coding assistants, and what data does it send?

7. Reporting and compliance

  1. Which standards can findings be mapped to (OWASP Top 10, CWE, PCI DSS, ISO 27001, NIST 800-53, regional frameworks)?
  2. Can reports be produced per application version for audit evidence, with dates and remediation status?
  3. Is there an executive view of risk trend across the portfolio?
  4. Can data be exported in open formats (SARIF, CSV, JSON, PDF)?
  5. How are accepted risks recorded, approved and reviewed?

8. Licensing and cost

  1. What is the pricing unit: developer, application, lines of code, scan, target, or a fixed scope?
  2. What exactly makes the price change during the contract term?
  3. Are static, dynamic, mobile and component analysis separate licences?
  4. What is the three-year total for our current scope and for the scope we expect in year three?
  5. Is a proof of concept on our own code included, and under which conditions?
  6. What do support, updates and professional services cost in addition?

9. Vendor and support

  1. Which security certifications does the vendor hold (for example ISO/IEC 27001), and can we see the certificate and scope?
  2. Where is the vendor incorporated, and under which law is the contract?
  3. What are the support hours, languages and response times?
  4. Does the vendor's own team offer manual code review and penetration testing?
  5. How are vulnerabilities in the vendor's own product reported and fixed?
  6. Can the vendor provide references in our sector and region?

Frequently asked questions

What should an RFP for application security testing tools include?

Questions on where analysis runs and where data is stored, coverage and evidence for static, dynamic and mobile testing, open-source component analysis, integrations, compliance reporting, the pricing unit and what changes the price, and the vendor’s own certifications and support.

Which RFP questions separate vendors most clearly?

Three do: whether the complete product can run with no internet access, what exactly makes the price change during the term, and whether a proof of concept on your own code is included. Answers to these differ far more than answers to feature lists.

Can we use this checklist in our own tender documents?

Yes. It is vendor neutral and free to copy and adapt. A CSV version is available for import into a scoring sheet.

Want Offensive360's written answers?

We answer every question on this list in writing and show the deployment answers live in a demo on a machine without internet access.

Book a demo

Related: why teams choose Offensive360, product comparisons and pricing.