CrowdStrike

circle-check

Released: Dec 2023

Note:

  • Use this reference config to create your own final config.

  • Specify the correct region in API & Request Token URLs. EU-1 region is taken as example here.

  • Syslog forwarding is enabled. Insert the IP address of the Logpoint in SYSLOG_SERVER_IP.

  • Events need to be enriched as the CrowdStrike's baseline config does not generate sufficiently detailed logs.

  • Enrichment added to the following events:

    • DetectionSummaryEvent

    • DetectionSummaryEvent_DnsRequests

    • DetectionSummaryEvent_NetworkAccesses

    • DetectionSummaryEvent_DocumentsAccessed

    • DetectionSummaryEvent_ScanResults

    • DetectionSummaryEvent_ExecutablesWritten

    • DetectionSummaryEvent_QuarantineFiles

    • UserActivityAuditEvent

    • AuthActivityAuditEvent

    • RemoteResponseSessionStartEvent

    • RemoteResponseSessionEndEvent

Configuration file (reference)

Procedures and UI workflows

chevron-rightChecking Installed Integrationshashtag
  1. In the Navigation Bar, click System Settings.

  2. Click Applications.

  3. You can search for the integration, or use the column headers to filter the list.

chevron-rightDownload and Install the .pakhashtag
  1. Download the .pak file from the Service Desk: https://servicedesk.logpoint.com/hc/en-us

  2. Go to Settings >> System Settings from the navigation bar and click Applications.

  3. Click Import.

  4. Browse to the downloaded .pak file.

  5. Click Upload.

  6. After installing it, you can find it under Settings >> System Settings >> Plugins.

Use Log Source Template to Ingest Logs

Using a Device to Ingest Logs

  • To use a device there are 5 steps:

chevron-rightConfiguring a Repohashtag

Repos are locations where incoming logs are stored.

  1. Go to Settings >> Configuration from the navigation bar and click Repos.

  2. Click Add.

  3. Enter a Repo Name.

  4. Select a Repo Path to store incoming logs.

  5. Set a Retention Day to keep logs in a repository before they are automatically deleted.

    1. You can add and remove multiple Repo Path and Retention Day.

  6. Select a Remote LogPoint and set a Available for (day).

  7. Click Submit.

chevron-rightNormalizing Crowdstrike logshashtag

Normalization Packages contain one or more signature-based normalizers. Each normalizer contains a list of signatures that are looked up in the log message. The signature ID of the line that the log message was matched against is added as a field to the log, in addition to a norm_id field with the name of the normalizer package used.

There are two types of Normalization Packages.

  • Vendor Packages are the Normalization Packages Logpoint developed and are part of the Log Source Integration. You can't modify or edit Vendor Packages. You can clone them and then make your changes or edits.

  • My Packages are the Normalization Packages that you create. You can create your own packages based on Vendor Packages. First clone a package, then make your changes. After that you can share your packages with other Logpoint A/Susers.

Compiled Normalizer

  • CrowdStrikeCEFCompiledNormalizer

Guide

1. Go to Settings >> Configuration from the navigation bar and click Normalization Policies.

2. Click Add.

3. Enter a Policy Name.

4. Select the required Compiled Normalizers and Normalization Packages.

5. Click Submit.

chevron-rightConfiguring a process policyhashtag

1. Go to Settings >> Configuration from the navigation bar and click Processing Policies.

2. Click Add .

3. Enter a Policy Name.

4. Select the previously created Normalization Policy.

5. Select the Enrichment Policy.

6. Select the Routing Policy.

7. Click Submit.

chevron-rightAdding CrowdStrike as a Devicehashtag

To collect CrowdStrike logs, add the Linux server IP address(es) where Falcon SIEM Connector is configured in Logpoint. The IP address(es) enables a connection between the CrowdStrike device in Logpoint and the Falcon SIEM Connector.

  1. Go to Settings>>Configuration from the navigation bar and click Devices.

  2. Click Add.

  3. Enter a device Name.

  4. Enter the Linux server IP address(es).

  5. Select the Device Groups.

  6. Select a Log Collection Policy for the logs.

  7. Select a collector or a forwarder from the Distributed Collector drop-down.

    1. It is optional to select the Device Groups, the Log Collection Policy and the Distributed Collector.

  8. Select a Time Zone. The timezone of the device must be same as its log source.

  9. Configure the Risk Values for Confidentiality, Integrity and Availability used to calculate the risk levels of the alerts generated from the device.

  10. Click Submit.

chevron-rightConfiguring the Syslog Collectorhashtag

Syslog Collector gathers and stores log data from Falcon SIEM Connector. It uses the 514 port, and TCP or UDP protocol to collect log messages.

  1. Go to Settings>>Configuration from the navigation bar and click Devices.

  2. Click the Add icon from Actions of the previously added device.

  3. Click Syslog Collector.

    1. You can select a different collector depending on your requirements and added device. To learn more about available collectors go to collectorsarrow-up-right. If you require assistance, contact our support teamarrow-up-right.

  4. Select Syslog Parser as Parser.

  5. Select the previously created Processing Policy.

  6. Select the Charset.

  7. In Proxy Server, select None

  8. Click Submit.

chevron-rightExpected Log Sample (CEF)hashtag
circle-info

We do our best to ensure that the content we provide is complete, accurate and up to date. Logpoint makes no representations or warranties of any kind, express or implied about the documentation. We update it on a best-effort basis.

Last updated

Was this helpful?