Operational Best Practices for NBC TRMG - Amazon Config
AWS 文档中描述的 AWS 服务或功能可能因区域而异。要查看适用于中国区域的差异,请参阅中国的 AWS 服务入门

本文属于机器翻译版本。若本译文内容与英语原文存在差异,则一律以英文原文为准。

Operational Best Practices for NBC TRMG

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 Amazon Config rules and Amazon 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 National Bank of Cambodia’s (NBC) Technology Risk Management (TRM) Guidelines framework and Amazon Config managed rules. Each Config rule applies to a specific Amazon resource, and relates to one or more NBC TRM Guideline. An NBC TRM Guideline can be related to multiple Config rules. Refer to the table below for more detail and guidance related to these mappings.

This sample conformance pack template contains mappings to controls within the National Bank of Cambodia’s (NBC) Technology Risk Management (TRM) Guidelines framework, which can be accessed here: National Bank of Cambodia: Technology Risk Mangement Guidelines.

Amazon Web Services 区域: All supported Amazon Web Services 区域 except Middle East (Bahrain)

控制 ID Control Description Amazon Config 规则 Guidance
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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 Amazon Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based Amazon Web Services 账户 to help to incorporate the principle of least functionality.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

zapi-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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

cloudwatch-alarm-action-check

Amazon CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation 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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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 Amazon Web Services 云 environment.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

Amazon Security Hub helps to monitor unauthorized personnel, connections, devices, and software. Amazon Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple Amazon services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, Amazon Identity and Access Management (IAM) Access Analyzer, and Amazon Firewall Manager, and Amazon Partner solutions.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

cw-log group reten-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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

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.
3.1.1(d) d) Among the important controls that need to be considered are: - A systematic process of applying and authorising the creation of user IDs and the access control matrix - Conducting a risk assessment and granting access rights based on the same. - Implementation of role-based access control designed to ensure effective segregation of duties - Changing default user names and/or passwords of systems and prohibiting sharing of user IDs and passwords of generic accounts - Modification of access rights whenever there is a change in role or responsibility and removal of access rights on cessation of employment/contract - Processes to notify in a timely manner the information security function regarding user additions, deletions and role changes - Periodic reconciliation of user IDs in a system and actual users required to have access and deletion of any unnecessary IDs, if any - Auditing, logging and monitoring of access to IT assets by all users and - Considering de-activating user IDs of users of critical applications who are on prolonged leave

iam-user-unused-credentials-check

Amazon 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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

access-keys-rotated

The credentials are audited for authorized devices, users, and processes by ensuring IAM access keys are rotated as per organizational policy. Changing the access keys on a regular schedule is a security best practice. It shortens the period an access key is active and reduces the business impact if the keys are compromised. This rule requires an access key rotation value (Config Default: 90). The actual value should reflect your organization's policies.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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).
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

encrypted-volumes

Because senstive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elastic Block Store (Amazon EBS) volumes.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

rds-snapshot-encrypted

