Deploys and configures CrowdStrike Falcon EDR agents across enterprise endpoints to enable real-time threat detection, behavioral analysis, and automated response. Use when onboarding endpoints to EDR coverage, configuring detection policies, or integrating Falcon telemetry with SIEM platforms. Activates for requests involving CrowdStrike deployment, Falcon sensor installation, EDR policy configuration, or endpoint detection and response.
Instrucciones de origen · Vista previa de solo lectura
name
deploying-edr-agent-with-crowdstrike
description
Deploys and configures CrowdStrike Falcon EDR agents across enterprise endpoints to enable real-time threat detection, behavioral analysis, and automated response. Use when onboarding endpoints to EDR coverage, configuring detection policies, or integrating Falcon telemetry with SIEM platforms. Activates for requests involving CrowdStrike deployment, Falcon sensor installation, EDR policy configuration, or endpoint detection and response.
Deploying CrowdStrike Falcon sensors to Windows, macOS, or Linux endpoints
Configuring Falcon prevention and detection policies for different endpoint groups
Integrating CrowdStrike telemetry with SIEM (Splunk, Elastic, Sentinel) for correlated detection
Troubleshooting sensor connectivity, performance, or detection issues
Do not use this skill for deploying other EDR solutions (Carbon Black, SentinelOne) or for Falcon cloud workload protection (use cloud-specific deployment guides).
Common Misconfigurations & Verification
Prevention policy in detect-only: a host can be Online yet have every Prevention toggle off (Falcon ships detection-only by default). In Host Management confirm the assigned Prevention policy has Behavioral Protection / Next-Gen AV / Malware Protection set to Block (not just Detect), or malware is alerted on but never stopped.
Sensor in Reduced Functionality Mode:falconctl -g --rfm-state must return rfm-state=false. RFM (kernel/cloud mismatch after an OS update) leaves the sensor present but blind.
Host parked in the default policy group: sensor grouping tags (/install ... GROUPING_TAGS="..." or falconctl -s --tags=) must match the assignment rules, or the endpoint silently inherits the permissive default policy instead of the workstation/server policy.
Over-broad exclusions: review Configuration → Exclusions; ML/sensor-visibility wildcards like C:\* or whole-drive paths disable IOAs in those paths.
Verify with a real test: run CsTestDetect.exe (or Atomic Red Team T1059) and confirm a detection appears in the console within ~60s AND streams to your SIEM via the Event Streams TA / FDR. No SIEM event means telemetry is deployed but not integrated.
Prerequisites
CrowdStrike Falcon console access with Falcon Administrator role
Customer ID (CID) and Falcon sensor installer package
Administrative/root access on target endpoints
Network access: endpoints must reach CrowdStrike cloud (ts01-b.cloudsink.net on port 443)
Deployment tool: SCCM, Intune, GPO, Ansible, or manual installation
Workflow
Step 1: Obtain Falcon Sensor Installer and CID
1. Log into Falcon Console: https://falcon.crowdstrike.com
2. Navigate: Host setup and management → Sensor downloads
3. Download the appropriate installer:
- Windows: WindowsSensor_<version>.exe
- macOS: FalconSensorMacOS_<version>.pkg
- Linux: falcon-sensor_<version>_amd64.deb / .rpm
4. Copy the Customer ID (CID) from the Sensor downloads page
- CID format: <32-char-hex>-<2-char-checksum>
# Install sensor packagesudo installer -pkg FalconSensorMacOS_7.18.pkg -target /
# Set CIDsudo /Applications/Falcon.app/Contents/Resources/falconctl license <YOUR_CID>
# Grant Full Disk Access and System Extension via MDM profile# Required for macOS Ventura+ (manual approval or MDM PPPC profile)# MDM payload: com.crowdstrike.falcon.Agent → SystemExtension + Full Disk Access# Verify sensor statussudo /Applications/Falcon.app/Contents/Resources/falconctl stats
Step 5: Configure Prevention Policies
In Falcon Console, navigate to Configuration → Prevention Policies:
Servers (moderate settings to avoid false positives on server workloads)
Critical infrastructure (maximum protection with exception lists)
Step 6: Configure Response Policies
Real-Time Response:
- Enable RTR for all sensor groups
- Configure RTR admin vs. RTR responder roles
- Enable script execution (for IR teams)
- Enable file extraction (for forensics)
Network Containment:
- Pre-authorize containment for specific host groups
- Configure containment exclusions (allow management traffic)
Automated Response:
- Enable automated remediation for high-confidence detections
- Configure kill process action for ransomware detections
- Enable quarantine for malware file detections
Step 7: Validate Deployment
# Windows: Check Falcon sensor status
sc query csagent
# Expected: RUNNING
# Check sensor version
reg query "HKLM\SYSTEM\CrowdStrike\{9b03c1d9-3138-44ed-9fae-d9f4c034b88d}\{16e0423f-7058-48c9-a204-725362b67639}\Default" /v AgentVersion
# Verify cloud connectivity
# In Falcon Console: Host Management → Hosts → search for hostname
# Status should show "Online" with last seen timestamp < 5 minutes
Test detection capability:
# CrowdStrike provides test detection samples
# Download CsTestDetect.exe from Falcon Console → Host setup
# Run on endpoint to generate a test detection
.\CsTestDetect.exe
# Verify detection appears in Falcon Console within 60 seconds
Step 8: SIEM Integration
# Falcon SIEM Connector (Streaming API)
# Configure in Falcon Console: Support → API Clients and Keys
# Create API client with scope: Event Streams → Read
# Use falcon-siem-connector or Falcon Data Replicator (FDR)
# Splunk integration:
# Install CrowdStrike Falcon Event Streams Technical Add-on from Splunkbase
# Configure: Settings → Data inputs → CrowdStrike Falcon Event Streams
# Enter API Client ID and Secret
# Index: crowdstrike_events
# Elastic integration:
# Use Elastic Agent with CrowdStrike module
# Configure: Fleet → Agent policies → Add integration → CrowdStrike
Key Concepts
Term
Definition
Falcon Sensor
Lightweight kernel-mode agent (25-30 MB) that collects endpoint telemetry and enforces prevention policies
CID (Customer ID)
Unique identifier that associates the sensor with your CrowdStrike Falcon tenant
RFM (Reduced Functionality Mode)
State where sensor operates with limited capability due to cloud connectivity loss
Sensor Grouping Tags
Labels applied during installation to auto-assign hosts to groups and policies
RTR (Real-Time Response)
Remote shell capability for incident responders to interact with endpoints through Falcon
IOA (Indicators of Attack)
Behavioral detections based on adversary techniques rather than static signatures
Tools & Systems
CrowdStrike Falcon Console: Cloud-hosted management platform for all Falcon modules
Falcon SIEM Connector: Streams detection and audit events to SIEM platforms
Falcon Data Replicator (FDR): Streams raw endpoint telemetry to S3/cloud storage for hunting
CrowdStrike Falcon API (OAuth2): RESTful API for automation, integration, and custom workflows
PSFalcon: PowerShell module for CrowdStrike Falcon API automation
Common Pitfalls
Missing CID during installation: Sensor installs but never connects to Falcon cloud. Always pass CID during install, not after.
Proxy not configured: In environments with web proxies, configure proxy during installation: /install /quiet CID=<CID> APP_PROXYNAME=proxy.corp.com APP_PROXYPORT=8080.
macOS System Extension blocked: macOS requires explicit approval for kernel/system extensions. Use MDM to pre-approve CrowdStrike extensions before deployment.
Conflicting security products: Running multiple EDR/AV products causes performance issues and false positives. Coordinate exclusions or remove legacy AV before Falcon deployment.
Sensor version pinning: Falcon auto-updates sensors by default. Pin sensor versions in the console for change-controlled environments before testing new versions.
