image-sprawl

Traces a container detection to its image and maps every cluster and cloud running it.

3|1|Updated Sep 1, 2026
One-click install
npx skills add https://github.com/kyle9021/fal_con_2026_AI-Powered-Cloud-Security-Ops-Falcon-Mcp --skill image-sprawl-kyle9021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: image-sprawl
Source: https://github.com/kyle9021/fal_con_2026_AI-Powered-Cloud-Security-Ops-Falcon-Mcp/tree/main/.claude/skills/image-sprawl
Command: npx skills add https://github.com/kyle9021/fal_con_2026_AI-Powered-Cloud-Security-Ops-Falcon-Mcp --skill image-sprawl-kyle9021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A container detection looks like one compromised workload, but images get reused across namespaces, clusters, and clouds. This Skill turns a single Falcon detection into a scoped blast radius: which image caused it, where else that image runs, and what vulnerabilities it carries. ## Core Features & Use Cases - Detection-to-image pivot: Distinguishes image scan detections (cwpp) from runtime node detections and joins on agent_id to identify the exact image digest. - Cross-cluster sprawl search: Queries Falcon Kubernetes container inventory to count every running instance of the image across clusters, namespaces, and cloud accounts, flagging tag drift and cross-account sprawl. - Vulnerability assessment: Pulls CVEs for the image via falcon_search_images_vulnerabilities, sorted by CVSS score. - Evidence-backed dashboard: Renders a self-contained HTML report with verdict, metrics, tables, and full query provenance. - Use Case: A high-severity detection fires on an EKS node. Use this Skill to identify the image digest, discover it running in 34 containers across 4 clusters and 2 cloud accounts, and produce a dashboard a responder can act on in a minute. ## Quick Start Triage this container detection and show me everywhere else the same image is running across all clusters and clouds.

Frequently Asked Questions about image-sprawl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find everywhere a container image is running?▼

Search the Falcon Kubernetes container inventory with falcon_search_kubernetes_containers filtered on the image repository or digest. Aggregate results by cluster, namespace, and cloud account rather than listing raw container records.

How do I triage a Kubernetes detection in CrowdStrike Falcon?▼

First determine whether it is an image scan detection (product:'cwpp') or a runtime node detection. For runtime detections, pivot from the detection's agent_id into container inventory to identify the image, then search for that image across all clusters.

Should I join containers to hosts by hostname or agent_id?▼

Use agent_id. Hostname joins on node_name are unreliable because the same node can appear in different casings, while agent_id is the sensor's own identifier present on both records and either matches or does not.

Why does falcon_count_kubernetes_containers return a validation error?▼

On current builds the tool returns a payload its own schema rejects, producing a pydantic int_type error. Use falcon_search_kubernetes_containers and count the results yourself instead; this is a known upstream defect.

Can this Skill contain hosts or delete compromised images?▼

No. It performs read-only investigation only. Containment, pod termination, and image deletion are intentionally out of scope; the Skill hands responders decision-ready remediation options instead.

Why compare image digests instead of tags?▼

Tags are mutable: the same tag can point to different images on different clusters, and one digest can carry several tags. Digests must be normalized first, since detections report bare hex while inventory prefixes them with sha256:.