Operational Best Practices for FFIEC

Conformance packs provide a general-purpose compliance framework designed to enable you to create security, operational or cost-optimization governance checks using managed or custom AWS Config rules and AWS Config remediation actions. Conformance Packs, as sample templates, are not designed to fully ensure compliance with a specific governance or compliance standard. You are responsible for making your own assessment of whether your use of the Services meets applicable legal and regulatory requirements.

The following provides a sample mapping between the Federal Financial Institutions Examination Council (FFIEC) Cyber Security Assessment Tool domains and AWS managed Config rules. Each Config rule applies to a specific AWS resource, and relates to one or more FFIEC Cyber Security Assessment Tool controls. A FFIEC Cyber Security Assessment Tool control can be related to multiple Config rules. Refer to the table below for more detail and guidance related to these mappings.

Control ID	Control Description	AWS Config Rule	Guidance
D1.G.IT.B.1	An inventory of organizational assets (for example, hardware, software, data, and systems hosted externally) is maintained.	ec2-instance-managed-by-systems-manager	An inventory of the software platforms and applications within the organization is possible by managing Amazon Elastic Compute Cloud (Amazon EC2) instances with AWS Systems Manager. Use AWS Systems Manager to provide detailed system configurations, operating system patch levels, services name and type, software installations, application name, publisher and version, and other details about your environment.
D1.G.IT.B.1	An inventory of organizational assets (for example, hardware, software, data, and systems hosted externally) is maintained.	ec2-stopped-instance	Enable this rule to help with the baseline configuration of Amazon Elastic Compute Cloud (Amazon EC2) instances by checking whether Amazon EC2 instances have been stopped for more than the allowed number of days, according to your organization's standards.
D1.G.IT.B.1	An inventory of organizational assets (for example, hardware, software, data, and systems hosted externally) is maintained.	ec2-volume-inuse-check	This rule ensures that Amazon Elastic Block Store volumes that are attached to Amazon Elastic Compute Cloud (Amazon EC2) instances are marked for deletion when an instance is terminated. If an Amazon EBS volume isn't deleted when the instance that it's attached to is terminated, it may violate the concept of least functionality.
D1.G.IT.B.1	An inventory of organizational assets (for example, hardware, software, data, and systems hosted externally) is maintained.	eip-attached	This rule ensures Elastic IPs allocated to a Amazon Virtual Private Cloud (Amazon VPC) are attached to Amazon Elastic Compute Cloud (Amazon EC2) instances or in-use Elastic Network Interfaces. This rule helps monitor unused EIPs in your environment.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	autoscaling-group-elb-healthcheck-required	The Elastic Load Balancer (ELB) health checks for Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling groups support maintenance of adequate capacity and availability. The load balancer periodically sends pings, attempts connections, or sends requests to test Amazon EC2 instances health in an auto-scaling group. If an instance is not reporting back, traffic is sent to a new Amazon EC2 instance.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	s3-bucket-replication-enabled	Amazon Simple Storage Service (Amazon S3) Cross-Region Replication (CRR) supports maintaining adequate capacity and availability. CRR enables automatic, asynchronous copying of objects across Amazon S3 buckets to help ensure that data availability is maintained.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	rds-in-backup-plan	To help with data back-up processes, ensure your Amazon Relational Database Service (Amazon RDS) instances are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	efs-in-backup-plan	To help with data back-up processes, ensure your Amazon Elastic File System (Amazon EFS) file systems are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	ebs-in-backup-plan	To help with data back-up processes, ensure your Amazon Elastic Block Store (Amazon EBS) volumes are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	dynamodb-in-backup-plan	To help with data back-up processes, ensure your Amazon DynamoDB tables are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	elasticache-redis-cluster-automatic-backup-check	When automatic backups are enabled, Amazon ElastiCache creates a backup of the cluster on a daily basis. The backup can be retained for a number of days as specified by your organization. Automatic backups can help guard against data loss. If a failure occurs, you can create a new cluster, which restores your data from the most recent backup.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	rds-multi-az-support	Multi-AZ support in Amazon Relational Database Service (Amazon RDS) provides enhanced availability and durability for database instances. When you provision a Multi-AZ database instance, Amazon RDS automatically creates a primary database instance, and synchronously replicates the data to a standby instance in a different Availability Zone. Each Availability Zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. In case of an infrastructure failure, Amazon RDS performs an automatic failover to the standby so that you can resume database operations as soon as the failover is complete.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	db-instance-backup-enabled	The backup feature of Amazon RDS creates backups of your databases and transaction logs. Amazon RDS automatically creates a storage volume snapshot of your DB instance, backing up the entire DB instance. The system allows you to set specific retention periods to meet your resilience requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	aurora-resources-protected-by-backup-plan	To help with data back-up processes, ensure your Amazon Aurora resources are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	backup-plan-min-frequency-and-min-retention-check	To help with data back-up processes, ensure your AWS Backup plan is set for a minimum frequency and retention. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. This rule allows you to set the requiredFrequencyValue (Config default: 1), requiredRetentionDays (Config default: 35) and requiredFrequencyUnit (Config default: days) parameters. The actual value should reflect your organizations requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	backup-recovery-point-manual-deletion-disabled	Ensure that your AWS Backup recovery points have an attached resource-based policy which prevents deletion of recovery points. Using a resource-based policy to prevent deletion of recovery points can assist in preventing accidental or intentional deletion.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	backup-recovery-point-minimum-retention-check	To help with data back-up processes, ensure your AWS Backup recovery points have a minimum retention period set. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. This rule allows you to set the requiredRetentionDays (config default: 35) parameter. The actual value should reflect your organizations requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	ec2-resources-protected-by-backup-plan	To help with data back-up processes, ensure your Amazon Elastic Compute Cloud (Amazon EC2) resources are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D1.RM.Rm.B.1	An information security and business continuity risk management function(s) exists within the institution.	redshift-backup-enabled	To help with data back-up processes, ensure your Amazon Redshift clusters have automated snapshots. When automated snapshots are enabled for a cluster, Redshift periodically takes snapshots of that cluster. By default, Redshift takes a snapshot every eight hours or every 5 GB for each node of data changes, or whichever comes first.
D1.RM.RA.B.2	The risk assessment identifies Internet- based systems and high-risk transactions that warrant additional authentication controls.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D1.RM.RA.B.2	The risk assessment identifies Internet- based systems and high-risk transactions that warrant additional authentication controls.	annual-risk-assessment-performed (process check)	Perform an annual risk assessment on your organization. Risk assessments can assist in determining the likelihood and impact of identified risks and/or vulnerabilities affecting an organization.
D1.TC.Tr.B.2	Annual information security training includes incident response, current cyber threats (for example,phishing, spear phishing, social engineering, and mobile security), and emerging issues.	security-awareness-program-exists (process check)	Establish and maintain a security awareness program for your organization. Security awareness programs educate employees on how to protect their organization from various security breaches or incidents.
D2.IS.Is.B.1	Information security threats are gathered and shared with applicable internal employees.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D2.IS.Is.B.1	Information security threats are gathered and shared with applicable internal employees.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D2.IS.Is.B.1	Information security threats are gathered and shared with applicable internal employees.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	s3-bucket-logging-enabled	Amazon Simple Storage Service (Amazon S3) server access logging provides a method to monitor the network for potential cybersecurity events. The events are monitored by capturing detailed records for the requests that are made to an Amazon S3 bucket. Each access log record provides details about a single access request. The details include the requester, bucket name, request time, request action, response status, and an error code, if relevant.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	s3-bucket-default-lock-enabled	Ensure that your Amazon Simple Storage Service (Amazon S3) bucket has lock enabled, by default. Because sensitive data can exist at rest in S3 buckets, enforce object locks at rest to help protect that data.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	cw-loggroup-retention-period-check	Ensure a minimum duration of event log data is retained for your log groups to help with troubleshooting and forensics investigations. The lack of available past event log data makes it difficult to reconstruct and identify potentially malicious events.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	rds-logging-enabled	To help with logging and monitoring within your environment, ensure Amazon Relational Database Service (Amazon RDS) logging is enabled. With Amazon RDS logging, you can capture events such as connections, disconnections, queries, or tables queried.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	wafv2-logging-enabled	To help with logging and monitoring within your environment, enable AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D2.MA.Ma.B.1	Audit log records and other security event logs are reviewed and retained in a secure manner.	elasticsearch-logs-to-cloudwatch	Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	s3-bucket-logging-enabled	Amazon Simple Storage Service (Amazon S3) server access logging provides a method to monitor the network for potential cybersecurity events. The events are monitored by capturing detailed records for the requests that are made to an Amazon S3 bucket. Each access log record provides details about a single access request. The details include the requester, bucket name, request time, request action, response status, and an error code, if relevant.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D2.MA.Ma.B.2	Computer event logs are used for investigations after an event has occurred.	elasticsearch-logs-to-cloudwatch	Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues.
D2.TI.Ti.B.1	The institution belongs or subscribes to a threat and vulnerability information-sharing source(s) that provides information on threats (for example, FS-ISAC, US- CERT).	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D2.TI.Ti.B.1	The institution belongs or subscribes to a threat and vulnerability information-sharing source(s) that provides information on threats (for example, FS-ISAC, US- CERT).	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D2.TI.Ti.B.2	Threat information is used to monitor threats and vulnerabilities.	ec2-managedinstance-patch-compliance-status-check	Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures.
D2.TI.Ti.B.2	Threat information is used to monitor threats and vulnerabilities.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D2.TI.Ti.B.2	Threat information is used to monitor threats and vulnerabilities.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D2.TI.Ti.B.3	Threat information is used to enhance internal risk management and controls.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D2.TI.Ti.B.3	Threat information is used to enhance internal risk management and controls.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.CC.PM.B.1	A patch management program is implemented and ensures that software and firmware patches are applied in a timely manner.	ec2-managedinstance-patch-compliance-status-check	Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures.
D3.CC.PM.B.1	A patch management program is implemented and ensures that software and firmware patches are applied in a timely manner.	elastic-beanstalk-managed-updates-enabled	Enabling managed platform updates for an Amazon Elastic Beanstalk environment ensures that the latest available platform fixes, updates, and features for the environment are installed. Keeping up to date with patch installation is a best practice in securing systems.
D3.CC.PM.B.1	A patch management program is implemented and ensures that software and firmware patches are applied in a timely manner.	rds-automatic-minor-version-upgrade-enabled	Enable automatic minor version upgrades on your Amazon Relational Database Service (RDS) instances to ensure the latest minor version updates to the Relational Database Management System (RDBMS) are installed, which may include security patches and bug fixes.
D3.CC.PM.B.1	A patch management program is implemented and ensures that software and firmware patches are applied in a timely manner.	redshift-cluster-maintenancesettings-check	This rule ensures that Amazon Redshift clusters have the preferred settings for your organization. Specifically, that they have preferred maintenance windows and automated snapshot retention periods for the database. This rule requires you to set the allowVersionUpgrade. The default is true. It also lets you optionally set the preferredMaintenanceWindow (the default is sat:16:00-sat:16:30), and the automatedSnapshotRetentionPeriod (the default is 1). The actual values should reflect your organization's policies.
D3.CC.PM.B.3	Patch management reports are reviewed and reflect missing security patches.	ec2-managedinstance-patch-compliance-status-check	Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures.
D3.CC.PM.B.3	Patch management reports are reviewed and reflect missing security patches.	elastic-beanstalk-managed-updates-enabled	Enabling managed platform updates for an Amazon Elastic Beanstalk environment ensures that the latest available platform fixes, updates, and features for the environment are installed. Keeping up to date with patch installation is a best practice in securing systems.
D3.CC.PM.B.3	Patch management reports are reviewed and reflect missing security patches.	rds-automatic-minor-version-upgrade-enabled	Enable automatic minor version upgrades on your Amazon Relational Database Service (RDS) instances to ensure the latest minor version updates to the Relational Database Management System (RDBMS) are installed, which may include security patches and bug fixes.
D3.CC.PM.B.3	Patch management reports are reviewed and reflect missing security patches.	redshift-cluster-maintenancesettings-check	This rule ensures that Amazon Redshift clusters have the preferred settings for your organization. Specifically, that they have preferred maintenance windows and automated snapshot retention periods for the database. This rule requires you to set the allowVersionUpgrade. The default is true. It also lets you optionally set the preferredMaintenanceWindow (the default is sat:16:00-sat:16:30), and the automatedSnapshotRetentionPeriod (the default is 1). The actual values should reflect your organization's policies.
D3.DC.An.B.1	The institution is able to detect anomalous activities through monitoring across the environment.	guardduty-non-archived-findings	Amazon GuardDuty helps you understand the impact of an incident by classifying findings by severity: low, medium, and high. You can use these classifications for determining remediation strategies and priorities. This rule allows you to optionally set the daysLowSev (Config Default: 30), daysMediumSev (Config Default: 7), and daysHighSev (Config Default: 1) for non-archived findings, as required by your organization's policies.
D3.DC.An.B.1	The institution is able to detect anomalous activities through monitoring across the environment.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D3.DC.An.B.1	The institution is able to detect anomalous activities through monitoring across the environment.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.DC.An.B.2	Customer transactions generating anomalous activity alerts are monitored and reviewed.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.DC.An.B.2	Customer transactions generating anomalous activity alerts are monitored and reviewed.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	s3-bucket-logging-enabled	Amazon Simple Storage Service (Amazon S3) server access logging provides a method to monitor the network for potential cybersecurity events. The events are monitored by capturing detailed records for the requests that are made to an Amazon S3 bucket. Each access log record provides details about a single access request. The details include the requester, bucket name, request time, request action, response status, and an error code, if relevant.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	rds-logging-enabled	To help with logging and monitoring within your environment, ensure Amazon Relational Database Service (Amazon RDS) logging is enabled. With Amazon RDS logging, you can capture events such as connections, disconnections, queries, or tables queried.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	wafv2-logging-enabled	To help with logging and monitoring within your environment, enable AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D3.DC.An.B.3	Logs of physical and/or logical access are reviewed following events.	elasticsearch-logs-to-cloudwatch	Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	rds-logging-enabled	To help with logging and monitoring within your environment, ensure Amazon Relational Database Service (Amazon RDS) logging is enabled. With Amazon RDS logging, you can capture events such as connections, disconnections, queries, or tables queried.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	wafv2-logging-enabled	To help with logging and monitoring within your environment, enable AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	s3-bucket-logging-enabled	Amazon Simple Storage Service (Amazon S3) server access logging provides a method to monitor the network for potential cybersecurity events. The events are monitored by capturing detailed records for the requests that are made to an Amazon S3 bucket. Each access log record provides details about a single access request. The details include the requester, bucket name, request time, request action, response status, and an error code, if relevant.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D3.DC.An.B.4	Access to critical systems by third parties is monitored for unauthorized or unusual activity	elasticsearch-logs-to-cloudwatch	Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues.
D3.DC.An.B.5	Elevated privileges are monitored.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.DC.An.B.5	Elevated privileges are monitored.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.DC.Ev.B.1	A normal network activity baseline is established.	lambda-concurrency-check	This rule ensures that a Lambda function's concurrency high and low limits are established. This can assist in baselining the number of requests that your function is serving at any given time.
D3.DC.Ev.B.1	A normal network activity baseline is established.	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D3.DC.Ev.B.1	A normal network activity baseline is established.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.DC.Ev.B.1	A normal network activity baseline is established.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.DC.Ev.B.1	A normal network activity baseline is established.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D3.DC.Ev.B.1	A normal network activity baseline is established.	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D3.DC.Ev.B.1	A normal network activity baseline is established.	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D3.DC.Ev.B.1	A normal network activity baseline is established.	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D3.DC.Ev.B.1	A normal network activity baseline is established.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D3.DC.Ev.B.2	Mechanisms (for example, antivirus alerts, log event alerts) are in place to alert management to potential attacks.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.DC.Ev.B.3	Processes are in place to monitor for the presence of unauthorized users, devices, connections, and software.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D3.DC.Ev.B.3	Processes are in place to monitor for the presence of unauthorized users, devices, connections, and software.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.DC.Ev.B.3	Processes are in place to monitor for the presence of unauthorized users, devices, connections, and software.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D3.DC.Ev.B.3	Processes are in place to monitor for the presence of unauthorized users, devices, connections, and software.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.DC.Th.B.1	Independent testing (including penetration testing and vulnerability scanning) is conducted according to the risk assessment for external-facing systems and the internal network.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D3.DC.Th.B.1	Independent testing (including penetration testing and vulnerability scanning) is conducted according to the risk assessment for external-facing systems and the internal network.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D3.DC.Th.B.1	Independent testing (including penetration testing and vulnerability scanning) is conducted according to the risk assessment for external-facing systems and the internal network.	ec2-managedinstance-patch-compliance-status-check	Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-group-has-users-check	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-root-access-key-check	Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their AWS Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based AWS accounts to help to incorporate the principle of least functionality.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-user-group-membership-check	AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-user-no-policies-check	This rule ensures AWS Identity and Access Management (IAM) policies are attached only to groups or roles to control access to systems and assets. Assigning privileges at the group or the role level helps to reduce opportunity for an identity to receive or retain excessive privileges.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-no-inline-policy-check	Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	ec2-instance-profile-attached	EC2 instance profiles pass an IAM role to an EC2 instance. Attaching an instance profile to your instances can assist with least privilege and permissions management.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	ecs-task-definition-user-for-host-mode-check	If a task definition has elevated privileges it is because the customer has specifically opted-in to those configurations. This control checks for unexpected privilege escalation when a task definition has host networking enabled but the customer has not opted-in to elevated privileges.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-customer-policy-blocked-kms-actions	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing blocked actions on all AWS Key Management Service keys. Having more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-inline-policy-blocked-kms-actions	Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to allow blocked actions on all AWS Key Management Service keys. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning, rolling back, and delegating permissions management. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies.
D3.PC.Am.B.1	Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.10	Production and non-production environments are segregated to prevent unauthorized access or changes to information assets. (*N/A if no production environment exists at the institution or the institution’s third-party.)	ec2-instances-in-vpc	Deploy Amazon Elastic Compute Cloud (Amazon EC2) instances within an Amazon Virtual Private Cloud (Amazon VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection. All traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. Assign Amazon EC2 instances to an Amazon VPC to properly manage access.
D3.PC.Am.B.10	Production and non-production environments are segregated to prevent unauthorized access or changes to information assets. (*N/A if no production environment exists at the institution or the institution’s third-party.)	vpc-sg-open-only-to-authorized-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
D3.PC.Am.B.10	Production and non-production environments are segregated to prevent unauthorized access or changes to information assets. (*N/A if no production environment exists at the institution or the institution’s third-party.)	restricted-ssh	Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
D3.PC.Am.B.10	Production and non-production environments are segregated to prevent unauthorized access or changes to information assets. (*N/A if no production environment exists at the institution or the institution’s third-party.)	restricted-common-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	emr-kerberos-enabled	The access permissions and authorizations can be managed and incorporated with the principles of least privilege and separation of duties, by enabling Kerberos for Amazon EMR clusters. In Kerberos, the services and the users that need to authenticate are known as principals. The principals exist within a Kerberos realm. Within the realm, a Kerberos server is known as the key distribution center (KDC). It provides a means for the principals to authenticate. The KDC authenticates by issuing tickets for authentication. The KDC maintains a database of the principals within its realm, their passwords, and other administrative information about each principal.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	ec2-ebs-encryption-by-default	To help protect data at rest, ensure that encryption is enabled for your Amazon Elastic Block Store (Amazon EBS) volumes. Because sensitive data can exist at rest in these volumes, enable encryption at rest to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	s3-bucket-server-side-encryption-enabled	To help protect data at rest, ensure encryption is enabled for your Amazon Simple Storage Service (Amazon S3) buckets. Because sensitive data can exist at rest in Amazon S3 buckets, enable encryption to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	s3-bucket-ssl-requests-only	To help protect data in transit, ensure that your Amazon Simple Storage Service (Amazon S3) buckets require requests to use Secure Socket Layer (SSL). Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	rds-storage-encrypted	To help protect data at rest, ensure that encryption is enabled for your Amazon Relational Database Service (Amazon RDS) instances. Because sensitive data can exist at rest in Amazon RDS instances, enable encryption at rest to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	encrypted-volumes	Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elastic Block Store (Amazon EBS) volumes.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	opensearch-encrypted-at-rest	Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon OpenSearch Service domains.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	opensearch-node-to-node-encryption-check	Ensure node-to-node encryption for Amazon OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	efs-encrypted-check	Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elastic File System (EFS).
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	elasticsearch-encrypted-at-rest	Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon OpenSearch Service (OpenSearch Service) domains.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	elasticsearch-node-to-node-encryption-check	Ensure node-to-node encryption for Amazon OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	alb-http-to-https-redirection-check	To help protect data in transit, ensure that your Application Load Balancer automatically redirects unencrypted HTTP requests to HTTPS. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	elb-tls-https-listeners-only	Ensure that your Elastic Load Balancers (ELBs) are configured with SSL or HTTPS listeners. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	redshift-require-tls-ssl	Ensure that your Amazon Redshift clusters require TLS/SSL encryption to connect to SQL clients. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	api-gw-ssl-enabled	Ensure Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	backup-recovery-point-encrypted	Ensure that encryption is enabled for your AWS Backup recovery points. Because sensitive data can exist at rest, enable encryption at rest to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	redshift-cluster-kms-enabled	To help protect data at rest, ensure encryption with AWS Key Management Service (AWS KMS) is enabled for your Amazon Redshift cluster. Because sensitive data can exist at rest in Redshift clusters, enable encryption at rest to help protect that data.
D3.PC.Am.B.12	All passwords are encrypted in storage and in transit.	s3-default-encryption-kms	Ensure that encryption is enabled for your Amazon Simple Storage Service (Amazon S3) buckets. Because sensitive data can exist at rest in an Amazon S3 bucket, enable encryption at rest to help protect that data.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	elb-acm-certificate-required	Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS services and internal resources.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	alb-http-to-https-redirection-check	To help protect data in transit, ensure that your Application Load Balancer automatically redirects unencrypted HTTP requests to HTTPS. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	elb-tls-https-listeners-only	Ensure that your Elastic Load Balancers (ELBs) are configured with SSL or HTTPS listeners. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	redshift-require-tls-ssl	Ensure that your Amazon Redshift clusters require TLS/SSL encryption to connect to SQL clients. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	s3-bucket-ssl-requests-only	To help protect data in transit, ensure that your Amazon Simple Storage Service (Amazon S3) buckets require requests to use Secure Socket Layer (SSL). Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	api-gw-ssl-enabled	Ensure Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway.
D3.PC.Am.B.13	Confidential data is encrypted when transmitted across public or untrusted networks (for example, Internet).	elbv2-acm-certificate-required	Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS services and internal resources.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	s3-bucket-ssl-requests-only	To help protect data in transit, ensure that your Amazon Simple Storage Service (Amazon S3) buckets require requests to use Secure Socket Layer (SSL). Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	root-account-hardware-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	root-account-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	mfa-enabled-for-iam-console-access	Manage access to resources in the AWS Cloud by ensuring that MFA is enabled for all AWS Identity and Access Management (IAM) users that have a console password. MFA adds an extra layer of protection on top of sign-in credentials. By requiring MFA for users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	alb-http-to-https-redirection-check	To help protect data in transit, ensure that your Application Load Balancer automatically redirects unencrypted HTTP requests to HTTPS. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	api-gw-ssl-enabled	Ensure Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway.
D3.PC.Am.B.15	Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.	redshift-require-tls-ssl	Ensure that your Amazon Redshift clusters require TLS/SSL encryption to connect to SQL clients. Because sensitive data can exist, enable encryption in transit to help protect that data.
D3.PC.Am.B.16	Administrative, physical, or technical controls are in place to prevent users without administrative responsibilities from installing unauthorized software.	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.16	Administrative, physical, or technical controls are in place to prevent users without administrative responsibilities from installing unauthorized software.	iam-group-has-users-check	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege.
D3.PC.Am.B.16	Administrative, physical, or technical controls are in place to prevent users without administrative responsibilities from installing unauthorized software.	iam-user-group-membership-check	AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.16	Administrative, physical, or technical controls are in place to prevent users without administrative responsibilities from installing unauthorized software.	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.2	Employee access to systems and confidential data provides for separation of duties.	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.2	Employee access to systems and confidential data provides for separation of duties.	iam-user-group-membership-check	AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.2	Employee access to systems and confidential data provides for separation of duties.	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls)	root-account-hardware-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls)	root-account-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls).	iam-group-has-users-check	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls)	iam-root-access-key-check	Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their AWS Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based AWS accounts to help to incorporate the principle of least functionality.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls)	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.3	Elevated privileges (for example, administrator privileges) are limited and tightly controlled (for example, assigned to individuals, not shared, and require stronger password controls)	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-user-unused-credentials-check	AWS Identity and Access Management (IAM) can help you with access permissions and authorizations by checking for IAM passwords and access keys that are not used for a specified time period. If these unused credentials are identified, you should disable and/or remove the credentials, as this may violate the principle of least privilege. This rule requires you to set a value to the maxCredentialUsageAge (Config Default: 90). The actual value should reflect your organization's policies.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-password-policy	The identities and the credentials are issued, managed, and verified based on an organizational IAM password policy. They meet or exceed requirements as stated by NIST SP 800-63 and the AWS Foundational Security Best Practices standard for password strength. This rule allows you to optionally set RequireUppercaseCharacters (AWS Foundational Security Best Practices value: true), RequireLowercaseCharacters (AWS Foundational Security Best Practices value: true), RequireSymbols (AWS Foundational Security Best Practices value: true), RequireNumbers (AWS Foundational Security Best Practices value: true), MinimumPasswordLength (AWS Foundational Security Best Practices value: 14), PasswordReusePrevention (AWS Foundational Security Best Practices value: 24), and MaxPasswordAge (AWS Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-user-mfa-enabled	Enable this rule to restrict access to resources in the AWS Cloud. This rule ensures multi-factor authentication (MFA) is enabled for all users. MFA adds an extra layer of protection on top of sign-in credentials. Reduce the incidents of compromised accounts by requiring MFA for users.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	mfa-enabled-for-iam-console-access	Manage access to resources in the AWS Cloud by ensuring that MFA is enabled for all AWS Identity and Access Management (IAM) users that have a console password. MFA adds an extra layer of protection on top of sign-in credentials. By requiring MFA for users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	root-account-hardware-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	root-account-mfa-enabled	Manage access to resources in the AWS Cloud by ensuring MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-group-has-users-check	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-user-group-membership-check	AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-user-no-policies-check	This rule ensures AWS Identity and Access Management (IAM) policies are attached only to groups or roles to control access to systems and assets. Assigning privileges at the group or the role level helps to reduce opportunity for an identity to receive or retain excessive privileges.
D3.PC.Am.B.6	Identification and authentication are required and managed for access to systems, applications, and hardware.	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Am.B.7	Access controls include password complexity and limits to password attempts and reuse.	iam-password-policy	The identities and the credentials are issued, managed, and verified based on an organizational IAM password policy. They meet or exceed requirements as stated by NIST SP 800-63 and the AWS Foundational Security Best Practices standard for password strength. This rule allows you to optionally set RequireUppercaseCharacters (AWS Foundational Security Best Practices value: true), RequireLowercaseCharacters (AWS Foundational Security Best Practices value: true), RequireSymbols (AWS Foundational Security Best Practices value: true), RequireNumbers (AWS Foundational Security Best Practices value: true), MinimumPasswordLength (AWS Foundational Security Best Practices value: 14), PasswordReusePrevention (AWS Foundational Security Best Practices value: 24), and MaxPasswordAge (AWS Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
D3.PC.Am.B.8	All default passwords and unnecessary default accounts are changed before system implementation.	iam-root-access-key-check	Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their AWS Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based AWS accounts to help to incorporate the principle of least functionality.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	acm-certificate-expiration-check	Ensure network integrity is protected by ensuring X509 certificates are issued by AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	dms-replication-not-public	Manage access to the AWS Cloud by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	ebs-snapshot-public-restorable-check	Manage access to the AWS Cloud by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	ec2-instance-no-public-ip	Manage access to the AWS Cloud by ensuring Amazon Elastic Compute Cloud (Amazon EC2) instances cannot be publicly accessed. Amazon EC2 instances can contain sensitive information and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	elasticsearch-in-vpc-only	Manage access to the AWS Cloud by ensuring Amazon OpenSearch Service (OpenSearch Service) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An OpenSearch Service domain within an Amazon VPC enables secure communication between OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	emr-master-no-public-ip	Manage access to the AWS Cloud by ensuring Amazon EMR cluster master nodes cannot be publicly accessed. Amazon EMR cluster master nodes can contain sensitive information and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	restricted-ssh	Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	ec2-instances-in-vpc	Deploy Amazon Elastic Compute Cloud (Amazon EC2) instances within an Amazon Virtual Private Cloud (Amazon VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection. All traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. Assign Amazon EC2 instances to an Amazon VPC to properly manage access.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	lambda-function-public-access-prohibited	Manage access to resources in the AWS Cloud by ensuring AWS Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	lambda-inside-vpc	Deploy AWS Lambda functions within an Amazon Virtual Private Cloud (Amazon VPC) for a secure communication between a function and other services within the Amazon VPC. With this configuration, there is no requirement for an internet gateway, NAT device, or VPN connection. All the traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. To properly manage access, AWS Lambda functions should be assigned to a VPC.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	rds-instance-public-access-check	Manage access to resources in the AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information, and principles and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	rds-snapshots-public-prohibited	Manage access to resources in the AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information and principles and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	redshift-cluster-public-access-check	Manage access to resources in the AWS Cloud by ensuring that Amazon Redshift clusters are not public. Amazon Redshift clusters can contain sensitive information and principles and access control is required for such accounts.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	restricted-common-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	s3-bucket-public-read-prohibited	Manage access to resources in the AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	s3-bucket-public-write-prohibited	Manage access to resources in the AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	sagemaker-notebook-no-direct-internet-access	Manage access to resources in the AWS Cloud by ensuring that Amazon SageMaker notebooks do not allow direct internet access. By preventing direct internet access, you can keep sensitive data from being accessed by unauthorized users.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	vpc-default-security-group-closed	Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	alb-waf-enabled	Ensure AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	vpc-sg-open-only-to-authorized-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	api-gw-associated-with-waf	AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	autoscaling-launch-config-public-ip-disabled	If you configure your Network Interfaces with a public IP address, then the associated resources to those Network Interfaces are reachable from the internet. EC2 resources should not be publicly accessible, as this may allow unintended access to your applications or servers.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	no-unrestricted-route-to-igw	Ensure Amazon EC2 route tables do not have unrestricted routes to an internet gateway. Removing or limiting the access to the internet for workloads within Amazon VPCs can reduce unintended access within your environment.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	s3-account-level-public-access-blocks-periodic	Manage access to resources in the AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access. This rule allows you to optionally set the ignorePublicAcls (Config Default: True), blockPublicPolicy (Config Default: True), blockPublicAcls (Config Default: True), and restrictPublicBuckets parameters (Config Default: True). The actual values should reflect your organization's policies.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	s3-bucket-level-public-access-prohibited	Manage access to resources in the AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access at the bucket level.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	ssm-document-not-public	Ensure AWS Systems Manager (SSM) documents are not public, as this may allow unintended access to your SSM documents. A public SSM document can expose information about your account, resources and internal processes.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	opensearch-in-vpc-only	Manage access to the AWS Cloud by ensuring Amazon OpenSearch Service domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon OpenSearch Service domain within an Amazon VPC enables secure communication between Amazon OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	subnet-auto-assign-public-ip-disabled	Manage access to the AWS Cloud by ensuring Amazon Virtual Private Cloud (VPC) subnets are not automatically assigned a public IP address. Amazon Elastic Compute Cloud (EC2) instances that are launched into subnets that have this attribute enabled have a public IP address assigned to their primary network interface.
D3.PC.Im.B.1	Network perimeter defense tools (for example, border router and firewall) are used.	redshift-enhanced-vpc-routing-enabled	Enhanced VPC routing forces all COPY and UNLOAD traffic between the cluster and data repositories to go through your Amazon VPC. You can then use VPC features such as security groups and network access control lists to secure network traffic. You can also use VPC flow logs to monitor network traffic.
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	vpc-default-security-group-closed	Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources.
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	vpc-sg-open-only-to-authorized-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	restricted-ssh	Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	restricted-common-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	api-gw-associated-with-waf	AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks
D3.PC.IM.B.2	Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.	alb-waf-enabled	Ensure AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment.
D3.PC.IM.B.3	All ports are monitored.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.PC.IM.B.3	All ports are monitored.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.PC.IM.B.3	All ports are monitored.	api-gw-execution-logging-enabled	API Gateway logging displays detailed views of users who accessed the API and the way they accessed the API. This insight enables visibility of user activities.
D3.PC.IM.B.3	All ports are monitored.	wafv2-logging-enabled	To help with logging and monitoring within your environment, enable AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched.
D3.PC.IM.B.3	All ports are monitored.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D3.PC.IM.B.3	All ports are monitored.	vpc-flow-logs-enabled	The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol.
D3.PC.Im.B.5	Systems configurations (for servers, desktops, routers, etc.) follow industry standards and are enforced	ec2-managedinstance-association-compliance-status-check	Use AWS Systems Manager Associations to help with inventory of software platforms and applications within an organization. AWS Systems Manager assigns a configuration state to your managed instances and allows you to set baselines of operating system patch levels, software installations, application configurations, and other details about your environment.
D3.PC.Im.B.5	Systems configurations (for servers, desktops, routers, etc.) follow industry standards and are enforced	ec2-instance-managed-by-systems-manager	An inventory of the software platforms and applications within the organization is possible by managing Amazon Elastic Compute Cloud (Amazon EC2) instances with AWS Systems Manager. Use AWS Systems Manager to provide detailed system configurations, operating system patch levels, services name and type, software installations, application name, publisher and version, and other details about your environment.
D3.PC.Im.B.5	Systems configurations (for servers, desktops, routers, etc.) follow industry standards and are enforced	ec2-managedinstance-patch-compliance-status-check	Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures.
D3.PC.IM.B.6	Ports, functions, protocols and services are prohibited if no longer needed for business purposes.	vpc-sg-open-only-to-authorized-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
D3.PC.IM.B.6	Ports, functions, protocols and services are prohibited if no longer needed for business purposes.	vpc-default-security-group-closed	Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources.
D3.PC.IM.B.6	Ports, functions, protocols and services are prohibited if no longer needed for business purposes.	restricted-ssh	Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
D3.PC.IM.B.6	Ports, functions, protocols and services are prohibited if no longer needed for business purposes.	restricted-common-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	iam-user-group-membership-check	AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	iam-user-no-policies-check	This rule ensures AWS Identity and Access Management (IAM) policies are attached only to groups or roles to control access to systems and assets. Assigning privileges at the group or the role level helps to reduce opportunity for an identity to receive or retain excessive privileges.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	iam-no-inline-policy-check	Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	iam-policy-no-statements-with-admin-access	AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D3.PC.Im.B.7	Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.	iam-policy-no-statements-with-full-access	Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
D3.PC.Se.B.1	Developers working for the institution follow secure program coding practices, as part of a system development life cycle (SDLC), that meet industry standards.	codebuild-project-envvar-awscred-check	Ensure authentication credentials AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY do not exist within AWS Codebuild project environments. Do not store these variables in clear text. Storing these variables in clear text leads to unintended data exposure and unauthorized access.
D3.PC.Se.B.1	Developers working for the institution follow secure program coding practices, as part of a system development life cycle (SDLC), that meet industry standards.	codebuild-project-source-repo-url-check	Ensure the GitHub or Bitbucket source repository URL does not contain personal access tokens, sign-in credentials within AWS Codebuild project environments. Use OAuth instead of personal access tokens or sign-in credentials to grant authorization for accessing GitHub or Bitbucket repositories.
D4.C.Co.B.2	The institution ensures that third-party connections are authorized.	vpc-sg-open-only-to-authorized-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
D4.C.Co.B.2	The institution ensures that third-party connections are authorized.	vpc-default-security-group-closed	Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources.
D4.C.Co.B.2	The institution ensures that third-party connections are authorized.	restricted-ssh	Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
D4.C.Co.B.2	The institution ensures that third-party connections are authorized.	restricted-common-ports	Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
D5.DR.De.B.1	Alert parameters are set for detecting information security incidents that prompt mitigating actions.	cloudwatch-alarm-action-check	Amazon CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation periods. The alarm performs one or more actions based on the value of the metric or expression relative to a threshold over a number of time periods. This rule requires a value for alarmActionRequired (Config Default: True), insufficientDataActionRequired (Config Default: True), okActionRequired (Config Default: False). The actual value should reflect the alarm actions for your environment.
D5.DR.De.B.1	Alert parameters are set for detecting information security incidents that prompt mitigating actions.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D5.DR.De.B.1	Alert parameters are set for detecting information security incidents that prompt mitigating actions.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D5.DR.De.B.2	System performance reports contain information that can be used as a risk indicator to detect information security incidents	lambda-dlq-check	Enable this rule to help notify the appropriate personnel through Amazon Simple Queue Service (Amazon SQS) or Amazon Simple Notification Service (Amazon SNS) when a function has failed.
D5.DR.De.B.2	System performance reports contain information that can be used as a risk indicator to detect information security incidents	dynamodb-throughput-limit-check	Enable this rule to ensure that provisioned throughput capacity is checked on your Amazon DynamoDB tables. This is the amount of read/write activity that each table can support. DynamoDB uses this information to reserve sufficient system resources to meet your throughput requirements. This rule generates an alert when the throughput approaches the maximum limit for a customer's account. This rule allows you to optionally set accountRCUThresholdPercentage (Config Default: 80) and accountWCUThresholdPercentage (Config Default: 80) parameters. The actual values should reflect your organization's policies.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	cloudtrail-enabled	AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	elb-logging-enabled	Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	cloudtrail-s3-dataevents-enabled	The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	multi-region-cloudtrail-enabled	AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	redshift-cluster-configuration-check	To protect data at rest, ensure that encryption is enabled for your Amazon Redshift clusters. You must also ensure that required configurations are deployed on Amazon Redshift clusters. The audit logging should be enabled to provide information about connections and user activities in the database. This rule requires that a value is set for clusterDbEncrypted (Config Default : TRUE), and loggingEnabled (Config Default: TRUE). The actual values should reflect your organization's policies.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	s3-bucket-logging-enabled	Amazon Simple Storage Service (Amazon S3) server access logging provides a method to monitor the network for potential cybersecurity events. The events are monitored by capturing detailed records for the requests that are made to an Amazon S3 bucket. Each access log record provides details about a single access request. The details include the requester, bucket name, request time, request action, response status, and an error code, if relevant.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	rds-logging-enabled	To help with logging and monitoring within your environment, ensure Amazon Relational Database Service (Amazon RDS) logging is enabled. With Amazon RDS logging, you can capture events such as connections, disconnections, queries, or tables queried.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	wafv2-logging-enabled	To help with logging and monitoring within your environment, enable AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	cloud-trail-cloud-watch-logs-enabled	Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	cloudwatch-alarm-action-check	Amazon CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation periods. The alarm performs one or more actions based on the value of the metric or expression relative to a threshold over a number of time periods. This rule requires a value for alarmActionRequired (Config Default: True), insufficientDataActionRequired (Config Default: True), okActionRequired (Config Default: False). The actual value should reflect the alarm actions for your environment.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	guardduty-enabled-centralized	Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your AWS Cloud environment.
D5.DR.De.B.3	Tools and processes are in place to detect, alert, and trigger the incident response program.	securityhub-enabled	AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions.
D5.ER.Es.B.4	Incidents are classified, logged and tracked.	guardduty-non-archived-findings	Amazon GuardDuty helps you understand the impact of an incident by classifying findings by severity: low, medium, and high. You can use these classifications for determining remediation strategies and priorities. This rule allows you to optionally set the daysLowSev (Config Default: 30), daysMediumSev (Config Default: 7), and daysHighSev (Config Default: 1) for non-archived findings, as required by your organization's policies.
D5.IR.Pl.B.1	The institution has documented how it will react and respond to cyber incidents.	response-plan-exists-maintained (process check)	Ensure incident response plans are established, maintained, and distributed to responsible personnel.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	s3-bucket-versioning-enabled	Amazon Simple Storage Service (Amazon S3) bucket versioning helps keep multiple variants of an object in the same Amazon S3 bucket. Use versioning to preserve, retrieve, and restore every version of every object stored in your Amazon S3 bucket. Versioning helps you to easily recover from unintended user actions and application failures.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	dynamodb-autoscaling-enabled	Amazon DynamoDB auto scaling uses the AWS Application Auto Scaling service to adjust provisioned throughput capacity that automatically responds to actual traffic patterns. This enables a table or a global secondary index to increase its provisioned read/write capacity to handle sudden increases in traffic, without throttling.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	dynamodb-pitr-enabled	Enable this rule to check that information has been backed up. It also maintains the backups by ensuring that point-in-time recovery is enabled in Amazon DynamoDB. The recovery maintains continuous backups of your table for the last 35 days.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	vpc-vpn-2-tunnels-up	Redundant Site-to-Site VPN tunnels can be implemented to achieve resilience requirements. It uses two tunnels to help ensure connectivity in case one of the Site-to-Site VPN connections becomes unavailable. To protect against a loss of connectivity, in case your customer gateway becomes unavailable, you can set up a second Site-to-Site VPN connection to your Amazon Virtual Private Cloud (Amazon VPC) and virtual private gateway by using a second customer gateway.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	dynamodb-throughput-limit-check	Enable this rule to ensure that provisioned throughput capacity is checked on your Amazon DynamoDB tables. This is the amount of read/write activity that each table can support. DynamoDB uses this information to reserve sufficient system resources to meet your throughput requirements. This rule generates an alert when the throughput approaches the maximum limit for a customer's account. This rule allows you to optionally set accountRCUThresholdPercentage (Config Default: 80) and accountWCUThresholdPercentage (Config Default: 80) parameters. The actual values should reflect your organization's policies.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	rds-enhanced-monitoring-enabled	Enable Amazon Relational Database Service (Amazon RDS) to help monitor Amazon RDS availability. This provides detailed visibility into the health of your Amazon RDS database instances. When the Amazon RDS storage is using more than one underlying physical device, Enhanced Monitoring collects the data for each device. Also, when the Amazon RDS database instance is running in a Multi-AZ deployment, the data for each device on the secondary host is collected, and the secondary host metrics.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	elb-cross-zone-load-balancing-enabled	Enable cross-zone load balancing for your Elastic Load Balancers (ELBs) to help maintain adequate capacity and availability. The cross-zone load balancing reduces the need to maintain equivalent numbers of instances in each enabled availability zone. It also improves your application's ability to handle the loss of one or more instances.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	rds-instance-deletion-protection-enabled	Ensure Amazon Relational Database Service (Amazon RDS) instances have deletion protection enabled. Use deletion protection to prevent your Amazon RDS instances from being accidentally or maliciously deleted, which can lead to loss of availability for your applications.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	elb-deletion-protection-enabled	This rule ensures that Elastic Load Balancing has deletion protection enabled. Use this feature to prevent your load balancer from being accidentally or maliciously deleted, which can lead to loss of availability for your applications.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	autoscaling-group-elb-healthcheck-required	The Elastic Load Balancer (ELB) health checks for Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling groups support maintenance of adequate capacity and availability. The load balancer periodically sends pings, attempts connections, or sends requests to test Amazon EC2 instances health in an auto-scaling group. If an instance is not reporting back, traffic is sent to a new Amazon EC2 instance.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	s3-bucket-replication-enabled	Amazon Simple Storage Service (Amazon S3) Cross-Region Replication (CRR) supports maintaining adequate capacity and availability. CRR enables automatic, asynchronous copying of objects across Amazon S3 buckets to help ensure that data availability is maintained.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	rds-in-backup-plan	To help with data back-up processes, ensure your Amazon Relational Database Service (Amazon RDS) instances are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	efs-in-backup-plan	To help with data back-up processes, ensure your Amazon Elastic File System (Amazon EFS) file systems are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	ebs-in-backup-plan	To help with data back-up processes, ensure your Amazon Elastic Block Store (Amazon EBS) volumes are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	dynamodb-in-backup-plan	To help with data back-up processes, ensure your Amazon DynamoDB tables are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	elasticache-redis-cluster-automatic-backup-check	When automatic backups are enabled, Amazon ElastiCache creates a backup of the cluster on a daily basis. The backup can be retained for a number of days as specified by your organization. Automatic backups can help guard against data loss. If a failure occurs, you can create a new cluster, which restores your data from the most recent backup.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	rds-multi-az-support	Multi-AZ support in Amazon Relational Database Service (Amazon RDS) provides enhanced availability and durability for database instances. When you provision a Multi-AZ database instance, Amazon RDS automatically creates a primary database instance, and synchronously replicates the data to a standby instance in a different Availability Zone. Each Availability Zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. In case of an infrastructure failure, Amazon RDS performs an automatic failover to the standby so that you can resume database operations as soon as the failover is complete.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	db-instance-backup-enabled	The backup feature of Amazon RDS creates backups of your databases and transaction logs. Amazon RDS automatically creates a storage volume snapshot of your DB instance, backing up the entire DB instance. The system allows you to set specific retention periods to meet your resilience requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	lambda-concurrency-check	This rule ensures that a Lambda function's concurrency high and low limits are established. This can assist in baselining the number of requests that your function is serving at any given time.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	aurora-resources-protected-by-backup-plan	To help with data back-up processes, ensure your Amazon Aurora resources are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	backup-plan-min-frequency-and-min-retention-check	To help with data back-up processes, ensure your AWS Backup plan is set for a minimum frequency and retention. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. This rule allows you to set the requiredFrequencyValue (Config default: 1), requiredRetentionDays (Config default: 35) and requiredFrequencyUnit (Config default: days) parameters. The actual value should reflect your organizations requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	backup-recovery-point-minimum-retention-check	To help with data back-up processes, ensure your AWS Backup recovery points have a minimum retention period set. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. This rule allows you to set the requiredRetentionDays (config default: 35) parameter. The actual value should reflect your organizations requirements.
D5.IR.Pl.B.6	The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.	ec2-resources-protected-by-backup-plan	To help with data back-up processes, ensure your Amazon Elastic Compute Cloud (Amazon EC2) resources are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements.

Template

The template is available on GitHub: Operational Best Practices for FFIEC.