Skip to content
Threat Feed
medium advisory

CrowdStrike Falcon SIEM Integrates with Microsoft Defender EDR

CrowdStrike Falcon Next-Gen SIEM is expanding its capabilities to integrate with third-party EDR solutions, starting with Microsoft Defender, to enable organizations to extend their AI-native SOC across heterogeneous environments without replacing existing endpoint agents.

CrowdStrike Falcon Next-Gen SIEM is evolving to support third-party endpoint detection and response (EDR) solutions, beginning with Microsoft Defender. This integration allows organizations to modernize their Security Operations Center (SOC) without necessitating the replacement of existing endpoint agents. The Falcon platform combines index-free, petabyte-scale search performance with AI-native threat detection, frontline adversary intelligence, and agentic automation. This expansion includes Falcon Onum, a feature embedded within the Falcon platform that facilitates real-time data pipeline management. Falcon Onum ingests, filters, enriches, and routes data in motion to reduce noise, improve data fidelity, and lower infrastructure costs. The goal is to provide a data-agnostic path to an agentic SOC, streamlining data onboarding and reducing storage costs.

Attack Chain

This brief focuses on SIEM integration rather than a specific attack chain, but here’s a generalized scenario where this integration could improve detection:

  1. Initial Access: An attacker gains initial access to an endpoint via phishing or exploitation of a vulnerability.
  2. Execution: The attacker executes malicious code on the endpoint using a tool like PowerShell or a custom script.
  3. Persistence: The attacker establishes persistence by creating a scheduled task or modifying registry keys.
  4. Lateral Movement: The attacker attempts to move laterally to other systems on the network using techniques like pass-the-hash or exploiting SMB vulnerabilities.
  5. Command and Control: The attacker establishes a command and control (C2) channel to communicate with the compromised system.
  6. Data Exfiltration: The attacker identifies and exfiltrates sensitive data from the compromised network.
  7. Impact: The attacker achieves their objective, such as data theft or ransomware deployment.

In this scenario, Microsoft Defender would detect initial malicious activity. Falcon Next-Gen SIEM would ingest and analyze Defender telemetry, correlating it with other data sources to provide a more complete picture of the attack and accelerate response.

Impact

Successful attacks can lead to data breaches, financial losses, and reputational damage. Organizations can experience slower detection and delayed response due to fragmented security systems. The integration of Microsoft Defender telemetry into Falcon Next-Gen SIEM aims to address these challenges by unifying detection, investigation, and response, without altering existing endpoint deployments. By leveraging Falcon Onum, organizations can improve data fidelity, lower infrastructure costs, and strengthen the foundation for AI-driven security operations across the entire ecosystem.

Recommendation

  • Utilize Falcon Next-Gen SIEM to ingest and analyze Microsoft Defender telemetry for enhanced threat detection and response.
  • Implement Falcon Onum for real-time data pipeline management to reduce noise, enrich data, and optimize data routing, as described in the overview.
  • Leverage the federated search capabilities of Falcon Next-Gen SIEM to investigate across live, network, and archived data sources without costly re-ingestion.

Detection coverage 2

Detect PowerShell Downgrade Attack

medium

Detects PowerShell downgrade attacks by monitoring for the execution of older PowerShell versions.

sigma tactics: defense_evasion techniques: T1059.001 sources: process_creation, windows

Detect Suspicious Process Creation from WScript

medium

Detects potential script-based attacks by monitoring process creation events originating from WScript.

sigma tactics: initial_access techniques: T1204.002 sources: process_creation, windows

Detection queries are kept inside the platform. Get full rules →