SNS topic is publicly accessible
- Severity
- Medium
- Service
- SNS
- Check ID
- SNS_PUBLIC
What this check finds
This SNS topic's policy allows access from anyone, not only principals in your own account. This may allow an attacker to read or write messages to this topic.
Passing looks like: SNS topics not publicly accessible.
How to fix it
Update the SNS topic policy to restrict access to specific IAM principals.
AWS CLI
aws sns set-topic-attributes --topic-arn TOPIC_ARN --attribute-name Policy --attribute-value 'JSON_POLICY'
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
SNS → Topics → select topic → Access policy → Edit.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| SOC 2 — Trust Services Criteria |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs