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

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

Operational Best Practices for MAS Notice 655

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

The following provides a sample mapping between the Monetary Authority of Singapore (MAS) Notice 655 – Cyber Hygiene and Amazon Config managed rules. Each Config rule applies to a specific Amazon resource, and relates to one or more MAS Notice 655 – Cyber Hygiene controls. A MAS Notice 655 – Cyber Hygiene control can be related to multiple Config rules. Refer to the table below for more detail and guidance related to these mappings.

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

控制 ID Amazon Config 规则 Guidance
4.1

iam-user-no-policies-check

This rule ensures Amazon Identity and Access Management (IAM) policies are attached only to groups or roles to control access to systems and assets. Assigning privileges at the group or the role level helps to reduce opportunity for an identity to receive or retain excessive privileges.
4.1

access-keys-rotated

The credentials are audited for authorized devices, users, and processes by ensuring IAM access keys are rotated as per organizational policy. Changing the access keys on a regular schedule is a security best practice. It shortens the period an access key is active and reduces the business impact if the keys are compromised. This rule requires an access key rotation value (Config Default: 90). The actual value should reflect your organization's policies.
4.1

iam-user-unused-credentials-check

Amazon Identity and Access Management (IAM) can help you with access permissions and authorizations by checking for IAM passwords and access keys that are not used for a specified time period. If these unused credentials are identified, you should disable and/or remove the credentials, as this may violate the principle of least privilege. This rule requires you to set a value to the maxCredentialUsageAge (Config Default: 90). The actual value should reflect your organization's policies.
4.1

iam-password-policy

