Cloud security audit checklist: the evidence to collect for each access check
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
A cloud security audit checklist pairs each access control with the evidence an auditor can inspect. This one maps the 40 checks of the assessment to artifacts such as the IAM credential report, role assignment exports and log configuration, and sets a rule for each answer: a screenshot is not evidence unless dated.
Start the assessment ยท All guides
Collect an artifact for each answer, not a statement
An audit checks that a control works, so every answer on the 40-check list needs something an outsider can inspect. A statement such as "we rotate keys" is a claim. The credential report that shows every key age is evidence.
The Word version (.docx) of this checklist adds three columns to each check: the artifact, the date it was produced and the person who produced it.
| Domain | Evidence an auditor can ask for | Source in the cloud |
|---|---|---|
| Identities and entitlements | Credential report with MFA and key age for each account; list of administrator assignments; last access review with removals | IAM credential report, Entra role assignments, IAM policy export |
| Network reachability | Inbound rules open to the internet; list of public IP addresses; last reachability analysis with owners | Security groups, network security groups, firewall rule lists |
| Data perimeter | Public access block settings; external access findings with age; list of third-party trusts with owners and end dates | S3 Block Public Access, Access Analyzer, Cloud Asset Inventory |
| AI workloads | Identity per agent; written action list per agent; model allow list; invocation log sample | Role policies, model access policies, AI service logs |
| Guardrails and drift | Deny policy list at the root; exception register with expiry; latest drift report | Service control policies, Azure Policy, organization policy |
| Evidence | Trail configuration for every account; log retention settings; test of an alert; revocation drill record | Organization trail, log sinks, alert rules, drill notes |
Four rules keep the evidence usable
- Date every artifact. An export without a date cannot show the state on the day of the audit.
- Produce it from the system, not from memory. Console exports and CLI output beat typed summaries.
- Cover every account. A sample of accounts is acceptable only if the audit plan says how it was drawn.
- Keep the query. Store the command or console path beside the output so the auditor can repeat it.
Two checks are tests, not exports
The access evidence on demand and revocation drill checks cannot be answered with a file. They ask whether the team can do something within a time limit, one working day for the first and one hour for the second. The evidence is a written run with the start and end time of each step.
NIST SP 800-53 Rev. 5 lists the matching controls: AC-2 for account management, AU-6 for audit record review and IR-4 for incident handling. The tool cites those three for the checks above (NIST, read 16 Nov 2026).
Audit findings should keep the assessment weights
Rate each failed check with the weight it carries in the score, 1 to 3, so the audit report and the assessment agree on what matters most. The 12 checks that weigh 3 are the ones to put first in any audit summary.
Track every finding with an owner and a due date in the risk register template. The methodology explains how the five fixes are chosen.
Three exports start the evidence file
Each cloud can produce one export that answers many checks at once. Run these first, save the output with the date and the account or subscription it came from, and then work through the rest of the list.
| Cloud | Command or path | Checks it helps answer |
|---|---|---|
| AWS | aws iam generate-credential-report, then aws iam get-credential-report | Root MFA, long-lived keys, workforce users with passwords |
| Azure | az role assignment list --all, and the Entra role assignment export | Administrator roles, standing privilege, access reviews |
| Google Cloud | gcloud projects get-iam-policy for each project, and the same at the organization | Administrator roles, external principals, service accounts |
Answers marked "not known" count as failed until shown
The scoring gives the lowest value to "no or not known". An audit should do the same. If nobody can produce the artifact within the audit window, record the check as failed and add the missing export to the fix list, with an owner.
Record who signed off each domain. A sign-off by the owner of the control, not by the person who collected the evidence, shows that two people looked.
This list stops at the access layer
A full cloud audit also covers workload vulnerabilities, data handling and vendor contracts. Those need other checklists. For what an access-layer audit covers and how it differs from an assessment, read the cloud security audit guide.
Download
- Cloud security audit checklist (.docx)Word document made from this page, edition 16 Nov 2026
Related pages
Sources
- NIST SP 800-53 Rev. 5, read 16 Nov 2026
- IAM security best practices, read 16 Nov 2026
- Microsoft cloud security benchmark overview, read 16 Nov 2026
- CSA Cloud Controls Matrix, read 16 Nov 2026
Last reviewed 16 Nov 2026.