SOPHOS LIVE DISCOVER / DATA LAKE: MAPPING RECIPE, NOT EXECUTABLE SQL
2026-10-21 | Behavioral hunt, not CVE-specific | Schema and tenant execution pending

Sophos documents Live Endpoint and Data Lake as different sources. Its query
editor uses osquery/SQL, but that does not establish identical tables or fields.
The public documentation inspected did not establish the complete Linux process
creation HISTORY and parent schema needed here. No guessed HISTORY table or column
names are supplied as an executable query. A separate current-state-only example,
../sophos_live_process_snapshot.sql, uses upstream official osquery processes columns.
It is NOT a Data Lake query and is NOT historical process-creation telemetry.

Operator mapping steps:
1. Open Designer Mode and choose the exact source and Linux platform. Check that
   the relevant licensed data is uploaded, retained, and available for the hosts.
2. Follow the official source-specific schema links. Record table, event-time
   units, host identity, child executable/name, command line, parent executable/name,
   and stable process/parent identity fields. Confirm which are actually populated.
3. If this is a process-creation history source, restrict to an agreed time window.
   Select direct children using the parent runtime-name set in ../linux_web_child.yml
   (including frankenphp/lsphp); select the child set in ../linux_web_child.yml.
4. If the source is only a current-process snapshot, label the hunt SNAPSHOT ONLY.
   A parent PID self-join is not equivalent to historical lineage: parents can exit
   and PIDs can be reused. Short-lived commands will be missed. Do not promote this
   to a historical detection without a suitable event source and stable linkage.
5. Have a qualified operator validate a read-only query on synthetic/authorized
   data, then confirm both a known event and a negative control in the tenant.
   Only then save a schema-specific SQL version with the verification record.

False positives: configured local-mail shell handoff, image/video wrappers,
deployment hooks, authorized maintenance, and diagnostics. Check effective
sendmail_path and owned wrapper paths/arguments; do not blanket-exclude sendmail.
Blind spots: no child process, renamed tools, missing parents, uninstrumented
containers, snapshots missing short-lived processes, incomplete retained history.
Triage: inspect the command and ancestry, application ownership, recent changes,
file writes and outbound connections. A match does not establish exploit origin.

Primary sources checked:
https://docs.sophos.com/central/customer/help/en-us/ManageYourProducts/ThreatAnalysisCenter/LiveDiscover/index.html
https://docs.sophos.com/central/customer/help/en-us/ManageYourProducts/ThreatAnalysisCenter/LiveDiscover/EditOrCreateQuery/index.html
https://github.com/osquery/osquery/blob/master/specs/processes.table
https://github.com/osquery/osquery/blob/master/docs/wiki/introduction/sql.md
