Your development team has started using AWS resources for development purposes.
The AWS account has just been created.
Your IT Security team is worried about possible leakage of AWS keys.
What is the first level of measure that should be taken to protect the AWS account.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A.
The first level or measure that should be taken is to delete the keys for the IAM root user.
As per the best practices for managing AWS access keys, the following are the key guidelines.
Remove (or don't generate) an account access key for Root Account.
Use Groups to Assign Permissions to IAM Users.
Use temporary security credentials (IAM roles) instead of long-term access keys.
Start Using Permissions with AWS Managed Policies.
So as per the AWS best practices guidelines, we do see removing the access keys for root users should be the first level of measure to protect your AWS account.
For more information, refer to the following URLs:
https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.htmlThe first level of measure that should be taken to protect the AWS account when a new AWS account is created is to delete the AWS keys for the root account.
AWS root account credentials provide complete access to all AWS resources, including sensitive data and services. If these credentials are compromised or leaked, an attacker can gain complete control of the AWS account and resources.
Therefore, AWS strongly recommends that the root account credentials should be used only to create the first IAM user, and then those credentials should be deleted. AWS recommends using IAM users with appropriate permissions to access AWS resources.
To delete the root account access keys, log in to the AWS Management Console using root account credentials. Then, navigate to the Security Credentials page, where you can manage the access keys. From there, you can delete the access keys for the root account.
After deleting the root account access keys, you can create IAM users and groups, assign appropriate permissions to them using IAM policies, and control access to AWS resources. IAM Roles are another option, which allow you to grant permissions to entities that you trust, such as IAM users in your own account or AWS services. IAM Roles are recommended for granting permissions to AWS services.
Therefore, options B, C, and D are all important measures to protect the AWS account. However, deleting the AWS keys for the root account is the first level of measure that should be taken to protect the AWS account.