Ensure that encryption is enabled for your Amazon Relational Database Service (Amazon RDS) snapshots. Because sensitive data can exist at rest, enable encryption at rest to help protect that data.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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. KDC 维护一个包含其领域中的委托人、它们的密码及其他有关每个委托人的管理信息的数据库。
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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 Centers for Internet Security (CIS) Amazon Foundations Benchmark for password strength. This rule allows you to optionally set RequireUppercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireLowercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireSymbols (Amazon Foundational Security Best Practices value: true), RequireNumbers (Amazon Foundational Security Best Practices value: true), MinimumPasswordLength (Amazon Foundational Security Best Practices value: 14), PasswordReusePrevention (Amazon Foundational Security Best Practices value: 24), and MaxPasswordAge (Amazon Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

iam-policy-no-statements-with-admin-access

Amazon 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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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 Amazon Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based Amazon Web Services 账户 to help to incorporate the principle of least functionality.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

iam-user-mfa-enabled

Enable this rule to restrict access to resources in the Amazon Web Services 云. This rule ensures multi-factor authentication (MFA) is enabled for all IAM users. MFA 在用户名和密码之上增加了一层额外的防护。Reduce the incidents of compromised accounts by requiring MFA for IAM users.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

iam-user-no-policies-check

This rule ensures Amazon 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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

iam-user-unused-credentials-check

Amazon 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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

mfa-enabled-for-iam-console-access

Manage access to resources in the Amazon Web Services 云 by ensuring that MFA is enabled for all Amazon Identity and Access Management (IAM) users that have a console password. MFA 在用户名和密码之上增加了一层额外的防护。By requiring MFA for IAM users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

Manage access to resources in the Amazon Web Services 云 by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

Manage access to resources in the Amazon Web Services 云 by ensuring MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

iam-NON-CONPRONT

Ensure an Amazon Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. Amazon recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

zapi-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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

cw-log group reten-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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.1.1(h) h) System administrators, security officers, programmers and staff performing critical operations invariably possess the capability to inflict severe damage on the financial systems they maintain or operate by virtue of their job functions and privileged access. Personnel with elevated system access entitlements should be closely supervised with all their systems activities logged, as they have inside knowledge and the resources to circumvent systems controls and security procedures. Some of the control and security practices enumerated below need to be considered: - Implementing two-factor authentication for privileged users - Instituting strong controls over remote access by privileged users - Restricting the number of privileged users - Granting privileged access on a ‘need-to-have’ or ‘need-to-do’ basis - Maintaining audit logging of system activities performed by privileged users - Ensuring that privileged users do not have access to systems logs in which their activities are being captured - Conducting regular audit or management review of the logs - Prohibiting sharing of privileged IDs and their access codes - Disallowing vendors and contractors from gaining privileged access to systems without close supervision and monitoring and _ Protecting backup data from unauthorised access

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.
3.1.2(a) a) The BFI should install network security devices, such as firewalls, anti-virus/anti-malware software as well as intrusion detection and prevention systems, at critical junctures of its IT infrastructure, to protect the network perimeters.

