> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/event-reporting/crowdstrike-ng-siem.md).
# CrowdStrike Falcon Next-Gen SIEM
Integrating Keeper SIEM push to Crowdstrike Falcon Next-Gen SIEM
### Overview
Keeper supports event streaming into CrowdStrike Next-Gen SIEM. External logging is real-time, and new events will appear within a few minutes. Setup instructions are below.
{% stepper %}
{% step %}
### Add the Data Connector
* From the CrowdStrike dashboard, visit the Data Onboarding > Data Connectors screen.
* Select "+ Add connection" and search for Keeper.
* Click "Configure", assign a name, and then "Create connection".
Data connectors
{% endstep %}
{% step %}
### Create the API Key
* From the Data Connector screen, in the Keeper row click the overflow menu and then "Generate API Key".
* Save the `API Key` and `API URL` for the next step.
Create API Key
Copy the API Key and API URL
{% endstep %}
{% step %}
### Activate the Integration
* From the **Keeper Admin Console**, go to **Reporting & Alerts** > **External Logging.**
* Select **CrowdStrike Falcon Next-Gen SIEM.**
* Provide the `API Key` and `API URL` from Step 2.
* Click **Test** and then **Save**.
{% endstep %}
{% endstepper %}
### Setup Complete!
When audit events are sent from Keeper to CrowdStrike, the data will begin to populate in the "Third Party" source within minutes.
Event Logs in CrowdStrike
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/enterprise-guide/event-reporting/crowdstrike-ng-siem.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
