ShopifySimar SinghProblem & solution
Building Overexposed: understanding application exposure (2026) - Shopify
Summary
Shopify built Overexposed, a scanner that checks which applications have internet-facing endpoints and whether they allow anonymous access. It scans Kubernetes Ingresses on GKE and Cloud Run services by querying GCP’s Cloud Asset Inventory for deployed resources, then sending anonymous HTTP probes—HEAD requests first, up to three redirects, checking for authentication challenges. The scanner classifies each endpoint into six verdicts—exposed, expected, protected, not found, unreachable, or inconclusive—based on the probe response and an allowlist of approved public endpoints. Overexposed reduced inconclusive Ingress results by about 80% within weeks by refining classification rules and testing changes against historical scan data. The project revealed that reading configuration files is insufficient because they show intent, not enforcement; the true inventory must come from what the cloud actually runs, and each verdict includes a reason for investigation.
Context
Shopify needed to track which applications have internet-facing endpoints and whether they allow anonymous access, across many teams and cloud services. Reading configuration files from repositories proved unreliable because they show intent, not enforcement, leading to false alarms, misses, and blind spots.
Approach / What changed
Overexposed uses GCP’s Cloud Asset Inventory to find deployed Kubernetes Ingresses and Cloud Run services, then sends anonymous HTTP probes—HEAD requests first, up to three redirects—to each endpoint. It classifies responses into six verdicts using a rule table and an allowlist of approved public endpoints. It protects against SSRF by checking hostnames and IPs, rejecting private addresses, and restricting network access. Mutation testing and canary targets validate classification rules.
Takeaways
Reading configuration files from repositories is insufficient because they show intent, not enforcement; the true inventory must come from what the cloud actually runs after admission controllers.
A single HTTP status code can have different meanings depending on the service type; for example, a 404 behind an Ingress means the path doesn’t exist, but on Cloud Run it may come from Google’s front end before the app runs.
Overexposed reduced inconclusive Ingress results by about 80% within weeks by grouping results by reason, adding clearer verdicts like not found and unreachable, and testing rule changes against saved historical results.
FAQ
How does Overexposed find internet-facing services?
It uses GCP's Cloud Asset Inventory API to find deployed Kubernetes Ingresses and Cloud Run services, rather than reading configuration files from repositories. This gives the true inventory of what the cloud actually runs after admission controllers.
What verdicts does Overexposed assign?
Six verdicts: exposed, expected, protected, not found, unreachable, and inconclusive. The verdict depends on the probe response, the service type, and whether the endpoint is on an approved allowlist.
How does Overexposed protect against SSRF?
It checks each hostname and IP address from DNS, rejects private and loopback addresses, connects directly to the checked IP without re-resolving DNS, and restricts the scanner's network access to block internal services and cloud metadata endpoints.
Source and freshness
- Source
- shopify.engineering
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.