Collects detailed information on IoT devices managed by CrowdStrike, including security status and activity logs. This integration supports monitoring and securing IoT environments.
Details
Monad uses the cron field to run this input on specific intervals and returns all IoT assets' details, performing a full sync of data each time.
Requirements
Before you connect Monad to CrowdStrike, you need a Client ID and Client Secret. Log in to falcon.crowdstrike.com 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.
setup documentation
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
Setting
Type
Required
Description
Cron
string
Yes
Cron string for scheduling tasks. Ex: '0 0 * * *' for daily execution at midnight.
Cloud Type
string
No
Your cloud type for CrowdStrike. Ex: 'autodiscover', 'us-1', 'us-2', 'eu-1', 'us-gov-1'.
Secrets
Secret
Type
Required
Description
Client ID
string
Yes
Client ID for the CrowdStrike API. This is required to authenticate requests.
Client Secret
string
Yes
Client Secret for the CrowdStrike API. This is required to authenticate requests.
Custom Schema Handling
If the source data doesn't align with any of the OpenSecurityControlFramework (OSCF) schemas, you can create a custom transformation using our JQ transform pipeline. For example:
For more information on JQ and how to write your own JQ transformations see the JQ docs here
If you believe this data source should be included in the standard OSCF schema set, please reach out to our team at support@monad.com. We're always looking to expand our coverage of security control frameworks based on community needs.
