Skip to main content
Security libraryReviewed

Penetration testing templates, checklists and comparisons, arranged by the job in front of you

Fifteen working documents for the buyer's side of a web application test, from house rules and release checks through quotes, permission and preparation to the remediation tracker and the retest.

The table gives each one's format, its counted length, what to have to hand before you open it and the invented example it carries.

Pages in this section

15 pages

Templates

12 pages

  • Penetration Test Scope Template

    A scope schedule you can copy and complete for any provider: exact URLs and API paths, environments, roles and route counts, test accounts, third-party services, source addresses, data limits, exclusions and the retest boundary. A completed example for an invented two-role software product shows every part filled in.

  • Penetration Test Authorisation Letter

    A letter you can copy, adapt and put in front of a solicitor. It covers who signs, which systems, which hosts have agreed, when and from where testing runs, what testers may do, how testing stops and what happens to the evidence. This is general information, not legal advice: have a solicitor review the letter before anyone signs it.

  • Penetration Testing Rules of Engagement

    A rules of engagement template for web application and API tests, with staging and production side by side. Each rule sets out the choice to make, a starting default for each environment and what both parties write down before the first request, from request limits and stop phrases to critical-finding escalation and clean-up.

  • Penetration Test Report Template

    A free outline for a web application penetration test report: document control, an executive summary, scope and limitations, a rating method, a finding block and a retest ledger. Use it to write a report, to keep in-house test results consistent, or to tell a provider what the report you are paying for should contain.

  • Vulnerability Disclosure Policy Template

    A policy you can copy and adapt that tells security researchers which systems they may look at, how to report what they find and what your business will do next, with a security.txt checklist and one report followed from first email to closure. It is general information, not legal advice: your organisation approves its own scope, contacts and terms, and its solicitor should review the safe-harbour and privacy wording before it goes live.

  • Security Policy Template

    A modular policy for one web application, written for a business with a small team and an outside developer. Every clause names an owner, the evidence that shows it is followed and when it is reviewed, and a filled-in exception register shows how gaps are tracked. It is a starting point for your own decisions, not a certificate.

  • Vendor Security Questionnaire Template

    For the business doing the buying. Each question names the evidence to ask for, the person on your side who judges the answer, what a weak answer looks like and what to ask next, with a review date to fill in. The page also shows how to cut the forty down for a low-risk vendor, and why a completed questionnaire is a claim rather than proof.

  • Cyber Insurance Security Checklist

    A renewal worksheet that keeps your web application evidence (the last test report, the retest ledger, access and backup records) apart from the exact wording of your insurer's questions, with one worked answer for a control that is only partly in place. It is not insurance advice or legal advice: what your insurer requires and what your policy covers are questions for your broker.

  • Penetration Test Readiness Checklist

    A countdown your own team works through before the first day of testing: who takes and restores the backup, who sets up test accounts and synthetic data, who gets the host's answer and proves domain control, who freezes changes and briefs the people watching alerts, and who signs the go or no-go. The seven days are your preparation plan, counted back from a testing date you have already agreed. They are not a provider's lead time.

  • Penetration Testing Provider Scorecard

    Check each provider against pass or fail gates for accreditation and independence, then score the rest on eight criteria, from relevant experience and sample-report quality to retest terms and exclusions. The weights are yours to set, every score carries its evidence, and a moderation sheet settles differences when several people score.

  • Penetration Test Remediation Plan Template

    A free remediation tracker for the work between a penetration test report and its retest. Each row ties a finding to its route and role, root cause, owner, fix branch, deployment and evidence. A decision not to fix stays on the record as an open risk with a named owner, a reason and a review date, rather than as a resolved finding.

  • Penetration Test Retest Checklist

    A finding-by-finding checklist for the round after the fixes: what your team hands over and holds still, how whoever performs the retest repeats each finding and checks around it, the evidence each of the four outcomes needs and who may record it, and a close-out sheet both sides sign. It starts where a remediation plan stops, with findings marked ready for retest.

Comparisons

3 pages

  • Penetration Testing vs Vulnerability Scanning

    A vulnerability scan, a vulnerability assessment and a penetration test answer different questions and leave different gaps. This page sets out what each can show, how each deals with false positives, and a decision table for eight situations a business with a website or web application runs into, from a launch to a suspected hack.

  • Black Box vs White Box vs Grey Box Testing

    What a tester is told decides what a penetration test can find. This page sets out how NIST, the UK NCSC and OWASP draw the lines between black box, grey box and white box testing, where they disagree, what each approach asks of your team, and how one invented booking application looks when it is tested all three ways.

  • SAST vs DAST

    Static application security testing reads your code without running it. Dynamic application security testing sends requests to a running build and judges the responses. They fail in different places, so this page compares them on what each sees, when each can run and the evidence each leaves, then follows one invented flaw past both of them and into a reviewer's hands.

Fifteen buyer assets in task order

Read down the first column for the task in front of you, then across for the asset's format, its counted length, what to gather before you open it and the invented example it carries. Rows run in the order the work happens, and every page in the second column is linked under Pages in this section.

15 rows

Fifteen buyer assets in task order

Task groupAsset and addressFormatLength (counted)Have readyWorked example
Before launch1. Security Policy Template, at /web-security/security-policy-templateText template to copy into your own document: a modular policy for one web application9 numbered sections: scope and roles, 7 modules holding 37 clauses (A1 to T7), and an exception register. Every clause names an owner, its evidence and when it is reviewed.The application's environments, hosting and supplier list, a named owner for each clause you keep, where each clause's evidence is kept, and someone with authority over the business to approve the policy.An example exception register with five entries (EX-01 to EX-05) for an invented online booking service.
Before launch2. SAST vs DAST, at /web-security/sast-vs-dastComparison page whose asset is a Markdown worked example, ending in a workflow to copy into a release checklist7 parts, the last a 10-step combined remediation workflowA release checklist to copy the workflow into, a test account for every role your scans can use, and a list of your routes to compare scan coverage against.An invented wholesale bakery's Next.js order app: pull request #219, which let café delivery notes run script on the staff dispatch board, followed from commit to release.
Before launch3. Vulnerability Disclosure Policy Template, at /web-security/vulnerability-disclosure-policy-templateMarkdown template to adapt and publish: a policy, a security.txt checklist and a worked report3 parts: a policy of 9 sections, a security.txt checklist of 17 tick boxes with an example file, and the worked exampleYour decisions on scope, who reads reports and how fast, disclosure timing, personal information and sign-off; test accounts and a staging copy for reproducing reports; and a solicitor to review sections 4 and 8.Part C follows one invented report, VDP-004, about another trade customer's invoice in a building-supplies wholesaler's trade portal, from first email to closure.
Procurement: choosing the kind of test4. Penetration Testing vs Vulnerability Scanning, at /web-security/penetration-testing-vs-vulnerability-scanningComparison page built around a decision table you read across8 situations (rows) by 8 columns, from a launch to a request for PCI DSS scansThe proposal you have been sent, and the exact wording of any customer, contract or tender request behind it.In the page body rather than the table: one year of scans, assessments and tests for an invented trade quoting portal. The table's rows are situations, not clients.
Procurement: choosing the kind of test5. Black Box vs White Box vs Grey Box Testing, at /web-security/black-box-vs-white-box-vs-grey-box-testingComparison page built around a walkthrough table you read down or across10 rows by 4 columns: four rows for four flaws, and six for what the tester is given, what you set up, the paths taken, what stays out of view, the evidence and where each lens fitsAnswers to three questions: which accounts the tester will hold and in which roles, what the tester may read, and which environment will be tested.The table is the example: book.lab.test, an invented booking application for a mobile dog-grooming business, tested black box, grey box and white box.
Procurement: asking for quotes6. Penetration Test Scope Template, at /web-security/penetration-test-scope-templateText template to copy into a document: a fill-in scope schedule, blank and then completed12 parts with 53 numbered lines in the blank scheduleThe exact wording of whoever asked for the test, a route export from a named build, your DNS zone, the outside services the application calls or loads, each host's and vendor's testing terms with the date read, and usernames for the test accounts.The same schedule completed for an invented two-role product: a pre-start vehicle check app at prestart.lab.test, used by fleet managers and drivers.
Procurement: asking for quotes7. Penetration Test Report Template, at /web-security/penetration-test-report-templateMarkdown template to copy: a report skeleton with a finding block and a retest ledger8 parts, numbered 0 to 7, from document control to the appendicesTo brief providers, only the template, attached to your request for quotes. To write a report, the statement of work, the build tested, the accounts used and the evidence for each finding.Finding F-03, a bookkeeper role that can issue credit notes and void invoices, filled in for an invented billing application at billing.example.test, with its ledger entry after a first retest round.
Procurement: choosing the tester8. Penetration Testing Provider Scorecard, at /web-security/penetration-testing-provider-scorecardText template to copy into a spreadsheet or shared document7 parts (A to G): 8 set-up lines, 6 pass or fail gates, 8 weighted criteria with scoring anchors, a score sheet, a moderation sheet and the worked exampleThe exact wording of the request, any accreditation, independence, evidence-storage or insurance condition it sets, the names of your evaluators and a moderator, and weights signed off before any proposal is opened.Part G: an invented booking and records platform for allied health clinics, choosing between Providers A, B and C under two sets of weights.
Procurement: before testing starts9. Penetration Test Authorisation Letter, at /web-security/penetration-test-authorisation-letterText template to copy onto your letterhead: a letter with three schedules, for a solicitor to review13 clauses holding 47 numbered sub-clauses, then Schedules A to C for targets, host and third-party permissions, and test accountsThe scope, rules of engagement and statement of work it refers to, evidence of the signatory's authority, proof of control for each domain, each host's and third party's testing terms with the date read, and a solicitor.None. Prompts in round brackets give examples for some blanks.
Procurement: before testing starts10. Penetration Testing Rules of Engagement, at /web-security/penetration-testing-rules-of-engagementTable to fill in with your provider and have both parties sign14 rules (rows) by 5 columns, each with a staging default and a production defaultThe scope and the authorisation letter, the throttling point and the list of third-party services from whoever runs your hosting and integrations, and everyone on the contact list for the kickoff call.None. Each rule carries starting defaults for staging and production instead.
Procurement: before testing starts11. Penetration Test Readiness Checklist, at /web-security/penetration-test-readiness-checklistTick-box checklist to print or copy into a shared document, ending in a sign-off sheet22 steps grouped by day, from seven days out to the day before testing. The days are your own preparation plan, counted back from a date already agreed.A first day of testing confirmed in writing, the agreed scope version, the authorisation letter and rules of engagement, and a real name against each of six roles, from engagement owner to monitoring contact.None.
Procurement: questionnaires12. Vendor Security Questionnaire Template, at /web-security/vendor-security-questionnaire-templateTable to copy into a spreadsheet, one row per question, for the business doing the buying40 questions (rows) by 5 columns in 7 groups, with tiers of 8, 23 or all 40 rowsAnswers to three questions about the vendor (what it will hold or see, what stops without it, what it can do on your behalf), a name for each of five answer-owner roles, a reply date and a trial account.None.
Procurement: questionnaires13. Cyber Insurance Security Checklist, at /web-security/cyber-insurance-security-checklistText worksheet to copy into a document or spreadsheet. Not insurance or legal advice.3 parts: 11 evidence lines (A1 to A11), one block for each insurer question, and the worked illustration, then 4 checks before anyone signsFor each web application, your latest test or review report, retest ledger, administrator account list, multi-factor sign-in settings, backup and incident records; and the current proposal form or renewal questionnaire from your broker.Part C: one invented question, Q14, answered for an invented booking company from its report and retest ledger.
Remediation14. Penetration Test Remediation Plan Template, at /web-security/penetration-test-remediation-plan-templateTable to copy into a spreadsheet or issue tracker9 columns, with a blank row to copy and 7 worked rowsThe report, with its finding IDs, titles, routes, roles and ratings copied unchanged, one named owner for each finding, and the test accounts the tester used.portal.training-demo.test, an invented course portal with learner, trainer and office roles: one root cause behind three report findings and one item found during remediation, plus a deferral and an accepted risk.
Retest15. Penetration Test Retest Checklist, at /web-security/penetration-test-retest-checklistTick-box checklist to copy into a shared document, ending in a close-out sheet both sides sign22 items: 7 handover steps, 5 steps for each finding, 4 outcome checks, 3 special cases and 3 close-out stepsFindings marked ready for retest, every fix on one named build, a fix note for each finding, the original test accounts and records, and an authorisation that covers the retest dates.In the page body rather than the checklist: an invented job management portal, where finding F-04 is partially fixed and an unlisted sibling route becomes a new finding, F-11.

