Skip to content

Commit 145da17

Browse files
clarify usage of fdr
rephrase words in menifest.yml
1 parent 7e03b95 commit 145da17

File tree

5 files changed

+15
-15
lines changed

5 files changed

+15
-15
lines changed

packages/crowdstrike/_dev/build/docs/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The integration collects and ingests events from multiple CrowdStrike Falcon dat
4040

4141
4. **Falcon Data Replicator (FDR)**:
4242

43-
This collects events in near real time from your endpoints, cloud workloads, identities, via the Falcon platform’s lightweight agent. CrowdStrike Falcon Data Replicator (FDR) enables you with actionable insights to improve SOC performance.
43+
The FDR feed consists of regular transfers of data (data dumps) rather than ongoing streams of data from your endpoints, cloud workloads, identities, via the Falcon platform’s lightweight agent. CrowdStrike Falcon Data Replicator (FDR) enables you with actionable insights to improve SOC performance. FDR isn't useful for real-time alerts because it's not an ongoing stream of data.
4444

4545
Logs received from the Falcon Data Replicator are indexed into the `fdr` dataset in Elasticsearch.
4646

packages/crowdstrike/data_stream/falcon/manifest.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,12 +40,12 @@ streams:
4040
Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.
4141
4242
template_path: log.yml.hbs
43-
title: Falcon events
44-
description: Collect Falcon events via Falcon SIEM Connector.
43+
title: CrowdStrike Falcon events
44+
description: Collect CrowdStrike Falcon events through Falcon SIEM Connector.
4545
- input: streaming
4646
template_path: streaming.yml.hbs
47-
title: Falcon events
48-
description: Collect Falcon events via Event Streams API.
47+
title: CrowdStrike Falcon events
48+
description: Collect CrowdStrike Falcon events using Event Streams API.
4949
enabled: false
5050
vars:
5151
- name: url

packages/crowdstrike/data_stream/fdr/manifest.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ streams:
226226
`event.timezone` and `log.offset`.
227227
- input: logfile
228228
title: Falcon Data Replicator logs
229-
description: Collect Falcon Data Replicator logs via file system.
229+
description: Collect Falcon Data Replicator logs through file system.
230230
enabled: false
231231
vars:
232232
- name: paths

packages/crowdstrike/docs/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The integration collects and ingests events from multiple CrowdStrike Falcon dat
4040

4141
4. **Falcon Data Replicator (FDR)**:
4242

43-
This collects events in near real time from your endpoints, cloud workloads, identities, via the Falcon platform’s lightweight agent. CrowdStrike Falcon Data Replicator (FDR) enables you with actionable insights to improve SOC performance.
43+
The FDR feed consists of regular transfers of data (data dumps) rather than ongoing streams of data from your endpoints, cloud workloads, identities, via the Falcon platform’s lightweight agent. CrowdStrike Falcon Data Replicator (FDR) enables you with actionable insights to improve SOC performance. FDR isn't useful for real-time alerts because it's not an ongoing stream of data.
4444

4545
Logs received from the Falcon Data Replicator are indexed into the `fdr` dataset in Elasticsearch.
4646

packages/crowdstrike/manifest.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -60,17 +60,17 @@ policy_templates:
6060
team: security-service-integrations
6161
inputs:
6262
- type: logfile
63-
title: Collect Falcon events and Falcon Data Replicator logs via file system
64-
description: Collecting logs from Falcon SIEM Connector and Falcon Data Replicator via file system.
63+
title: Collect Falcon events and Falcon Data Replicator logs through file system
64+
description: Collecting logs from Falcon SIEM Connector and Falcon Data Replicator through file system.
6565
- type: aws-s3
66-
title: Collect Falcon Data Replicator logs via AWS S3
67-
description: Collecting logs from Falcon Data Replicator via AWS S3.
66+
title: Collect Falcon Data Replicator logs using AWS S3
67+
description: Collecting logs from Falcon Data Replicator using AWS S3.
6868
- type: streaming
69-
title: Collect Falcon events via Event Streams API
70-
description: Collecting Falcon events via Event Streams API.
69+
title: Collect CrowdStrike Falcon events using Event Streams API
70+
description: Collecting CrowdStrike Falcon logs using Event Streams API.
7171
- type: cel
72-
title: Collect Falcon Alerts, Hosts and Vulnerabilities
73-
description: Collect Falcon Alerts, Hosts and Vulnerabilities.
72+
title: Collect CrowdStrike Falcon Alerts, Hosts and Vulnerabilities
73+
description: Collect CrowdStrike Falcon Alerts, Hosts and Vulnerabilities.
7474
vars:
7575
- name: client_id
7676
type: text

0 commit comments

Comments
 (0)