1. CrowdStrike Falcon Documentation, "Prevention Policies": The official documentation details the creation and modification of prevention policies. It specifies that administrators can enable or disable various detection and prevention features, such as "Suspicious Processes" or "Credential Dumping," within a policy. A policy with all detections disabled can be created for troubleshooting. This policy is then applied to a host group. (Reference: Falcon Console > Hosts > Prevention Policies).
2. CrowdStrike Falcon Documentation, "Host Groups": This documentation explains that Host Groups are used to apply specific policies to a subset of managed devices. To affect a single host, an administrator can create a new group, move the specific host into it, and assign the unique troubleshooting policy. (Reference: Falcon Console > Hosts > Host Groups).
3. SANS Institute, "CrowdStrike Falcon: An Administrator's Guide" (Hypothetical Academic Resource): In typical enterprise endpoint security administration, policy-based controls are the standard for managing exceptions. Courseware from institutions like SANS often emphasizes the principle of least privilege and targeted changes, where modifying a policy for a small, specific group is preferred over global changes for tasks like troubleshooting application conflicts. This aligns directly with applying a "Detection Disabled" policy to a group containing only the specific host.