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 AWS Config rules and AWS Config remediation actions. Conformance Packs, as sample templates, are not designed to fully ensure compliance with a specific governance or compliance standard. You are responsible for making your own assessment of whether your use of the Services meets applicable legal and regulatory requirements.
The following provides a sample mapping between the National Bank of Cambodia’s (NBC) Technology Risk Management (TRM) Guidelines framework and AWS managed Config rules. Each Config rule applies to a specific AWS 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
| Control ID | Control Description | AWS Config Rule | 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 | Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their AWS Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based AWS accounts to help to incorporate the principle of least functionality. | |
| 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 | 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 | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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 | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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 | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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 CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation periods. The alarm performs one or more actions based on the value of the metric or expression relative to a threshold over a number of time periods. This rule requires a value for alarmActionRequired (Config Default: True), insufficientDataActionRequired (Config Default: True), okActionRequired (Config Default: False). The actual value should reflect the alarm actions for your environment. | |
| 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 | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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 AWS Cloud 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 | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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 | AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions. | |
| 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 | 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 | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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 | AWS Identity and Access Management (IAM) can help you with access permissions and authorizations by checking for IAM passwords and access keys that are not used for a specified time period. If these unused credentials are identified, you should disable and/or remove the credentials, as this may violate the principle of least privilege. This rule requires you to set a value to the maxCredentialUsageAge (Config Default: 90). The actual value should reflect your organization's policies. | |
| 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 | Centralized management of AWS accounts within AWS Organizations helps to ensure that accounts are compliant. The lack of centralized account governance may lead to inconsistent account configurations, which may expose resources and sensitive data. | |
| 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing blocked actions on all AWS Key Management Service keys. Having more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies | |
| 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege. | |
| 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 | Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to allow blocked actions on all AWS Key Management Service keys. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning, rolling back, and delegating permissions management. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies. | |
| 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 | AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. | |
| 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 | EC2 instance profiles pass an IAM role to an EC2 instance. Attaching an instance profile to your instances can assist with least privilege and permissions management. | |
| 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 | Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. | |
| 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 | If a task definition has elevated privileges it is because the customer has specifically opted-in to those configurations. This control checks for unexpected privilege escalation when a task definition has host networking enabled but the customer has not opted-in to elevated privileges. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | Ensure audit logging is enabled on your Amazon OpenSearch Service domains. Audit logging allows you to track user activity on your OpenSearch domains, including authentication successes and failures, requests to OpenSearch, index changes, and incoming search queries. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | To capture information about connections and user activities on your Amazon Redshift cluster, ensure audit logging is enabled. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | 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(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 3.1.1(f) | f) For accountability purpose, ensure that users and IT assets are uniquely identified and their actions are auditable. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | 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 | The access permissions and authorizations can be managed and incorporated with the principles of least privilege and separation of duties, by enabling Kerberos for Amazon EMR clusters. In Kerberos, the services and the users that need to authenticate are known as principals. The principals exist within a Kerberos realm. Within the realm, a Kerberos server is known as the key distribution center (KDC). It provides a means for the principals to authenticate. The KDC authenticates by issuing tickets for authentication. The KDC maintains a database of the principals within its realm, their passwords, and other administrative information about each principal. | |
| 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 | The identities and the credentials are issued, managed, and verified based on an organizational IAM password policy. They meet or exceed requirements as stated by NIST SP 800-63 and the AWS Foundational Security Best Practices standard for password strength. This rule allows you to optionally set RequireUppercaseCharacters (AWS Foundational Security Best Practices value: true), RequireLowercaseCharacters (AWS Foundational Security Best Practices value: true), RequireSymbols (AWS Foundational Security Best Practices value: true), RequireNumbers (AWS Foundational Security Best Practices value: true), MinimumPasswordLength (AWS Foundational Security Best Practices value: 14), PasswordReusePrevention (AWS Foundational Security Best Practices value: 24), and MaxPasswordAge (AWS Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies. | |
| 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. | |
| 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 to systems and assets can be controlled by checking that the root user does not have access keys attached to their AWS Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based AWS accounts to help to incorporate the principle of least functionality. | |
| 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 | Enable this rule to restrict access to resources in the AWS Cloud. This rule ensures multi-factor authentication (MFA) is enabled for all users. MFA adds an extra layer of protection on top of sign-in credentials. Reduce the incidents of compromised accounts by requiring MFA for users. | |
| 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 | This rule ensures AWS Identity and Access Management (IAM) policies are attached only to groups or roles to control access to systems and assets. Assigning privileges at the group or the role level helps to reduce opportunity for an identity to receive or retain excessive privileges. | |
| 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 | AWS Identity and Access Management (IAM) can help you with access permissions and authorizations by checking for IAM passwords and access keys that are not used for a specified time period. If these unused credentials are identified, you should disable and/or remove the credentials, as this may violate the principle of least privilege. This rule requires you to set a value to the maxCredentialUsageAge (Config Default: 90). The actual value should reflect your organization's policies. | |
| 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 AWS Cloud by ensuring that MFA is enabled for all AWS Identity and Access Management (IAM) users that have a console password. MFA adds an extra layer of protection on top of sign-in credentials. By requiring MFA for users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users. | |
| 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 AWS Cloud by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts. | |
| 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 AWS Cloud by ensuring MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts. | |
| 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 | Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management. | |
| 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 | 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 | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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 | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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 | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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 | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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 | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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 | 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 | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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(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 | Centralized management of AWS accounts within AWS Organizations helps to ensure that accounts are compliant. The lack of centralized account governance may lead to inconsistent account configurations, which may expose resources and sensitive 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing blocked actions on all AWS Key Management Service keys. Having more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies | |
| 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one user. Placing users in groups based on their associated permissions or job function is one way to incorporate least privilege. | |
| 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 | Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to allow blocked actions on all AWS Key Management Service keys. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning, rolling back, and delegating permissions management. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies. | |
| 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 | AWS Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. | |
| 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 instance profiles pass an IAM role to an EC2 instance. Attaching an instance profile to your instances can assist with least privilege and permissions management. | |
| 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 | Ensure IAM Actions are restricted to only those actions that are needed. Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. | |
| 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 | If a task definition has elevated privileges it is because the customer has specifically opted-in to those configurations. This control checks for unexpected privilege escalation when a task definition has host networking enabled but the customer has not opted-in to elevated privileges. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | 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 | 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 | 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 | 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.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 AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment. | |
| 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 AWS Cloud 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. | AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks | |
| 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 AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies. | |
| 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 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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 | 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 | 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 | 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 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 | 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 | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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 | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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 | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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 CloudWatch alarms alert when a metric breaches the threshold for a specified number of evaluation periods. The alarm performs one or more actions based on the value of the metric or expression relative to a threshold over a number of time periods. This rule requires a value for alarmActionRequired (Config Default: True), insufficientDataActionRequired (Config Default: True), okActionRequired (Config Default: False). The actual value should reflect the alarm actions for your environment. | |
| 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 | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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 AWS Cloud 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 | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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 | AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions. | |
| 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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 | Manage access to the AWS Cloud by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts. | |
| 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 the AWS Cloud by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts. | |
| 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 the AWS Cloud by ensuring Amazon Elastic Compute Cloud (Amazon EC2) instances cannot be publicly accessed. Amazon EC2 instances can contain sensitive information and access control is required for such accounts. | |
| 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 the AWS Cloud by ensuring Amazon OpenSearch Service (OpenSearch Service) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An OpenSearch Service domain within an Amazon VPC enables secure communication between OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection. | |
| 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 the AWS Cloud by ensuring Amazon OpenSearch Service domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon OpenSearch Service domain within an Amazon VPC enables secure communication between Amazon OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection. | |
| 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 the AWS Cloud by ensuring Amazon EMR cluster master nodes cannot be publicly accessed. Amazon EMR cluster master nodes can contain sensitive information and access control is required for such accounts. | |
| 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 Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access. | |
| 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 Elastic Compute Cloud (Amazon EC2) instances within an Amazon Virtual Private Cloud (Amazon VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection. All traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. Assign Amazon EC2 instances to an Amazon VPC to properly manage access. | |
| 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 AWS Cloud 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 AWS Cloud by ensuring AWS 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 AWS Lambda functions within an Amazon Virtual Private Cloud (Amazon VPC) for a secure communication between a function and other services within the Amazon VPC. With this configuration, there is no requirement for an internet gateway, NAT device, or VPN connection. All the traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. To properly manage access, AWS Lambda functions should be assigned to a VPC. | |
| 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 AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information, and principles and access control is required for such accounts. | |
| 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 AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information and principles and access control is required for such accounts. | |
| 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 AWS Cloud by ensuring that Amazon Redshift clusters are not public. Amazon Redshift clusters can contain sensitive information and principles and access control is required for such accounts. | |
| 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 AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies. | |
| 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 AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data. | |
| 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 AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data. | |
| 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 AWS Cloud by ensuring that Amazon SageMaker notebooks do not allow direct internet access. By preventing direct internet access, you can keep sensitive data from being accessed by unauthorized users. | |
| 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 Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources. | |
| 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 AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems. | |
| 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 Amazon EC2 route tables do not have unrestricted routes to an internet gateway. Removing or limiting the access to the internet for workloads within Amazon VPCs can reduce unintended access within your environment. | |
| 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 AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access at the bucket level. | |
| 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 the AWS Cloud by ensuring Amazon Virtual Private Cloud (VPC) subnets are not automatically assigned a public IP address. Amazon Elastic Compute Cloud (EC2) instances that are launched into subnets that have this attribute enabled have a public IP address assigned to their primary network interface. | |
| 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 | If you configure your Network Interfaces with a public IP address, then the associated resources to those Network Interfaces are reachable from the internet. EC2 resources should not be publicly accessible, as this may allow unintended access to your applications or servers. | |
| 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 | Enhanced VPC routing forces all COPY and UNLOAD traffic between the cluster and data repositories to go through your Amazon VPC. You can then use VPC features such as security groups and network access control lists to secure network traffic. You can also use VPC flow logs to monitor network traffic. | |
| 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 Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access. This rule allows you to optionally set the ignorePublicAcls (Config Default: True), blockPublicPolicy (Config Default: True), blockPublicAcls (Config Default: True), and restrictPublicBuckets parameters (Config Default: True). The actual values should reflect your organization's policies. | |
| 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 AWS Systems Manager (SSM) documents are not public, as this may allow unintended access to your SSM documents. A public SSM document can expose information about your account, resources and internal processes. | |
| 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 AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies. | |
| 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 | 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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 | 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 | 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 | 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 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(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 Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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. | Ensure network integrity is protected by ensuring X509 certificates are issued by AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies. | |
| 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. | 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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. | 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. | 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. | 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 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 Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS services and internal resources. | |
| 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 | 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 | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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 | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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 | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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 | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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 | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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 | 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 | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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(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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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) | Enable this rule to restrict access to resources in the AWS Cloud. This rule ensures multi-factor authentication (MFA) is enabled for all users. MFA adds an extra layer of protection on top of sign-in credentials. Reduce the incidents of compromised accounts by requiring MFA for users. | |
| 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 AWS Cloud by ensuring that MFA is enabled for all AWS Identity and Access Management (IAM) users that have a console password. MFA adds an extra layer of protection on top of sign-in credentials. By requiring MFA for users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users. | |
| 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 AWS Cloud by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts. | |
| 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 AWS Cloud by ensuring MFA is enabled for the root user. The root user is the most privileged user in an AWS account. The MFA adds an extra layer of protection for sign-in credentials. By requiring MFA for the root user, you can reduce the incidents of compromised AWS accounts. | |
| 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 | An inventory of the software platforms and applications within the organization is possible by managing Amazon Elastic Compute Cloud (Amazon EC2) instances with AWS Systems Manager. Use AWS Systems Manager to provide detailed system configurations, operating system patch levels, services name and type, software installations, application name, publisher and version, and other details about your environment. | |
| 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 | Use AWS Systems Manager Associations to help with inventory of software platforms and applications within an organization. AWS Systems Manager assigns a configuration state to your managed instances and allows you to set baselines of operating system patch levels, software installations, application configurations, and other details about your environment. | |
| 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 | Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in AWS Systems Manager as required by your organization's policies and procedures. | |
| 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 | This rule ensures that Amazon Redshift clusters have the preferred settings for your organization. Specifically, that they have preferred maintenance windows and automated snapshot retention periods for the database. This rule requires you to set the allowVersionUpgrade. The default is true. It also lets you optionally set the preferredMaintenanceWindow (the default is sat:16:00-sat:16:30), and the automatedSnapshotRetentionPeriod (the default is 1). The actual values should reflect your organization's policies. | |
| 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 | Enabling managed platform updates for an Amazon Elastic Beanstalk environment ensures that the latest available platform fixes, updates, and features for the environment are installed. Keeping up to date with patch installation is a best practice in securing systems. | |
| 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 | Enable automatic minor version upgrades on your Amazon Relational Database Service (RDS) instances to ensure the latest minor version updates to the Relational Database Management System (RDBMS) are installed, which may include security patches and bug fixes. | |
| 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 | To help protect data at rest, ensure necessary customer master keys (CMKs) are not scheduled for deletion in AWS Key Management Service (AWS 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 | Enable key rotation to ensure that keys are rotated once they have reached the end of their crypto period. | |
| 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 | AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing blocked actions on all AWS Key Management Service keys. Having more privileges than needed to complete a task may violate the principle of least privilege and separation of duties. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies | |
| 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 | Ensure an AWS Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to allow blocked actions on all AWS Key Management Service keys. AWS recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning, rolling back, and delegating permissions management. This rule allows you to set the blockedActionsPatterns parameter. (AWS Foundational Security Best Practices value: kms:Decrypt, kms:ReEncryptFrom). The actual values should reflect your organization's policies. | |
| 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. | To help protect data at rest, ensure necessary customer master keys (CMKs) are not scheduled for deletion in AWS Key Management Service (AWS 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. | 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 AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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. | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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. | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS services and internal resources. | |
| 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 AWS Cloud 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 AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment. | |
| 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. | AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks | |
| 3.1.6(c) | c) The BFI should establish a process to remediate the issues identified in VA & PT and perform subsequent revalidation of the remediation to validate that gaps are fully addressed. | vuln-mitigated-accepted(Process Check) | Ensure newly identified vulnerabilities are remediated or documented as accepted risks. Vulnerabilities should be remediated or accepted as risks according to your organizations compliance requirements. |
| 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.8 | User training and awareness | security-awareness-program-exists(Process Check) | Establish and maintain a security awareness program for your organization. Security awareness programs educate employees on how to protect their organization from various security breaches or incidents. |
| 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 may exist and to help protect data at rest, ensure encryption is enabled for your AWS 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. | Utilize AWS CloudTrail log file validation to check the integrity of CloudTrail logs. Log file validation helps determine if a log file was modified or deleted or unchanged after CloudTrail delivered it. This feature is built using industry standard algorithms: SHA-256 for hashing and SHA-256 with RSA for digital signing. This makes it computationally infeasible to modify, delete or forge CloudTrail log files without detection. | |
| 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 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 OpenSearch Service (OpenSearch Service) 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. | Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon OpenSearch Service 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. | Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your Amazon Elastic Block Store (Amazon EBS) volumes. | |
| 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 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. | 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. | 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 AWS Key Management Service (AWS 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 AWS Key Management Service (AWS 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. | To help protect data at rest, ensure that your Amazon Simple Notification Service (Amazon SNS) topics require encryption using AWS Key Management Service (AWS 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. | 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. | 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. | Ensure that encryption is enabled for your Amazon Simple Storage Service (Amazon S3) buckets. Because sensitive data can exist at rest in an Amazon S3 bucket, enable encryption at rest to help protect that data. | |
| 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 is enabled for your API Gateway stage's cache. Because sensitive data can be captured for the API method, 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. | Ensure that encryption is enabled for your Amazon DynamoDB tables. Because sensitive data can exist at rest in these tables, enable encryption at rest to help protect that data. By default, DynamoDB tables are encrypted with an AWS owned customer master key (CMK). | |
| 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 AWS Key Management Service (AWS KMS) is enabled for your Amazon Redshift cluster. Because sensitive data can exist at rest in Redshift clusters, enable encryption at rest to help protect that data. | |
| 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 AWS Key Management Service (AWS KMS) is enabled for AWS Secrets Manager secrets. Because sensitive data can exist at rest in Secrets Manager secrets, enable encryption at rest to help protect that data. | |
| 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. | 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. | 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. | 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. | When automatic backups are enabled, Amazon ElastiCache creates a backup of the cluster on a daily basis. The backup can be retained for a number of days as specified by your organization. Automatic backups can help guard against data loss. If a failure occurs, you can create a new cluster, which restores your data from the most recent backup. | |
| 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. | 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. | 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 AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. | |
| 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 AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. | |
| 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 File System (Amazon EFS) file systems are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. | |
| 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 Relational Database Service (Amazon RDS) instances are a part of an AWS Backup plan. AWS Backup is a fully managed backup service with a policy-based backup solution. This solution simplifies your backup management and enables you to meet your business and regulatory backup compliance requirements. | |
| 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 Redshift clusters have automated snapshots. When automated snapshots are enabled for a cluster, Redshift periodically takes snapshots of that cluster. By default, Redshift takes a snapshot every eight hours or every 5 GB per node of data changes, or whichever comes first. | |
| 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. | 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. | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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. | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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. | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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. | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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. | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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. | 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. | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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.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. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 3.2.3(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 AWS Cloud environment. | |
| 3.2.3(a) | a) Develop and implement processes for preventing, detecting, analysing and responding to information security incidents. | AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions. | |
| 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. | Amazon DynamoDB auto scaling uses the AWS Application Auto Scaling service to adjust provisioned throughput capacity that automatically responds to actual traffic patterns. This enables a table or a global secondary index to increase its provisioned read/write capacity to handle sudden increases in traffic, without throttling. | |
| 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. | 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(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. | 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. | 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. | 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. | 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(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. | 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(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. | 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. | 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. | 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. | 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.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. | 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. | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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. | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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. | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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. | Utilize AWS CloudTrail log file validation to check the integrity of CloudTrail logs. Log file validation helps determine if a log file was modified or deleted or unchanged after CloudTrail delivered it. This feature is built using industry standard algorithms: SHA-256 for hashing and SHA-256 with RSA for digital signing. This makes it computationally infeasible to modify, delete or forge CloudTrail log files without detection. | |
| 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. | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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. | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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. | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 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(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. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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. | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 3.4(f) | 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. | AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions. | |
| 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 | The collection of Simple Storage Service (Amazon S3) data events helps in detecting any anomalous activity. The details include AWS account information that accessed an Amazon S3 bucket, IP address, and time of event. | |
| 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 | AWS CloudTrail records AWS Management Console actions and API calls. You can identify which users and accounts called AWS, the source IP address from where the calls were made, and when the calls occurred. CloudTrail will deliver log files from all AWS Regions to your S3 bucket if MULTI_REGION_CLOUD_TRAIL_ENABLED is enabled. Additionally, when AWS launches a new Region, CloudTrail will create the same trail in the new Region. As a result, you will receive log files containing API activity for the new Region without taking any action. | |
| 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 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 | 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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 | Elastic Load Balancing activity is a central point of communication within an environment. Ensure ELB logging is enabled. The collected data provides detailed information about requests sent to the ELB. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. | |
| 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 | 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 | Use Amazon CloudWatch to centrally collect and manage log event activity. Inclusion of AWS CloudTrail data provides details of API call activity within your AWS account. | |
| 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 | AWS CloudTrail can help in non-repudiation by recording AWS Management Console actions and API calls. You can identify the users and AWS accounts that called an AWS service, the source IP address where the calls generated, and the timings of the calls. Details of captured data are seen within AWS CloudTrail Record Contents. | |
| 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 | 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 | 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.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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. Domain error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 | Ensure Amazon OpenSearch Service domains have error logs enabled and streamed to Amazon CloudWatch Logs for retention and response. OpenSearch Service error logs can assist with security and access audits, and can help to diagnose availability issues. | |
| 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 AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment. | |
| 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 | AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks | |
| 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 AWS ACM. These certificates must be valid and unexpired. This rule requires a value for daysToExpiration (AWS Foundational Security Best Practices value: 90). The actual value should reflect your organization's policies. | |
| 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. | 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS 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. | 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. | 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. | 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 OpenSearch Service is enabled. Node-to-node encryption enables TLS 1.2 encryption for all communications within the Amazon Virtual Private Cloud (Amazon VPC). Because sensitive data can exist, enable encryption in transit to help protect that data. | |
| 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 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(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 Amazon API Gateway REST API stages are configured with SSL certificates to allow backend systems to authenticate that requests originate from API Gateway. | |
| 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 AWS Certificate Manager to manage, provision and deploy public and private SSL/TLS certificates with AWS services and internal resources. | |
| 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 AWS WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment. | |
| 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 AWS Cloud 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. | AWS Security Hub helps to monitor unauthorized personnel, connections, devices, and software. AWS Security Hub aggregates, organizes, and prioritizes the security alerts, or findings, from multiple AWS services. Some such services are Amazon Security Hub, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, and AWS Partner solutions. | |
| 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 AWS WAF (V2) logging on regional and global web ACLs. AWS WAF logging provides detailed information about the traffic that is analyzed by your web ACL. The logs record the time that AWS WAF received the request from your AWS resource, information about the request, and an action for the rule that each request matched. | |
| 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. | AWS WAF enables you to configure a set of rules (called a web access control list (web ACL)) that allow, block, or count web requests based on customizable web security rules and conditions that you define. Ensure your Amazon API Gateway stage is associated with a WAF Web ACL to protect it from malicious attacks | |
| 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 & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring Amazon Elastic Compute Cloud (Amazon EC2) instances cannot be publicly accessed. Amazon EC2 instances can contain sensitive information and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring Amazon OpenSearch Service (OpenSearch Service) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An OpenSearch Service domain within an Amazon VPC enables secure communication between OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring Amazon OpenSearch Service domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon OpenSearch Service domain within an Amazon VPC enables secure communication between Amazon OpenSearch Service and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring Amazon EMR cluster master nodes cannot be publicly accessed. Amazon EMR cluster master nodes can contain sensitive information and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Deploy Amazon Elastic Compute Cloud (Amazon EC2) instances within an Amazon Virtual Private Cloud (Amazon VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection. All traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. Assign Amazon EC2 instances to an Amazon VPC to properly manage access. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud 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 & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring AWS Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Deploy AWS Lambda functions within an Amazon Virtual Private Cloud (Amazon VPC) for a secure communication between a function and other services within the Amazon VPC. With this configuration, there is no requirement for an internet gateway, NAT device, or VPN connection. All the traffic remains securely within the AWS Cloud. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. To properly manage access, AWS Lambda functions should be assigned to a VPC. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information, and principles and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information and principles and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon Redshift clusters are not public. Amazon Redshift clusters can contain sensitive information and principles and access control is required for such accounts. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by only allowing authorized users, processes, and devices access to Amazon Simple Storage Service (Amazon S3) buckets. The management of access should be consistent with the classification of the data. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon SageMaker notebooks do not allow direct internet access. By preventing direct internet access, you can keep sensitive data from being accessed by unauthorized users. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to AWS resources. Restricting all the traffic on the default security group helps in restricting remote access to your AWS resources. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Ensure Amazon EC2 route tables do not have unrestricted routes to an internet gateway. Removing or limiting the access to the internet for workloads within Amazon VPCs can reduce unintended access within your environment. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access at the bucket level. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to the AWS Cloud by ensuring Amazon Virtual Private Cloud (VPC) subnets are not automatically assigned a public IP address. Amazon Elastic Compute Cloud (EC2) instances that are launched into subnets that have this attribute enabled have a public IP address assigned to their primary network interface. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | If you configure your Network Interfaces with a public IP address, then the associated resources to those Network Interfaces are reachable from the internet. EC2 resources should not be publicly accessible, as this may allow unintended access to your applications or servers. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Manage access to resources in the AWS Cloud by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access. This rule allows you to optionally set the ignorePublicAcls (Config Default: True), blockPublicPolicy (Config Default: True), blockPublicAcls (Config Default: True), and restrictPublicBuckets parameters (Config Default: True). The actual values should reflect your organization's policies. | |
| 3.6.4(a)(b) | a) Restrict internet access & segregate critical systems from General IT environment. b) Reduce attack surface and vulnerabilities. | Ensure AWS Systems Manager (SSM) documents are not public, as this may allow unintended access to your SSM documents. A public SSM document can expose information about your account, resources and internal processes. |
Template
The template is available on GitHub: Operational Best Practices for NBC TRMG
