Unused Virtual Private Gateways
Remove unused Amazon Virtual Private Gateways in order to adhere to best practices and to avoid reaching the service limit.
Remove unused Amazon Virtual Private Gateways in order to adhere to best practices and to avoid reaching the service limit.
VPC flow logs record all traffic flowing in to and out of a VPC. These logs are critical for auditing and review after security incidents.
Subnet flow logs record all traffic flowing in to and out of a Subnet. These logs are critical for auditing and review after security incidents.
Maintaining unused resources increases risks of misconfigurations and increases the difficulty of audits.
Non-default security groups were defined which were unused and may not be required. This being the case, their existence in the configuration increases the risk that they may be inappropriately assigned. The unused security groups should be reviewed and removed if no longer required.
Ensure that your AWS EC2 default security groups restrict all inbound public traffic in order to enforce AWS users (EC2 administrators, resource managers, etc) to create custom security groups that exercise the rule of least privilege instead of using the default security groups.
Ensure the default security groups block all traffic by default. EC2 instances should not be associated with default security groups.
Ensure the default security groups block all traffic by default. EC2 instances should not be associated with default security groups with public access.
Determine if there are an excessive number of security groups in the account. AWS applies the most permissive rule amongst all the Security Groups assigned to any EC2 instance.
Ensure that unknown EC2 instances are not publicly accessible. It is good practice to maintain a list of known, publicly accessible instances and flag all other instances that meet this criteria.
Determine if security group has all ports or protocols open to the public. Security groups should be created on a per-service basis and avoid allowing all ports or protocols.
Determine if security group has all ports or protocols open to the internal traffic. Security groups should be created on a per-service basis and avoid allowing all ports or protocols even for internal access.
Ensure that ICMP ports are not open for EC2 instances.
Ensures RDS instances are not launched into the public cloud. Unless there is a specific business requirement, RDS instances should not have a public endpoint and should be accessed from within a VPC only.
Ensures Redshift clusters are not launched into the public cloud. Unless there is a specific business requirement, Redshift clusters should not have a public endpoint and should be accessed from within a VPC only.
Ensure MQ brokers are not launched into public cloud. Unless there is a specific business requirement, MQ Brokers should not have a public endpoint and should be accessed from within a VPC only.
If you are not yet convinced to sign up with Cloudanix, that's not a problem. We recommend you use a comprehensive checklist which your team can use to perform a manual assessment of your workload.