AWS Introduction
AWS Pricing
AWS Threats
AWS Misconfigurations
- Getting Started with AWS Audit
- Permissions required for Misconfigurations Detection
- API Gateway Audit
- Cloudformation Audit
- CloudFront Audit
- CloudTrail Audit
- Cloudwatch Audit
- DynamoDB Audit
- EC2 Audit
- Elastic Search Audit
- ELB Audit
- IAM Audit
- KMS Audit
- Kubernetes Audit
- Lambda Audit
- RDS Audit
- Redshift Audit
- Route53 Audit
- S3 Audit
- Security Groups Audit
- SES Audit
- SNS Audit
- IAM Deep Dive
- App Sync Audit
- Code Build Audit
- Open Search Audit
- Shield Audit
- SQS Audit
EKS Cluster Should Allow Inbound Traffic only from Port 443(HTTPS)
More Info:
Security groups associated with EKS clusters should allow inbound traffic only on TCP port 443 (HTTPS). This prevents any malicious activities such as brute-force attacks and also meets compliance requirements.
Risk Level
Medium
Address
Security
Compliance Standards
SOC2, GDPR, PCIDSS, NIST, HITRUST, NISTCSF
Triage and Remediation
Remediation
To remediate the misconfiguration in AWS, follow the steps below:
-
Login to the AWS console and navigate to the Amazon EKS service.
-
Select the EKS cluster that needs to be remediated.
-
Click on the “Configuration” tab in the left-hand menu.
-
Scroll down to the “Networking” section and click on the “Edit” button.
-
In the “Security group rules” section, locate the security group that is associated with your EKS cluster.
-
Click on the “Edit” button next to the security group.
-
In the “Inbound rules” section, locate the rule that allows inbound traffic on port 443.
-
If the rule is missing, click on the “Add rule” button and select “HTTPS” from the dropdown menu.
-
If the rule is present but allows traffic from other ports as well, click on the “Edit” button next to the rule and change the port range to only allow traffic on port 443.
-
Once the rule has been updated, click on the “Save rules” button to apply the changes.
-
Verify that the inbound traffic is now restricted to port 443 by checking the security group rules.
Your EKS cluster should now only allow inbound traffic on port 443, which will remediate the misconfiguration.
To remediate this misconfiguration for an EKS cluster in AWS using AWS CLI, follow these steps:
-
Open the AWS CLI on your local machine.
-
Run the following command to list all the EKS clusters in your AWS account:
aws eks list-clusters
- Choose the EKS cluster that you want to remediate and run the following command to update the cluster’s security group:
aws eks update-cluster-config --name <cluster_name> --region <region_name> --resources-vpc-config securityGroupIds=<security_group_id>
Replace the <cluster_name> with the name of your EKS cluster, <region_name> with the AWS region where your cluster is located and <security_group_id> with the ID of the security group associated with your EKS cluster.
- Run the following command to create a new security group rule that allows inbound traffic only from port 443:
aws ec2 authorize-security-group-ingress --group-id <security_group_id> --protocol tcp --port 443 --cidr 0.0.0.0/0
Replace the <security_group_id> with the ID of the security group associated with your EKS cluster.
- Verify that the new security group rule has been added successfully by running the following command:
aws ec2 describe-security-groups --group-ids <security_group_id>
This should return a JSON object containing the details of the security group associated with your EKS cluster, including the new inbound rule for port 443.
Your EKS cluster is now configured to allow inbound traffic only from port 443.
To remediate the misconfiguration of allowing inbound traffic only from port 443 for an EKS Cluster in AWS, you can follow the below steps using Python:
- Install the AWS SDK for Python (Boto3) using the following command:
pip install boto3
- Create a Boto3 client for Amazon EKS using the following code:
import boto3
eks_client = boto3.client('eks')
- Get the details of the EKS cluster using the following code:
cluster_name = 'your_cluster_name'
response = eks_client.describe_cluster(name=cluster_name)
- Get the security group ID of the worker nodes using the following code:
security_group_id = response['cluster']['resourcesVpcConfig']['clusterSecurityGroupId']
- Get the details of the security group using the following code:
ec2_client = boto3.client('ec2')
response = ec2_client.describe_security_groups(GroupIds=[security_group_id])
- Update the inbound rules of the security group to allow traffic only from port 443 using the following code:
ip_permissions = response['SecurityGroups'][0]['IpPermissions']
for permission in ip_permissions:
if permission['IpProtocol'] == 'tcp' and permission['FromPort'] != 443:
ec2_client.revoke_security_group_ingress(
GroupId=security_group_id,
IpPermissions=[
{
'IpProtocol': 'tcp',
'FromPort': permission['FromPort'],
'ToPort': permission['ToPort'],
'IpRanges': permission['IpRanges'],
'Ipv6Ranges': permission['Ipv6Ranges'],
'PrefixListIds': permission['PrefixListIds'],
'UserIdGroupPairs': permission['UserIdGroupPairs']
}
]
)
ec2_client.authorize_security_group_ingress(
GroupId=security_group_id,
IpPermissions=[
{
'IpProtocol': 'tcp',
'FromPort': 443,
'ToPort': 443,
'IpRanges': [
{
'CidrIp': '0.0.0.0/0'
}
]
}
]
)
This code will remove all the existing inbound rules that allow traffic from ports other than 443 and add a new inbound rule that allows traffic only from port 443.
Note: Replace ‘your_cluster_name’ with the actual name of your EKS cluster. Also, make sure you have the necessary permissions to modify the security group.