CrowdStrike Falcon

Bring CrowdStrike Falcon alerts into the security signal inbox for review.

The CrowdStrike Falcon connector reads new alerts from your Falcon tenant and places each one in the security signal inbox (a holding list where a person decides what every alert becomes). A sync never creates an incident on its own: a reviewer accepts, merges or dismisses each signal in Incidents. The connection is server to server, using a Falcon API client, so nobody signs in to CrowdStrike through the browser.

At a glance

Direction Into Aegis.
What it brings in Falcon alerts whose Falcon status is new and whose severity is at or above the minimum you choose, most severe first, up to 100 alerts per sync.
Where it lands The security signal inbox (/incidents/signals); a sync never creates an incident (see Incidents).
Credentials and permissions A Falcon API client (client ID and secret) with the scope Alerts: Read, and the cloud region of your Falcon tenant (US_1, US_2, EU_1 or GOV_1). Server to server: no browser sign-in.
Owner of imported records A signal has no owner; the incident created on acceptance belongs to the reviewer.
When it runs On demand, with Sync Now on the connector page. Scheduled syncs are not yet available for this connector (see Tips and limits).
Set it up /connectors/crowdstrike, by an Admin or Manager, on a plan that includes the CrowdStrike connector.

Who uses it

Admin Manager open the page, save the configuration, authorise, test the connection, run a sync and disconnect the connector.

Contributor Viewer cannot open /connectors/crowdstrike; they are redirected with an access-denied notice. They can still work with the signals the connector brings in, as far as their role allows in Incidents.

The connector is also licensed separately. If your plan does not include it, saving, testing, authorising and syncing are refused, even for an Admin.

What's on this screen

No screenshot of this page was captured for this edition of the guide; the description below follows the page as it is built. From top to bottom:

Create the API client in Falcon

This part happens in the CrowdStrike Falcon console, not in Aegis.

  1. Sign in to your CrowdStrike Falcon console.
  2. Go to Support > API Clients and Keys and create a new OAuth2 API client.
  3. Give it the scope Alerts: Read. The test and the sync read the Alerts API only, so no other scope is needed.
  4. Copy the client ID and the client secret. Falcon shows the secret only once, so store it somewhere safe until you have saved it in Aegis.
  5. Note which cloud region your Falcon tenant is hosted in; you choose it in Aegis next.

Save the configuration

  1. Open Connectors and choose CrowdStrike Falcon, or go to /connectors/crowdstrike. The page opens with the Configuration panel at the top.
  2. Enter the client ID in API Client ID. Save Configuration stays disabled until this field has a value.
  3. Enter the secret in API Client Secret. Once a secret is stored, the field shows a mask; leave it blank to keep the stored secret.
  4. Choose the region in CrowdStrike Cloud Region: US-1 (api.crowdstrike.com), US-2 (api.us-2.crowdstrike.com), EU-1 (api.eu-1.crowdstrike.com) or GovCloud (api.laggar.gcw.crowdstrike.com). The default is US-1.
  5. Select Save Configuration. The button reads Saving... while it works, a confirmation toast appears, and the Connection Status panel changes to Not Tested with an Authorize button.
Saving does not connect

Saving never marks the connector as connected. A new or changed configuration stays disconnected until an authorisation, connection test or sync succeeds. Saving the same values again keeps the stored status.

Authorise and test the connection

  1. In Connection Status, select Authorize. The button reads Authorizing... while Aegis exchanges the stored client ID and secret for an access token with Falcon. No browser window opens.
  2. Aegis then tests the connection automatically by reading up to ten recent alerts. On success the status changes to Connected, a green box reads Connected to CrowdStrike Falcon API with the number of recent detections found (and a count per severity band, high, medium or low, for each band that has any), and the Detection Sync panel appears.
  3. If it fails, the status changes to Connection Failed and a red box explains why. Check the secret, the scope and the region, then try again.
  4. Later, select Test Connection at any time to check the connection again. The button reads Testing... while it runs, and a failed test also marks the stored connector as failed.

Run a sync

  1. In Detection Sync, move the severity slider to the lowest severity you want to bring in. It runs from Informational (1) to Critical (5) and starts at Medium (3). The label under it reads, for example, Medium+ selected, with a line explaining which detections will be imported as security signals.
  2. Select Sync Now. The button reads Syncing... and a blue message shows that detections are being synced from CrowdStrike Falcon.
  3. Read the result under Sync History. A green Sync Complete entry shows how many security signals were created and how many were skipped, out of how many alerts Falcon returned. A red Sync Failed entry shows the reason.
  4. Select Review in the security signal inbox →. The Security Signals list opens, where the new signals wait as pending for a person to decide.

Before the first sync, Sync History reads No sync history yet. After that it shows Last successful sync: with the date and time of the last completed sync, which stays after a reload. The individual results are kept on the page only: it lists the last five of this visit and clears them when you reload. The lasting record is the audit log, which records every save, authorisation, connection test and sync with the counts.

What a signal contains

Signal field Taken from the Falcon alert
Title The alert name (or display name, or description).
Description The alert description, plus the tactic, technique, pattern, file name, the first 200 characters of the command line and the agent, where Falcon supplies them.
Type Data breach when the tactic, technique or description mentions exfiltration or data theft; security incident otherwise.
Data breach flag Set when those fields mention exfiltration, data theft, data loss, data breach or information disclosure. A person still confirms or dismisses any breach decision.
Affected systems Host name, device, user name and local IP address, up to ten entries.
Detected at The alert's start time, or the first behaviour or creation time.
Severity Mapped from the Falcon severity, as in the next table.

Severity mapping

Falcon severity Aegis severity
Critical (5) Critical
High (4) High
Medium (3) Medium
Low (2) Low
Informational (1) Low

Disconnect the connector

  1. At the bottom of the connector panels, under Disconnect connector, select Disconnect. A confirmation dialog asks whether to disconnect CrowdStrike.
  2. Confirm with Disconnect. Aegis deletes the stored configuration and credentials, and the sync schedules and mappings that use it, then returns you to the connectors overview.

Signals and incidents already brought in stay in Aegis. You can configure the connector again later.

The AI assist

The connector page itself has no AI. When a sync adds new signals and AI assistance is switched on, Aegis asks the AI to pre-sort that batch in the signal inbox (one AI credit per batch). The AI only suggests: a person reviews and decides every signal, and the AI never creates, merges or dismisses one on its own. See Incidents.

Tips and limits

Where this connects