SQS queue policy is public and access is not restricted to specific services or principals misconfig

Rule Details

Cortex AppSec Rule ID	APPSEC_AWS_168
Category - Subcategory	IAM - Overly Permissive
Provider	AWS
Severity	HIGH
Framework	Terraform, Terraform Plan

Impact

It is generally a best practice to restrict access to Amazon Simple Queue Service (SQS) queues to only the specific services or principals that require access. This can help to reduce the risk of unauthorized access to the data stored in your queues and protect against potential data breaches.

How to Fix

Resource: aws_sqs_queue_policy

• Arguments: Statement [source,go]

---

resource "aws_sqs_queue_policy" "test" { ... policy = <<POLICY { "Version":"2012-10-17", "Statement":[ { "Principal": "*",

• "Effect": "Deny", "Action": "sqs:SendMessage", "Resource": "${aws_sqs_queue_policy.q.arn}" } ] } POLICY }

---