Task group

Asset and address

  1. Before launch1. Security Policy Template, at /web-security/security-policy-template
    Format
    Text template to copy into your own document: a modular policy for one web application
    Length (counted)
    9 numbered sections: scope and roles, 7 modules holding 37 clauses (A1 to T7), and an exception register. Every clause names an owner, its evidence and when it is reviewed.
    Have ready
    The application's environments, hosting and supplier list, a named owner for each clause you keep, where each clause's evidence is kept, and someone with authority over the business to approve the policy.
    Worked example
    An example exception register with five entries (EX-01 to EX-05) for an invented online booking service.

    Open Security Policy Template

  2. Before launch2. SAST vs DAST, at /web-security/sast-vs-dast
    Format
    Comparison page whose asset is a Markdown worked example, ending in a workflow to copy into a release checklist
    Length (counted)
    7 parts, the last a 10-step combined remediation workflow
    Have ready
    A release checklist to copy the workflow into, a test account for every role your scans can use, and a list of your routes to compare scan coverage against.
    Worked example
    An invented wholesale bakery's Next.js order app: pull request #219, which let café delivery notes run script on the staff dispatch board, followed from commit to release.

    Open SAST vs DAST

  3. Before launch3. Vulnerability Disclosure Policy Template, at /web-security/vulnerability-disclosure-policy-template
    Format
    Markdown template to adapt and publish: a policy, a security.txt checklist and a worked report
    Length (counted)
    3 parts: a policy of 9 sections, a security.txt checklist of 17 tick boxes with an example file, and the worked example
    Have ready
    Your decisions on scope, who reads reports and how fast, disclosure timing, personal information and sign-off; test accounts and a staging copy for reproducing reports; and a solicitor to review sections 4 and 8.
    Worked example
    Part C follows one invented report, VDP-004, about another trade customer's invoice in a building-supplies wholesaler's trade portal, from first email to closure.

    Open Vulnerability Disclosure Policy Template

  4. Procurement: choosing the kind of test4. Penetration Testing vs Vulnerability Scanning, at /web-security/penetration-testing-vs-vulnerability-scanning
    Format
    Comparison page built around a decision table you read across
    Length (counted)
    8 situations (rows) by 8 columns, from a launch to a request for PCI DSS scans
    Have ready
    The proposal you have been sent, and the exact wording of any customer, contract or tender request behind it.
    Worked example
    In the page body rather than the table: one year of scans, assessments and tests for an invented trade quoting portal. The table's rows are situations, not clients.

    Open Penetration Testing vs Vulnerability Scanning

  5. Procurement: choosing the kind of test5. Black Box vs White Box vs Grey Box Testing, at /web-security/black-box-vs-white-box-vs-grey-box-testing
    Format
    Comparison page built around a walkthrough table you read down or across
    Length (counted)
    10 rows by 4 columns: four rows for four flaws, and six for what the tester is given, what you set up, the paths taken, what stays out of view, the evidence and where each lens fits
    Have ready
    Answers to three questions: which accounts the tester will hold and in which roles, what the tester may read, and which environment will be tested.
    Worked example
    The table is the example: book.lab.test, an invented booking application for a mobile dog-grooming business, tested black box, grey box and white box.

    Open Black Box vs White Box vs Grey Box Testing

  6. Procurement: asking for quotes6. Penetration Test Scope Template, at /web-security/penetration-test-scope-template
    Format
    Text template to copy into a document: a fill-in scope schedule, blank and then completed
    Length (counted)
    12 parts with 53 numbered lines in the blank schedule
    Have ready
    The exact wording of whoever asked for the test, a route export from a named build, your DNS zone, the outside services the application calls or loads, each host's and vendor's testing terms with the date read, and usernames for the test accounts.
    Worked example
    The same schedule completed for an invented two-role product: a pre-start vehicle check app at prestart.lab.test, used by fleet managers and drivers.

    Open Penetration Test Scope Template

  7. Procurement: asking for quotes7. Penetration Test Report Template, at /web-security/penetration-test-report-template
    Format
    Markdown template to copy: a report skeleton with a finding block and a retest ledger
    Length (counted)
    8 parts, numbered 0 to 7, from document control to the appendices
    Have ready
    To brief providers, only the template, attached to your request for quotes. To write a report, the statement of work, the build tested, the accounts used and the evidence for each finding.
    Worked example
    Finding F-03, a bookkeeper role that can issue credit notes and void invoices, filled in for an invented billing application at billing.example.test, with its ledger entry after a first retest round.

    Open Penetration Test Report Template

  8. Procurement: choosing the tester8. Penetration Testing Provider Scorecard, at /web-security/penetration-testing-provider-scorecard
    Format
    Text template to copy into a spreadsheet or shared document
    Length (counted)
    7 parts (A to G): 8 set-up lines, 6 pass or fail gates, 8 weighted criteria with scoring anchors, a score sheet, a moderation sheet and the worked example
    Have ready
    The exact wording of the request, any accreditation, independence, evidence-storage or insurance condition it sets, the names of your evaluators and a moderator, and weights signed off before any proposal is opened.
    Worked example
    Part G: an invented booking and records platform for allied health clinics, choosing between Providers A, B and C under two sets of weights.

    Open Penetration Testing Provider Scorecard

  9. Procurement: before testing starts9. Penetration Test Authorisation Letter, at /web-security/penetration-test-authorisation-letter
    Format
    Text template to copy onto your letterhead: a letter with three schedules, for a solicitor to review
    Length (counted)
    13 clauses holding 47 numbered sub-clauses, then Schedules A to C for targets, host and third-party permissions, and test accounts
    Have ready
    The scope, rules of engagement and statement of work it refers to, evidence of the signatory's authority, proof of control for each domain, each host's and third party's testing terms with the date read, and a solicitor.
    Worked example
    None. Prompts in round brackets give examples for some blanks.

    Open Penetration Test Authorisation Letter

  10. Procurement: before testing starts10. Penetration Testing Rules of Engagement, at /web-security/penetration-testing-rules-of-engagement
    Format
    Table to fill in with your provider and have both parties sign
    Length (counted)
    14 rules (rows) by 5 columns, each with a staging default and a production default
    Have ready
    The scope and the authorisation letter, the throttling point and the list of third-party services from whoever runs your hosting and integrations, and everyone on the contact list for the kickoff call.
    Worked example
    None. Each rule carries starting defaults for staging and production instead.

    Open Penetration Testing Rules of Engagement

  11. Procurement: before testing starts11. Penetration Test Readiness Checklist, at /web-security/penetration-test-readiness-checklist
    Format
    Tick-box checklist to print or copy into a shared document, ending in a sign-off sheet
    Length (counted)
    22 steps grouped by day, from seven days out to the day before testing. The days are your own preparation plan, counted back from a date already agreed.
    Have ready
    A first day of testing confirmed in writing, the agreed scope version, the authorisation letter and rules of engagement, and a real name against each of six roles, from engagement owner to monitoring contact.
    Worked example
    None.

    Open Penetration Test Readiness Checklist

  12. Procurement: questionnaires12. Vendor Security Questionnaire Template, at /web-security/vendor-security-questionnaire-template
    Format
    Table to copy into a spreadsheet, one row per question, for the business doing the buying
    Length (counted)
    40 questions (rows) by 5 columns in 7 groups, with tiers of 8, 23 or all 40 rows
    Have ready
    Answers to three questions about the vendor (what it will hold or see, what stops without it, what it can do on your behalf), a name for each of five answer-owner roles, a reply date and a trial account.
    Worked example
    None.

    Open Vendor Security Questionnaire Template

  13. Procurement: questionnaires13. Cyber Insurance Security Checklist, at /web-security/cyber-insurance-security-checklist
    Format
    Text worksheet to copy into a document or spreadsheet. Not insurance or legal advice.
    Length (counted)
    3 parts: 11 evidence lines (A1 to A11), one block for each insurer question, and the worked illustration, then 4 checks before anyone signs
    Have ready
    For each web application, your latest test or review report, retest ledger, administrator account list, multi-factor sign-in settings, backup and incident records; and the current proposal form or renewal questionnaire from your broker.
    Worked example
    Part C: one invented question, Q14, answered for an invented booking company from its report and retest ledger.

    Open Cyber Insurance Security Checklist

  14. Remediation14. Penetration Test Remediation Plan Template, at /web-security/penetration-test-remediation-plan-template
    Format
    Table to copy into a spreadsheet or issue tracker
    Length (counted)
    9 columns, with a blank row to copy and 7 worked rows
    Have ready
    The report, with its finding IDs, titles, routes, roles and ratings copied unchanged, one named owner for each finding, and the test accounts the tester used.
    Worked example
    portal.training-demo.test, an invented course portal with learner, trainer and office roles: one root cause behind three report findings and one item found during remediation, plus a deferral and an accepted risk.

    Open Penetration Test Remediation Plan Template

  15. Retest15. Penetration Test Retest Checklist, at /web-security/penetration-test-retest-checklist
    Format
    Tick-box checklist to copy into a shared document, ending in a close-out sheet both sides sign
    Length (counted)
    22 items: 7 handover steps, 5 steps for each finding, 4 outcome checks, 3 special cases and 3 close-out steps
    Have ready
    Findings marked ready for retest, every fix on one named build, a fix note for each finding, the original test accounts and records, and an authorisation that covers the retest dates.
    Worked example
    In the page body rather than the checklist: an invented job management portal, where finding F-04 is partially fixed and an unlisted sibling route becomes a new finding, F-11.

    Open Penetration Test Retest Checklist

