Skip to main content

Kubernetes container compliance

Kubernetes container compliance image findings for this CID — CombinedImagesFindings (PEP 8 image_findings). The path is GET /container-compliance/combined/findings-by-images/v2.

This collection is not CrowdStrike production. It does not call Falcon cloud. It is not the image-compliance aggregate.

RPC field notes: K8sContainerComplianceService. Unused query keys filter, limit, offset, and sort are ignored.

Auth​

Every call needs a console session or a Bearer token:

  • Cookie cs_console from CreateSession (POST /identity/entities/sessions/v1)
  • Authorization: Bearer with k8s-container-compliance:read

A session cookie bypasses OAuth scopes and can list. Seed client cs-local-hosts (hosts:read only) cannot list (403 missing scope k8s-container-compliance:read). Unit tests use a client named cs-local-kcc with k8s-container-compliance:read; that client is not seeded in Compose.

HTTP paths​

Empty query params on GET return every finding in this CID. Default sort is image_id ascending. Empty store → empty resources, still 200.

JSON is snake_case MSA. Clone success is 200. This list returns image_id, image_repository, image_tag, and image_registry. Nested assessments are not returned.

The other nine collection GETs are not implemented, including node findings and the aggregate routes.

Seed findings​

List returns img-lab-1 then img-lab-2. Both use repository lab/repo and registry registry.lab. Tags are 1.0 then 2.0.

Success returns img-lab-1 then img-lab-2.

The other nine operations are not implemented (not yet). No further roadmap row. Remaining operations stay under Not yet implemented. This is not Unidentified containers and not Image compliance.