What it does. 'Deploys and configures CrowdStrike Falcon EDR agents across enterprise Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).

Upstream	mukul975/Anthropic-Cybersecurity-Skills
Skill file	skills/deploying-edr-agent-with-crowdstrike/SKILL.md
License	Apache-2.0 (skill folder LICENSE)
Author	mukul975
Fetched	2026-09-10

Install

• npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill deploying-edr-agent-with-crowdstrike, or copy the skill folder into ~/.claude/skills/deploying-edr-agent-with-crowdstrike/.
• Raw file: curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/deploying-edr-agent-with-crowdstrike/SKILL.md

SKILL.md (verbatim)

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.

  '
domain: cybersecurity
subdomain: endpoint-security
tags:
- endpoint
- edr
- CrowdStrike
- Falcon
- threat-detection
- sensor-deployment
version: 1.0.0
author: mahipal
license: Apache-2.0
nist_ai_rmf:
- GOVERN-1.1
- MEASURE-2.7
- MANAGE-3.1
- MAP-5.1
- MANAGE-2.4
atlas_techniques:
- AML.T0070
- AML.T0066
- AML.T0082
nist_csf:
- PR.PS-01
- PR.PS-02
- DE.CM-01
- PR.IR-01
mitre_attack:
- T1003.001
- T1055
- T1059.001
- T1486
- T1071.001

Deploying EDR Agent with CrowdStrike

When to Use

Use this skill when:

• 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).

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>

Step 2: Deploy Falcon Sensor - Windows

Silent installation via command line:

WindowsSensor_7.18.17106.exe /install /quiet /norestart CID=<YOUR_CID>

SCCM deployment:

1. Create an Application in SCCM
2. Deployment type: Script Installer
3. Install command: WindowsSensor_7.18.17106.exe /install /quiet /norestart CID=<CID>
4. Detection method: Registry key exists
   - HKLM\SYSTEM\CrowdStrike\{9b03c1d9-3138-44ed-9fae-d9f4c034b88d}\{16e0423f-7058-48c9-a204-725362b67639}\Default
5. Deploy to target collection
6. Deployment purpose: Required (for mandatory installation)

Microsoft Intune deployment:

1. Navigate: Devices → Windows → Configuration profiles
2. Create Win32 app deployment
3. Upload .intunewin package (wrapped sensor installer)
4. Install command: WindowsSensor_7.18.17106.exe /install /quiet /norestart CID=<CID>
5. Detection rule: File exists C:\Windows\System32\drivers\CrowdStrike\csagent.sys
6. Assign to device group

GPO deployment:

