| Plugin Title | Open All Ports Protocols |
| Cloud | AWS |
| Category | EC2 |
| Description | Determine if security group has all ports or protocols open to the public |
| More Info | Security groups should be created on a per-service basis and avoid allowing all ports or protocols. |
| AWS Link | http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html |
| Recommended Action | Modify the security group to specify a specific port and protocol to allow. |
- Log into the AWS Management Console.
- Select the "Services" option and search for EC2.
- Scroll down the left navigation panel and choose "Security Group" under "Network & Security".
- Select the "EC2 Security Group" that needs to be verified.
- Scroll down the bottom panel and choose "Inbound". Verify the value for "Source" column and if any rule have value set to "0.0.0.0/0" or "::/0 " then the selected "Security Group" has one or many ports open to the public.
- Repeat steps number 2 - 5 to verify other "Security Groups" in the selected AWS region.
- Navigate to "Security Groups" under "Network & Security" and select the "Security Group" that needs to modify to restrict the access to specific ip address.
- Scroll down the "Security Group" page and select the "Inbound" and click on the "Edit" button.
- In the "Edit inbound rules" tab select the "MyIP" from the "Source" column to allow inbound traffic only from specific IP address.
- In the "Edit inbound rules" tab select the "Custom" from the "Source" column as per the requirements and specify the "static IP" address of the permitted host along with "Description" for the "Security Group" rule.
- Click on the "Save" button to make the necessary changes.
- Repeat steps number 7 - 11 to modify the security group to specify a specific port and protocol to allow.
