CloudWiki
Rules
Detect, troubleshoot & optimize AWS environments in real-time ->
High

Ensure Simple Email Service (SES) identities are not exposed

Description

In order to prevent unauthorized users from sending emails from domains or addresses owned by your AWS SES account, it is important to identify any exposed Amazon Simple Email Service (SES) identities and update their sending authorization policies. To restrict access only to trusted entities, you can implement appropriate AWS SES sending authorization policies. These policies specify the conditions under which other AWS accounts, IAM users and AWS services can send emails for your identity. By implementing these measures, you can ensure that only authorized users are able to send emails on your behalf, while preventing unauthorized access to your SES identities.

Remediation

To ensure that your Simple Email Service (SES) identities are not exposed, you can take the following remediation steps:

  1. Review your SES identities: Review your SES identities and ensure that they are using domain-based email addresses instead of personal email addresses. This will help prevent the exposure of personal email addresses and improve email deliverability.
  2. Configure DKIM and SPF: Configure DomainKeys Identified Mail (DKIM) and Sender Policy Framework (SPF) for your SES identities. This will help prevent email spoofing and ensure email deliverability. It's also important to monitor your DKIM and SPF records to ensure they are properly configured and up to date.
  3. Implement access controls: Restrict access to your SES identities to trusted entities by implementing appropriate AWS SES sending authorization policies. These policies specify which other AWS accounts, IAM users and AWS services can send emails for your identity, and under what conditions.
  4. Secure your AWS account: Ensure that your AWS account is secure by using strong passwords, enabling multi-factor authentication, and restricting access to AWS resources based on the principle of least privilege.
  5. Encrypt sensitive data: Encrypt any sensitive data contained in your email messages to prevent unauthorized access and ensure the privacy of your data.
  6. Monitor your SES activity: Monitor your SES activity using Amazon CloudWatch, and review your email sending and receiving logs to ensure that your SES identities are not being exposed or misused. Set up alerts for suspicious activity or unusual email patterns, and investigate any suspicious activity promptly.

By implementing these remediation steps, you can help ensure that your SES identities are secure and that only authorized entities are able to send emails on your behalf.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.
Deploy cloud infrastructure changes with confidence. Troubleshoot faster with the complete context of your cloud environment.
GET STARTED