Within the AWS environment, there are all kinds of vulnerabilities that require continuous attention. Misconfigured servers, open S3 buckets, unsupervised traffic and a host of other issues must be identified and addressed before they create major risks for an enterprise.
Out-of-the-box AWS configurations can help, but only to a point. The cloud is dynamic, and because it’s constantly shifting in response to internal change and customer needs, it demands continuous monitoring and guidelines for responsive remediation.
Here are the 12 critical steps that are intended to help you strengthen your AWS environment
With these, you can develop a disciplined framework for your team and create a stronger security posture for your data and IT assets.
- Enable AWS CloudTrail
- Disable root API access and secret keys
- Enable MFA tokens
- Reduce the number of IAM users with admin rights
- Use roles for Amazon EC2
- Employ least privilege – use strong policies to limit what IAM entities can do
- Ensure access logging is enabled on the CloudTrail S3 bucket
- Rotate keys regularly
- Apply IAM roles with STS
- Use Auto Scaling to dampen DDoS effectsEnable security measures when Auto Scaling is not an option
- Enable security measures when Auto Scaling is not an option
- Watch world-readable and listable Amazon S3 bucket policies
As new stakeholders enter the organization, older methods become challenging to manage and difficult to visualize, sometimes presenting opportunities for administrators to lose track of security checks for older products. Most security functions are built with default deny rules, but these rules can be circumvented if an organization fails to keep track of where or what it is allowing when new systems are built on top of older ones.
To avoid internal incidents that result from multiple products being used simultaneously, Amazon web service recommends the best practice of choosing and sticking with one product. When an organization takes the time to carefully select and maintain a system, security will act as it is expected to.
Download this whitepaper to read more in detail.
You may also like to Read:
Top Five Requirements for Effective Endpoint Protection