AWS Network Audit

Audit your Network to safe gaurd your data

What we do?

Unused Virtual Private Gateways Should Be Removed

Unused Amazon Virtual Private Gateways should be removed in order to adhere to best practices and to avoid reaching the service limit.

Flow Logs on VPC Should Be Enabled

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.

Flow Logs Should be Enabled on Subnet

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.

Unused Network ACLs Should Be Removed

Maintaining unused resources increases risks of misconfigurations and increases the difficulty of audits. Unused Network ACLs should therefore be discarded.

Unused Security Groups Should Be Removed

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.

Default Security Groups Should Not Allow Unrestricted Inbound Access

Your AWS EC2 default security groups should 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.

Default Security Groups Should Block All Traffic

Default security groups should block all traffic by default. EC2 instances should not be associated with default security groups.

Default Security Group Should Not Be Publicly Accessible

Default security groups should block all traffic by default. EC2 instances should not be associated with default security groups with public access.

Excessive Number of Security Groups Should Not Be Present

There should not be 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.

EC2 instances Should Not Be Publicly Accessible

Unknown EC2 instances should not be publicly accessible. It is good practice to maintain a list of known, publicly accessible instances and flag all other instances that meet this criteria.

Ports Should Not Be Open for External Traffic

Security groups should not have 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.

Ports Should Not Be Open for Internal Traffic

Security groups should not have 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.

EC2 Instance Should Not Have Open ICMP ports

ICMP ports should not be open for EC2 instances.

RDS Instances Should Not Be Publicly Accessible

RDS instances should not be 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.

Redshift Should Not Be Publicly Accessible

Redshift clusters should not be 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.

MQ Broker Should Not Be Publicly Accessible

MQ brokers should not be 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.


Not ready for a free signup yet? No worries!

We suggest you use the checklist!

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.