Skip to content
Cloud Security Risk Assessment

Cloud security checklist: 15 items to finish before a new account takes traffic

The cloud security checklist here has 15 items for a new AWS, Azure or Google Cloud account, taken from the 40 assessment checks: five on identity, two on network, two on data, two on guardrails and four on logs and alerts. Finish it on day one, before the account takes production traffic.

Start the assessment ยท All guides

Fifteen items are enough for day one

A new account needs a small list that one person can finish in a day. The 15 items below are a subset of the 40 checks in the assessment checklist, chosen because each is low or medium effort when the account is empty and expensive to retrofit later.

The order matters more than the list

Do identity first, because every later setting depends on who can change it. Then close the network, then block public data, then write the deny policies, and turn on logs before anyone deploys. Logs switched on later cannot show what happened earlier.

If you do only three things, do root account MFA, audit logging and public storage blocking. Each is rated low effort and weighs 3 in the score.

Where the list stops

The list leaves out the AI workload checks and several data perimeter checks, because a new account rarely has either on day one. Add them when the first agent or sensitive data store arrives. The AI identity and sensitive data location checks are the first to add.

The list is a floor. It does not tell you the state of an older estate, which needs the scored assessment.

Use the provider guidance for settings the list does not cover

The three providers publish their own baselines: the AWS Well-Architected Security Pillar, the Microsoft cloud security benchmark and Google Cloud security best practices. All three are linked below and each question page cites the one that applies (read 16 Nov 2026).

Run the 15 items again after the first month, then run the full 40-check list. The options page lists tools that can report on several of these items for you.

Three tests, one per cloud

For no open admin ports, AWS shows it in security group rules with source 0.0.0.0/0, Azure in network security group inbound rules with source Any or Internet, and Google Cloud in firewall rules with source range 0.0.0.0/0. The question pages give the same split for each of the 15 items, so a team on any of the three clouds can run the list.

Record the result for the account

Write the date, the person and the evidence for each item, and store them with the account record. A one-page record lets a later audit see that the account started clean, and it gives the risk register template a baseline if anything regresses.

Sources

  1. AWS Well-Architected Security Pillar, read 16 Nov 2026
  2. Microsoft cloud security benchmark overview, read 16 Nov 2026
  3. Google Cloud security best practices, read 16 Nov 2026
  4. NIST SP 800-53 Rev. 5, read 16 Nov 2026

Last reviewed 16 Nov 2026.