About this library

Penetration testing templates for the buyer's side of a test

A penetration test ends in a report, and around it sits paperwork that the business being tested owns: the scope that tells providers what to quote for, the letter that gives permission, the rules that govern the testing window, the tracker that turns findings into assigned work and the checklist that closes each finding on a named build.

This page gathers fifteen of those documents in one place. Twelve are templates, checklists and trackers to copy or fill in.

The other three are security testing comparisons that set approaches side by side, each built around a table or a worked example of its own.

Each asset is written to be used away from its page: copied into a document, printed, or read across as a table. The pages around them explain the reasoning and cite their sources. This index does a different job. It tells you which asset to open first for the task you have, what it asks of you before you start, and which other assets it hands work to.

The briefing documents, the scorecard and the checklists are written for any provider rather than one firm's process. If Clever Ops is on your list, the provider scorecard asks you to put it through the same gates and criteria as everyone else.

Four task groups, in the order a test unfolds

Used as a pentest template library, the table sorts the fifteen assets by the job a buyer is doing when they need one, not by page type.

Each asset sits in one group, chosen from what its own page says it is for, and the rows run in the order the work happens. The row numbers in the table are the numbers used on the rest of this page.

  • Before launch, rows 1 to 3: the security policy template, SAST vs DAST and the vulnerability disclosure policy template. Two of these are standing documents rather than one-off tasks. They sit here because launch is the latest sensible point to have them, and each carries its own review date from then on.
  • Procurement, rows 4 to 13: choosing the kind of test, asking for quotes, choosing the tester, getting permission and preparation in place before testing starts, and two questionnaires, one you send to a software vendor and one you answer for an insurer.
  • Remediation, row 14: the tracker that runs from the day the report arrives until each fix is ready for retest.
  • Retest, row 15: the checklist that repeats each finding on one named build and closes the round with two signatures.

