Answering security questionnaires on pentesting

What customer questionnaires ask about penetration testing, how to answer, and what to attach.

Books, pencils, a laptop and a phone on a desk

What the questions look like

Large customers send standard questionnaires, such as the SIG from Shared Assessments or the CAIQ from the Cloud Security Alliance, or their own forms. The testing questions are usually simple: whether independent testing is done, how often, who does it, and whether findings are fixed.

What to state

A clear answer has facts a reviewer can check:

  • The date of the latest test and who performed it.
  • What was in scope: for example the web application, its APIs and the cloud environment.
  • The method: manual testing guided by a recognised standard.
  • The result: how many findings by severity, and the status of high and critical findings.
  • Whether a retest confirmed the fixes, and when.

What to attach

Most vendors offer an executive summary or a letter of attestation, often under NDA. The full report holds details an attacker could use, so share it only where the customer needs it and has agreed to protect it.

What to avoid

Do not describe a vulnerability scan as a penetration test, and do not say everything was fixed unless a retest showed it. Reviewers often follow up on vague answers, and a precise answer closes the question faster.

Keep the evidence current

Many customers ask for a test from the last 12 months. Plan the next test before the current report ages out, and after any major change to the product.

Sources

General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.

Need this done?

Tell us what needs testing and when. We reply within 1 business day.

Request a proposal
Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.