Cribl Bought Radiant’s AI SOC Assets—not the Whole Company

On August 19, 2026, Cribl disclosed the purchase of technology assets from Radiant Security’s AI-native security operations center product. The deal includes intellectual property for autonomously triaging, investigating and resolving security alerts, while its financial terms were not disclosed.

The transaction was described as an asset purchase, not an acquisition of Radiant Security as a corporate entity. Cribl has identified a destination for the acquired technology, but the public announcement does not establish what will happen to Radiant’s standalone platform, existing customer contracts, support commitments, connectors or pricing.

What Cribl bought

SiliconANGLE’s account of the transaction identifies the purchased property as technology assets and the intellectual property behind software that can triage, investigate and resolve security alerts. Cribl is adapting the technology to run as an application on its telemetry data platform.

The planned capability would generate custom triage logic for individual alerts instead of relying solely on predefined playbooks, then conduct investigations against telemetry where the data resides. Faster threat detection and fewer false positives are stated product goals, not independently measured results or evidence of a generally available release.

No launch date has been provided for the Radiant-derived application. Cribl has scheduled broader platform updates for CriblCon on September 28, 2026, but it has not committed to presenting this application, a migration plan or customer-transition details at the event.

Why an asset purchase is different from buying a company

A company acquisition transfers ownership or control of the corporate entity. An asset purchase instead transfers the property specified in the transaction; contracts, liabilities and other obligations do not automatically move merely because selected technology and intellectual property have changed hands.

That distinction limits what can be concluded from the deal. Cribl obtained identified technology and IP, but the announcement does not show that it acquired Radiant Security’s shares, assumed every customer agreement, hired the entire team or accepted all existing support liabilities.

ChannelNews’ independent coverage likewise characterizes the transaction as a purchase of technology assets and intellectual property intended for an application on Cribl’s platform. It does not describe a transfer of the whole company.

What has been disclosed—and what has not

The available disclosures support a short checklist of confirmed facts:

• Assets: Cribl acquired technology assets from Radiant Security’s AI-native SOC product.
• Intellectual property: The deal includes IP for autonomous alert triage, investigation and resolution.
• Intended integration: Cribl is adapting the technology as an application on its telemetry platform.
• Operating model: The planned capability would create alert-specific triage logic and investigate telemetry where it resides.
• Deal value: Financial terms have not been made public.

The same disclosures leave several customer-facing issues unresolved:

• Corporate scope: Which assets, liabilities or personnel beyond the identified technology and IP were included?
• Customer contracts: Which legal entity will administer current agreements, renewals and service-level commitments?
• Standalone platform: Will Radiant’s existing product remain available, and will customers receive an end-of-sale, maintenance or end-of-life schedule?
• Support: Who will handle open cases, fixes, detection updates and model improvements during the transition?
• Connectors: Which integrations were transferred, which will remain supported and how will they map to the planned Cribl application?
• Pricing and licensing: Will current entitlements carry over, and how will Cribl package the new capability?
• Timing: When will the application become available, and will existing deployments require migration?

What Radiant customers still cannot infer

Ownership of the underlying technology does not by itself determine service continuity for an existing Radiant customer. A deployment may remain governed by an agreement with a different legal entity even though Cribl now owns technology used by the product. The public materials cannot identify who is responsible for a particular customer’s support, renewal or service-level obligations.

Security teams evaluating Radiant face a related architecture question. The future capability is planned as an application on Cribl’s telemetry platform, but the available disclosures do not specify whether that platform will be mandatory, which deployment models will be supported or whether existing connections will transfer without modification.

D3 Security’s analysis of the deal also separates the asset purchase from a company acquisition and flags unanswered questions about contracts, support, the standalone platform and connectors. D3 is a competing security vendor, so its product recommendations are commercial positioning; the disclosure gaps it identifies can nevertheless be checked against the limited information released by Cribl.

The confirmed position remains narrower than the shorthand “Cribl acquired Radiant Security.” Cribl owns specified AI SOC technology assets and plans to integrate them with its telemetry platform. The status of existing Radiant customer relationships and the standalone product will remain uncertain until contract notices, support terms, connector details, pricing and an integration schedule are published or communicated directly to customers.