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
Unrestricted SMTP Access Should Not Be Allowed
More Info:
No security group should allow unrestricted inbound access to TCP port 25 (SMTP).
Risk Level
Medium
Address
Security
Compliance Standards
HITRUST, AWSWAF, GDPR, SOC2, NISTCSF, PCIDSS, FedRAMP
Triage and Remediation
Remediation
To remediate the unrestricted SMTP access issue in AWS, follow these steps:
- Open the AWS Management Console and navigate to the EC2 service.
- Select the EC2 instance that is allowing unrestricted SMTP access.
- Click on the “Security” tab and scroll down to the “Security groups” section.
- Click on the security group that is associated with the instance.
- Click on the “Inbound rules” tab.
- Locate the rule that allows SMTP traffic (port 25) with the source of “0.0.0.0/0” or ”::/0”.
- Click on the “Edit” button next to the rule.
- Change the source to a specific IP address range or security group that requires SMTP access.
- Click the “Save” button to apply the changes.
By following these steps, you have successfully remediated the unrestricted SMTP access issue in AWS.
To remediate this issue in AWS, you can follow the below steps using AWS CLI:
-
Open the AWS CLI on your local machine or EC2 instance.
-
Run the following command to list all the active SMTP settings in the AWS account:
aws ses get-account-sending-enabled
- If the command output shows that the “SendingEnabled” parameter is set to “true”, then you need to disable it. Run the following command to disable SMTP access:
aws ses update-account-sending-enabled --no-sending-enabled
- After running the above command, verify that the “SendingEnabled” parameter is set to “false” by running the following command:
aws ses get-account-sending-enabled
- If the “SendingEnabled” parameter is set to “false”, then SMTP access has been successfully restricted in your AWS account.
Note: This remediation will disable SMTP access for all users in your AWS account. If you need to enable SMTP access for specific users, you can create an IAM policy that allows SMTP access and attach it to their IAM user or role.
To remediate unrestricted SMTP access in AWS using Python, you can follow the steps below:
- Create a Python script to check for SMTP access:
import boto3
client = boto3.client('ec2')
response = client.describe_security_groups()
for group in response['SecurityGroups']:
for permission in group['IpPermissions']:
if permission.get('FromPort') == 25 and permission.get('IpRanges') == [{'CidrIp': '0.0.0.0/0'}]:
group_id = group['GroupId']
print(f"Found unrestricted SMTP access in security group {group_id}")
- Once you have identified the security group(s) with unrestricted SMTP access, you can update the security group rules to restrict SMTP access to specific IP addresses or ranges.
import boto3
client = boto3.client('ec2')
response = client.authorize_security_group_ingress(
GroupId='SECURITY_GROUP_ID',
IpPermissions=[
{
'IpProtocol': 'tcp',
'FromPort': 25,
'ToPort': 25,
'IpRanges': [
{
'CidrIp': 'ALLOWED_IP_ADDRESS/32'
}
]
}
]
)
Replace SECURITY_GROUP_ID with the ID of the security group that needs to be updated and ALLOWED_IP_ADDRESS with the IP address or range that should be allowed to access SMTP.
- Run the Python script to check for and remediate unrestricted SMTP access in AWS.