Ensure Amazon 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.
3.1.2(a) a) The BFI should install network security devices, such as firewalls, anti-virus/anti-malware software as well as intrusion detection and prevention systems, at critical junctures of its IT infrastructure, to protect the network perimeters.

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 Amazon Web Services 云 environment.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Ensure network integrity is protected by ensuring X509 certificates are issued by Amazon ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (Amazon Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use Amazon Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with Amazon services and internal resources.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

启用了 alb-http 丢弃标题

Ensure that your Elastic Load Balancers (ELB) are configured to drop http headers. Because sensitive data can exist, enable encryption in transit to help protect that data.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Ensure node-to-node encryption for Amazon Elasticsearch 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

ELB-TLS-https-仅侦听器

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

zapi-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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

cloudwatch-alarm-action-check

Amazon CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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 Amazon Web Services 云 environment.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Amazon Security Hub helps to monitor unauthorized personnel, connections, devices, and software. Amazon Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple Amazon services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, Amazon Identity and Access Management (IAM) Access Analyzer, and Amazon Firewall Manager, and Amazon Partner solutions.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

dms-replication-not-public

Manage access to the Amazon Web Services 云 by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

ebs-snapshot-public-restorable-check

Manage access to the Amazon Web Services 云 by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

ec2-instance-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

elasticsearch-in-vpc-only

Manage access to the Amazon Web Services 云 by ensuring Amazon Elasticsearch Service (Amazon ES) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon ES domain within an Amazon VPC enables secure communication between Amazon ES and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

emr-master-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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 Amazon resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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 Amazon Web Services 云. Because of their logical isolation, domains that reside within anAmazon 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

internet-gateway-authorized-vpc-only

Manage access to resources in the Amazon Web Services 云 by ensuring that internet gateways are only attached to authorized Amazon Virtual Private Cloud (Amazon VPC). Internet gateways allow bi-directional internet access to and from the Amazon VPC that can potentially lead to unauthorized access to Amazon VPC resources.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Manage access to resources in the Amazon Web Services 云 by ensuring Amazon Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Deploy Amazon 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 Amazon Web Services 云. 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, Amazon Lambda functions should be assigned to a VPC.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

rds-instance-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

rds-snapshots-public-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

redshift-cluster-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

restricted-common-ports

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

s3-account-level-public-access-blocks

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

s3-bucket-public-read-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

s3-bucket-public-write-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

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 Amazon resources. Restricting all the traffic on the default security group helps in restricting remote access to your Amazon resources.
3.1.2(c) c) Controls should be implemented to ensure the security of information in networks and the protection of connected services from unauthorised access. In particular, the following items should be considered: - Responsibilities and procedures for the management of networking equipment should be established - Operational responsibility for networks should be separated from computer operations where appropriate - Special controls should be established to safeguard the confidentiality and integrity of data passing over public networks or over wireless networks and to protect the connected systems and applications (include network encryption protocols when connecting to untrusted systems/ networks. - Appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security - Management activities should be closely coordinated both to optimise the service to the organisation and to ensure that controls are consistently applied across the information processing infrastructure - Systems on the network should be authenticated and - Untrusted system connections to the network should be restricted

vpc-sg-open-only-to-authorized-ports

Manage access to resources in the Amazon Web Services 云 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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

Ensure network integrity is protected by ensuring X509 certificates are issued by Amazon ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (Amazon Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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. KDC 维护一个包含其领域中的委托人、它们的密码及其他有关每个委托人的管理信息的数据库。
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

iam-policy-no-statements-with-admin-access

Amazon 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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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 Amazon Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based Amazon Web Services 账户 to help to incorporate the principle of least functionality.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

iam-user-group-membership-check

Amazon Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring IAM 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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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 Centers for Internet Security (CIS) Amazon Foundations Benchmark for password strength. This rule allows you to optionally set RequireUppercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireLowercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireSymbols (Amazon Foundational Security Best Practices value: true), RequireNumbers (Amazon Foundational Security Best Practices value: true), MinimumPasswordLength (Amazon Foundational Security Best Practices value: 14), PasswordReusePrevention (Amazon Foundational Security Best Practices value: 24), and MaxPasswordAge (Amazon Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

iam-NON-CONPRONT

Ensure an Amazon Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. Amazon recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

iam-user-mfa-enabled

Enable this rule to restrict access to resources in the Amazon Web Services 云. This rule ensures multi-factor authentication (MFA) is enabled for all IAM users. MFA 在用户名和密码之上增加了一层额外的防护。Reduce the incidents of compromised accounts by requiring MFA for IAM users.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

mfa-enabled-for-iam-console-access

Manage access to resources in the Amazon Web Services 云 by ensuring that MFA is enabled for all Amazon Identity and Access Management (IAM) users that have a console password. MFA 在用户名和密码之上增加了一层额外的防护。By requiring MFA for IAM users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

Manage access to resources in the Amazon Web Services 云 by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

Manage access to resources in the Amazon Web Services 云 by ensuring MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use Amazon Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with Amazon services and internal resources.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

启用了 alb-http 丢弃标题

Ensure that your Elastic Load Balancers (ELB) are configured to drop http headers. Because sensitive data can exist, enable encryption in transit to help protect that data.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

Ensure node-to-node encryption for Amazon Elasticsearch 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.
3.1.2(e) e) Network services can range from simple unmanaged bandwidth to sophisticated services such as VPN, Voice over IP, VSAT, etc. Security features of network services should be: - Technology applied for security of network services, such as authentication, encryption and network connection controls - Technical parameters required for secured connection with the network services in accordance with the security and network connection rules and - Procedures for the network service usage to restrict access to network services or applications, where necessary

ELB-TLS-https-仅侦听器

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.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

Ensure network integrity is protected by ensuring X509 certificates are issued by Amazon ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (Amazon Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

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.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use Amazon Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with Amazon services and internal resources.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

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.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

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.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

启用了 alb-http 丢弃标题

Ensure that your Elastic Load Balancers (ELB) are configured to drop http headers. Because sensitive data can exist, enable encryption in transit to help protect that data.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

Ensure node-to-node encryption for Amazon Elasticsearch 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.
3.1.3(e) e) Use encryption to protect communication channels between the remote access device and the institution to restrict the risks related to network spoofing.

ELB-TLS-https-仅侦听器

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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

dms-replication-not-public

Manage access to the Amazon Web Services 云 by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

ebs-snapshot-public-restorable-check

Manage access to the Amazon Web Services 云 by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

ec2-instance-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

elasticsearch-in-vpc-only

Manage access to the Amazon Web Services 云 by ensuring Amazon Elasticsearch Service (Amazon ES) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon ES domain within an Amazon VPC enables secure communication between Amazon ES and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

emr-master-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

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 Amazon resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

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 Amazon Web Services 云. Because of their logical isolation, domains that reside within anAmazon 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

internet-gateway-authorized-vpc-only

Manage access to resources in the Amazon Web Services 云 by ensuring that internet gateways are only attached to authorized Amazon Virtual Private Cloud (Amazon VPC). Internet gateways allow bi-directional internet access to and from the Amazon VPC that can potentially lead to unauthorized access to Amazon VPC resources.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

Manage access to resources in the Amazon Web Services 云 by ensuring Amazon Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

Deploy Amazon 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 Amazon Web Services 云. 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, Amazon Lambda functions should be assigned to a VPC.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

rds-instance-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

rds-snapshots-public-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

redshift-cluster-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

restricted-common-ports

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

s3-account-level-public-access-blocks

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

s3-bucket-public-read-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

s3-bucket-public-write-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

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 Amazon resources. Restricting all the traffic on the default security group helps in restricting remote access to your Amazon resources.
3.1.3(f) f) While using TCP/IP Internet-based remote access, organisations need to establish a virtual private network over the Internet to securely communicate data packets over this public infrastructure. Further, VLANs’, network segments to restrict remote access to authorised network areas and applications within the institution.

vpc-sg-open-only-to-authorized-ports

Manage access to resources in the Amazon Web Services 云 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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

zapi-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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

cw-log group reten-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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

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.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.1.3(g) g) Maintain logs for remote access communications. Logs should include the date, time, user, user location, duration, and purpose for all remote access including all activities carried out through remote access

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.
3.1.3(i) i)Enforce two-factor authentication process for remote access (e.g., PIN based token card with a one-time random password generator, or token based PKI)

