AWS security assessment: 12 checks you can run yourself | Forrict Skip to main content
Security

AWS security assessment: 12 checks you can run yourself

Forrict
AWS security assessment: 12 checks you can run yourself
What does an AWS security assessment check? Twelve baseline checks from AWS's own standards, what they mean and how to verify them today.

“Is our AWS environment actually secure?” We hear that question a lot. The honest answer: it depends on a handful of baseline settings that, in practice, are often not quite right.

The good news: you don’t have to guess. AWS publishes standards with controls, and AWS Security Hub CSPM can check your accounts against them automatically. Below are the twelve checks we look at first in an AWS security assessment, with the name of the matching control in Security Hub CSPM, so you can find them yourself.

Where do these checks come from?

Security Hub CSPM supports, among others, two standards that matter here:

StandardFromWhat it is
AWS Foundational Security Best Practices (FSBP)AWSA set of controls that checks AWS accounts and resources against AWS best practices
CIS AWS Foundations BenchmarkCenter for Internet SecurityA widely used benchmark for the baseline setup of an AWS account. Security Hub CSPM supports v5.0.0, v3.0.0, v1.4.0 and v1.2.0

The control IDs in the tables below (such as IAM.4) are the names Security Hub CSPM uses. Each check shows which of the two standards it appears in; for CIS this means the recent versions unless stated otherwise.

Access: who can do what?

Most incidents start with access rights, so that is where most of the list sits.

#CheckWhy it mattersControlStandard
1MFA on the root userThe root user can do anything. Without MFA, one leaked password is enoughIAM.9CIS
2No access keys on the root userA root access key is a key to everything that can end up in scripts or on laptopsIAM.4FSBP and CIS
3MFA for everyone with a console passwordPasswords leak. MFA makes that leak far less seriousIAM.5FSBP and CIS
4Access keys rotated within 90 daysThe older a key, the bigger the chance it sits somewhere it shouldn’tIAM.3FSBP and CIS
5No policies with full * privilegesA policy that allows all actions on all resources is often added “temporarily” and never removedIAM.1FSBP (CIS up to v1.4.0)

Seeing what happens

When something goes wrong, you want to be able to see what happened. Ideally, you notice before a customer does.

#CheckWhy it mattersControlStandard
6CloudTrail on in all regionsWithout CloudTrail you don’t know who did what. Also check that log file validation is on (CloudTrail.4)CloudTrail.1FSBP and CIS
7GuardDuty enabledGuardDuty flags suspicious behavior, such as unusual API callsGuardDuty.1FSBP
8AWS Config enabledConfig records how your resources are configured. Security Hub CSPM uses Config rules for most of its controlsConfig.1FSBP and CIS

Data and network

#CheckWhy it mattersControlStandard
9S3 Block Public Access onA publicly readable bucket is one of the best-known causes of cloud data leaksS3.1FSBP and CIS
10EBS default encryptionWith this setting, every new volume is encrypted automatically, even if someone forgetsEC2.7FSBP and CIS
11No admin ports open to the whole internetSSH or RDP open to 0.0.0.0/0 invites login attempts. Also check that the default security group blocks all traffic (EC2.2)EC2.53CIS

Being reachable

#CheckWhy it mattersControlStandard
12Security contact registeredIf AWS sees something suspicious in your account, they need to reach the right personAccount.1FSBP and CIS

How to check it yourself

  1. Enable AWS Security Hub CSPM in your account, or better: centrally for your whole AWS Organization.
  2. Turn on the AWS Foundational Security Best Practices and CIS AWS Foundations Benchmark standards.
  3. Make sure AWS Config is enabled in every region where Security Hub CSPM runs. Without Config you get no control findings.
  4. Review the failed controls and look up the twelve from this list by their control ID.
  5. Start with root and IAM. That is usually where the biggest risk sits for the least effort.

Our take: what a checklist doesn’t show

This part is Forrict’s opinion, based on our own experience.

Green is not the same as secure. An environment can pass all twelve checks and still be vulnerable. For example because a role that neatly uses MFA can, in practice, do far more than it needs to.

An alert nobody reads doesn’t help. Turning on GuardDuty and Security Hub CSPM is step one. The question is who sees the alerts, and what happens next.

Not every failed control matters equally. An open port on a test environment without data is different from a public bucket with customer data. Prioritizing takes knowledge of your organization, not just of AWS.

That is exactly what an AWS security assessment is about: we look with you, weigh the findings against your situation and put the improvements in order. Running Azure next to AWS? Also read how Security Hub now covers Azure.

Request an AWS security assessment →

Sources

F

Forrict

AWS expert and consultant at Forrict, specializing in cloud architecture and AWS best practices for Dutch businesses.

Tags

AWS Security Security Assessment AWS Security Hub CIS Benchmark

Stay in the loop

Get AWS insights and tips delivered to your inbox.

Stay in the loop

Get AWS insights and tips delivered to your inbox.

Related Articles