Three placements that needed a judgement call

The report template sits under procurement because, for a buyer, its job is to tell providers what the report you are paying for should contain. Its finding ledger returns at the retest. The readiness checklist sits with the letter and the rules of engagement because its whole purpose is to make the promises in those documents true on the first morning of testing.

The cyber insurance worksheet counts as a questionnaire you answer, so it sits beside the vendor questionnaire you send.

What each column tells you, and how the lengths were counted

Format says what kind of thing you are opening: a text or Markdown template to copy into your own document, a table to copy into a spreadsheet or fill in with a provider, a tick-box checklist, or a comparison page built around a table or worked example.

Length is counted from each asset as it is published today: parts and numbered lines for a schedule, clauses for a letter or policy, rows and columns for a table, steps or items for a checklist. There are no completion times.

How long an asset takes depends on your application, on how many people hold the information and on how much of it already exists in writing, so any figure would be a guess.

Have ready comes from each page's own list of things to gather, or from the first step its asset asks you to complete. Where a page names an outside person, such as a solicitor for the authorisation letter or a broker for the insurance worksheet, the cell names them too.

Worked example names the invented case each asset carries. Every one is labelled on its page as an illustration, not a client. Four assets have none, and two keep their example in the page body rather than in the asset itself; the cell says which.

The table cannot hold links, so the second column gives each page's address. The same fifteen pages are linked under Pages in this section, where they are listed by page type: twelve templates and three comparisons.

