Skip to main content

AWS Audit

The 10 domains covered by the AWS audit

Ten domains are analysed in every audit, across the regions you choose, from the configuration of your AWS account.

The ten domains

  • Inventory

    Map of your resources (EC2, RDS, Lambda, S3, DynamoDB…) and tagging quality.

  • Security

    Compliance with AWS Foundational Security Best Practices v1.0.0 and the CIS AWS Foundations Benchmark v5.0.0.

  • FinOps

    Cost optimisation: Cost Explorer, Reserved Instances, Savings Plans, Compute Optimizer.

  • Well-Architected

    The six pillars of the AWS Well-Architected Framework, with Trusted Advisor and AWS Config.

  • Resilience

    Backups, disaster recovery, multi-AZ deployments, RTO and RPO objectives.

  • Network

    VPCs, subnets, routing, peering, VPN, Transit Gateway, NACLs and security groups.

  • Web security

    CloudFront, ALB, API Gateway, WAF, Shield, HTTP headers, TLS and certificates.

  • IAM

    Users, roles, policies, MFA, access key age and excessive privileges.

  • Containers and serverless

    ECS, EKS, Lambda and App Runner: configuration, exposure and best practices.

  • Secrets and encryption

    KMS, Secrets Manager, key and secret rotation, encryption at rest.

Frameworks

  • AWS Foundational Security Best Practices v1.0.0 - the AWS Security Hub security standard.
  • CIS AWS Foundations Benchmark v5.0.0 - the Center for Internet Security hardening baseline.
  • AWS Well-Architected Framework - operational excellence, security, reliability, performance, cost and sustainability.

Optional DAST scan

On request, an OWASP ZAP scan tests the public endpoints of your account, discovered automatically (CloudFront, API Gateway, ALB). Two modes: baseline, passive, up to 20 targets; full, active, with attack payloads, up to 10 targets. With the scan, the audit also reads the HTTP headers of each internet-facing server (one request per server): the CVE watch then spots the software they announce, even on instances without SSM. A scan failure does not stop the audit.

Regions

20 commercial regions are offered (Europe, North America, Asia Pacific, South America). Opt-in regions, GovCloud and China are not covered.

How the audit analyses your account

The audit runs in three stages, with no work from your teams once the role is deployed.

  • Collection: ten collectors, one per domain, call AWS read APIs (Describe, List, Get) in each selected region, through the read-only role.
  • Per-domain analysis: each domain is analysed separately from the collected data. Findings name the affected resource and the reference control.
  • Cross-domain analysis: findings from the ten domains are combined into 5 to 10 attack scenarios, which then set the priority of the actions.

When AWS Security Hub is enabled, the audit reuses its FSBP and CIS results and de-duplicates them. Otherwise, the controls are evaluated from direct collection.

What each domain reads

A selection of the AWS services read by the collectors. These are configuration calls: none of them reads the content of your data.

AWS services read per audit domain
DomainServices and settings read
InventoryEC2, Auto Scaling, Lambda, ECS, EKS, RDS, DynamoDB, ElastiCache, Redshift, S3, VPC, load balancers, SQS, SNS, EventBridge, Step Functions, Glue, SageMaker, Cognito
SecuritySecurity Hub (enabled standards and findings), GuardDuty, CloudTrail, AWS Config, IAM Access Analyzer, S3 Block Public Access, EBS and RDS encryption, security groups
FinOpsCost Explorer (costs, forecast, Savings Plans, reservations, rightsizing), orphaned volumes and snapshots, Elastic IP addresses, VPC endpoints, Trusted Advisor
Well-ArchitectedAWS Config, Compute Optimizer, CloudWatch alarms and dashboards, X-Ray, Organizations, resource tagging, Shield, Macie
ResilienceAWS Backup, RDS and EBS snapshots, DynamoDB continuous backups, S3 replication and versioning, multi-AZ deployments, Route 53 health checks, Elastic Disaster Recovery
NetworkVPCs, subnets, route tables, NACLs, security groups, NAT, Transit Gateway, peering, VPN, Direct Connect, Network Firewall, Flow Logs, Route 53 and DNSSEC
Web securityCloudFront and header policies, ALB, API Gateway, AppSync, Elastic Beanstalk, WAF, ACM certificates, S3 websites
IAMCredential report, users, roles, groups, policies, MFA, key age and last use, IAM Identity Center, SAML and OIDC federation, SCPs
Containers and serverlessECS (clusters, services, task definitions), EKS (clusters, node groups, add-ons), ECR and scan results, Lambda (configuration, URLs, policies), API Gateway
Secrets and encryptionKMS (keys, policies, rotation, grants), Secrets Manager, Parameter Store, encryption of S3, EBS, RDS, DynamoDB, EFS, OpenSearch, SQS and SNS

What the audit does not read

  • The content of your S3 buckets, databases, message queues and application logs.
  • The value of your secrets and parameters: only their metadata (rotation, encryption, policy) is read.
  • The inside of your instances and containers: no agent is installed, the operating system is not inspected.
  • Kubernetes objects inside EKS clusters: only the configuration exposed by the EKS API is read.

For full coverage

The audit works on any account. Some AWS services, when enabled, give more precise findings:

  • Security Hub with the FSBP and CIS v5.0 standards: their results are reused and de-duplicated.
  • Cost Explorer: required to quantify costs and savings in the FinOps domain.
  • Compute Optimizer: feeds the instance rightsizing recommendations.
  • AWS Config and IAM Access Analyzer: complement the Well-Architected, Security and IAM domains.

A disabled service does not stop the audit. Its absence is reported in the "Audit limitations" section of the relevant report and, for a security control, as a finding.

What the audit does not do

The audit reads configuration: it modifies no resource, installs no agent, and does not replace a manual penetration test or a certification.

Scope: frequently asked questions

Does the audit cover my whole AWS organisation?

No: an audit covers one account. For several accounts, deploy the role in each one and run one audit per account.

Do I need to enable Security Hub before the audit?

No. Without Security Hub, the FSBP and CIS v5.0 controls are evaluated from direct collection. When enabled, it enriches the analysis.

Should I audit every region?

Select the regions where you have resources, and those where unexpected activity would worry you. Global services (IAM, CloudFront, Route 53) are read whatever the selection.

Does the audit replace a penetration test?

No. The optional DAST scan tests your public endpoints automatically, but does not replace a penetration test carried out by a person.

Can the audit modify or slow down my resources?

No. The role only grants read permissions, and configuration calls have no effect on your workloads.

Ready to audit your AWS account?

Subscribe on AWS Marketplace, deploy the read-only role and get your reports within the hour.