Comparison
FSBP or CIS v5.0: what are the differences, which to enable?
AWS Foundational Security Best Practices and the CIS AWS Foundations Benchmark are the two most widely used security standards on AWS. They partly overlap, but they have neither the same goal nor the same scope.
In short
- FSBP is AWS's own standard: many controls, service by service, extended over time.
- CIS v5.0 is an independent benchmark: a versioned account hardening baseline, recognised beyond AWS.
- The right answer is often both: FSBP for service coverage, CIS for the baseline and external recognition.
FSBP and CIS v5.0 side by side
| Criterion | AWS FSBP | CIS AWS Foundations v5.0 |
|---|---|---|
| Publisher | AWS | Center for Internet Security, by practitioner consensus |
| Goal | Security best practices specific to each AWS service | Secure baseline configuration of an AWS account |
| Scope | Dozens of services: EC2, S3, RDS, Lambda, ECS, EKS, API Gateway, CloudFront, OpenSearch… | Five sections: IAM, storage, logging, monitoring, networking |
| Size | Over 200 controls | A few dozen recommendations, automated or manual |
| Evolution | Controls added continuously by AWS | Numbered versions (1.2, 1.4, 3.0, 5.0) |
| Recognition | AWS native standard | Frequent reference for external auditors (SOC 2, ISO 27001) |
| In Security Hub | Standard you can enable | CIS v5.0.0 standard you can enable, automating part of the recommendations |
Where they overlap
Some controls exist in both standards, under different identifiers:
- MFA and no access keys on the root user;
- MFA for console users, access key rotation, over-permissive policies;
- multi-region CloudTrail, log validation and encryption;
- S3 buckets that are public or accept HTTP;
- default EBS encryption and RDS encryption;
- security groups open on administration ports.
What only FSBP covers
- Controls specific to application services: outdated Lambda runtimes, privileged ECS task definitions, API Gateway logging, CloudFront and load balancer configuration.
- Data services beyond S3 and RDS: DynamoDB, OpenSearch, Redshift, ElastiCache…
- Backups and high availability for many services.
What only CIS covers
- Password policy details and disabling credentials unused for 45 days.
- Permissions granted through groups, the dedicated AWS Support role.
- The 15 CloudWatch metric filters and alarms of section 4.
- MFA Delete on critical S3 buckets.
Mapping of the shared controls
Security Hub gives each control a unique identifier, made of the service and a number (IAM.4, S3.5…), the same whichever standard includes it. The table maps the most common ones to their CIS v5.0.0 recommendation number.
| Check | Security Hub control | CIS v5.0.0 |
|---|---|---|
| No access key on the root user | IAM.4 | 1.3 |
| Root user MFA (hardware: IAM.6, 1.5) | IAM.9 | 1.4 |
| MFA for console users | IAM.5 | 1.9 |
| Access key rotation within 90 days | IAM.3 | 1.13 |
| S3 buckets: TLS required | S3.5 | 2.1.1 |
| S3 buckets: block public access | S3.1, S3.8 | 2.1.4 |
| RDS instance encryption | RDS.3 | 2.2.1 |
| Multi-Region CloudTrail | CloudTrail.1 | 3.1 |
| CloudTrail log file validation | CloudTrail.4 | 3.2 |
| AWS Config enabled | Config.1 | 3.3 |
| CloudTrail KMS encryption | CloudTrail.2 | 3.5 |
| KMS key rotation | KMS.4 | 3.6 |
| VPC flow logs | EC2.6 | 3.7 |
| EBS default encryption | EC2.7 | 5.1.1 |
| Admin ports open to 0.0.0.0/0 | EC2.53 | 5.3 |
| Default security group closed | EC2.2 | 5.5 |
| IMDSv2 on EC2 instances | EC2.8 | 5.7 |
Source: AWS Security Hub documentation, mapping of controls to CIS requirements. In an audit, quote both references: the Security Hub ID finds the finding, the CIS number answers the auditor.
What Security Hub actually checks for CIS v5.0
Enabling the CIS v5.0.0 standard in Security Hub does not check the whole benchmark. Security Hub maps about forty automated controls to it; the rest needs a manual check.
- Section 4 is not checked: since v3.0, AWS lists the CloudWatch metric filters and alarms as manual checks. A 100% CIS score in Security Hub says nothing about your monitoring.
- Other recommendations are not mapped to any Security Hub control: according to AWS, many can only be assessed by reviewing the state of the resources by hand.
- Levels 1 and 2: Security Hub is certified by CIS for both levels of the v5.0.0 benchmark. Level 1 is the baseline, Level 2 adds stricter measures.
- Delay: a control that shares its AWS Config rule with an already enabled standard can take up to 18 hours to produce its first findings.
Moving from CIS v3.0 to v5.0
AWS recommends v5.0.0. The Security Hub controls stay the same, but part of the CIS numbers change, which breaks the tracking sheets and reports that quote them.
- Section 1 shifts by one: the root access key moves from 1.4 to 1.3, console user MFA from 1.10 to 1.9, key rotation from 1.14 to 1.13.
- EBS default encryption leaves section 2: 2.2.1 in v3.0, 5.1.1 in v5.0. Number 2.2.1 now refers to RDS encryption.
- New requirement: Multi-AZ deployment of RDS instances and clusters (2.2.4). EFS file system encryption moves from 2.4.1 to 2.3.1.
- Enable v5.0.0 before you disable v3.0.0, so there is no period without checks. Both versions can run side by side.
Which one to enable?
- Both, if your Security Hub budget allows: they complement each other.
- Turn on Security Hub's consolidated control findings option: a control shared by both standards then produces a single finding per resource.
- If you must choose: FSBP for broad service coverage; CIS if a customer, an auditor or a regulator asks for it.
How the Silamir audit combines the two
- A score per standard, then an overall score.
- Shared findings are deduplicated: a single line, tagged
FSBP+CIS, with both references. - Findings specific to each standard stay identified, so you know where each gap comes from.
- Everything is prioritised with the other nine domains, based on the attack scenarios it enables.
FSBP and CIS: frequently asked questions
Should I enable FSBP and CIS at the same time?
It gives the widest coverage: FSBP covers the services, CIS the account baseline and external recognition. With consolidated control findings, a shared control produces a single finding per resource, so there are no duplicates.
Is an FSBP-compliant account CIS compliant?
No. Part of the controls are shared, but CIS adds requirements that FSBP lacks (password policy, credentials unused for 45 days, section 4 alarms, MFA Delete). CIS has to be assessed on its own.
Does Security Hub check every CIS v5.0 recommendation?
No. Security Hub automates about forty controls; the section 4 metric filters and alarms, among others, still need a manual check. The Silamir audit assesses them by reading the metric filters configured on the CloudTrail logs.
Which CIS version should I enable in Security Hub?
v5.0.0, which AWS recommends. If v3.0.0 is enabled, enable v5.0.0 first and keep the old one until the first findings arrive, then update the numbers quoted in your reports.
Where does your AWS account stand?
Ten questions, three minutes, no access to your account: a security score, a FinOps score and the article to read for each of your three weakest points. Your answers stay in your browser.
Ready to audit your AWS account?
Subscribe on AWS Marketplace, deploy the read-only role and get your reports within the hour.