Connect CrowdStrike to Anzenna
This guide walks you through integrating Anzenna with CrowdStrike Falcon to enable comprehensive endpoint security monitoring, device management, and optional remediation capabilities.
Prerequisites
- CrowdStrike Falcon administrator access
Anzenna account with integration permissions
Ability to create API clients in CrowdStrike
Overview
The integration enables:
- Real-time alerts and detections monitoring
- Device inventory and status tracking
- Host group and policy management
Optional: Remote remediation capabilities via Real Time Response
- NGSIEM log forwarding
Step-by-Step Instructions
Part 1: Initiate Connection
Log into Anzenna at
app.anzenna.ai
Navigate to Settings > Integrations
Find the CrowdStrike integration card
Click Connect to CrowdStrike
You'll be redirected to CrowdStrike Falcon login
Part 2: Create API Client in CrowdStrike
Log into your CrowdStrike Falcon console
Click the Menu icon (☰)
Navigate to Support and resources
Select API clients and keys
Click Create API client
Enter the client name:
Anzenna
Part 3: Configure API Permissions
| Scope | Permission | Purpose |
|---|---|---|
| Alerts | Read | Monitor security alerts |
| Detections | Read | Access detection events |
| Hosts | Read | View device inventory |
| Device Control Policies | Read | Check policy configurations |
| Host Groups | Read | Monitor device groupings |
| User Management | Read | User attribution |
| NGSIEM | Read/Write | Log forwarding |
Select each permission from the scopes list above
Part 4: Optional Remediation Permissions
If you want Anzenna to perform automated remediations:
Add Hosts permission: Write (in addition to Read)
Add Host Groups permission: Write (in addition to Read)
Part 5: Enable Real Time Response
Find Real Time Response in the scopes list
Grant Read access
Grant Write access
Find Real Time Response (admin) in the scopes list
Grant Write access for probe capabilities
RTR capabilities allow Anzenna to execute remote commands and scripts on endpoints for investigation and remediation.
Part 6: Save and Copy Credentials
Click Save to create the API client
Copy the Client ID immediately
Paste the Client ID into the Anzenna integration form
- Return to CrowdStrike
Copy the Client Secret (you won't be able to see it again)
Paste the Client Secret into Anzenna's secret field
In Anzenna, click Save to establish the connection
Part 7: Configure Device Control Policies
In CrowdStrike, navigate to Configuration > Device Control
Select your Windows policy
Enable Enhanced file metadata detection
This provides visibility into potential exfiltration activities
Select your Mac policy
Enable Enhanced file metadata detection
Click Save for both policies
Part 8: Configure Response Policies
Enable Real Time Response for all operating systems:
For Mac Policy
Navigate to Host setup and management > Response policies
Select your Mac policy
Enable Real Time Response
Enable Custom Scripts
Enable Put, Run, Put-and-run commands
Click Save
For Windows Policy
Select your Windows policy
Enable Real Time Response
Enable Custom Scripts
Enable Put, Run, Put-and-run commands
Click Save
For Linux Policy
Select your Linux policy
Enable Real Time Response
Enable Custom Scripts
Enable Put, Run, Put-and-run commands
Click Save
Verification
After completing setup, verify the integration:
Return to Anzenna > Integrations
Confirm CrowdStrike shows as Connected
Navigate to Anzenna's Endpoints dashboard
Verify devices from CrowdStrike are appearing
Check that recent alerts and detections are visible
The CrowdStrike integration is now active across all operating systems in your environment.
What Data is Collected
Security Events
- Real-time detections
- Security alerts
- Threat intelligence indicators
- Incident details
Device Information
- Endpoint inventory
- OS versions and patch levels
- Installed software
- Network information
- Device health status
Policy Data
- Device control policies
- Prevention policies
- Response policies
- Host group assignments
User Data
- User logins
- Account information
- Activity attribution
Remediation Capabilities
With write permissions enabled, Anzenna can:
Isolate endpoints - Network isolation for containment
Execute scripts - Run remediation scripts via RTR
Collect forensic data - Gather evidence from endpoints
Modify host groups - Dynamic device management
Kill processes - Terminate malicious processes
Delete files - Remove threats
Troubleshooting
Connection Fails
"Invalid credentials" error:
- Verify Client ID was copied correctly
- Ensure Client Secret is complete
- Check API client is enabled in CrowdStrike
- Confirm client wasn't deleted/revoked
Missing Data
No devices showing in Anzenna:
- Wait 15-30 minutes for initial sync
- Verify Hosts Read permission is granted
Check that devices are online in CrowdStrike
Ensure API client has access to your cloud environment
Remediation Not Working
Cannot execute remote actions:
Verify Real Time Response is enabled in policies
Check both Read and Write permissions are granted
- Ensure RTR admin access is enabled
- Verify custom scripts option is enabled
Permission Errors
API returns 403 Forbidden:
Review all granted scopes match requirements
- Regenerate API credentials if needed
- Check that NGSIEM read/write is enabled
- Verify user management read permission
Security Considerations
API credentials - Store securely, don't share
Least privilege - Only enable remediations if needed
Audit logging - All actions logged in both systems
Credential rotation - Rotate API keys annually
Scope review - Audit permissions quarterly
Best Practices
Test remediation - Start with read-only, add write later
Monitor initial sync - Watch for any errors during first sync
Set up alerts - Configure Anzenna alerts for critical detections
Document setup - Save API client details securely
Regular reviews - Audit integration health monthly
Update policies - Keep device control policies current
Train team - Ensure SOC knows integration capabilities
Integration Maintenance
Monitoring Health
- Anzenna integration status indicator
- Last successful sync timestamp
- Error logs if any issues occur
Credential Expiration
CrowdStrike API clients don't expire by default, but:
- Implement annual credential rotation
- Monitor for API client deletion
- Set up alerts for connection failures
Updating Permissions
- Edit the API client in CrowdStrike
- Modify scope permissions
- No reconnection needed in Anzenna
- Changes take effect immediately
Related Resources
Need help? Contact
Anzenna Support
for assistance.