Skip to content

anyshift-io/sre-skills / skills/sqs-queue-auditor

sqs-queue-auditor

Verified

FileKindSize
FAILURE_MODES.mdmarkdown6.6 KB
README.mdmarkdown4.9 KB
SKILL.mdskill md13.3 KB
examples/01-no-dlq.mdmarkdown2.9 KB
examples/02-dlq-retention-shorter-than-source.mdmarkdown3.3 KB
examples/03-maxreceivecount-too-low.mdmarkdown2.8 KB
examples/04-poison-ages-out-before-dlq.mdmarkdown3.9 KB
examples/05-default-visibility-short-retention.mdmarkdown3.2 KB
examples/06-public-queue-policy.mdmarkdown3.6 KB
examples/07-fifo-dedup-off.mdmarkdown2.8 KB
examples/08-clean-standard.mdmarkdown2.6 KB
fixtures/01-no-dlq/queue.jsonconfig564 B
fixtures/02-dlq-retention-shorter-than-source/dlq.jsonconfig649 B
fixtures/02-dlq-retention-shorter-than-source/queue.jsonconfig632 B
fixtures/03-maxreceivecount-too-low/dlq.jsonconfig659 B
fixtures/03-maxreceivecount-too-low/queue.jsonconfig637 B
fixtures/04-poison-ages-out-before-dlq/dlq.jsonconfig663 B
fixtures/04-poison-ages-out-before-dlq/queue.jsonconfig648 B
fixtures/05-default-visibility-short-retention/dlq.jsonconfig650 B
fixtures/05-default-visibility-short-retention/queue.jsonconfig631 B
fixtures/06-public-queue-policy/dlq.jsonconfig663 B
fixtures/06-public-queue-policy/queue.jsonconfig908 B
fixtures/07-fifo-dedup-off/dlq.jsonconfig748 B
fixtures/07-fifo-dedup-off/queue.jsonconfig804 B
fixtures/08-clean-standard/dlq.jsonconfig672 B
fixtures/08-clean-standard/queue.jsonconfig1.0 KB
tests/README.mdmarkdown4.2 KB
tests/_audit.pyscript21.8 KB
tests/_replay.pyscript720 B
tests/eval/README.mdmarkdown8.4 KB
tests/eval/eval_results.jsonconfig220.4 KB
tests/eval/judge_prompt.mdmarkdown1.4 KB
tests/eval/queues.pyscript7.6 KB
tests/eval/rubric.mdmarkdown2.6 KB
tests/eval/run_eval.pyscript11.5 KB
tests/replay_01_no_dlq.pyscript1.5 KB
tests/replay_02_dlq_retention.pyscript1.5 KB
tests/replay_03_maxreceivecount.pyscript1.3 KB
tests/replay_04_poison_ages_out.pyscript1.6 KB
tests/replay_05_default_visibility.pyscript1.8 KB
tests/replay_06_public_policy.pyscript1.4 KB
tests/replay_07_fifo_dedup_off.pyscript1.4 KB
tests/replay_08_clean_standard.pyscript1.6 KB

examples/06-public-queue-policy.md

View on GitHub
# Worked example 6: open resource policy on an unencrypted queue (R7, R8)

A queue whose resource policy authorises any AWS principal to send to it, with no encryption at rest. The exposure example. Fixtures and replay test under `../fixtures/06-public-queue-policy/` and `../tests/replay_06_public_policy.py`.

## Scenario

- **Queue**: `inbound-webhooks`. Intended to receive events from one specific SNS topic.
- **Symptom**: the resource policy was written to "allow sends" during a hurried integration and never scoped. As written, anyone with an AWS account can push messages onto it.

## Step 1: parse the attributes

```
SqsManagedSseEnabled   false
Policy                 {"Version":"2012-10-17","Statement":[{"Sid":"AllowSend",
                        "Effect":"Allow","Principal":"*","Action":"sqs:SendMessage",
                        "Resource":"...:inbound-webhooks"}]}
RedrivePolicy          {"deadLetterTargetArn":"...:inbound-webhooks-dlq","maxReceiveCount":5}
```

The `Policy` is a JSON string; parsing it gives one `Allow` statement with `Principal: "*"` and **no `Condition`**.

## Step 4: audit exposure

- The statement allows `Principal: "*"` for `sqs:SendMessage` with no narrowing condition (`aws:SourceArn`, `aws:SourceAccount`, `aws:PrincipalOrgID`). That is **R7 (high)**. As written, the policy authorises any AWS principal to send to the queue: the classic confused-deputy and public-queue exposure. A queue that should only accept messages from one SNS topic accepts them from anyone, which means anyone can inject events into the webhook pipeline.
- `SqsManagedSseEnabled` is `false` and there is no `KmsMasterKeyId`, so message bodies are not encrypted at rest. That is **R8 (low)**: low because whether it matters depends on what the webhook payloads contain, which the queue does not tell you.

The contrast that matters: a wildcard principal is not automatically wrong. The standard SNS-to-SQS subscription uses `Principal: "*"` *with* an `aws:SourceArn` condition pinning it to the topic. Example 8 has exactly that pattern and the skill does not flag it. R7 fires on the missing condition, not on the wildcard.

## Steps 2-3, 5: redrive, lifecycle, FIFO

Clean. DLQ present with sane `maxReceiveCount` and good retention (no R1/R2/R3). `5 x 120 = 600s` under retention (no R4). Visibility deliberate at 120s (no R5), retention default (no R6), standard queue.

## Findings

| Code | Severity | Attribute | Fix |
|---|---|---|---|
| R7 | high | `Policy` | Add a `Condition` pinning the principal to the intended source (`aws:SourceArn` for the SNS topic), or name explicit principal ARNs instead of `"*"`. |
| R8 | low | `SqsManagedSseEnabled` / `KmsMasterKeyId` | Enable SQS-managed SSE or a KMS key unless the payloads are confirmed non-sensitive. |

## Boundary

R7 reads the resource policy. That is only half the access story.

- The effective set of principals that can act on this queue is the *union* of this resource policy and every IAM identity policy in the account. A clean resource policy would not prove the queue is private. Join: queue to the account's IAM graph.
- Whether the open policy has actually been used to inject messages is the send metrics by source principal, a time-series. Join: queue to its metrics over time.

## Why this is the R7 / R8 reference

It exercises the precision the check needs: flag the wildcard-with-no-condition, do **not** flag the wildcard-with-`SourceArn` that is the legitimate SNS pattern. And it names the boundary that keeps R7 honest: a resource-policy audit can never be a complete access audit, because identity policies live outside the queue.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall