| Plugin Title | Open RPC |
| Cloud | AWS |
| Category | EC2 |
| Description | Determine if TCP port 135 for RPC is open to the public |
| More Info | While some ports such as HTTP and HTTPS are required to be open to the public to function properly, more sensitive services such as RPC should be restricted to known IP addresses. |
| AWS Link | http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html |
| Recommended Action | Restrict TCP port 135 to known IP addresses |
- 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 for "Custom TCP Rule" under "Type" for port "135" and if any rule have value set to "0.0.0.0/0" or "::/0 " then the selected "Security Group" has "TCP" port for "RPC" 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 of "TCP" port 135 for "RPC" to specific ip address.
- Scroll down the page and select the "Inbound" and click on the "Edit" button.
- In the "Edit inbound rules" tab select either the "MyIP" or "Custom" from the "Source" column.
- In the "Edit inbound rules" tab select the "MyIP" from the "Source" column to allow "RPC" inbound traffic only from specific IP address.
- In the "Edit inbound rules" tab select the "Custom" from the "Source" column as per the requirements for "RPC" and specify static IP/Elastic IP address along with "Description" for the "Security Group" rule.
- Click on the "Save" button to make the necessary changes.
- Repeat steps number 7 - 12 to restrict TCP port 135 for "RPC" to known IP address.
