Cloud security checklist: 15 items to finish before a new account takes traffic
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
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.
- Root or global administrator has phishing-resistant MFA and no keys: Turn on phishing-resistant MFA for the root or top administrator and delete any root keys.
- People sign in through single sign-on with MFA: Connect people to the cloud through single sign-on and disable local users.
- Long-lived keys removed or rotated every 90 days: Create no long-lived access keys; if one exists, set a 90-day rotation.
- Administrator roles are few, named and separate: Name the few administrators and give each a separate daily account.
- Emergency accounts tested twice a year: Create two emergency accounts and alert on every sign-in.
- No admin or database port open to the internet: Close SSH, RDP and database ports to the whole internet.
- No public IP address by default: Deny public IP addresses by default on compute and databases.
- Public object storage blocked organization-wide: Block public access to object storage at the organization level.
- External access findings reviewed weekly: Turn on external access analysis and send findings to an owner.
- Deny policies at the organization level: Write organization-level deny policies for your riskiest actions.
- Guardrails protected from tampering: Stop everyone but a security role from turning off logs and guardrails.
- Audit logs on in every account and region: Turn on audit logs in every region of the account.
- Logs stored where workload admins cannot change them: Send logs to a separate security account and lock them.
- Logs kept 365 days, 90 searchable: Keep audit logs for at least 365 days.
- Identity alerts reach a person: Alert on root sign-in, policy changes, new keys and disabled logging.
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.
Related pages
Sources
- AWS Well-Architected Security Pillar, read 16 Nov 2026
- Microsoft cloud security benchmark overview, read 16 Nov 2026
- Google Cloud security best practices, read 16 Nov 2026
- NIST SP 800-53 Rev. 5, read 16 Nov 2026
Last reviewed 16 Nov 2026.