/deploying-edr-agent-with-crowdstrike
Deploys and configures CrowdStrike Falcon EDR agents across enterprise
$ npx -y skills add mukul975/Anthropic-Cybersecurity-Skills --skill deploying-edr-agent-with-crowdstrike --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/deploying-edr-agent-with-crowdstrike
Context preview
The summary Claude sees to decide when to auto-load this skill.
Deploys and configures CrowdStrike Falcon EDR agents across enterprise
SKILL.md
deploying-edr-agent-with-crowdstrike.SKILL.mdname: 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 extrac
Read more
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 extrac
817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io standard · Works with Claude Code, GitHub Copilot, Codex CLI, Cursor, Gemini CLI & 20+ platforms · 29 security domains · Apache 2.0
Repo: mukul975/Anthropic-Cybersecurity-Skills
Other skills on cybersecurity-skills.
- /abusing-dpapi-for-credential-access
Extract and decrypt Windows DPAPI-protected secrets (Credential Manager, browser logins/cookies, Wi-Fi credentials, KeePass keys) online or offline using SharpDPAPI, SharpChrome, Mimikatz, or Impacket's dpapi.py, including domain-wide decryption via the DPAPI backup key. Use
Open skill - /abusing-shadow-credentials-for-privesc
Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows
Open skill - /achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the
Open skill - /acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images with dd or dcfldd on a Linux forensic workstation, preserving evidence integrity through hash verification (MD5/SHA) during acquisition. Use when imaging a suspect drive, USB device, or memory card for investigation, preserving
Open skill - /analyzing-active-directory-acl-abuse
Detect dangerous ACL misconfigurations in Active Directory using ldap3
Open skill - /analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and
Open skill

