Identity Security
CrowdStrike User Metadata
Collects user information from CrowdStrike, including user profiles. This provides visibility into user activities and helps in detecting anomalous behavior.
Sync Type: Full Synchronisation
Requirements
- Before you connect Monad to CrowdStrike, you need a Client ID and Client Secret. Log in to your CrowdStrike portal, and under Support & Resources, click on 'API Client and Keys' to create your credentials.
- Enter a Client Name, Description and API Scopes to define the API client. Ensure read roles for User Management are enabled.
- Click Done.
- Copy the ClientID and ClientSecret key. You'll need them when you set up the Monad connector.
Details
Monad uses the cron field to run this input on specific intervals and returns all users, performing a full sync of data each time.
If a sync is interrupted, the next sync continues from where it stopped rather than starting again from the beginning.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
cron | string (cron) | Yes | 0 * * * * | Cron string for scheduling the ingest of your input. eg: 0 0 * * * - Daily at midnight, or */15 * * * * - Every 15 minutes. Defaults to an hour. |
cloud_type | string | Yes | autodiscover | Your cloud type for CrowdStrike. Ex: 'autodiscover', 'us-1', 'us-2', 'eu-1', 'us-gov-1'. Allowed values: autodiscover, us-1, us-2, eu-1, us-gov-1. |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
client_id | secret | Yes | Client ID for the CrowdStrike API. This is required to authenticate requests. |
client_secret | secret | Yes | Client Secret for the CrowdStrike API. This is required to authenticate requests. |
Sample Record
Code
Sync frequency
This input runs on a cron schedule (default hourly, 0 * * * *), which you can configure on the pipeline.
See Input Sync Frequency for details.
Last modified on