InformationA _security group_ acts as a virtual firewall for your instance to control inbound and outbound traffic. When you launch an instance in the AWS Virtual Private Cloud (VPC), you can assign the instance to up to five security groups. Security groups act at the instance level, not the subnet level. Therefore, each instance in a subnet in your VPC could be assigned to a different set of security groups. If you don't specify a particular group at launch time, the instance is automatically assigned to the default security group for the VPC.
For each security group, you add _rules_ that control the inbound traffic to instances, and a separate set of rules that control the outbound traffic.
This is required for both the configured port and protocol for the listener on the back-end instance and the port and protocol used for the health check.
This protects the Web-server tier from unauthorized access, it is recommended to add inbound security group rules that allow traffic for the specific application protocol and ports by referencing as source the security group associated with the Web tier ELB.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
SolutionUsing the Amazon unified command line interface:
* First remove all the ingress rules for the Web tier security group (use the "WebTierSecurityGroup" element from Audit procedure):
aws ec2 describe-security-groups --group-id _<__web_tier_security_group_> --query "SecurityGroups.IpPermissions" > /tmp/IpPermissions.json
aws ec2 revoke-security-group-ingress --group-id _<__web_tier_security_group_> --ip-permissions file:///tmp/IpPermissions.json
* Add an ingress rule for a specific port, using --source-group option to specify the Web tier ELB security group as the source of the connections:
aws ec2 authorize-security-group-ingress --group-id _<__web_tier_security_group_> --protocol tcp --port _<specific_port>_ --source-group _<web_tier_elb_security_group>_