-
AWS IAM
Monitoring your AWS IAM configuration and policies is vital aspects to have a secure setup. This recipe monitors several for rules and best practices recommended by AWS and industry leaders.
Security
Access Keys For Root Account
Root account has full permissions across the entire account. Root account should not have access keys. Also, it certainly shouldn't access any service. Instead, create IAM users with predefined roles.
Root account has full permissions across the entire account. Root account should not have access keys. Also, it certainly shouldn't access any service. Instead, create IAM users with predefined roles.
Root Account Access Keys Rotation
Root account should not have access keys. If at all you have that, then the keys should be rotated periodically.
Root account should not have access keys. If at all you have that, then the keys should be rotated periodically.
Root account MFA
Multifactor Authentication is strongly recommended to be enabled for every account with no exceptions.
Multifactor Authentication is strongly recommended to be enabled for every account with no exceptions.
MFA on user accounts
MFA must be enabled on user accounts. AWS recommends that you configure multi-factor authentication (MFA) to help protect your AWS resources.
MFA must be enabled on user accounts. AWS recommends that you configure multi-factor authentication (MFA) to help protect your AWS resources.
User console access inactive
Users who are infrequent or do not need access to console, their account access should be cleared off.
Users who are infrequent or do not need access to console, their account access should be cleared off.
User account service inactivity
Checks inactivity of any user on a service. Those priviledges should be removed for better security posture.
Checks inactivity of any user on a service. Those priviledges should be removed for better security posture.
User Inline Policies
IAM users should not have Inline policies. It is recommended that IAM policies be applied directly to groups and roles but not users.
IAM users should not have Inline policies. It is recommended that IAM policies be applied directly to groups and roles but not users.
User account with multiple access keys
Multiple access keys for the same user should be avoided. There should be just 1 access key per user account.
Multiple access keys for the same user should be avoided. There should be just 1 access key per user account.
Sources
Help Us Improve!
If you have any suggestions to improve this checklist, please let us know by filling out this form.