Skip to content

anyshift-io/sre-skills / skills/s3-estate-calibration-auditor

s3-estate-calibration-auditor

Verified

FileKindSize
FAILURE_MODES.mdmarkdown7.5 KB
SKILL.mdskill md22.5 KB
fixtures/01-media-platform-clean/01-acme-media-thumbnails/bucket-acl.jsonconfig531 B
fixtures/01-media-platform-clean/01-acme-media-thumbnails/meta.jsonconfig127 B
fixtures/01-media-platform-clean/01-acme-media-thumbnails/public-access-block.jsonconfig121 B
fixtures/01-media-platform-clean/02-acme-media-origin/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/02-acme-media-origin/bucket-policy.jsonconfig266 B
fixtures/01-media-platform-clean/02-acme-media-origin/meta.jsonconfig129 B
fixtures/01-media-platform-clean/02-acme-media-origin/public-access-block.jsonconfig120 B
fixtures/01-media-platform-clean/03-acme-media-shared-config/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/03-acme-media-shared-config/bucket-policy.jsonconfig451 B
fixtures/01-media-platform-clean/03-acme-media-shared-config/meta.jsonconfig127 B
fixtures/01-media-platform-clean/03-acme-media-shared-config/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/04-acme-media-uploads/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/04-acme-media-uploads/meta.jsonconfig103 B
fixtures/01-media-platform-clean/04-acme-media-uploads/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/05-acme-media-transcode-tmp/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/05-acme-media-transcode-tmp/meta.jsonconfig85 B
fixtures/01-media-platform-clean/05-acme-media-transcode-tmp/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/06-acme-media-cdn-logs/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/06-acme-media-cdn-logs/bucket-policy.jsonconfig378 B
fixtures/01-media-platform-clean/06-acme-media-cdn-logs/meta.jsonconfig102 B
fixtures/01-media-platform-clean/06-acme-media-cdn-logs/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/07-acme-media-office-exports/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/07-acme-media-office-exports/bucket-policy.jsonconfig433 B
fixtures/01-media-platform-clean/07-acme-media-office-exports/meta.jsonconfig138 B
fixtures/01-media-platform-clean/07-acme-media-office-exports/public-access-block.jsonconfig121 B
fixtures/01-media-platform-clean/08-acme-media-delivery-ap/access-points.jsonconfig725 B
fixtures/01-media-platform-clean/08-acme-media-delivery-ap/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/08-acme-media-delivery-ap/meta.jsonconfig141 B
fixtures/01-media-platform-clean/08-acme-media-delivery-ap/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/09-acme-media-archive/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/09-acme-media-archive/meta.jsonconfig72 B
fixtures/01-media-platform-clean/09-acme-media-archive/public-access-block.jsonconfig119 B
fixtures/01-media-platform-clean/10-acme-media-staging/bucket-acl.jsonconfig373 B
fixtures/01-media-platform-clean/10-acme-media-staging/meta.jsonconfig102 B
fixtures/01-media-platform-clean/10-acme-media-staging/public-access-block.jsonconfig120 B
fixtures/01-media-platform-clean/meta.jsonconfig376 B
fixtures/02-data-lake-clean/01-acme-lake-raw/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/01-acme-lake-raw/meta.jsonconfig59 B
fixtures/02-data-lake-clean/01-acme-lake-raw/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/02-acme-lake-curated/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/02-acme-lake-curated/bucket-policy.jsonconfig497 B
fixtures/02-data-lake-clean/02-acme-lake-curated/meta.jsonconfig122 B
fixtures/02-data-lake-clean/02-acme-lake-curated/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/03-acme-lake-glue-scripts/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/03-acme-lake-glue-scripts/meta.jsonconfig68 B
fixtures/02-data-lake-clean/03-acme-lake-glue-scripts/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/04-acme-lake-athena-results/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/04-acme-lake-athena-results/bucket-policy.jsonconfig270 B
fixtures/02-data-lake-clean/04-acme-lake-athena-results/meta.jsonconfig136 B
fixtures/02-data-lake-clean/04-acme-lake-athena-results/public-access-block.jsonconfig120 B
fixtures/02-data-lake-clean/05-acme-lake-emr-logs/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/05-acme-lake-emr-logs/bucket-policy.jsonconfig376 B
fixtures/02-data-lake-clean/05-acme-lake-emr-logs/meta.jsonconfig76 B
fixtures/02-data-lake-clean/05-acme-lake-emr-logs/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/06-acme-lake-export/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/06-acme-lake-export/bucket-policy.jsonconfig416 B
fixtures/02-data-lake-clean/06-acme-lake-export/meta.jsonconfig119 B
fixtures/02-data-lake-clean/06-acme-lake-export/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/07-acme-lake-quarantine/bucket-acl.jsonconfig531 B
fixtures/02-data-lake-clean/07-acme-lake-quarantine/meta.jsonconfig117 B
fixtures/02-data-lake-clean/07-acme-lake-quarantine/public-access-block.jsonconfig121 B
fixtures/02-data-lake-clean/08-acme-lake-checkpoints/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/08-acme-lake-checkpoints/meta.jsonconfig67 B
fixtures/02-data-lake-clean/08-acme-lake-checkpoints/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/09-acme-lake-models/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/09-acme-lake-models/meta.jsonconfig62 B
fixtures/02-data-lake-clean/09-acme-lake-models/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/10-acme-lake-feature-store/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/10-acme-lake-feature-store/meta.jsonconfig69 B
fixtures/02-data-lake-clean/10-acme-lake-feature-store/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/11-acme-lake-tmp/bucket-acl.jsonconfig373 B
fixtures/02-data-lake-clean/11-acme-lake-tmp/meta.jsonconfig59 B
fixtures/02-data-lake-clean/11-acme-lake-tmp/public-access-block.jsonconfig119 B
fixtures/02-data-lake-clean/meta.jsonconfig295 B
fixtures/03-saas-tenancy-clean/01-acme-tenant-assets/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/01-acme-tenant-assets/bucket-policy.jsonconfig445 B
fixtures/03-saas-tenancy-clean/01-acme-tenant-assets/meta.jsonconfig121 B
fixtures/03-saas-tenancy-clean/01-acme-tenant-assets/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/02-acme-tenant-uploads/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/02-acme-tenant-uploads/meta.jsonconfig65 B
fixtures/03-saas-tenancy-clean/02-acme-tenant-uploads/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/03-acme-tenant-billing/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/03-acme-tenant-billing/bucket-policy.jsonconfig378 B
fixtures/03-saas-tenancy-clean/03-acme-tenant-billing/meta.jsonconfig77 B
fixtures/03-saas-tenancy-clean/03-acme-tenant-billing/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/04-acme-tenant-partner-feed/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/04-acme-tenant-partner-feed/bucket-policy.jsonconfig432 B
fixtures/03-saas-tenancy-clean/04-acme-tenant-partner-feed/meta.jsonconfig119 B
fixtures/03-saas-tenancy-clean/04-acme-tenant-partner-feed/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/05-acme-tenant-exports/bucket-acl.jsonconfig531 B
fixtures/03-saas-tenancy-clean/05-acme-tenant-exports/meta.jsonconfig116 B
fixtures/03-saas-tenancy-clean/05-acme-tenant-exports/public-access-block.jsonconfig121 B
fixtures/03-saas-tenancy-clean/06-acme-tenant-config/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/06-acme-tenant-config/bucket-policy.jsonconfig260 B
fixtures/03-saas-tenancy-clean/06-acme-tenant-config/meta.jsonconfig120 B
fixtures/03-saas-tenancy-clean/06-acme-tenant-config/public-access-block.jsonconfig120 B
fixtures/03-saas-tenancy-clean/07-acme-tenant-backups/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/07-acme-tenant-backups/meta.jsonconfig65 B
fixtures/03-saas-tenancy-clean/07-acme-tenant-backups/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/08-acme-tenant-logs/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/08-acme-tenant-logs/meta.jsonconfig62 B
fixtures/03-saas-tenancy-clean/08-acme-tenant-logs/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/09-acme-tenant-search-index/bucket-acl.jsonconfig373 B
fixtures/03-saas-tenancy-clean/09-acme-tenant-search-index/meta.jsonconfig70 B
fixtures/03-saas-tenancy-clean/09-acme-tenant-search-index/public-access-block.jsonconfig119 B
fixtures/03-saas-tenancy-clean/meta.jsonconfig287 B
fixtures/04-backup-estate-clean/01-acme-backup-daily/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/01-acme-backup-daily/meta.jsonconfig63 B
fixtures/04-backup-estate-clean/01-acme-backup-daily/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/02-acme-backup-weekly/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/02-acme-backup-weekly/meta.jsonconfig64 B
fixtures/04-backup-estate-clean/02-acme-backup-weekly/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/03-acme-backup-snapshots/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/03-acme-backup-snapshots/bucket-policy.jsonconfig264 B
fixtures/04-backup-estate-clean/03-acme-backup-snapshots/meta.jsonconfig123 B
fixtures/04-backup-estate-clean/03-acme-backup-snapshots/public-access-block.jsonconfig120 B
fixtures/04-backup-estate-clean/04-acme-backup-db-dumps/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/04-acme-backup-db-dumps/bucket-policy.jsonconfig380 B
fixtures/04-backup-estate-clean/04-acme-backup-db-dumps/meta.jsonconfig78 B
fixtures/04-backup-estate-clean/04-acme-backup-db-dumps/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/05-acme-backup-restore-stage/bucket-acl.jsonconfig531 B
fixtures/04-backup-estate-clean/05-acme-backup-restore-stage/meta.jsonconfig122 B
fixtures/04-backup-estate-clean/05-acme-backup-restore-stage/public-access-block.jsonconfig121 B
fixtures/04-backup-estate-clean/06-acme-backup-office-share/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/06-acme-backup-office-share/bucket-policy.jsonconfig428 B
fixtures/04-backup-estate-clean/06-acme-backup-office-share/meta.jsonconfig120 B
fixtures/04-backup-estate-clean/06-acme-backup-office-share/public-access-block.jsonconfig121 B
fixtures/04-backup-estate-clean/07-acme-backup-config/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/07-acme-backup-config/meta.jsonconfig64 B
fixtures/04-backup-estate-clean/07-acme-backup-config/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/08-acme-backup-vault/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/08-acme-backup-vault/meta.jsonconfig63 B
fixtures/04-backup-estate-clean/08-acme-backup-vault/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/09-acme-backup-archive-glacier/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/09-acme-backup-archive-glacier/meta.jsonconfig73 B
fixtures/04-backup-estate-clean/09-acme-backup-archive-glacier/public-access-block.jsonconfig119 B
fixtures/04-backup-estate-clean/10-acme-backup-test-restore/bucket-acl.jsonconfig373 B
fixtures/04-backup-estate-clean/10-acme-backup-test-restore/meta.jsonconfig70 B
fixtures/04-backup-estate-clean/10-acme-backup-test-restore/public-access-block.jsonconfig120 B
fixtures/04-backup-estate-clean/meta.jsonconfig295 B
fixtures/05-logging-estate-needle/01-acme-log-app/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/01-acme-log-app/meta.jsonconfig58 B
fixtures/05-logging-estate-needle/01-acme-log-app/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/02-acme-log-access/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/02-acme-log-access/meta.jsonconfig61 B
fixtures/05-logging-estate-needle/02-acme-log-access/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/03-acme-log-cloudtrail/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/03-acme-log-cloudtrail/bucket-policy.jsonconfig378 B
fixtures/05-logging-estate-needle/03-acme-log-cloudtrail/meta.jsonconfig77 B
fixtures/05-logging-estate-needle/03-acme-log-cloudtrail/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/04-acme-log-vpc-flow/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/04-acme-log-vpc-flow/meta.jsonconfig63 B
fixtures/05-logging-estate-needle/04-acme-log-vpc-flow/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/05-acme-log-elb/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/05-acme-log-elb/bucket-policy.jsonconfig254 B
fixtures/05-logging-estate-needle/05-acme-log-elb/meta.jsonconfig124 B
fixtures/05-logging-estate-needle/05-acme-log-elb/public-access-block.jsonconfig120 B
fixtures/05-logging-estate-needle/06-acme-log-shipping/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/06-acme-log-shipping/bucket-policy.jsonconfig387 B
fixtures/05-logging-estate-needle/06-acme-log-shipping/meta.jsonconfig215 B
fixtures/05-logging-estate-needle/06-acme-log-shipping/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/07-acme-log-waf/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/07-acme-log-waf/meta.jsonconfig58 B
fixtures/05-logging-estate-needle/07-acme-log-waf/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/08-acme-log-cloudfront/bucket-acl.jsonconfig531 B
fixtures/05-logging-estate-needle/08-acme-log-cloudfront/meta.jsonconfig116 B
fixtures/05-logging-estate-needle/08-acme-log-cloudfront/public-access-block.jsonconfig121 B
fixtures/05-logging-estate-needle/09-acme-log-archive/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/09-acme-log-archive/meta.jsonconfig62 B
fixtures/05-logging-estate-needle/09-acme-log-archive/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/10-acme-log-metrics/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/10-acme-log-metrics/meta.jsonconfig62 B
fixtures/05-logging-estate-needle/10-acme-log-metrics/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/11-acme-log-audit/bucket-acl.jsonconfig373 B
fixtures/05-logging-estate-needle/11-acme-log-audit/bucket-policy.jsonconfig406 B
fixtures/05-logging-estate-needle/11-acme-log-audit/meta.jsonconfig117 B
fixtures/05-logging-estate-needle/11-acme-log-audit/public-access-block.jsonconfig119 B
fixtures/05-logging-estate-needle/meta.jsonconfig403 B
fixtures/06-analytics-estate-needle/01-acme-analytics-events-org/bucket-acl.jsonconfig373 B
fixtures/06-analytics-estate-needle/01-acme-analytics-events-org/bucket-policy.jsonconfig453 B
fixtures/06-analytics-estate-needle/01-acme-analytics-events-org/meta.jsonconfig128 B
fixtures/06-analytics-estate-needle/01-acme-analytics-events-org/public-access-block.jsonconfig119 B
fixtures/06-analytics-estate-needle/02-acme-analytics-dashboards/bucket-acl.jsonconfig373 B
fixtures/06-analytics-estate-needle/02-acme-analytics-dashboards/meta.jsonconfig71 B
fixtures/06-analytics-estate-needle/02-acme-analytics-dashboards/public-access-block.jsonconfig119 B
fixtures/06-analytics-estate-needle/03-acme-analytics-partner-extract/bucket-acl.jsonconfig373 B
fixtures/06-analytics-estate-needle/03-acme-analytics-partner-extract/bucket-policy.jsonconfig444 B
fixtures/06-analytics-estate-needle/03-acme-analytics-partner-extract/meta.jsonconfig125 B
fixtures/06-analytics-estate-needle/03-acme-analytics-partner-extract/public-access-block.jsonconfig121 B
fixtures/06-analytics-estate-needle/04-acme-analytics-reports/bucket-acl.jsonconfig373 B
fixtures/06-analytics-estate-needle/04-acme-analytics-reports/bucket-policy.jsonconfig384 B
fixtures/06-analytics-estate-needle/04-acme-analytics-reports/meta.jsonconfig80 B
fixtures/06-analytics-estate-needle/04-acme-analytics-reports/public-access-block.jsonconfig119 B
fixtures/06-analytics-estate-needle/05-acme-analytics-clickstream/bucket-acl.jsonconfig373 B
fixtures/06-analytics-estate-needle/05-acme-analytics-clickstream/bucket-policy.jsonconfig269 B
fixtures/06-analytics-estate-needle/05-acme-analytics-clickstream/meta.jsonconfig275 B
fixtures/06-analytics-estate-needle/05-acme-analytics-clickstream/public-access-block.jsonconfig122 B
fixtures/06-analytics-estate-needle/06-acme-analytics-ml-features/bucket-acl.jsonconfig373 B

