Skip to content
The first pages of the Security Vulnerability Report template

Security Vulnerability Report

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Difficulty
Beginner
Updated
November 12, 2026

Every page (7)

Overview

A vague security report sends developers back with questions, and a long one hides the single defect that matters. This Google Docs vulnerability report keeps one defect per document, in the order a developer and a triage lead read it: a summary of observable behaviour, the affected versions, a proof of concept with reproduction results, and a suggested fix with a timeline. The structure works for responsible disclosure as well as internal bugs.

The sample is set at Netherby Cloud, a fictional company, and describes a token that survives logout on its export API, with reproduction in three of five attempts and a hotfix plan. Replace the summary, build numbers and evidence with your own, remove personal data from every attachment, and set severity with your triage definitions rather than the volume of reports.

Useful for

  • A researcher sending a responsible disclosure report to a vendor's security team
  • A QA engineer filing a defect with steps a developer can follow on the first try
  • A triage lead deciding whether a high-severity defect blocks the next release

What's included

  • Summary page with headline figures, key findings and a recommendation
  • Impact scorecard with targets, trends and status for each measure
  • Affected versions timeline with a table of builds and results
  • Proof of concept with testimonials and a glossary of terms
  • Suggested fix in ordered steps with a tip callout and owners
  • Make-it-yours guide with steps for evidence and severity

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the summary with one sentence of observable behaviour, and check it against your own reproduction.

  3. 3

    Fill in the environment with the build number, device, OS and account type where the defect occurs.

  4. 4

    Remove personal data, customer names and secrets from every log, screenshot and recording before sharing.

  5. 5

    Delete the guide page, then share the report with the triage lead and set severity using your definitions.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Are the company, people and figures in the sample real?

No. Netherby Cloud, every person named, every email address ending in .example, and every build number, count and percentage in the sample are fictional and included only to show the expected detail.

Should a report cover more than one defect?

No. One defect per report lets the team close it cleanly and track it on its own. If two problems share a cause, link the reports rather than merging them into one.

How do I set severity fairly?

Rate severity by impact on users and data, not by how many people complained. Use your triage definitions for S1 to S4, and record the reason in one line so the rating can be challenged.

  • #bug-report-template
  • #security-vulnerability-report
  • #defect-report-example
  • #bug-triage-template
  • #responsible-disclosure-report
  • #how-to-write-a-bug-report

More bug report templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…