Connectors and Data Ingestion

Connect your security stack to Radiant, ingest alerts and threat intelligence, and configure storage for your security logs.

Connect Your Data

Radiant requires visibility across your security environment to triage alerts automatically. This section covers everything needed to establish and manage that visibility: how your security tools connect to Radiant, how ingested data flows through the platform, and how to configure storage for your security logs.

Before connecting your first data source, read The Radiant Data Pipeline to understand how data moves from ingestion through indexing and into alert triage. If you have multiple source types and are unsure which connection method to use, see Choose the Right Connection Method.

Data Connectors

The Data Connectors page in Radiant is where you add, manage, and monitor every active integration, including data connectors, action connectors, and threat intelligence feeds. For instructions on navigating the page and adding a connector, see Data Connectors.

Phishing email forwarding

Radiant ingests user-reported phishing and business email compromise (BEC) reports through direct forwarding integrations with major email platforms and phishing reporting tools.

• Phishing email forwarding overview: prerequisites, phishing configuration in Radiant, and how to choose a forwarding method for your environment.

Storage and retention

Radiant Log Management stores all ingested security data with flexible retention options. You can store data in Radiant-managed infrastructure or in your own AWS S3 bucket (BYOB). Radiant recommends BYOB for all production environments.

• Storage and Retention: storage configuration options, retention policies, and how to choose between Radiant-managed storage and BYOB.

• Bring Your Own Bucket for Log Management: configure an AWS S3 bucket as your primary log storage.

• Bring Your Own Bucket for Log Management with Terraform: provision and configure your BYOB storage using Terraform.