K8s zero-day
Kubernetes zero-day is the zero-day-affected-container-count collection
for this CID — FindContainersCountAffectedByZeroDayVulnerabilities. The path is
GET /container-security/aggregates/containers/count-by-zero-day/v1.
Remaining Kubernetes Protection mutations /
Image assessment policies / remaining cloud are not implemented (not yet). This is not
Container vulnerabilities ReadCombinedVulnerabilities
(/container-security/combined/vulnerabilities/v1):
Container vulnerabilities. This is not
Kubernetes runtimes FindContainersByContainerRunTimeVersion
(/container-security/aggregates/containers/find-by-runtimeversion/v1):
K8s runtimes. This is not the HelloService
template sample (GET /api/hello).
This collection is not CrowdStrike production. It does not call Falcon cloud. It is not CrowdStrike Falcon Container Image cloud.
RPC field notes: ContainerImagesService. REST schemas: API reference. Filter syntax: FQL. Kubernetes zero-day does use FQL (unlike Kubernetes clusters and combined cloud clusters).
These curls use Host: crowdstrike-api.localhost against Compose
Traefik on :8088. If the hostname already resolves to Traefik, you can
omit the Host header and call http://crowdstrike-api.localhost instead.
Auth
Every call needs a console session or a Bearer token:
- Cookie
cs_consolefromCreateSession(POST /identity/entities/sessions/v1) Authorization: Bearerwithfalcon-container-image:read
A session cookie bypasses OAuth scopes. Seed client cs-local-hosts
(hosts:read only) cannot list zero-day counts (403) — it is missing
falcon-container-image:read. Unit tests use a client named
cs-local-cimg with falcon-container-image:read; that client can
list zero-day counts. It is not in the production seed. Use the
console cookie, or a client you created with that scope. Missing or
revoked token → 401. This RPC does not use
kubernetes-protection:read.
HTTP paths
| Method | Path | Use |
|---|---|---|
GET | /container-security/aggregates/containers/count-by-zero-day/v1 | List zero-day affected container counts. Query: filter, limit, offset. |
Empty filter returns every zero-day count row in this CID. Allowed FQL
properties: label, cid. Unknown
property or invalid filter → 400. limit and offset must be ≥ 0
else 400. Omitted limit defaults to 100 (capped at 200).
Empty sort is ignored. Default sort is label.asc.
JSON is DESIGN snake_case flattened fields (three fields this
slice): label, count, cid.
This is not Container vulnerabilities ReadCombinedVulnerabilities, Kubernetes
runtimes FindContainersByContainerRunTimeVersion, or the HelloService
template. Container vulnerabilities uses
/container-security/combined/vulnerabilities/v1:
Container vulnerabilities. Kubernetes runtimes uses
/container-security/aggregates/containers/find-by-runtimeversion/v1:
K8s runtimes. Remaining Kubernetes Protection mutations /
Image assessment policies / remaining cloud are not implemented (not yet).
Seed zero-day counts
label | count |
|---|---|
none | 0 |
zero-day | 2 |
cid is cid-local-1. Empty filters return both (label ASC:
none then zero-day). filter=label:'zero-day' returns
zero-day (count 2). filter=label:'none' returns
none (count 0).
Session cookie
curl -sS -c cookies.txt -H 'Host: crowdstrike-api.localhost' \
-H 'Content-Type: application/json' \
-d '{"email":"[email protected]","password":"FalconLocal!1","cloud":"us-1"}' \
http://127.0.0.1:8088/identity/entities/sessions/v1
List zero-day counts (cookie)
Empty filters return at least the two seed labels, including
none and zero-day:
curl -sS -H 'Host: crowdstrike-api.localhost' -b cookies.txt \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1'
filter=label:'zero-day' returns zero-day (count 2):
curl -sS -H 'Host: crowdstrike-api.localhost' -b cookies.txt \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1?filter=label:%27zero-day%27'
Unknown FQL property is 400:
curl -sS -o /dev/null -w '%{http_code}\n' \
-H 'Host: crowdstrike-api.localhost' -b cookies.txt \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1?filter=bogus:%27x%27'
No cookie and no Bearer is 401:
curl -sS -o /dev/null -w '%{http_code}\n' \
-H 'Host: crowdstrike-api.localhost' \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1'
cs-local-hosts (hosts:read only, missing
falcon-container-image:read) is 403:
TOKEN='<access_token from cs-local-hosts>'
curl -sS -o /dev/null -w '%{http_code}\n' \
-H 'Host: crowdstrike-api.localhost' \
-H "Authorization: Bearer ${TOKEN}" \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1'
Remaining Kubernetes Protection mutations /
Image assessment policies / remaining cloud are not implemented (not yet). Container vulnerabilities is a
separate collection:
Container vulnerabilities. Kubernetes runtimes is a
separate collection:
K8s runtimes. This is not
the HelloService template (GET /api/hello).
List (Bearer)
TOKEN='<access_token from a client with falcon-container-image:read>'
curl -sS -H 'Host: crowdstrike-api.localhost' \
-H "Authorization: Bearer ${TOKEN}" \
'http://127.0.0.1:8088/container-security/aggregates/containers/count-by-zero-day/v1'
falcon-container-image:read → 200 (including unit-test client
cs-local-cimg). A token without that scope (including hosts:read
only, e.g. cs-local-hosts) → 403. Missing or revoked token →
401. This RPC does not use kubernetes-protection:read.
OAuth2 mint/revoke: OAuth2. Accessible scopes: API clients.