iam-user-mfa-enabled

Enable this rule to restrict access to resources in the Amazon Web Services 云. This rule ensures multi-factor authentication (MFA) is enabled for all IAM users. MFA 在用户名和密码之上增加了一层额外的防护。Reduce the incidents of compromised accounts by requiring MFA for IAM users.
3.1.3(i) i)Enforce two-factor authentication process for remote access (e.g., PIN based token card with a one-time random password generator, or token based PKI)

mfa-enabled-for-iam-console-access

Manage access to resources in the Amazon Web Services 云 by ensuring that MFA is enabled for all Amazon Identity and Access Management (IAM) users that have a console password. MFA 在用户名和密码之上增加了一层额外的防护。By requiring MFA for IAM users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
3.1.3(i) i)Enforce two-factor authentication process for remote access (e.g., PIN based token card with a one-time random password generator, or token based PKI)

Manage access to resources in the Amazon Web Services 云 by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.3(i) i)Enforce two-factor authentication process for remote access (e.g., PIN based token card with a one-time random password generator, or token based PKI)

Manage access to resources in the Amazon Web Services 云 by ensuring MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
3.1.4(c)(e) c) The patch management process should include aspects like: - Determining methods of obtaining and validating patches for ensuring that the patch is from an authorised source - Identifying vulnerabilities that are applicable to applications and systems used by the organisation - Assessing the business impact of implementing patches (or not implementing a particular patch) - Ensuring patches are tested - Describing methods for deploying patches, e.g. automatically - Reporting on the status of patch deployment across the organisation and - Including methods for dealing with the failed deployment of a patch (e.g., redeployment of the patch). e) BFIs should deploy automated patch management tools and software update tools for all systems for which such tools are available and safe

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 Amazon Secrets Manager. Use Amazon Secrets 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.
3.1.4(c)(e) c) The patch management process should include aspects like: - Determining methods of obtaining and validating patches for ensuring that the patch is from an authorised source - Identifying vulnerabilities that are applicable to applications and systems used by the organisation - Assessing the business impact of implementing patches (or not implementing a particular patch) - Ensuring patches are tested - Describing methods for deploying patches, e.g. automatically - Reporting on the status of patch deployment across the organisation and - Including methods for dealing with the failed deployment of a patch (e.g., redeployment of the patch). e) BFIs should deploy automated patch management tools and software update tools for all systems for which such tools are available and safe

ec2-managedinstance-association-compliance-status-check