# Create startup script that checks for existing installation
$sensorPath = "C:\Windows\System32\drivers\CrowdStrike\csagent.sys"
if (-not (Test-Path $sensorPath)) {
    Start-Process -FilePath "\\fileserver\CrowdStrike\WindowsSensor.exe" `
      -ArgumentList "/install /quiet /norestart CID=<CID>" -Wait
}

Step 3: Deploy Falcon Sensor - Linux

# Debian/Ubuntu
sudo dpkg -i falcon-sensor_7.18.0-17106_amd64.deb
sudo /opt/CrowdStrike/falconctl -s -f --cid=<YOUR_CID>
sudo systemctl start falcon-sensor
sudo systemctl enable falcon-sensor

# RHEL/CentOS
sudo yum install falcon-sensor-7.18.0-17106.el8.x86_64.rpm
sudo /opt/CrowdStrike/falconctl -s -f --cid=<YOUR_CID>
sudo systemctl start falcon-sensor
sudo systemctl enable falcon-sensor

# Verify sensor is running and connected
sudo /opt/CrowdStrike/falconctl -g --rfm-state
# Expected output: rfm-state=false (sensor is communicating with cloud)

Step 4: Deploy Falcon Sensor - macOS

# Install sensor package
sudo installer -pkg FalconSensorMacOS_7.18.pkg -target /

# Set CID
sudo /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 status
sudo /Applications/Falcon.app/Contents/Resources/falconctl stats

Step 5: Configure Prevention Policies

In Falcon Console, navigate to Configuration → Prevention Policies:

Recommended prevention policy settings:

Machine Learning:
  - Cloud ML: Aggressive (extra protection, may increase false positives)
  - Sensor ML: Moderate
  - Adware & PUP: Moderate

Behavioral Protection:
  - On Write: Enabled (detect malware on file creation)
  - On Sensor ML: Enabled
  - Interpreter-Only: Enabled (detect script-based attacks)

Exploit Mitigation:
  - Exploit behavior protection: Enabled
  - Memory scanning: Enabled (detects in-memory attacks)
  - Code injection: Enabled

Ransomware:
  - Ransomware protection: Enabled
  - Shadow copy protection: Enabled
  - MBR protection: Enabled

Create separate policies for:

• Workstations (aggressive settings)
• 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.

Other files in this skill

• LICENSE
• assets/template.md
• references/api-reference.md
• references/standards.md
• references/workflows.md
• scripts/agent.py
• scripts/process.py

assets/template.md (verbatim)

CrowdStrike Falcon EDR Deployment Template

Deployment Information

Field	Value
Falcon Tenant
Customer ID (CID)
Sensor Version
Deployment Tool	SCCM / Intune / GPO / Ansible / Manual
Target Environment	Production / Staging / Dev
Deployment Date
Deployment Lead

Pre-Deployment Checklist

• Falcon Console access verified with Administrator role
• CID obtained from Sensor downloads page
• Sensor installer downloaded for all target OS platforms
• Network connectivity verified: endpoints can reach ts01-b.cloudsink.net:443
• Proxy configuration documented (if applicable)
• Prevention policies created for each endpoint group
• Sensor update policy configured (auto-update or pinned version)
• Existing AV/EDR removal plan documented
• Exclusion list prepared for known LOB applications
• Change management ticket approved

Deployment Scope

Endpoint Group	Count	OS	Policy	Deployment Phase
Workstations		Windows 11	WS-Prevention-L1	Phase 1
Standard Servers		Windows Server 2022	SRV-Prevention	Phase 2
Linux Servers		Ubuntu 22.04	LNX-Prevention	Phase 2
macOS Endpoints		macOS Ventura	MAC-Prevention	Phase 3
Critical Servers		Mixed	CRIT-Prevention	Phase 4

Policy Configuration

Prevention Policy Settings

Setting	Workstations	Servers	Critical
Cloud ML	Aggressive	Moderate	Aggressive
Sensor ML	Moderate	Cautious	Moderate
On Write	Enabled	Enabled	Enabled
Script-based Execution	Enabled	Enabled	Enabled
Ransomware Protection	Enabled	Enabled	Enabled
Exploit Protection	Enabled	Enabled	Enabled

Exclusions Applied

Path/Process	Reason	Policy Group	Approved By

Post-Deployment Validation

• All target endpoints show "Online" in Falcon Console
• Correct prevention policy applied to each host group
• Test detection generated with CsTestDetect and visible in console
• No RFM (Reduced Functionality Mode) hosts
• No critical application performance degradation reported
• SIEM integration receiving events
• RTR access verified for IR team

Deployment Metrics

Metric	Target	Actual
Coverage (% of endpoints with sensor)	100%
Online rate	>98%
Sensor version compliance	>95% same version
Policy assignment accuracy	100%
Mean time to deploy (per phase)	<5 business days

Issues and Remediation

Issue	Affected Hosts	Root Cause	Resolution	Status

Sign-Off

Role	Name	Date
Security Engineer
IT Operations
SOC Manager

references/api-reference.md (verbatim)

CrowdStrike EDR Deployment — API Reference

Libraries

Library	Install	Purpose
crowdstrike-falconpy	pip install crowdstrike-falconpy	Official CrowdStrike Falcon SDK

Key FalconPy Service Classes

Class	Description
Hosts(client_id, client_secret)	Host/device management
Detections(client_id, client_secret)	Detection queries and management
RealTimeResponse(client_id, client_secret)	RTR session management
SensorDownload(client_id, client_secret)	Sensor installer download
Prevention(client_id, client_secret)	Prevention policy management

Key Methods

Method	Description
hosts.query_devices_by_filter(filter=, limit=)	Query host IDs
hosts.get_device_details(ids=[])	Get host details
hosts.perform_action(action_name="contain", ids=[])	Contain/lift containment
detections.query_detects(filter=, sort=)	Query detection IDs
detections.get_detect_summaries(body={"ids": []})	Get detection details

FQL Filter Examples

platform_name:'Windows' + status:'normal'
last_seen:>='2024-01-01T00:00:00Z'
hostname:'*server*'

External References

• FalconPy Documentation
• CrowdStrike API Swagger
• FalconPy GitHub

references/standards.md (verbatim)

Standards & References - Deploying EDR Agent with CrowdStrike

Primary Standards

MITRE ATT&CK Enterprise Framework

• Publisher: MITRE Corporation
• URL: https://attack.mitre.org/
• Relevance: CrowdStrike Falcon maps detections to ATT&CK techniques; understanding ATT&CK is essential for tuning detection policies
• Key tactics for EDR: Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Lateral Movement

NIST SP 800-83 Rev 1 - Guide to Malware Incident Prevention and Handling

• Publisher: NIST
• Relevance: Defines endpoint protection architecture including EDR placement and malware prevention controls

CIS Control 10 - Malware Defenses

• Publisher: Center for Internet Security
• Relevance: CIS Controls v8 Control 10 mandates deploying anti-malware with centralized management and automated updates

CrowdStrike-Specific References

CrowdStrike Falcon Deployment Guide

• Scope: Official deployment procedures for Windows, macOS, Linux sensors
• Key sections: Silent install parameters, proxy configuration, sensor grouping tags
• Access: Falcon Console → Support → Documentation

CrowdStrike Falcon API Documentation

• URL: https://falcon.crowdstrike.com/documentation/
• Scope: OAuth2 authentication, host management, detection management, RTR APIs
• Key endpoints: /devices/queries/devices/v1, /detects/queries/detects/v1

Falcon SIEM Integration Guide

• Scope: Event streaming via SIEM Connector, FDR, and direct API
• Supported SIEMs: Splunk, Elastic, Microsoft Sentinel, IBM QRadar, ArcSight

Compliance Mappings

Framework	Requirement	CrowdStrike Coverage
PCI DSS 4.0	5.2 - Anti-malware on systems	Falcon sensor on all in-scope endpoints
HIPAA	164.308(a)(5)(ii)(B) - Protection from malware	Falcon prevention + detection
SOC 2	CC6.8 - Malicious software prevention	Falcon sensor with prevention policies
NIST 800-171	3.14.2 - Malicious code protection	Falcon ML + behavioral detection
ISO 27001	A.12.2.1 - Controls against malware	Falcon sensor with automated response

Industry Benchmarks

• MITRE Engenuity ATT&CK Evaluations: CrowdStrike Falcon regularly achieves high detection scores in Enterprise evaluations
• Gartner Magic Quadrant for Endpoint Protection: CrowdStrike positioned as Leader
• Forrester Wave Endpoint Detection and Response: CrowdStrike rated Strong Performer/Leader

references/workflows.md (verbatim)

Workflows - Deploying EDR Agent with CrowdStrike

Workflow 1: Enterprise Sensor Rollout

[Plan Deployment]
    │
    ├── Obtain Falcon Console access and CID
    ├── Download sensor installer for each OS
    ├── Create deployment groups (Workstations, Servers, VDI)
    │
    ▼
[Configure Policies Before Deployment]
    │
    ├── Create prevention policies per group
    ├── Configure sensor update policies (pinned vs. auto-update)
    ├── Set sensor grouping tags for auto-assignment
    │
    ▼
[Pilot Deployment (5% of endpoints)]
    │
    ├── Deploy via SCCM/Intune to pilot group
    ├── Monitor for 1 week: performance impact, false positives
    ├── Tune exclusions for LOB applications
    │
    ▼
[Validation]
    │
    ├── All pilot hosts show "Online" in Falcon Console
    ├── Test detection with CsTestDetect
    ├── No critical application breakage
    │
    ▼
[Production Rollout (phased)]
    │
    ├── Phase 1: Workstations (2 weeks)
    ├── Phase 2: Standard servers (2 weeks)
    ├── Phase 3: Critical servers (1 week, change window)
    │
    ▼
[Post-Deployment]
    │
    ├── Enable SIEM integration
    ├── Configure automated response policies
    ├── Establish exclusion review cadence (monthly)
    └── Train SOC on Falcon Console workflows

Workflow 2: Detection Triage in Falcon Console

[New Detection Alert]
    │
    ▼
[Review Detection in Falcon Console]
    │
    ├── Severity: Critical/High/Medium/Low/Informational
    ├── Tactic & Technique (ATT&CK mapping)
    ├── Process tree visualization
    ├── Network connections
    │
    ▼
[Assess: True Positive or False Positive?]
    │
    ├── True Positive ──► [Contain Host via Network Containment]
    │                          │
    │                          ▼
    │                     [Launch RTR session for investigation]
    │                          │
    │                          ▼
    │                     [Collect artifacts, kill malicious processes]
    │                          │
    │                          ▼
    │                     [Remediate and release from containment]
    │
    └── False Positive ──► [Create exclusion rule]
                                │
                                ▼
                           [Document exclusion with justification]
                                │
                                ▼
                           [Mark detection as false positive]

Workflow 3: Sensor Troubleshooting

[Sensor Issue Reported]
    │
    ▼
[Check Falcon Console Host Status]
    │
    ├── Online ──► [Issue is not connectivity; check policy assignment]
    │
    └── Offline / RFM ──► [Check network connectivity]
                               │
                               ├── Can reach ts01-b.cloudsink.net:443?
                               │     │
                               │     ├── Yes ──► [Check proxy settings]
                               │     │              ▼
                               │     │          [Reconfigure: falconctl -s --apd=false --aph=proxy --app=8080]
                               │     │
                               │     └── No ──► [Firewall blocking; add CrowdStrike domains to allowlist]
                               │
                               ▼
                          [Check sensor service status]
                               │
                               ├── Service running ──► [Review sensor logs in C:\Windows\System32\drivers\CrowdStrike\]
                               │
                               └── Service stopped ──► [Restart: sc start csagent (Windows) or systemctl start falcon-sensor (Linux)]

Workflow 4: Sensor Version Upgrade

[New Sensor Version Available]
    │
    ▼
[Review Release Notes in Falcon Console]
    │
    ▼
[Test on pilot group (N-1 update policy)]
    │
    ├── No issues after 1 week ──► [Move production to N update policy]
    │
    └── Issues found ──► [Hold on current version, file support ticket]
                              │
                              ▼
                         [Pin current version in sensor update policy]

Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.