FAILURE_MODES.md

View on GitHub
# Failure modes: s3-estate-calibration-auditor

This skill composes the effective public/cross-account verdict across each bucket's four
config layers and rolls them up into an estate verdict. It is correct for what those configs
express and wrong in the predictable ways below. Read this before acting on a finding.

## 1. Effective exposure is not exploitability

A LIVE finding means a real public or cross-account grant survives the layer that would
neutralise it. It does **not** mean data is actually exposed or that the grant is reachable.
Each of these breaks an exposure-on-paper without changing a single bucket-config line:

- **No CDN context.** A bucket can be private while its objects are served publicly through a
  CloudFront distribution with Origin Access Control, and a flagged public bucket may sit
  behind a CDN that adds its own controls. The skill does not read the distribution.
- **The trusted principal does nothing.** A cross-account grant only matters in proportion to
  what the trusted account/role can do with it and whether it re-shares onward, neither of
  which is in this bucket config.
- **Data sensitivity.** A public or cross-account read on a bucket of public marketing assets
  is not the same finding as one on a bucket of PII; the config cannot tell you which.

The boundary section of every audit names these. A LIVE finding is a hypothesis to confirm
against the live estate, not a proven breach.

## 2. "Clean" means neutralised today, not safe

A clean verdict (no LIVE bucket) means every exposed-looking bucket is neutralised by BPA
(`IgnorePublicAcls` / `RestrictPublicBuckets` / `BlockPublicPolicy`) or scoped by a Condition.
It does **not** prove the estate is safe:

- The neutralisation depends on **account-level and bucket-level BPA staying on**. Turning a
  BPA switch off re-arms every POLICY-PUBLIC-BLOCKED and ACL-PUBLIC-IGNORED bucket into a live
  public bucket. Clean is one toggle away from exposed.
- A **per-object public ACL** (section 4) can make an object public even when the bucket is
  clean.
- A scoped grant's safety rests on the **condition value** being the intended one; a stale
  `aws:SourceIp` CIDR or a wrong org id is still scoped, just to the wrong scope.

The clean verdict always ships with the boundary, for exactly this reason. Do not read "clean"
as "audited and proven private."

## 3. BPA neutralisation is asymmetric, and it is easy to over-apply

BPA neutralises **public** grants and **only** public grants. The two mistakes:

- **Clearing on BPA-all-on alone.** Seeing all four BPA switches on and concluding the bucket
  is locked down is wrong: a cross-account bucket policy (XACCT-POLICY) and a cross-account
  canonical-user ACL (XACCT-ACL) are fully live with BPA all on. This is exactly how the
  needle hides on the logging and partner-share estates.
- **Condemning on Principal '*' alone.** Seeing a Principal '*' and calling the bucket public
  is wrong when `RestrictPublicBuckets` / `BlockPublicPolicy` is on (POLICY-PUBLIC-BLOCKED) or
  when a narrowing Condition scopes it (COND-SCOPED). `IgnorePublicAcls` kills the AllUsers
  group but not a named canonical user; `BlockPublicAcls` blocks only *new* public ACLs, not
  the existing grant. Reading the wrong BPA switch as the neutraliser produces the wrong
  verdict.

