> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/a-c-integrations/crowdstrike/crowdstrike-logscale-setup-for-workbench.md).

# CrowdStrike LogScale Setup for Workbench

## Prerequisites <a href="#h_01jffsvat526yv50fa2f4xxxdh" id="h_01jffsvat526yv50fa2f4xxxdh"></a>

1. You must have an existing LogScale user with the [Member role](https://library.humio.com/falcon-logscale-cloud/security-authorization-roles.html?highlight=member%20role#security-authorization-role-default-permissions) assigned.
2. You must have an existing Repository or View that contains the data Expel needs to access.

## Step 1: Generate API Credentials for LogScale <a href="#h_01jffv4s5es6mxng0cb11hk8p2" id="h_01jffv4s5es6mxng0cb11hk8p2"></a>

Make sure you have met the [prerequisites](#h_01jffsvat526yv50fa2f4xxxdh) before proceeding with this step.

1. Log into the CrowdStrike Falcon LogScale console.
2. From the homepage, select **Repositories and views**.
3. Select the Repository or View that contains the data Expel will access.
4. Select **Settings > Tokens**.
5. Select **+ Add new**.<br>

   <div align="left"><figure><img src="/files/5mVb15Ld6HBDNde31Ngh" alt="Select Add New on the Repository Tokens page of Crowdstrike." width="384"><figcaption></figcaption></figure></div>
6. Configure the new token with the following details:
   * For **Name**, enter "Expel Integration".
   * Under Permissions, select **Data Access**.<br>

     <div align="left"><figure><img src="/files/7nBSQLaaGRg9bG8kDWx0" alt="Data access and Dada read access are selected as Permissions on the New API token page in Crowdstrike." width="384"><figcaption></figcaption></figure></div>
7. Select **Create token**.
8. **Save the token value** in a safe place for use in a later step.

## Step 2: Enable Console Access <a href="#h_01jffwx12z5banshmwvdp3kca8" id="h_01jffwx12z5banshmwvdp3kca8"></a>

To provide effective triage and analysis, we ask that customers enable Expel with console access. Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

1. Create a local user in LogScale. Alternatively, provision access for Expel in your SSO provider. *This user must have the **Member** role in LogScale*. Note this user's credentials, as you will need to provide them in the next step.

## Step 3: Add CrowdStrike LogScale as a Security Device in Workbench <a href="#h_01jffwpdz0rkjs2s1ac739jrc1" id="h_01jffwpdz0rkjs2s1ac739jrc1"></a>

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “CrowdStrike” and then select the **CrowdStrike Logscale** integration.
5. A configuration pane displays. Complete the fields as follows:
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName LogScale”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example, “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **Connection Settings** - provide the appropriate information:
     * **Server address** - enter the address of the CrowdStrike LogScale instance.
     * **API token** - enter the value of the API token generated in [Step 1](#h_01jffv4s5es6mxng0cb11hk8p2).
     * **Repository name** - enter the name of the CrowdStrike Repository or View to monitor.
     * **LogScale query** - if you are sending your data to a specific repo or to a specific subset of alerts, and you would like us to ingest it, add the base LogScale query here (example: `#repo = expelAlerts`). If this does not apply to you, enter `#repo = *` as the query.
6. Select **Save**.
7. On the console access screen, select **Set up now.**
8. Enter your credentials into the Console Login section.
   * **Console URL** - enter your CrowdStrike Falcon LogScale console URL.
   * **Username** - provide the username for the new LogScale user you created in [Step 2](#h_01jffwx12z5banshmwvdp3kca8).
   * **Password** - provide the password for the new LogScale user you created in [Step 2](#h_01jffwx12z5banshmwvdp3kca8).
   * **Two-factor secret key (32-character code)** - depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, [contact support](/support/how-to-reach-us.md).
9. Select **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.expel.io/connect-your-technology/a-c-integrations/crowdstrike/crowdstrike-logscale-setup-for-workbench.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.