Use Amazon Secrets Manager Associations to help with inventory of software platforms and applications within an organization. Amazon Secrets 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.
3.1.4(c)(e) c) The patch management process should include aspects like: - Determining methods of obtaining and validating patches for ensuring that the patch is from an authorised source - Identifying vulnerabilities that are applicable to applications and systems used by the organisation - Assessing the business impact of implementing patches (or not implementing a particular patch) - Ensuring patches are tested - Describing methods for deploying patches, e.g. automatically - Reporting on the status of patch deployment across the organisation and - Including methods for dealing with the failed deployment of a patch (e.g., redeployment of the patch). e) BFIs should deploy automated patch management tools and software update tools for all systems for which such tools are available and safe

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 Amazon Secrets Manager as required by your organization’s policies and procedures.
3.1.5(d)(e) d) Appropriate key management requires secure processes for generating, storing, archiving, retrieving, distributing, retiring and destroying cryptographic keys e) All cryptographic keys should be protected against modification and loss. In addition, secret and private keys need protection against unauthorised use as well as disclosure. Equipment used to generate, store and archive keys should be physically protected

kms-cmk-not-scheduled-for-deletion

To help protect data at rest, ensure necessary customer master keys (CMKs) are not scheduled for deletion in Amazon Key Management Service (Amazon KMS). Because key deletion is necessary at times, this rule can assist in checking for all keys scheduled for deletion, in case a key was scheduled unintentionally.
3.1.5(d)(e) d) Appropriate key management requires secure processes for generating, storing, archiving, retrieving, distributing, retiring and destroying cryptographic keys e) All cryptographic keys should be protected against modification and loss. In addition, secret and private keys need protection against unauthorised use as well as disclosure. Equipment used to generate, store and archive keys should be physically protected

cmk-backing-key-rotation-enabled

Enable key rotation to ensure that keys are rotated once they have reached the end of their crypto period.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

kms-cmk-not-scheduled-for-deletion

To help protect data at rest, ensure necessary customer master keys (CMKs) are not scheduled for deletion in Amazon Key Management Service (Amazon KMS). Because key deletion is necessary at times, this rule can assist in checking for all keys scheduled for deletion, in case a key was scheduled unintentionally.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

cmk-backing-key-rotation-enabled

Enable key rotation to ensure that keys are rotated once they have reached the end of their crypto period.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

Ensure network integrity is protected by ensuring X509 certificates are issued by Amazon ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (Amazon Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use Amazon Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with Amazon services and internal resources.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.1.5(f) f) A key management system should be based on an agreed set of standards, procedures and secure methods for: - generating keys for different cryptographic systems and different applications - issuing and obtaining public key certificates - distributing keys to intended entities, including how keys should be activated when received - storing keys, including how authorised users obtain access to keys - changing or updating keys including rules on when keys should be changed and how this will be done - dealing with compromised keys - revoking keys including how keys should be withdrawn or deactivated, e.g. when keys have been compromised or when a user leaves an organisation (in which case keys should also be archived) - recovering keys that are lost or corrupted - backing up or archiving keys - destroying keys, and - logging and auditing of key management related activities.

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.1.6(a) a) The BFI should deploy a combination of automated tools and manual techniques to perform a comprehensive VA on a periodic basis. For web-based external facing systems, the scope of VA should include common web vulnerabilities such as SQL injection and cross-site scripting.

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 Amazon Web Services 云 environment.
3.1.6(a) a) The BFI should deploy a combination of automated tools and manual techniques to perform a comprehensive VA on a periodic basis. For web-based external facing systems, the scope of VA should include common web vulnerabilities such as SQL injection and cross-site scripting.

Ensure Amazon 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.
3.1.6(f) f) The security function should provide status updates regarding the number of unmitigated, critical vulnerabilities, for each department/division, and plan for mitigating to senior management on a periodic basis

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.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

cloud-trail-encryption-enabled

Because sensitive data may exist and to help protect data at rest, ensure encryption is enabled for your Amazon CloudTrail trails.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

To help protect sensitive data at rest, ensure encryption is enabled for your Amazon CloudWatch Log Groups.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

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).
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elasticsearch Service (Amazon ES) domains.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

encrypted-volumes

Because senstive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elastic Block Store (Amazon EBS) volumes.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

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.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

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.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

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.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

To help protect data at rest, ensure encryption with Amazon Key Management Service (Amazon KMS) is enabled for your SageMaker endpoint. Because sensitive data can exist at rest in SageMaker endpoint, enable encryption at rest to help protect that data.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

To help protect data at rest, ensure encryption with Amazon Key Management Service (Amazon KMS) is enabled for your SageMaker notebook. Because sensitive data can exist at rest in SageMaker notebook, enable encryption at rest to help protect that data.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

sns-encrypted-kms