## 4. Only the four bucket-config layers are in scope

The verdict is composed from exactly four inputs per bucket: `public-access-block.json`,
`bucket-policy.json`, `bucket-acl.json`, `access-points.json`. Outside that set:

- **Per-object ACLs** are not the bucket config. An object can be public-read while the bucket
  is private; this skill cannot see it.
- **CloudFront / CDN fronting, VPC-endpoint policies, and org SCPs** can add or remove access
  this config does not show. A bucket that looks private to this skill may be served publicly
  by a CDN; one that looks open may be capped by an SCP.
- **Account-level BPA** (as opposed to the per-bucket BPA in the fixture) can neutralise a
  grant the bucket config alone reports as live. If only the bucket-level config is supplied,
  the verdict is for that config.

## 5. The needle is one bucket; do not stop at the first one

On a needle estate exactly one bucket is live among many neutralised/scoped lookalikes. Two
symmetric mistakes:

- **Missing it** by reading each bucket's most prominent layer in isolation (the cross-account
  needle hides behind BPA-all-on; the public needle hides among conditional siblings; the
  cross-account ACL hides among ignored AllUsers grants).
- **Over-flagging the siblings** by calling the neutralised/scoped lookalikes live, which
  buries the real finding in noise. The estate verdict is "clean iff no bucket is live" and
  "the needle is the one live bucket"; both halves are load-bearing.

