-
Notifications
You must be signed in to change notification settings - Fork 224
CrowdStrike Threat Intel C2C Source #4656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a807ac1
CrowdStrike Threat Intel C2C Source
JV0812 0e0953f
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 ef03c71
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 f4de6b3
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 def3120
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 4c67e4a
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 268ed1e
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
JV0812 d42076a
Merge branch 'main' into Crowdstrike-Threat-Intel-C2C
jpipkin1 7f9a390
Prep for beta release
jpipkin1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| title: CrowdStrike Threat Intel C2C Source (Collection) | ||
| image: https://help.sumologic.com/img/sumo-square.png | ||
| keywords: | ||
| - collection | ||
| - crowdstrike-threat-intel | ||
| hide_table_of_contents: true | ||
| --- | ||
|
|
||
| import useBaseUrl from '@docusaurus/useBaseUrl'; | ||
|
|
||
| <a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a> | ||
|
|
||
| We're excited to announce the release of our new cloud-to-cloud source for CrowdStrike Threat Intel. This source helps you to collect indicators data from the CrowdStrike platform, and ingest them into Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/crowdstrike-threat-intel-source). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
127 changes: 127 additions & 0 deletions
127
...lectors/cloud-to-cloud-integration-framework/crowdstrike-threat-intel-source.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,127 @@ | ||
| --- | ||
| id: crowdstrike-threat-intel-source | ||
| title: CrowdStrike Threat Intel Source | ||
| sidebar_label: CrowdStrike Threat Intel | ||
| tags: | ||
| - cloud-to-cloud | ||
| - crowdstrike-threat-intel | ||
| description: Learn how to collect combined endpoint vulnerabilities data from the CrowdStrike Spotlight platform. | ||
| --- | ||
| import CodeBlock from '@theme/CodeBlock'; | ||
| import ExampleJSON from '/files/c2c/crowdstrike-threat-intel/example.json'; | ||
| import MyComponentSource from '!!raw-loader!/files/c2c/crowdstrike-threat-intel/example.json'; | ||
| import TerraformExample from '!!raw-loader!/files/c2c/crowdstrike-threat-intel/example.tf'; | ||
| import useBaseUrl from '@docusaurus/useBaseUrl'; | ||
|
|
||
| <img src={useBaseUrl('img/integrations/security-threat-detection/crowdstrike.png')} alt="thumbnail icon" width="85"/> | ||
|
|
||
| CrowdStrike is the leader in next-generation endpoint protection, threat intelligence, and response services. CrowdStrike’s core technology, the Falcon platform, stops breaches by preventing and responding to all types of attacks — both malware and malware-free. The CrowdStrike Threat Intel integration ingests the indicator data from CrowdStrike Combined API and sends it to Sumo Logic as normalized threat indicator. | ||
|
|
||
| :::important | ||
| The CrowdStrike API documentation is not public and can only be accessed by partners or customers. | ||
| ::: | ||
|
|
||
| ## Data collected | ||
|
|
||
| | Polling Interval | Data | | ||
| | :--- | :--- | | ||
| | 1 hour | Indicator data | | ||
|
|
||
| ## Setup | ||
|
|
||
| ### Vendor configuration | ||
|
|
||
| **Prerequisites** | ||
|
|
||
| To collect vulnerability data from the CrowdStrike platform, you must have an authorized CrowdStrike account. CrowdStrike APIs use an OAuth 2.0 authorization token to make authorized API calls. CrowdStrike API Client is required to get the OAuth 2.0 authorization token. To define a CrowdStrike API client, you must be designated as a `CrowdStrike Falcon Administrator` role. | ||
|
|
||
| In this configuration, you will set up the CrowdStrike Threat Intel and configure it to be authorized and authenticated to use indicator information from CrowdStrike Threat Intel API. To obtain the auth token, you will need the following parameters. | ||
|
|
||
| #### API Client and API Secret | ||
|
|
||
| The **API security token** is used to authenticate with CrowdStrike Threat Intel API. After successfully creating the API client, you will get the **Client Id**, **Client Secret**, and **Base URL**. | ||
|
|
||
| To get the **CrowdStrike API Client**, follow the steps below: | ||
|
|
||
| 1. Sign in to [CrowdStrike Platform](https://falcon.crowdstrike.com/login/). | ||
| 1. Sign in using your email address and password. After you've completed the two-factor authentication, you'll be directed to the application dashboard.<br/><img src={useBaseUrl('img/send-data/crowdstrike-fdr-host-inventory-login-screen.png')} style={{border: '1px solid gray'}} alt="crowdstrike-spotlight-login-screen.png" width="600" /> | ||
| 1. From the CrowdStrike console, select the **Support and resources** option from the menu.<br/><img src={useBaseUrl('img/send-data/crowdstrike-fdr-host-inventory-support-and-resources.png')} style={{border: '1px solid gray'}} alt="<crowdstrike-fspotlight-support-and-resources.png>" width="600" /> | ||
JV0812 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| 1. In the **Resources and tools** section, select the **API clients and keys** option. You can then view existing clients or add new API clients from there.<br/><img src={useBaseUrl('img/send-data/crowdstrike-fdr-host-inventory-api-key-client.png')} style={{border: '1px solid gray'}} alt="<crowdstrike-spotlight-api-key-client.png>" width="600" /> | ||
JV0812 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| 1. Click **Add new API client**. You will be prompted to give a descriptive name and select the appropriate API scopes.<br/><img src={useBaseUrl('img/send-data/crowdstrike-fdr-host-inventory-new-client.png')} style={{border: '1px solid gray'}} alt="<crowdstrike-spotlight-new-client.png>" width="600" /> | ||
JV0812 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| 1. Provide a proper name and description and select the **indicators(Falcon Intelligence):read scope** scope. Click on `ADD` to complete the process. | ||
| 1. After you click on `ADD` a dialogue box will appear with the **Client ID**, **Client Secret**, and **Base URL**. Copy and save the Client Id, Client Secret, and Base URL to a folder location because you will need them while configuring the [CrowdStrike Threat Intel Source](#source-configuration).<br/><img src={useBaseUrl('img/send-data/crowdstrike-fdr-host-inventory-copy-creds.png')} style={{border: '1px solid gray'}} alt="<crowdstrike-spotlight-copy-creds.png>" width="600" /> | ||
JV0812 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| #### Region | ||
|
|
||
| Identify your **Region** based on your **Base URL**. The region can be selected from the list below. | ||
|
|
||
| | Region | Base URL | | ||
| | :------ | :-------------------------- | | ||
| | US-1 | https://api.crowdstrike.com | | ||
| | US-2 | https://api.us-2.crowdstrike.com | | ||
| | EU-1 | https://api.eu-1.crowdstrike.com | | ||
| | US-GOV-1 | https://api.laggar.gcw.crowdstrike.com | | ||
|
|
||
| ### Source configuration | ||
|
|
||
| When you create a CrowdStrike Spotlight Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see [Configure a Hosted Collector](/docs/send-data/hosted-collectors/configure-hosted-collector). | ||
|
|
||
| To configure the CrowdStrike Spotlight Source: | ||
| 1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. | ||
| 1. On the Collectors page, click **Add Source** next to a Hosted Collector. | ||
| 1. Search for and select **CrowdStrike Spotlight** icon. | ||
| 1. Enter a **Name** to display for the Source in the Sumo Logic web application. The description is optional. | ||
| 1. (Optional) For **Source Category**, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called `_sourceCategory`. | ||
| 1. (Optional) **Fields**. Click the **+Add Field** link to define the fields you want to associate. Each field needs a name (key) and value. | ||
| *  A green circle with a check mark is shown when the field exists in the Fields table schema. | ||
| *  An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped. | ||
| 1. In **Region**, choose the region as per your Base URL. See [Region](#region) section to know your region. | ||
| 1. In **Client ID**, enter the Client ID you generated and secured from the [API Client](#api-client-and-api-secret) section. | ||
| 1. In **Client Secret**, enter the Client Secret you generated and secured from the [API Secret](#api-client-and-api-secret) section. | ||
| 1. In **Sumo Logic Threat Intel Source ID**, enter the Sumo Logic namespace in which the indicators are stored. | ||
| 1. (Optional) In **Mallicious Confidence**, enter the type of confidence to collect data from. Possible values: `high`, `medium`,`low`, or `unverified`. | ||
| 1. The **Polling Interval** is set for one hour by default, you can adjust it based on your needs. This sets how often the integration will fetch complete vulnerability instance data that has been updated within most recent polling interval duration. | ||
| 1. When you are finished configuring the Source, click **Save**. | ||
|
|
||
| ## JSON schema | ||
|
|
||
| Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See [how to use JSON to configure Sources](/docs/send-data/use-json-configure-sources) for details. | ||
JV0812 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| | Parameter | Type | Value | Required | Description | | ||
| |:--|:--|:--|:--|:--| | ||
| | schemaRef | JSON Object | `{"type":"Crowdstrike Threat Intel"}` | Yes | Define the specific schema type. | | ||
| | sourceType | String | `"Universal"` | Yes | Type of source. | | ||
| | config | JSON Object | [Configuration object](#configuration-object) | Yes | Source type specific values. | | ||
|
|
||
| ### Configuration Object | ||
|
|
||
| | Parameter | Type | Required | Default | Description | Example | | ||
| |:--|:--|:--|:--|:--|:--| | ||
| | name | String | Yes | `null` | Type a desired name of the source. The name must be unique per Collector. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_source`. | `"mySource"` | | ||
| | description | String | No | `null` | Type a description of the source. | `"Testing source"` | ||
| | category | String | No | `null` | Type a category of the source. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/best-practices) for details. | `"mySource/test"` | ||
| | fields | JSON Object | No | `null` | JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field `_siemForward` to enable forwarding to SIEM.|`{"_siemForward": false, "fieldA": "valueA"}` | | ||
| | baseURL | String | Yes | `US-1` | The Region of your CrowdStrike account. | | | ||
| | clientID | String | Yes | `null` | The CrowdStrike Client ID you want to use to authenticate collection requests. | | | ||
| | clientSecret | String | Yes | `null`| The CrowdStrike Client Secret you want to use to authenticate collection requests. | | | ||
| | userSourceID | String | Yes | `null`| The Sumo Logic namespace in which the indicators will be stored. | | | ||
| | pollingInterval | Integer | No | 1 hour | This sets how often the Source checks for new data. | | | ||
| | maliciousConfidence | String | No | `null` | Type of confidence to collect data from. Possible values: `high`, `medium`,`low`, or `unverified`. | | | ||
|
|
||
| ### JSON example | ||
|
|
||
| <CodeBlock language="json">{MyComponentSource}</CodeBlock> | ||
|
|
||
| <a href="/files/c2c/crowdstrike-threat-intel/example.json" target="_blank">Download example</a> | ||
|
|
||
| ### Terraform example | ||
|
|
||
| <CodeBlock language="json">{TerraformExample}</CodeBlock> | ||
|
|
||
| <a href="/files/c2c/crowdstrike-threat-intel/example.tf" target="_blank">Download example</a> | ||
|
|
||
| ## FAQ | ||
|
|
||
| :::info | ||
| Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. | ||
| ::: | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.