Ensure SNS is not publicly accessible

Security & Compliance

Amazon Simple Notification Service (SNS) is a web service that allows users to send messages or notifications to a variety of endpoints, such as email, SMS, and HTTP/HTTPS endpoints. Ensuring that SNS is not publicly accessible is important to protect against unauthorized access, data breaches, and other security threats. By default, SNS is not publicly accessible, but it is possible to make it publicly accessible through the use of access policies and permissions. Publicly accessible SNS endpoints can be vulnerable to attacks such as cross-site scripting (XSS), injection attacks, and brute-force attacks. By ensuring that SNS is not publicly accessible, organizations can help reduce the risk of security vulnerabilities and protect their data and infrastructure from malicious attacks.‍


If an organization has identified that their SNS is publicly accessible, they should take immediate remediation steps to prevent unauthorized access and protect their data and infrastructure. Here are some recommended steps to take:

  1. Review SNS access policies: Review the access policies for the SNS resources to ensure that they are only accessible from authorized sources. Access policies should limit access to SNS resources to trusted IP addresses, security groups, or AWS accounts.
  2. Disable public access: Disable public access to SNS resources by removing the "Allow" permission for the "Everyone" or "Anonymous" group in the access policies.
  3. Monitor access logs: Monitor the access logs for the SNS resources to detect any unauthorized access attempts or suspicious activity. This can help to identify security threats and prevent data breaches.
  4. Enable SNS encryption: Enable encryption for SNS messages to ensure that they are secure and protected from interception.
  5. Use SNS topic policies: Use SNS topic policies to restrict who can publish or subscribe to SNS topics. This can help to ensure that only authorized users have access to the SNS resources.
  6. Review AWS IAM users and roles: Review the AWS Identity and Access Management (IAM) users and roles that have permissions to access SNS resources. Remove any unnecessary permissions and ensure that permissions are granted based on the principle of least privilege.

By taking these remediation steps, organizations can help ensure that SNS is not publicly accessible, reduce the risk of unauthorized access and data breaches, and help ensure the overall security of their network and systems.

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.