Process every bucket; do not generalise from the first two or three.

## 6. The estate config is what was supplied, not the whole account

The estate verdict is over the buckets and layers handed to the audit. If a bucket was omitted,
or a layer (its policy, its ACL, its access points) was not supplied, a real live grant or a
neutralising BPA setting may be missing, and the verdict is incomplete. A clean estate means
"clean across the configs supplied," not "this account has no public bucket." Escalate to a
human when the estate inventory is uncertain, when a flagged cross-account or public grant
needs a business-intent decision (is the trust deliberate, is the public read intended), or
when closing a boundary join (per-object ACLs, the CDN, the trusted account's privileges)
requires reads this skill does not perform.

## 7. Residual over-flag variance on neutralised buckets (measured)

This is a measured reliability limit of the agent applying the skill, not a gap in the
methodology, and it does not fully close with prompting or a deterministic decode. On a minority
of runs the agent reports a **neutralised** bucket as live — typically by asserting
`IgnorePublicAcls: false` (and thus an `ACL-PUBLIC` finding) when the actual config says
`true`. The misread happens *inside* the step-1 mitigations (read the boolean verbatim, paste
the raw `public-access-block.json` block) and persists at temperature 0: the value is
hallucinated within the pasted block.

What measurably triggers it: a bucket that carries an `AllUsers` / `AuthenticatedUsers` ACL
grant, especially with a name that suggests exposure (`exports`, `public`, `share`, `partner`,
`cdn`). The name plus the grant primes "this is the exposed one," and the boolean is then read
to fit that expectation.

Scale, from the control/treatment eval (temperature 0, 3 trials/fixture): the skill lifts the
"does not over-flag the neutralised baits" item from a control pass rate of **0.00** to **0.76**
— a large, real improvement, but not 1.0. Six of seven estates land at or near a clean 7/7;
the over-flag surfaces intermittently across the deceptive-clean estates and most frequently on
`03-saas-tenancy` (the `acme-tenant-exports` bucket), which oscillates between 7/7 and a
false-positive ~3/7. The deterministic reference engine is always correct; the variance is in
the model's transcription of the boolean.

Operational guidance: when this skill reports a bucket as live `ACL-PUBLIC` or `POLICY-PUBLIC`,
**re-read that bucket's `public-access-block.json` directly** before acting — confirm the
quoted `IgnorePublicAcls` / `RestrictPublicBuckets` value against the source. A single live
finding on a shareable-sounding bucket with an `AllUsers` grant is the case most worth
double-checking, precisely because it is the case the model is most likely to get wrong.
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: 472kUpdated 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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated 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: 196kUpdated Claude CodeCodexVerifiedInstall