CrowdStrike Falcon Integration¶
CrowdStrike Falcon integrates with Parapet Security through the Falcon Event Streams API (Streaming API) or Falcon LogScale. This guide covers both methods.
Prerequisites¶
- CrowdStrike Falcon subscription
- API credentials with appropriate scopes
- Your Parapet Security webhook URL and token
Integration Methods¶
| Method | Best For | Complexity |
|---|---|---|
| Streaming API (SIEM Connector) | Real-time detection forwarding | Medium |
| Falcon LogScale | Centralized log forwarding | Easy |
| CrowdStrike Store App | Marketplace integration | Easy |
Method 1: SIEM Connector (Streaming API)¶
Step 1: Create API Credentials¶
- Log in to the Falcon Console
- Go to Support → API Clients and Keys
- Click Add new API client
- Configure the client:
| Field | Value |
|---|---|
| Client name | Parapet Security |
| Description | SIEM integration for alert triage |
| API scopes | Event streams: Read |
- Save the Client ID and Secret
Step 2: Get Your Parapet Credentials¶
- Log in to app.parapetsecurity.com
- Go to Settings → Service Tokens
- Click Generate New Token
- Save both:
- Webhook URL:
https://webhook-{region}.parapetsecurity.com/webhook/{tenant-id} - Service Token:
pst_...(shown only once)
- Webhook URL:
Step 3: Deploy SIEM Connector¶
CrowdStrike provides a SIEM Connector that forwards events to webhooks.
Option A: Docker Deployment¶
docker run -d \
--name falcon-siem-connector \
--restart unless-stopped \
-e FALCON_CLIENT_ID=YOUR_CLIENT_ID \
-e FALCON_CLIENT_SECRET=YOUR_CLIENT_SECRET \
-e OUTPUT_TYPE=webhook \
-e WEBHOOK_URL=https://webhook-us.parapetsecurity.com/webhook/YOUR-TENANT-ID \
-e WEBHOOK_TOKEN=pst_YOUR_TOKEN \
crowdstrike/falcon-siem-connector:latest
Option B: Direct Script¶
Download and configure the SIEM Connector:
# Download connector
curl -O https://github.com/CrowdStrike/falcon-integration-gateway/releases/latest/download/fig_linux_amd64
# Make executable
chmod +x fig_linux_amd64
# Create config file
cat > config.ini << EOF
[CrowdStrike]
client_id = YOUR_CLIENT_ID
client_secret = YOUR_CLIENT_SECRET
cloud = us-1
[Webhook]
url = https://webhook-us.parapetsecurity.com/webhook/YOUR-TENANT-ID
authorization = Bearer pst_YOUR_TOKEN
[Filter]
severity_threshold = 3
detection_types = all
EOF
# Run connector
./fig_linux_amd64 -config config.ini
Step 4: Configure Event Filtering¶
Filter which detections are forwarded:
[Filter]
# Minimum severity (1-5, where 5 is Critical)
severity_threshold = 3
# Detection types to include
detection_types = all
# Or specific types: detection_types = malware,exploit,ransomware
# Exclude specific detection names (regex)
exclude_patterns = Test.*,Benign.*
Method 2: Falcon LogScale (Humio)¶
If you're using Falcon LogScale:
Step 1: Create a Webhook Action¶
- Go to Settings → Actions
- Click New Action → Webhook
- Configure:
| Field | Value |
|---|---|
| Name | Parapet Security |
| Endpoint URL | https://webhook-us.parapetsecurity.com/webhook/YOUR-TENANT-ID |
| HTTP Method | POST |
- Add header:
- Name:
Authorization - Value:
Bearer pst_YOUR_TOKEN
Step 2: Create an Alert¶
- Go to Alerts → New Alert
- Create a query for detections:
- Attach the Parapet Security webhook action
- Set trigger conditions (e.g., "on every event")
Step 3: Configure Payload Template¶
{
"source": "crowdstrike",
"timestamp": "{@timestamp}",
"detection": {
"id": "{DetectId}",
"name": "{DetectName}",
"description": "{DetectDescription}",
"severity": "{Severity}",
"severity_name": "{SeverityName}"
},
"host": {
"name": "{ComputerName}",
"platform": "{Platform}",
"os_version": "{OSVersion}",
"agent_id": "{AgentIdString}"
},
"user": {
"name": "{UserName}",
"domain": "{UserDomain}"
},
"tactic": "{Tactic}",
"technique": "{Technique}",
"ioc": {
"type": "{IOCType}",
"value": "{IOCValue}"
},
"file": {
"name": "{FileName}",
"path": "{FilePath}",
"sha256": "{SHA256String}"
},
"command_line": "{CommandLine}"
}
Method 3: CrowdStrike Store App¶
Coming Soon
A dedicated Parapet Security app for the CrowdStrike Store is in development. For now, use the SIEM Connector or LogScale methods above.
Sample Alert Payload¶
Here's what CrowdStrike sends to Parapet Security:
{
"source": "crowdstrike",
"timestamp": "2026-01-28T15:30:00.000Z",
"detection": {
"id": "ldt:abc123:456",
"name": "ProcessHollowing",
"description": "Process hollowing technique detected",
"severity": 4,
"severity_name": "High"
},
"host": {
"name": "DESKTOP-ABC123",
"platform": "Windows",
"os_version": "Windows 10",
"agent_id": "1234567890abcdef"
},
"user": {
"name": "jsmith",
"domain": "CORP"
},
"tactic": "Defense Evasion",
"technique": "T1055.012",
"file": {
"name": "suspicious.exe",
"path": "C:\\Users\\jsmith\\Downloads\\suspicious.exe",
"sha256": "abc123..."
},
"command_line": "suspicious.exe --hidden"
}
Parapet Security's AI normalizes this to extract:
- Severity: High (from severity 4)
- Category: Endpoint/Evasion
- MITRE ATT&CK: T1055.012 (Process Hollowing)
- Host: DESKTOP-ABC123
- User: CORP\jsmith
- IOC: File hash, path, command line
Configuration Options¶
Severity Mapping¶
CrowdStrike severity maps to Parapet Security:
| CrowdStrike | Value | Parapet Security |
|---|---|---|
| Informational | 1 | Low |
| Low | 2 | Low |
| Medium | 3 | Medium |
| High | 4 | High |
| Critical | 5 | Critical |
Detection Filtering¶
Filter by detection type in your config:
[Filter]
# Include only specific types
detection_types = malware,exploit,ransomware,persistence
# Or exclude specific types
exclude_types = policy_violation,pup
Real-Time vs. Batch¶
| Mode | Latency | Best For |
|---|---|---|
| Real-time | Seconds | Critical detections |
| Batch (5 min) | Minutes | High-volume environments |
Troubleshooting¶
No Events Received¶
-
Verify API credentials:
-
Check connector logs:
-
Verify event stream access: Ensure API client has "Event streams: Read" scope
Missing Detections¶
-
Check severity threshold: Lower
severity_thresholdto capture more events -
Verify detection types: Set
detection_types = allto confirm events flow -
Check Falcon console: Verify detections exist in Falcon → Activity → Detections
Authentication Errors¶
If you see 401 or 403 errors:
- Regenerate API credentials in Falcon Console
- Verify correct cloud URL (us-1, us-2, eu-1)
- Check API client hasn't expired
Security Considerations¶
- Credential storage: Use secrets management (Vault, AWS Secrets Manager)
- Network security: Ensure connector can reach both CrowdStrike API and Parapet Security
- Rate limiting: CrowdStrike has API rate limits; connector handles this automatically
Next Steps¶
- Configure Slack notifications for real-time alerts
- Set up alert filters to focus on what matters
- Understand AI triage results