The identities and the credentials are issued, managed, and verified based on an organizational IAM password policy. They meet or exceed requirements as stated by NIST SP 800-63 and the Centers for Internet Security (CIS) Amazon Foundations Benchmark for password strength. This rule allows you to optionally set RequireUppercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireLowercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireSymbols (Amazon Foundational Security Best Practices value: true), RequireNumbers (Amazon Foundational Security Best Practices value: true), MinimumPasswordLength (Amazon Foundational Security Best Practices value: 14), PasswordReusePrevention (Amazon Foundational Security Best Practices value: 24), and MaxPasswordAge (Amazon Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
4.1

Manage access to resources in the Amazon Web Services 云 by ensuring MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
4.1

iam-root-access-key-check

Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their Amazon Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based Amazon Web Services 账户 to help to incorporate the principle of least functionality.
4.1

Manage access to resources in the Amazon Web Services 云 by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
4.1

mfa-enabled-for-iam-console-access

Manage access to resources in the Amazon Web Services 云 by ensuring that MFA is enabled for all Amazon Identity and Access Management (IAM) users that have a console password. MFA 在用户名和密码之上增加了一层额外的防护。By requiring MFA for IAM users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
4.1

iam-user-mfa-enabled

Enable this rule to restrict access to resources in the Amazon Web Services 云. This rule ensures multi-factor authentication (MFA) is enabled for all IAM users. MFA 在用户名和密码之上增加了一层额外的防护。Reduce the incidents of compromised accounts by requiring MFA for IAM users.
4.1

emr-kerberos-enabled

The access permissions and authorizations can be managed and incorporated with the principles of least privilege and separation of duties, by enabling Kerberos for Amazon EMR clusters. In Kerberos, the services and the users that need to authenticate are known as principals. The principals exist within a Kerberos realm. Within the realm, a Kerberos server is known as the key distribution center (KDC). It provides a means for the principals to authenticate. The KDC authenticates by issuing tickets for authentication. KDC 维护一个包含其领域中的委托人、它们的密码及其他有关每个委托人的管理信息的数据库。
4.1

iam-user-group-membership-check

Amazon Identity and Access Management (IAM) can help you restrict access permissions and authorizations, by ensuring IAM users are members of at least one group. Allowing users more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
4.1

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

Amazon Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, restricting policies from containing "Effect": "Allow" with "Action": "*" over "Resource": "*". Allowing users to have more privileges than needed to complete a task may violate the principle of least privilege and separation of duties.
4.1

iam-NON-CONPRONT

Ensure an Amazon Identity and Access Management (IAM) user, IAM role or IAM group does not have an inline policy to control access to systems and assets. Amazon recommends to use managed policies instead of inline policies. The managed policies allow reusability, versioning and rolling back, and delegating permissions management.
4.1

iam-group-has-users-check

Amazon 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 IAM user. Placing IAM users in groups based on their associated permissions or job function is one way to incorporate least privilege.
4.1

secretsmanager-rotation-enabled-check

This rule ensures Amazon Secrets Manager secrets have rotation enabled. Rotating secrets on a regular schedule can shorten the period a secret is active, and potentially reduce the business impact if the secret is compromised.
4.1

secretsmanager-scheduled-rotation-success-check

This rule ensures that Amazon Secrets Manager secrets have rotated successfully according to the rotation schedule. Rotating secrets on a regular schedule can shorten the period that a secret is active, and potentially reduce the business impact if it is compromised.
4.1

elb-deletion-protection-enabled

This rule ensures that Elastic Load Balancing has deletion protection enabled. Use this feature to prevent your load balancer from being accidentally or maliciously deleted, which can lead to loss of availability for your applications.
4.1

rds-实例deletion-protection-enabled

Ensure Amazon Relational Database Service (Amazon RDS) instances have deletion protection enabled. Use deletion protection to prevent your Amazon RDS instances from being accidentally or maliciously deleted, which can lead to loss of availability for your applications.
4.2

ec2-instance-managed-by-systems-manager

An inventory of the software platforms and applications within the organization is possible by managing Amazon Elastic Compute Cloud (Amazon EC2) instances with Amazon Secrets Manager. Use Amazon Secrets Manager to provide detailed system configurations, operating system patch levels, services name and type, software installations, application name, publisher and version, and other details about your environment.
4.2

ec2-managedinstance-patch-compliance-status-check

Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in Amazon Secrets Manager as required by your organization’s policies and procedures.
4.2

ec2-managedinstance-association-compliance-status-check

Use Amazon Secrets Manager Associations to help with inventory of software platforms and applications within an organization. Amazon Secrets Manager assigns a configuration state to your managed instances and allows you to set baselines of operating system patch levels, software installations, application configurations, and other details about your environment.
4.2

redshift-cluster-maintenancesettings-check

This rule ensures that Amazon Redshift clusters have the preferred settings for your organization. Specifically, that they have preferred maintenance windows and automated snapshot retention periods for the database. This rule requires you to set the allowVersionUpgrade. 默认值为 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.
4.2

电子邮件 2 检查

Ensure the Instance Metadata Service Version 2 (IMDSv2) method is enabled to help protect access and control of Amazon Elastic Compute Cloud (Amazon EC2) instance metadata. With its new session-based controls, changes to instance metadata can be restricted. Additionally, updating to IMDSV2 can provide additional protection against misconfigured-open website application firewalls, reverse proxies, layer-3 firewalls and network address translation, as well as unpatched SSRF vulnerabilities.
4.3

codebuild-project-envvar-awscred-check

Ensure authentication credentials AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY do not exist within Amazon CodeBuild project environments. Do not store these variables in clear text. Storing these variables in clear text leads to unintended data exposure and unauthorized access.
4.4

Ensure Amazon WAF is enabled on Elastic Load Balancers (ELB) to help protect web applications. A WAF helps to protect your web applications or APIs against common web exploits. These web exploits may affect availability, compromise security, or consume excessive resources within your environment.
4.4

codebuild-project-envvar-awscred-check

Ensure authentication credentials AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY do not exist within Amazon CodeBuild project environments. Do not store these variables in clear text. Storing these variables in clear text leads to unintended data exposure and unauthorized access.
4.4

dms-replication-not-public

Manage access to the Amazon Web Services 云 by ensuring DMS replication instances cannot be publicly accessed. DMS replication instances can contain sensitive information and access control is required for such accounts.
4.4

ebs-snapshot-public-restorable-check

Manage access to the Amazon Web Services 云 by ensuring EBS snapshots are not publicly restorable. EBS volume snapshots can contain sensitive information and access control is required for such accounts.
4.4

ec2-instance-no-public-ip

Manage access to the Amazon Web Services 云 by ensuring Amazon Elastic Compute Cloud (Amazon EC2) instances cannot be publicly accessed. Amazon EC2 instances can contain sensitive information and access control is required for such accounts.
4.4

ec2-security-group-attached-to-eni

This rule ensures the security groups are attached to an Amazon Elastic Compute Cloud (Amazon EC2) instance or to an ENI. This rule helps monitoring unused security groups in the inventory and the management of your environment.
4.4

elasticsearch-in-vpc-only

Manage access to the Amazon Web Services 云 by ensuring Amazon Elasticsearch Service (Amazon ES) Domains are within an Amazon Virtual Private Cloud (Amazon VPC). An Amazon ES domain within an Amazon VPC enables secure communication between Amazon ES and other services within the Amazon VPC without the need for an internet gateway, NAT device, or VPN connection.
4.4

emr-master-no-public-ip

Manage access to the Amazon Web Services 云 by ensuring Amazon EMR cluster master nodes cannot be publicly accessed. Amazon EMR cluster master nodes can contain sensitive information and access control is required for such accounts.
4.4

Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your Amazon Web Services 云 environment.
4.4

restricted-ssh

Amazon Elastic Compute Cloud (Amazon EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to Amazon resources. Not allowing ingress (or remote) traffic from 0.0.0.0/0 to port 22 on your resources help you restricting remote access.
4.4

ec2-instances-in-vpc

Deploy Amazon Elastic Compute Cloud (Amazon EC2) instances within an Amazon Virtual Private Cloud (Amazon VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection. All traffic remains securely within the Amazon Web Services 云. Because of their logical isolation, domains that reside within anAmazon VPC have an extra layer of security when compared to domains that use public endpoints. Assign Amazon EC2 instances to an Amazon VPC to properly manage access.
4.4

internet-gateway-authorized-vpc-only

Manage access to resources in the Amazon Web Services 云 by ensuring that internet gateways are only attached to authorized Amazon Virtual Private Cloud (Amazon VPC). Internet gateways allow bi-directional internet access to and from the Amazon VPC that can potentially lead to unauthorized access to Amazon VPC resources.
4.4

Manage access to resources in the Amazon Web Services 云 by ensuring Amazon Lambda functions cannot be publicly accessed. Public access can potentially lead to degradation of availability of resources.
4.4

Deploy Amazon Lambda functions within an Amazon Virtual Private Cloud (Amazon VPC) for a secure communication between a function and other services within the Amazon VPC. With this configuration, there is no requirement for an internet gateway, NAT device, or VPN connection. All the traffic remains securely within the Amazon Web Services 云. Because of their logical isolation, domains that reside within an Amazon VPC have an extra layer of security when compared to domains that use public endpoints. To properly manage access, Amazon Lambda functions should be assigned to a VPC.
4.4

rds-instance-public-access-check

Manage access to resources in the Amazon Web Services 云 by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information, and principles and access control is required for such accounts.
4.4

rds-snapshots-public-prohibited

Manage access to resources in the Amazon Web Services 云 by ensuring that Amazon Relational Database Service (Amazon RDS) instances are not public. Amazon RDS database instances can contain sensitive information and principles and access control is required for such accounts.
4.4

redshift-cluster-public-access-check

Manage access to resources in the Amazon Web Services 云 by ensuring that Amazon Redshift clusters are not public. Amazon Redshift clusters can contain sensitive information and principles and access control is required for such accounts.
4.4

restricted-common-ports

Manage access to resources in the Amazon Web Services 云 by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) security groups. Not restricting access to ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. This rule allows you to optionally set blockedPort1 - blockedPort5 parameters (Config Defaults: 20,21,3389,3306,4333). The actual values should reflect your organization's policies.
4.4

s3-account-level-public-access-blocks

Manage access to resources in the Amazon Web Services 云 by ensuring that Amazon Simple Storage Service (Amazon S3) buckets cannot be publicly accessed. This rule helps keeping sensitive data safe from unauthorized remote users by preventing public access. This rule allows you to optionally set the ignorePublicAcls (Config Default: True), blockPublicPolicy (Config Default: True), blockPublicAcls (Config Default: True), and restrictPublicBuckets parameters (Config Default: True). The actual values should reflect your organization's policies.
4.4

Manage access to resources in the Amazon Web Services 云 by ensuring that Amazon SageMaker notebooks do not allow direct internet access. By preventing direct internet access, you can keep sensitive data from being accessed by unauthorized users.
4.4

vpc-default-security-group-closed

Amazon Elastic Compute Cloud (Amazon EC2) security groups can help in the management of network access by providing stateful filtering of ingress and egress network traffic to Amazon resources. Restricting all the traffic on the default security group helps in restricting remote access to your Amazon resources.
4.4

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

Manage access to resources in the Amazon Web Services 云 by ensuring common ports are restricted on Amazon Elastic Compute Cloud (Amazon EC2) Security Groups. Not restricting access on ports to trusted sources can lead to attacks against the availability, integrity and confidentiality of systems. By restricting access to resources within a security group from the internet (0.0.0.0/0) remote access can be controlled to internal systems.
4.5

ec2-instance-managed-by-systems-manager

An inventory of the software platforms and applications within the organization is possible by managing Amazon Elastic Compute Cloud (Amazon EC2) instances with Amazon Secrets Manager. Use Amazon Secrets Manager to provide detailed system configurations, operating system patch levels, services name and type, software installations, application name, publisher and version, and other details about your environment.
4.5

ec2-managedinstance-patch-compliance-status-check

Enable this rule to help with identification and documentation of Amazon Elastic Compute Cloud (Amazon EC2) vulnerabilities. The rule checks if Amazon EC2 instance patch compliance in Amazon Secrets Manager as required by your organization’s policies and procedures.
4.5

ec2-managedinstance-association-compliance-status-check

Use Amazon Secrets Manager Associations to help with inventory of software platforms and applications within an organization. Amazon Secrets Manager assigns a configuration state to your managed instances and allows you to set baselines of operating system patch levels, software installations, application configurations, and other details about your environment.
4.6

iam-password-policy

The identities and the credentials are issued, managed, and verified based on an organizational IAM password policy. They meet or exceed requirements as stated by NIST SP 800-63 and the Centers for Internet Security (CIS) Amazon Foundations Benchmark for password strength. This rule allows you to optionally set RequireUppercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireLowercaseCharacters (Amazon Foundational Security Best Practices value: true), RequireSymbols (Amazon Foundational Security Best Practices value: true), RequireNumbers (Amazon Foundational Security Best Practices value: true), MinimumPasswordLength (Amazon Foundational Security Best Practices value: 14), PasswordReusePrevention (Amazon Foundational Security Best Practices value: 24), and MaxPasswordAge (Amazon Foundational Security Best Practices value: 90) for your IAM Password Policy. The actual values should reflect your organization's policies.
4.6

Manage access to resources in the Amazon Web Services 云 by ensuring MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
4.6

iam-root-access-key-check

Access to systems and assets can be controlled by checking that the root user does not have access keys attached to their Amazon Identity and Access Management (IAM) role. Ensure that the root access keys are deleted. Instead, create and use role-based Amazon Web Services 账户 to help to incorporate the principle of least functionality.
4.6

Manage access to resources in the Amazon Web Services 云 by ensuring hardware MFA is enabled for the root user. The root user is the most privileged user in an Amazon Web Services 账户. The MFA adds an extra layer of protection for a user name and password. By requiring MFA for the root user, you can reduce the incidents of compromised Amazon Web Services 账户.
4.6

mfa-enabled-for-iam-console-access

Manage access to resources in the Amazon Web Services 云 by ensuring that MFA is enabled for all Amazon Identity and Access Management (IAM) users that have a console password. MFA 在用户名和密码之上增加了一层额外的防护。By requiring MFA for IAM users, you can reduce incidents of compromised accounts and keep sensitive data from being accessed by unauthorized users.
4.6

iam-user-mfa-enabled

Enable this rule to restrict access to resources in the Amazon Web Services 云. This rule ensures multi-factor authentication (MFA) is enabled for all IAM users. MFA 在用户名和密码之上增加了一层额外的防护。Reduce the incidents of compromised accounts by requiring MFA for IAM users.
4.5

Amazon GuardDuty can help to monitor and detect potential cybersecurity events by using threat intelligence feeds. These include lists of malicious IPs and machine learning to identify unexpected, unauthorized, and malicious activity within your Amazon Web Services 云 environment.

Template

The template is available on GitHub: Operational Best Practices for MAS Notice 655.