To help protect data at rest, ensure that your Amazon Simple Notification Service (Amazon SNS) topics require encryption using Amazon Key Management Service (Amazon KMS). Because sensitive data can exist at rest in published messages, enable encryption at rest to help protect that data.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

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.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

rds-snapshot-encrypted

Ensure that encryption is enabled for your Amazon Relational Database Service (Amazon RDS) snapshots. Because sensitive data can exist at rest, enable encryption at rest to help protect that data.
3.1.10(b) b) Sensitive information such as system documentation, application source code, and production transaction data should have more extensive controls to guard against alteration (e.g., integrity checkers, cryptographic hashes). Furthermore, policies should minimise the distribution of sensitive information, including printouts that contain the information.

s3-default-encryption-kms

To help protect data at rest, ensure that encryption is enabled for your S3 buckets. Because sensitive data can exist at rest in an Amazon S3 bucket, enable encryption at rest to help protect that data. For more information about the encryption process and administration, use the Amazon Key Management Service (Amazon KMS) customer-managed CMKs.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

ebs-optimized-instance

An optimized instance in Amazon Elastic Block Store (Amazon EBS) provides additional, dedicated capacity for Amazon EBS I/O operations. This optimization provides the most efficient performance for your EBS volumes by minimizing contention between Amazon EBS I/O operations and other traffic from your instance.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

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. 自动备份可以帮助防止数据丢失。If a failure occurs, you can create a new cluster, which restores your data from the most recent backup.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

备份中的动态计划

To help with data back-up processes, ensure your Amazon DynamoDB tables are a part of an Amazon Backup plan. Amazon 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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

备份计划

To help with data back-up processes, ensure your Amazon Elastic Block Store (Amazon EBS) volumes are a part of an Amazon Backup plan. Amazon 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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

EFS 进入备份计划

To help with data back-up processes, ensure your Amazon Elastic File System (Amazon EFS) file systems are a part of an Amazon Backup plan. Amazon 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.
3.2.1(h) h) To minimise risks associated with changes, BFIs should perform backups of affected systems or applications prior to the change. BFIs should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment.

备份计划中的 RDS

To help with data back-up processes, ensure your Amazon Relational Database Service (Amazon RDS) instances are a part of an Amazon Backup plan. Amazon 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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

zapi-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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

cw-log group reten-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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

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.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.2.1(k) k) Audit and security logs are useful information which facilitates investigations and trouble shooting. The BFI should ensure that the logging facility is enabled to record activities that are performed during the migration process.

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.
3.3.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

ebs-optimized-instance

An optimized instance in Amazon Elastic Block Store (Amazon EBS) provides additional, dedicated capacity for Amazon EBS I/O operations. This optimization provides the most efficient performance for your EBS volumes by minimizing contention between Amazon EBS I/O operations and other traffic from your instance.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

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. 自动备份可以帮助防止数据丢失。If a failure occurs, you can create a new cluster, which restores your data from the most recent backup.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

备份中的动态计划

To help with data back-up processes, ensure your Amazon DynamoDB tables are a part of an Amazon Backup plan. Amazon 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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

备份计划

To help with data back-up processes, ensure your Amazon Elastic Block Store (Amazon EBS) volumes are a part of an Amazon Backup plan. Amazon 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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

EFS 进入备份计划

To help with data back-up processes, ensure your Amazon Elastic File System (Amazon EFS) file systems are a part of an Amazon Backup plan. Amazon 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.
3.2.2(a) a) The key aspects that are required to be considered include: - Completeness— ensuring that the total number of records from the source database is transferred to the new database (assuming the number of fields is the same). - Availability of data backup— ensuring that data is backed up before migration for future reference or any emergency that might arise out of the data migration process. - Integrity of data— ensuring that the data is not altered manually or electronically during the migration process. If such a need exists, having a documented plan to validate pre and post values for the changed data set should exist. - Consistency of data— the field/record called for from the new application should be consistent with that of the original application and - Continuity—the new application should be able to continue with newer records (or appendage) and help in ensuring seamless business continuity

备份计划中的 RDS

To help with data back-up processes, ensure your Amazon Relational Database Service (Amazon RDS) instances are a part of an Amazon Backup plan. Amazon 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.
3.2.2(a) a) Develop and implement processes for preventing, detecting, analysing and responding to information security incidents.

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 Amazon Web Services 云 environment.
3.2.2(a) a) Develop and implement processes for preventing, detecting, analysing and responding to information security incidents.

