Skip to content
Cloud Security Risk Assessment

Cloud security audit: an access-layer audit tests controls and keeps the evidence

A cloud security audit tests whether controls work and keeps the evidence, where an assessment scores risk. An access-layer audit covers identities, network reachability, data perimeter, AI workloads, guardrails and logs, and ends with findings that each name a control, a test and an owner. Read 16 Nov 2026.

Start the assessment ยท All guides

An audit proves control operation and an assessment estimates risk

The two are often confused. An assessment asks how exposed you are and ranks the gaps. An audit asks whether a stated control operated as described over a period and keeps the proof.

This site does both in sequence: the assessment gives a score in about 20 minutes, and the audit checklist lists what to collect when someone needs to verify the answers. The guide on the cloud security assessment covers the first half.

Six areas make up an access-layer audit

  • Identities and entitlements: who can sign in, with which factors, and what they can do. Eight checks.
  • Network reachability: which services answer the internet and other networks. Seven checks.
  • Data perimeter: who can read stored data and from which networks. Seven checks.
  • AI workloads: the identity, permissions, data reach and logs of AI agents. Six checks.
  • Guardrails and drift: policies that block risky changes and the checks that catch drift. Six checks.
  • Evidence: audit logs, retention, alerts and the ability to cut off access. Six checks.

The audit steps follow a fixed order

  • Set the scope: list every account, subscription and project, and name the period covered.
  • Pick the test for each check from the question pages, which give AWS, Azure and Google Cloud commands.
  • Collect the artifact and note the date and the person who ran the test.
  • Rate each failed check with its weight and effort.
  • Write the finding with the control it fails, for example IA-2(1) in NIST SP 800-53 Rev. 5 for MFA.
  • Agree an owner and a due date, and recheck after the fix.

Auditors use standards as the yardstick

NIST SP 800-53 Rev. 5 is a catalog of security and privacy controls, and its families AC (access control), AU (audit and accountability), IA (identification and authentication) and IR (incident response) hold the controls behind most of the 40 checks (NIST, read 16 Nov 2026). The CIS Benchmarks give per-cloud configuration checks, and the CSA Cloud Controls Matrix gives a cloud-specific control set (CSA, read 16 Nov 2026).

The tool names the source control on every check. Sites that map controls across standards are a separate subject; this guide stays on the access layer.

A finding needs six fields

Findings written in the same shape are easier to track, close and recheck. The table shows the fields and one example drawn from the no open admin ports check.

FieldContentExample
CheckThe question and its idnet-01, SSH, RDP and database ports closed to the internet
ControlThe control it failsGoogle Cloud VPC firewall rules guidance; NIST SC-7
TestThe command or console pathList security groups with source 0.0.0.0/0 on port 22
ResultWhat the test returned, with the dateTwo groups open on port 22
OwnerOne named personThe team that owns the network account
Due dateDate of the recheckSet at the audit close

Frequent access-layer findings are old and plain

Audit findings at this layer are rarely exotic. They are keys that were never rotated, administrator roles that nobody reviewed, logs kept in the account they describe and exceptions that outlived their reason. The checks for these are long-lived keys, access reviews, protected logs and expiring exceptions.

Fixing them needs a calendar and an owner more than a new tool, which is why the register records both.

An internal audit and an external audit differ in what they accept

An internal audit can accept a live demonstration. An external one usually asks for dated exports. Plan for the stricter case: run each test from a script, save the output with a timestamp and store it with the finding. The register keeps the link between the finding and the artifact.

Sources

  1. NIST SP 800-53 Rev. 5, read 16 Nov 2026
  2. CIS Benchmarks, read 16 Nov 2026
  3. CSA Cloud Controls Matrix, read 16 Nov 2026

Last reviewed 16 Nov 2026.