crowdstrike-deploy

Deploy and verify CrowdStrike Falcon sensor on Linux hosts and Kubernetes clusters.

Updated May 3, 2026
One-click install
npx skills add https://github.com/miethe/boxbrain-2 --skill crowdstrike-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowdstrike-deploy
Source: https://github.com/miethe/boxbrain-2/tree/main/.claude/skills/crowdstrike-deploy
Command: npx skills add https://github.com/miethe/boxbrain-2 --skill crowdstrike-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the complexity of deploying and validating the CrowdStrike Falcon sensor across IBM-managed Linux virtual machines and Kubernetes clusters, helping teams establish endpoint protection consistently.

Core Features & Use Cases

  • Deployment Planning: Choose between standalone RPM or DEB installation for VMs and Helm DaemonSet deployment for Kubernetes.
  • Sensor Configuration: Configure CrowdStrike customer IDs, grouping tags, trace settings, registry access, and privileged Kubernetes namespaces.
  • Verification and Troubleshooting: Confirm sensor registration and agent identifiers, inspect DaemonSet status, and resolve common installation, startup, and authentication issues.
  • Use Case: Deploy Falcon to a new Linux VM or Kubernetes cluster, apply the required IBM configuration, and verify that the sensor is registered successfully.

Quick Start

Use the crowdstrike-deploy skill to install and verify the Falcon sensor on the specified Linux host or Kubernetes cluster using the appropriate deployment method.

Frequently Asked Questions about crowdstrike-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the CrowdStrike Falcon sensor on Linux VMs and Kubernetes clusters?

Deploy the Falcon sensor by choosing standalone RPM or DEB installation for Linux VMs, or Helm DaemonSet deployment for Kubernetes clusters. Apply required IBM configuration and verify successful sensor registration using applicable administrative tools.

What do I need to verify Falcon sensor registration and troubleshoot installation issues?

Verify Falcon sensor registration by confirming agent identifiers and inspecting DaemonSet status. Troubleshoot installation, startup, and authentication issues using sudo or Kubernetes administrative access, Falcon installation packages or registry credentials, and tools such as systemctl, kubectl, helm, curl, and jq.

Can I use Helm to deploy the Falcon sensor as a DaemonSet in a Kubernetes environment?

Yes, you can use Helm to deploy the Falcon sensor as a DaemonSet in Kubernetes. Configure privileged Kubernetes namespaces and registry access, then verify the DaemonSet status to ensure endpoint protection is established across the cluster.

How do I configure CrowdStrike customer IDs and grouping tags for the Falcon sensor?

Configure CrowdStrike customer IDs, grouping tags, trace settings, and registry access during sensor configuration on IBM-managed Linux hosts and Kubernetes clusters. Apply these settings through the deployment method chosen for your specific environment.

Why is my Falcon sensor not registering after deployment on an IBM-managed Linux host?

If your Falcon sensor is not registering, troubleshoot common installation, startup, and authentication issues. Confirm sensor registration and agent identifiers, verify sudo access, and ensure Falcon installation packages are properly applied to the IBM-managed Linux host.

Does the Falcon sensor deployment support both RPM and DEB package installations?

Yes, Falcon sensor deployment supports both RPM and DEB package installations for standalone Linux VMs. Choose the appropriate package format based on your Linux distribution, then proceed with sensor configuration and registration verification.