AWS wellarchitected documentation change
Summary
Modified reference from 'AWS Security Hub Security Standards' to 'AWS Security Hub CSPM Security Standards' for MFA monitoring guidance.
Security assessment
Change specifies the CSPM context of existing security standards without introducing new security controls or addressing vulnerabilities. Purely a branding/naming update.
Diff
diff --git a/wellarchitected/2024-06-27/framework/sec_identities_audit.md b/wellarchitected/2024-06-27/framework/sec_identities_audit.md index b403582bc..3be45cf3c 100644 --- a//wellarchitected/2024-06-27/framework/sec_identities_audit.md +++ b//wellarchitected/2024-06-27/framework/sec_identities_audit.md @@ -32 +32 @@ Periodic validation, preferably through an automated tool, is necessary to verif -We also recommend that you enforce and monitor MFA in your identity provider. You can set up [AWS Config Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html), or use [AWS Security Hub Security Standards](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-fsbp-controls.html#fsbp-iam-3), to monitor if users have configured MFA. Consider using IAM Roles Anywhere to provide temporary credentials for machine identities. In situations when using IAM roles and temporary credentials is not possible, frequent auditing and rotating access keys is necessary. +We also recommend that you enforce and monitor MFA in your identity provider. You can set up [AWS Config Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html), or use [AWS Security Hub CSPM Security Standards](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-fsbp-controls.html#fsbp-iam-3), to monitor if users have configured MFA. Consider using IAM Roles Anywhere to provide temporary credentials for machine identities. In situations when using IAM roles and temporary credentials is not possible, frequent auditing and rotating access keys is necessary.