# Section Overview

### 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](/radiant-connectors/section-overview/the-radiant-data-pipeline.md) 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](/radiant-connectors/section-overview/choose-the-right-connection-method.md).

### What's in this section

#### Data pipeline and connection methods

* **The Radiant Data Pipeline** — How security data flows from ingestion through indexing, filtering, deduplication, and alert triage.
* **Choose the Right Connection Method** — When to use a direct API connector, syslog or webhook, the Radiant Agent, or AWS S3.

#### Data Connectors

The Data Connectors page in Radiant is where you add, manage, and monitor all active integrations. For instructions on navigating the page and adding a connector, see Data Connectors.

#### Phishing configuration

Radiant supports ingestion of user-reported phishing emails through direct forwarding integrations with major email platforms and phishing simulation tools.

* [Phishing Configuration](/radiant-connectors/section-overview/phishing-configuration.md) — Overview of phishing email forwarding and supported platforms.
  * [Outlook Online Conditional Forwarding (Inbox Rules)](/radiant-connectors/section-overview/phishing-configuration/outlook-online-conditional-forwarding-inbox-rules.md)
  * [Set up Gmail to Forward Phishing Emails to Radiant Security](/radiant-connectors/section-overview/phishing-configuration/set-up-gmail-to-forward-phishing-emails-to-radiant-security.md)
  * [Set up KnowBe4 on Chrome to Forward Phishing Emails to Radiant Security](/radiant-connectors/section-overview/phishing-configuration/set-up-knowbe4-on-chrome-to-forward-phishing-emails-to-radiant-security.md)
  * [Set up KnowBe4 on O365 to Forward Phishing Emails to Radiant Security](/radiant-connectors/section-overview/phishing-configuration/set-up-knowbe4-on-o365-to-forward-phishing-emails-to-radiant-security.md)
  * [Set up O365 to Forward Phishing Emails to Radiant Security](/radiant-connectors/section-overview/phishing-configuration/set-up-o365-to-forward-phishing-emails-to-radiant-security.md)
  * [Set up Proofpoint PhishAlarm to Forward Phishing Emails to Radiant Security](/radiant-connectors/section-overview/phishing-configuration/set-up-proofpoint-phishalarm-to-forward-phishing-emails-to-radiant-security.md)

#### 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](/log-management/storage-and-retention.md) — Storage configuration options, retention policies, and how to choose between Radiant-managed storage and BYOB.
* [Bring Your Own Bucket for Log Management](/log-management/bring-your-own-bucket-byob/bring-your-own-bucket-for-log-management.md) — Configure an AWS S3 bucket as your primary log storage.
* [Bring Your Own Bucket for Log Management with Terraform](/log-management/bring-your-own-bucket-byob/bring-your-own-bucket-for-log-management-with-terraform.md) — Provision and configure your BYOB storage using Terraform.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.radiantsecurity.ai/radiant-connectors/section-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.