Five records that pass from one asset to the next

The assets are separate documents, but the same few records run through them.

Keep each record in a single place, and every asset after the first starts from the last one's output instead of from memory.

  • The exact wording of whoever asked for the test. The scope schedule asks you to paste it, the provider scorecard draws its gates from it, the decision table in the scanning comparison tells you to match it, and the insurance worksheet copies each question word for word.
  • Hostnames and the build reference. The scope lists every hostname and the build its route list came from, Schedule A of the letter repeats the targets, the readiness checklist freezes the build and records it, the remediation tracker names the build each fix reached, and the retest runs on one named build.
  • Test accounts: two for each role, in two customer organisations where one database serves several. They are set out in the scope, created and signed in to during readiness, used by your team to replay findings during remediation, and restored for the retest.
  • Finding IDs. The report template keeps the original IDs from round to round, the tracker copies them unchanged, the retest keeps them, and the retest ledger line in the insurance worksheet lists them.
  • The four retest outcomes: fixed, partially fixed, still reproducible and not retested. They appear in the report ledger, the tracker's status column, the retest checklist, the insurance worksheet, the vendor questionnaire's question on findings and the testing module of the security policy, and none of them counts a finding that was not retested as fixed.

Before launch: house rules, release checks and a reporting route

Start with the security policy template, row 1.

