# Linux process hunts: choose a real source

The five Sigma files use the established linux/process_creation taxonomy and only Image, ParentImage, CommandLine, and User in detection conditions. Typical sources include Sysmon for Linux Event 1 or another supported process-creation integration with a documented Sigma mapping. They need no Deception Check tables, lineage-validity flag, custom finding feed, or internal normalized schema.

Required values are strings from actual process events. Image and ParentImage are executable paths; CommandLine is captured process command text; User is the source's recorded account label. Missing required values fail the corresponding hunt. Do not substitute empty, zero, or nearby events for unavailable fields. Native translations use their actual documented fields, with differences below. A single event does not prove a complete exploit chain.

Microsoft: DeviceProcessEvents is restricted to a current DeviceInfo Linux inventory. The converted Linux pipeline uses FolderPath and InitiatingProcessFolderPath for image paths, ProcessCommandLine for command text, and AccountName for the process account. Check these fields on real Linux events. The query must refer to the initiating process, not its parent. Inventory absence/staleness and source truncation reduce coverage.

CrowdStrike: ProcessRollup2 with event_platform=Lin uses ImageFileName, CommandLine, ParentBaseFileName, and UID. The parent field is a basename, so the hand-native queries intentionally remove the leading path slash from the Sigma parent pattern. Root uses UID=0, not a missing account label. These queries do not assume Falcon runs on ESXi. Default Sigma backend parent-path conversion was not accepted as equivalent.

Splunk: select the index receiving Sysmon for Linux XML in syslog. The supplied queries require provider Linux-Sysmon and EventID 1, extract the actual EventData fields, and then apply the real Splunk backend expression. A supported Sysmon Linux add-on is another collection route. Inspect message truncation and field values. These files do not assume a populated CIM data model. XML entity decoding is performed for command text; a changed source layout must be tested before use.

Sumo: select the source category receiving full Sysmon for Linux XML messages. Queries isolate the Event element, require provider Linux-Sysmon and EventID 1, and use documented XPath extraction of real EventData fields. XML decoding preserves command text entities. Multiline, namespaced, truncated, or reformatted payloads need source-specific validation; a failed parse must be monitored separately. The predicates are source-scoped; these are not arbitrary JSON normalization requirements.

Sophos: select a connected supported Linux endpoint and the Live Endpoint/Live Discover query source. The supplied SQL reads the core osquery processes snapshot; it is not a Data Lake query and does not imply that Sophos has no historical capabilities. Snapshot pid joins use parent start-time ordering but /proc collection is not atomic. Exited parents, short-lived children, reparenting, and earlier privilege changes can be missed. euid=0 may be namespace root rather than host root. Versioned php-fpm GLOB is broader than the event regex, and D6 snapshot SQL intentionally misses combined short options such as -NTR. D2 snapshot SQL is a broader path/tool candidate than the event command regex. Review the actual process path and command text.

Run event hunts over a bounded 15-minute window, deduplicate by source event identity or asset plus stable process identity, and establish 7-14 days of reviewed application baselines before enabling alerts. Scope exceptions to an asset/service, exact executable or hash, account, owner, reason, and expiry. D4/D5/D6 use direct parents only; deeper ancestry and in-process PHP activity are outside this pack. D5 observes a root-account child; it does not establish that the parent was non-root or prove kernel privilege escalation. D6 records a candidate forwarding request, not tunnel success. D6 is lexical: option-like text in a remote command may match; verify SSH argument position, and expect spelling/case variants to be missed.


## Access and collection prerequisites

Use an authorized account with query access and an active entitlement for the chosen feature. These files do not supply licenses, onboard devices, enable process capture, or deploy collectors. Check edition, supported Linux distribution, sensor version, retention, and role access in the current product documentation and your tenant before use.

| Route | Normal collection and access needed | First local check |
| --- | --- | --- |
| Microsoft Defender XDR | Linux devices onboarded to Defender for Endpoint; an entitlement and role permitting Defender XDR Advanced Hunting over endpoint data; populated DeviceProcessEvents and DeviceInfo | Confirm a known Linux process event, its immediate initiating process, account, and fresh inventory |
| CrowdStrike Linux | Supported Falcon Linux sensor sending ProcessRollup2; licensed access to the event-search/CQL feature that holds these records | Select Lin records and inspect ImageFileName, ParentBaseFileName, CommandLine, and numeric UID |
| Splunk Linux | Sysmon for Linux configured to capture Event 1; syslog forwarding or supported add-on ingestion; licensed ingestion/search capacity and index search access | Replace REPLACE_LINUX_SYSMON_INDEX; verify intact XML, provider, event ID, and extracted paths |
| Sumo Logic Linux | Sysmon Event 1 XML collected through a configured collector/source; licensed ingestion/search and source-category access | Replace REPLACE_LINUX_SYSMON_SOURCE_CATEGORY; verify intact XML and successful XPath extraction |
| Sophos Linux | Supported connected Linux endpoint; product entitlement and role exposing Live Discover/Live Endpoint custom endpoint queries | Select the endpoint source, verify processes columns, and inspect a benign current parent/child pair |

Set a 15-minute time-picker window for CrowdStrike, Splunk, and Sumo event hunts. The Microsoft query includes that bound. Sophos returns current running state; the time picker cannot turn it into a history of process starts. Wider historical searches require a deliberate local adjustment and a new baseline.