Amazon Security Hub helps to monitor unauthorized personnel, connections, devices, and software. Amazon Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple Amazon services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, Amazon Identity and Access Management (IAM) Access Analyzer, and Amazon Firewall Manager, and Amazon Partner solutions.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

dynamodb-autoscaling-enabled

Amazon DynamoDB auto scaling uses the Amazon 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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

ebs-optimized-instance

An optimized instance in Amazon Elastic Block Store (Amazon EBS) provides additional, dedicated capacity for Amazon EBS I/O operations. This optimization provides the most efficient performance for your EBS volumes by minimizing contention between Amazon EBS I/O operations and other traffic from your instance.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

支持 ELB 跨区域负载平衡

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

rds-实例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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(a) a) Consider important factors associated with maintaining high system availability, adequate capacity, reliable performance, fast response time, scalability as part of the system design.

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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

备份中的动态计划

To help with data back-up processes, ensure your Amazon DynamoDB tables are a part of an Amazon Backup plan. Amazon 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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

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. 自动备份可以帮助防止数据丢失。If a failure occurs, you can create a new cluster, which restores your data from the most recent backup.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

备份计划

To help with data back-up processes, ensure your Amazon Elastic Block Store (Amazon EBS) volumes are a part of an Amazon Backup plan. Amazon 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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

EFS 进入备份计划

To help with data back-up processes, ensure your Amazon Elastic File System (Amazon EFS) file systems are a part of an Amazon Backup plan. Amazon 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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

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.
3.3.1(f) f) Install appropriate mechanisms to backup data to meet the RTO- Recovery Time Objective and RPO- Recovery Point Objective requirements as identified through the risk assessment process.

备份计划中的 RDS

To help with data back-up processes, ensure your Amazon Relational Database Service (Amazon RDS) instances are a part of an Amazon Backup plan. Amazon 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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

zapi-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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

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.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.4(a)(b)(c)(f)(j) a) Ensure that records of user access are uniquely identified and logged for audit and review purposes. b) Have accountability and identification of unauthorised access is documented. c) Enable audit logging of system activities performed by privileged users. f) Ensure appropriate logging and monitoring should be applied to enable recording and detection of actions that may affect, or are relevant to, information security. j) Ensure event logging sets the foundation for automated monitoring systems which are capable of generating consolidated reports and alerts on system security.

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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

cloudtrail-enabled

Amazon CloudTrail can help in non-repudiation by recording Amazon Web Services Management Console actions and API calls. You can identify the users and Amazon Web Services 账户 that called an Amazon service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within Amazon CloudTrail Record Contents.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

cloudtrail-s3-dataevents-enabled

The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include Amazon Web Services 账户 information that accessed an Amazon S3 bucket, IP address, and time of event.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

zapi-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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

cloud-trail-cloud-watch-logs-enabled

Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of Amazon CloudTrail data provides details of API call activity within your Amazon Web Services 账户.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

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. 每个日志都包含信息 (例如,收到请求的时间、客户端的 IP 地址、延迟、请求路径和服务器响应)。
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

启用多区域云跟踪

Amazon CloudTrail records Amazon Web Services Management Console actions and API calls. You can identify which users and accounts called Amazon, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all Amazon Web Services 区域 to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when Amazon 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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

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.
3.4(g) g) Ensure event logs include, when relevant: - User IDs - System activities - Dates, time and details of key events, e.g. log-on and log-off - Device identity or location if possible and system identifier - Records of successful and rejected system access attempts - Records of successful and rejected data and other resource access attempts - Changes to system configuration - Use of privileges - Use of system utilities and applications - Files accessed and the kind of access - Network addresses and protocols - Alarms raised by the access control system and - Records of transactions executed by users in applications and online customer transaction

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.6.1(a)(h) a) BFIs need to ensure suitable security measures for their web applications and take reasonable mitigating measures against various web security risks. h) BFIs need to ensure suitable security measures for their web applications and take reasonable mitigating measures against various web security risks

Ensure Amazon 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.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

