Skip to content
The first pages of the Cloud Security Review template

Cloud Security Review

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 security review is only useful if it shows how a system could be attacked, which controls stop that, and what risk remains before launch. This template works through identity, network, logging and encryption on one cloud account, then ranks the findings by severity with an owner and a date for each. It works as a security review template, a security assessment report template or a threat model template, and it gives a STRIDE threat model example to start from. It can also feed security posture board slides.

The sample reviews a cloud account at Underhill Labs, with 12 components across three trust boundaries, one critical and three high findings, and one residual risk that the CISO has accepted in writing. All names, scores and certifications are fictional. Replace the data-flow diagram, threats and findings with your own, rate each finding with its evidence, and give every high and critical item an owner and SLA date.

Useful for

  • A security engineer reviewing a new cloud account before it takes live customer data
  • An architect preparing a threat model for a change to the login flow
  • A CISO summarising residual risk for the board before a launch decision

What's included

  • Identity page with an architecture diagram of accounts, roles and trust boundaries
  • Network page with a two-column article on exposure, routing and trust
  • Logging page with a numbered method, a ruled table and definitions
  • Encryption page with three try-it-yourself tip cards
  • Findings page with a severity chart, a split by level and a sources caption
  • Guide page with numbered steps for replacing the sample review

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

    Redraw the data-flow diagram with your components, data stores and trust boundaries.

  3. 3

    Replace the threats table with STRIDE threats for each boundary, and rate each finding on your own scale.

  4. 4

    Assign an owner and an SLA date to every high and critical finding, and record who accepted any residual risk.

  5. 5

    Delete the guide page, then share the review with the CISO or present it to the board.

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 fictional?

Yes. Underhill Labs, its named people, the components, the CVSS scores and the certifications are fictional. Replace them with your own evidence before the review goes to approvers.

Is a threat model the same as a security review?

No. A threat model maps how the system could be attacked, while the security review checks which controls exist and what risk remains. Keep both current when the architecture changes.

How often should the review be refreshed?

Refresh it when the architecture changes, when a new data store or trust boundary is added, and at least once a year. Record the date and the reviewer on the cover each time.

  • #security-review
  • #threat-model
  • #stride-analysis
  • #cloud-security
  • #security-assessment
  • #google-docs

More security review templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…