It is written for one application and a small team, and it records who owns access, changes, dependencies, logging, incident escalation, supplier access and testing. Its clause T7 names where reports from outside the business arrive and who triages them, which is the job the disclosure policy does in public.

Delete the modules your team will not follow before you fill in the rest, and move anything you mean to do but cannot yet show into the exception register, where every entry has an expiry date.

SAST vs DAST, row 2, is the one to read if code changes reach production through a pipeline. Its worked example follows one invented change past a static warning that was dismissed and a nightly scan whose single account never reached the page that showed the flaw, until a reviewer confirmed it on staging.

The ten-step workflow at the end is the part to keep. Copy it into your release checklist, then give your scans an account for every role and compare their coverage with your route list.

Publish the vulnerability disclosure policy, row 3, once someone is named to read the security inbox and someone can fix what arrives. Its page asks for five decisions before any blank is filled in, a solicitor's review of the safe-harbour and privacy sections, and test accounts and a staging copy so a report can be reproduced without touching real customer records.

Part B then covers the security.txt file for each host that needs one. Whichever order you take these in, the response targets the policy publishes have to match whoever actually watches that inbox, including over holidays.

Procurement: from the first question to the first morning of testing

Ten of the fifteen assets sit in this group.

Work through them in row order; they fall into five steps, and each step leaves you with something the next one needs.

Choosing the kind of test: rows 4 and 5

Read the scanning comparison first. Find the row that matches why you are buying, whether that is a launch, a customer's request or an application nobody has examined, and read across to what fits. Then use the box comparison to settle what the tester will be given: which accounts in which roles, what they may read, and which environment. Those answers go straight into Parts 3 to 5 of the scope schedule.

Asking for quotes: rows 6 and 7

Fill in the scope schedule once and send the identical copy to every provider, so each quote prices the same work. Attach the report template as the list of parts the finished report has to contain. Neither needs a provider's input. Take the most care over the scope, because the letter, the rules of engagement and the readiness checklist all refer back to it.

Choosing the tester: row 8

Fill in Part A of the scorecard and sign off the weights before any proposal is opened. Its gates, such as a required accreditation or an independent tester, come from the exact wording of the request, and a provider that fails one is not scored at all. Price stays off the sheet. Quotes are compared on the same written scope once the scoring is done.

Before testing starts: rows 9 to 11

These three build on each other in order. The authorisation letter assumes a scope: its Schedule A lists the targets, and clause 13.1 names the scope document it is read with. The rules of engagement assume both, and they cannot widen what the letter permits. The readiness checklist assumes all three, and its sign-off records preparation only: it does not authorise testing or stand in for a host's approval.

Put the letter in front of a solicitor early. It waits on evidence of the signatory's authority and on each host's testing terms, and those outside answers are also the first things the readiness countdown chases.

Questionnaires, sent and answered: rows 12 and 13

The vendor questionnaire is for the business doing the buying. Work out the vendor's tier first and send only that tier's rows, eight for the lightest. The insurance worksheet runs the other way, helping you answer an insurer from evidence you already hold, and it says plainly that it is not insurance or legal advice.