Ensure network integrity is protected by ensuring X509 certificates are issued by Amazon ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (Amazon Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

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.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

Because sensitive data can exist and to help protect data at transit, ensure encryption is enabled for your Elastic Load Balancing. Use Amazon Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with Amazon services and internal resources.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

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.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

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.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

启用了 alb-http 丢弃标题

Ensure that your Elastic Load Balancers (ELB) are configured to drop http headers. Because sensitive data can exist, enable encryption in transit to help protect that data.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

Ensure node-to-node encryption for Amazon Elasticsearch 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.
3.6.1(b) b) BFIs need to evaluate security requirements associated with their internet banking systems and other relevant systems and adopt an encryption solution considering the degree of confidentiality and integrity required.

ELB-TLS-https-仅侦听器

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.
3.6.1(d) d) BFIs providing internet banking should be responsive to unusual network traffic conditions/system performance and sudden surge in system resource utilisation which could be an indication of a DDoS attack. Consequently, the success of any pre-emptive and reactive actions depends on the deployment of appropriate tools to effectively detect, monitor and analyse anomalies in networks and systems.

Ensure Amazon 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.
3.6.1(d) d) BFIs providing internet banking should be responsive to unusual network traffic conditions/system performance and sudden surge in system resource utilisation which could be an indication of a DDoS attack. Consequently, the success of any pre-emptive and reactive actions depends on the deployment of appropriate tools to effectively detect, monitor and analyse anomalies in networks and systems.

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 Amazon Web Services 云 environment.
3.6.1(d) d) BFIs providing internet banking should be responsive to unusual network traffic conditions/system performance and sudden surge in system resource utilisation which could be an indication of a DDoS attack. Consequently, the success of any pre-emptive and reactive actions depends on the deployment of appropriate tools to effectively detect, monitor and analyse anomalies in networks and systems.

Amazon Security Hub helps to monitor unauthorized personnel, connections, devices, and software. Amazon Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple Amazon services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, Amazon Identity and Access Management (IAM) Access Analyzer, and Amazon Firewall Manager, and Amazon Partner solutions.
3.6.1(d) d) BFIs providing internet banking should be responsive to unusual network traffic conditions/system performance and sudden surge in system resource utilisation which could be an indication of a DDoS attack. Consequently, the success of any pre-emptive and reactive actions depends on the deployment of appropriate tools to effectively detect, monitor and analyse anomalies in networks and systems.

To help with logging and monitoring within your environment, enable Amazon WAF (V2) logging on regional and global web ACLs. Amazon WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that Amazon WAF received the request from your Amazon resource, information about the request, and an action for the rule that each request matched.
3.6.1(e) e) BFIs need to regularly assess information security vulnerabilities and evaluate the effectiveness of the existing IT security risk management framework, making any necessary adjustments to ensure emerging vulnerabilities are addressed in a timely manner. This assessment should also be conducted as part of any material change.

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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

dms-replication-not-public

Manage access to the Amazon Web Services 云 by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

ebs-snapshot-public-restorable-check

Manage access to the Amazon Web Services 云 by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

ec2-instance-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

elasticsearch-in-vpc-only

Manage access to the Amazon Web Services 云 by ensuring Amazon Elasticsearch Service (Amazon ES) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon ES domain within an Amazon VPC enables secure communication between Amazon ES and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

emr-master-no-public-ip

Manage access to the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

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 Amazon resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

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 Amazon Web Services 云. Because of their logical isolation, domains that reside within anAmazon 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

internet-gateway-authorized-vpc-only

Manage access to resources in the Amazon Web Services 云 by ensuring that internet gateways are only attached to authorized Amazon Virtual Private Cloud (Amazon VPC). Internet gateways allow bi-directional internet access to and from the Amazon VPC that can potentially lead to unauthorized access to Amazon VPC resources.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

Manage access to resources in the Amazon Web Services 云 by ensuring Amazon Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

Deploy Amazon 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 Amazon Web Services 云. 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, Amazon Lambda functions should be assigned to a VPC.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

rds-instance-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

rds-snapshots-public-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

redshift-cluster-public-access-check

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

restricted-common-ports

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

s3-account-level-public-access-blocks

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

s3-bucket-public-read-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

s3-bucket-public-write-prohibited

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

Manage access to resources in the Amazon Web Services 云 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.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

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 Amazon resources. Restricting all the traffic on the default security group helps in restricting remote access to your Amazon resources.
3.6.4(a)(b) a) Restrict internet access and segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities.

vpc-sg-open-only-to-authorized-ports

Manage access to resources in the Amazon Web Services 云 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.

Template

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