GCS Bucket CORS Not Configured
Browsers refuse cross-origin requests to this bucket, so a web app that depends on it fails in a way that looks like a bug in the app.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Configure CORS on GCS bucket.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- GCS Buckets on Google Cloud
- The fix, by hand
- Determine whether the resource serves content directly to browsers (signed-URL downloads, static hosting). If not, an empty CORS config is correct.
- Inventory the exact origins, methods, and headers your frontend needs.
- Write a minimal cors.json:.
- Apply: gcloud storage buckets update gs://‹name› --cors-file=cors.json (or gsutil cors set cors.json gs://‹name›).
- Test from the browser dev tools network tab. Preflight OPTIONS should return 200 with the expected ACA-* headers.
- Never use "origin": ["*"] on a bucket holding non-public data.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1230- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.