The two meet at test evidence. Questions T1 to T4 ask a vendor for its scope, tester, findings with retest statuses and method, and lines A1 to A4 of the worksheet hold the same kinds of evidence about your own application. Whatever the questionnaire in front of you, answer from the evidence and take questions about cover to your broker.

Remediation: from the report to ready for retest

The remediation tracker, row 14, is the only asset in this group, and it starts the day the report arrives.

Copy each finding's ID, title, routes, roles and ratings across unchanged, give each finding one named owner, and let each owner set their own target date. A root cause behind several findings gets a row of its own, so one change can retire several findings while each still receives its own retest outcome.

Two rules in the tracker matter most when someone outside the team asks how things stand. Your developers move a row to fix deployed and then to ready for retest; only a retest moves it to fixed. A decision not to fix stays open as well: a deferral carries a target release and an interim measure, and an accepted risk carries a reason and a review date.

The management view keeps confirmed fixes apart from everything else, and the page treats that split view as the position to give a board, a customer or an insurer until the retest.

The tracker leans on the report. Findings written with clear IDs, affected routes and retest criteria, as the finding block in the report template asks, make every row easier to fill. It then hands over to the retest checklist: every fix on one build, the original accounts still in place, evidence attached to each row, and deferred or accepted findings listed so the tester can mark them not retested with your reason.

Retest: one named build, one outcome for each finding

The retest checklist, row 15, starts where the tracker stops.

Its seven handover steps belong to your team and happen once per round, before you ask for the retest. The per-finding steps and outcome checks belong to whoever performs it, which can be a provider or someone on your own team who did not write the fix.

Two earlier assets come back into play here. The authorisation letter ends its permission when its testing window closes, so a later retest needs a signed variation or a fresh letter, and the rules of engagement carry over with the build, window, contacts and accounts updated.

Settle the checklist's three special cases before the round starts: a sibling route the fix missed, a finding that stops reproducing for an unrelated reason, and a new issue found along the way.

The round closes with two signatures: the retester's on the results, and the engagement owner's on a decision for every finding not marked fixed. Then the outcomes travel back into the finding ledger of the report, into the retest ledger line of the insurance worksheet, into your answers to a customer's security questionnaire, and into any summary already shared, which the checklist asks you to replace with the updated one.

Frequently asked questions

Rows 6 to 11, 14 and 15 cover one test from quote to close-out: the scope schedule, the report template as a list of what the report must contain, the provider scorecard, the authorisation letter, the rules of engagement, the readiness checklist, the remediation tracker and the retest checklist. The comparisons in rows 4 and 5 help before you fill any of them in. The rest serve other jobs: the policy and release checks before launch, and the questionnaires when a vendor or an insurer is involved.

With their exact wording. If a customer, contract or tender asked, read the wording against row 2 of the decision table in the scanning comparison, then paste it into the scope schedule and use it to set the gates on the provider scorecard. If the question is on an insurer's proposal form, the cyber insurance worksheet shows how to answer each question from evidence you hold, and suggests reading the form before booking anything.

No. Each one is invented for its page and labelled there as an illustration. The businesses, hostnames, accounts, findings and scores in them belong to no real client. The sample penetration test report elsewhere in the library is also not client work: it is written about a lab application.

Because a time would be a guess. Filling in the same scope schedule is a different job for a site with one role than for an application with several roles, customer organisations and outside services. The length column counts what each asset contains instead, so you can judge the size of the job against your own application.

No. The authorisation letter and the disclosure policy template each describe themselves as general information rather than legal advice, and ask for a solicitor's review before anyone signs or publishes. The rules of engagement builder says it is not legal advice either. The insurance worksheet is neither insurance nor legal advice, and it sends questions about what your insurer requires and what you are covered for to your broker.

Yes. The tracker is your team's working record by design. The retest checklist can be run by someone on your team, preferably a person who did not write the fix, as long as the record names who ran each check and states that they work on the system, so a reader can weigh the result.

The readiness checklist, row 11, comes before testing, and the retest checklist, row 15, comes after the fixes. They record different things: readiness records that your team's preparation is done, and the retest records one outcome for each finding on a named build. Neither one authorises testing; that stays with the signed letter.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.