KubeBolt docs
ENES GitHub

Security

Security and compliance

Four finding lenses plus a runtime feed, fed by Trivy, Kyverno and Falco. What each one ingests, what becomes a finding, what it needs to work, and where detection stops.

On this page
  1. The four lenses
  2. The runtime feed
  3. What becomes a finding
  4. What it needs
  5. Wiring the sources
  6. Retention
  7. Security email on Cloud
  8. What is not here yet

KubeBolt does not scan your cluster itself. It reads the scanners you already run — or install in one command — normalizes their output onto one severity scale, and gives it a lifecycle: a stable identity across rollouts, a first-seen clock, and resolution when the problem stops being observed.

Scope, plainly. This is detection and posture, not automatic remediation. KubeBolt tells you what is wrong, which workload owns it, and what the remedy is. It does not patch images, rewrite manifests, or enforce policy — enforcement lives in Kyverno, patching lives in your pipeline.

The four lenses

Security in the sidebar opens Security & Compliance. It splits findings into four lenses. Each is a different question with a different fix, so they are never summed into one ranked list.

Security & Compliance: findings grouped per workload, not per scanner.
Security & Compliance: findings grouped per workload, not per scanner. KubeBolt 2.1.1
LensThe questionFed by
VulnerabilitiesWhat CVEs and exposed secrets are in the images we run?Trivy: VulnerabilityReport, ExposedSecretReport
ConfigurationWhat is misconfigured or violates policy?Trivy: ConfigAuditReport. Kyverno: PolicyReport, ClusterPolicyReport
PermissionsWhich Roles and ClusterRoles grant too much?Trivy: RbacAssessmentReport, ClusterRbacAssessmentReport
ComplianceWhich controls of a benchmark are failing?Trivy: ClusterComplianceReport (the CIS benchmark and any other spec the operator runs)

The page is fleet-wide: it reads every cluster you may see, not the cluster selected in the top bar. With more than one cluster, a selector next to the title narrows it to one.

The list you act on is workloads, not findings — Roles under Permissions, controls under Compliance. Hundreds of findings usually collapse to a couple of dozen workloads, and a workload is what actually gets changed. The finding-level counts stay on the card row above it: open criticals, the workloads affected (roles, on the Permissions lens), the share of findings with a published fix, and runtime threats in the last 24 hours. The criticals card carries the verdict in its color — red while any critical is open, amber with only highs, green with neither. The runtime-threats card is the one that lights red, whenever Falco reported anything in the last 24 hours.

Between the cards and the tabs, a By source row says what each scanner contributes across all lenses: Trivy CVEs, CIS controls failing, Kyverno violations and Falco threats in the last 24 hours. It sits above the tabs because “which of my scanners are reporting” does not change when you switch lens. The line under the title sums it up as N of 4 sources with findings.

The runtime feed

Runtime is the fifth tab and is not a lens. It is a stream of Falco events, stored separately from findings, and it behaves differently on purpose:

The tab shows the last 24 hours, up to the most recent 500 events: a priority breakdown, the Top 5 rules by hits, and one row per event with the rule and command, the file it touched, the pod (or the node, for a host-level rule), the user and the time.

Kobi reads all of this too: get_findings for the posture, get_finding_detail to re-read one finding live from the scanner, get_finding_workloads to get them grouped by workload with exposed secrets first, and get_runtime_events for what Falco saw processes actually do (24 hours by default, up to 720). See Kobi Copilot.

What becomes a finding

Every scanner reports more than is worth acting on. The gates are deliberate and differ per source:

SourceIngestedDropped
Trivy CVEsCRITICAL, HIGHMEDIUM, LOW, UNKNOWN — thousands of rows nobody finishes reading
Trivy config auditCRITICAL, HIGH, MEDIUMLOW — mostly “runs with a low UID” and “no CPU/memory limit”, which KubeBolt already raises as a capacity insight
Trivy RBAC assessmentCRITICAL, HIGH, MEDIUMLOW, and Kubernetes’ own bootstrap roles (system:*, cluster-admin, admin, edit, view), which the control plane reconciles back if you edit them
Trivy exposed secretsEvery severity — no gateNothing. The matched text is never stored: the finding says where, never what
Trivy complianceFailing controlsPassing controls produce nothing
Kyverno (PolicyReports)result: failpass, skip, warn, and error (an engine hiccup is not the workload’s fault)

Note the asymmetry between the CVE gate and the policy gate. A CVE with no severity label is dropped; a policy violation with no severity label becomes a medium finding. A policy is not a fact of nature — someone wrote it on purpose, so a failure matters even when nobody said how much. A failing compliance control keeps its severity when it is CRITICAL or HIGH and is filed as medium otherwise.

Exposed secrets are counted apart from CVEs: a credential baked into an image is not a dependency to upgrade.

A finding’s identity is its source, kind, title and resource. Trivy reports against the ReplicaSet; KubeBolt files the finding under the owning Deployment, so a rollout does not reset its age. A finding is resolved when a complete sweep no longer reports it. If any report type fails to list on a pass — CRD missing, permission denied, a timeout — nothing is resolved from that pass, because a partial view cannot prove anything is gone. A cluster KubeBolt is not connected to keeps its findings as they were until it comes back.

What it needs

On Cloud the first two are already true: clusters connect through the agent, whose default tier covers the sweep.

Wiring the sources

Three pages, one each:

Each scanner is detected by its pods, by label with a namespace fallback (the exact labels are on each page). The result is a card under Administration → Agents & Ingest → Integrations, for the cluster selected in the top bar: Installed, Degraded (pods present but not all Ready), Not installed, or Unknown (KubeBolt could not list pods). The card says the scanner runs; the By source row on the Security page says it reports. KubeBolt does not install the scanners: the Integrations page has no Install button for them.

Scanner sources are swept every 10 minutes, and once at boot as soon as a cluster is connected. Falco events arrive as Falco pushes them.

Retention

Security findings and runtime events share one horizon. Active findings never expire; a resolved finding is deleted once it has been resolved for longer than the horizon, and a runtime event once it is older than it. Cleanup rides the hourly retention pass.

In the open-source edition the horizon is KUBEBOLT_FINDINGS_RETENTION_HORIZON, default 720h (30 days). The Helm chart has no dedicated value for it; set it through extraEnv — see Environment variables.

On Cloud the window is a plan dimension:

PlanRetention
Free15 days
Team30 days
Business90 days
Enterprise365 days

Security email on Cloud

On Cloud, findings also reach people by email. The open-source edition does not send these.

From the Team plan up, “security” is the organization’s security destination — Administration → System → Notifications → Security destination, typically a distribution list — or the organization admins while none is set. On Free, the team is security. Both messages obey the organization’s notification switches (notifications on, email channel on). See Notifications.

What is not here yet