Control: VPC security groups should restrict ingress TCP and UDP access from 0.0.0.0/0
Description
Manage access to resources in the AWS Cloud by ensuring common ports are restricted on AWS Elastic Compute Cloud (AWS EC2) Security Groups.
Usage
Run the control in your terminal:
powerpipe control run aws_compliance.control.vpc_security_group_restrict_ingress_tcp_udp_allSnapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run aws_compliance.control.vpc_security_group_restrict_ingress_tcp_udp_all --shareSQL
This control uses a named query:
with bad_rules as (  select    group_id,    count(*) as num_bad_rules  from    aws_vpc_security_group_rule  where    type = 'ingress'    and cidr_ipv4 = '0.0.0.0/0'    and (      ip_protocol in ('tcp', 'udp')      or (        ip_protocol = '-1'        and from_port is null      )    )  group by    group_id)select  arn as resource,  case    when bad_rules.group_id is null then 'ok'    else 'alarm'  end as status,  case    when bad_rules.group_id is null then sg.group_id || ' does not allow ingress to TCP or UDP ports from 0.0.0.0/0.'    else sg.group_id || ' contains ' || bad_rules.num_bad_rules || ' rule(s) that allow ingress to TCP or UDP ports from 0.0.0.0/0.'  end as reason    , region, account_idfrom  aws_vpc_security_group as sg  left join bad_rules on bad_rules.group_id = sg.group_id;