On This Page

Home / Cribl.Cloud Government/Changelog: Cribl.Cloud Government

Changelog: Cribl.Cloud Government

This page summarizes new and expanded capabilities added to Cribl.Cloud Government by release. For a full comparison of Cribl.Cloud Government and commercial Cribl.Cloud capabilities, see What’s Different in Cribl.Cloud Government.

Cribl.Cloud Government 4.18.0

Local search and Lakehouse engines

Cribl.Cloud Government now supports the same local search engine and Lakehouse storage engine used in commercial Cribl Search. Previously, federal customers could only use the original search experience and classic Lake. The new engines run with FedRAMP-approved, FIPS-compliant cryptography and stay fully inside the Cribl.Cloud Government boundary.

Insights (Initial Support)

Cribl Insights is now enabled by default in Cribl.Cloud Government.

Authtoken Management: Provisioning Token Rotation

Provisioning Token Rotation is generally available across all environments (Cribl.Cloud, Cribl.Cloud Government, and on-prem) in this release. Admins can now:

  • Create multiple provisioning tokens, one per team, Fleet, or Group, instead of sharing a single static secret across all deployments.
  • Push a new token to individual Nodes or batches of Nodes without downtime.
  • Revoke the old shared token once all Nodes migrate.
  • Monitor which tokens are active, how many Nodes registered with each, and whether any registration attempts failed.