• Sources: primary
  • Summary: Shopify's first scanner read Kubernetes config from a repository. It raised false alarms, missed settings changed by admission controllers, and missed resources from other repositories. The rebuilt scanner pulls admitted Ingresses and Cloud Run services from GCP Cloud Asset Inventory and sends one anonymous request to each endpoint. It then assigns one of six verdicts with recorded evidence, checks a reviewed allowlist, and guards against SSRF by pinning resolved IPs. Shopify says replaying rule changes against saved results cut inconclusive Ingress verdicts by about 80 percent.
  • Why it matters: The post gives a concrete pattern for exposure auditing: inventory from the cloud control plane rather than the repository, and status codes read differently per platform, such as a Cloud Run 404 that says nothing about auth.