Skip to content

Endpoint Visibility Edr Telemetry

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

Host-level instrumentation โ€” turn endpoints into rich telemetry sources for detection and hunting

Part of the ULTIMATE CYBERSECURITY MASTER GUIDE ยท Incident Response section

Blue Team Telemetry Windows | Linux


Collection and detection links: Velociraptor evidence-triage workflow and Sigma/osquery/Elastic rule validation complement Sysmon, auditd and osquery. Agent telemetry alone is not evidence of full detection coverage.

๐ŸŽฏ Purpose

Index for the Endpoint Visibility sub-section โ€” deployment and configuration guides for the host-level instrumentation that feeds a SIEM: Windows Sysmon, Linux auditd/syslog, and cross-platform Osquery.

โš™๏ธ Function

Links to a guide per instrumentation source โ€” installation, configuration, the key events/queries that matter for detection, and how to forward the resulting telemetry into a SIEM.

๐Ÿ† Goal

Enable a defender to instrument Windows and Linux hosts so that process, network, file, and authentication activity is captured with enough fidelity to detect and reconstruct an attack.

๐Ÿ“‹ When To Use

  • Standing up endpoint telemetry before (or alongside) a SIEM
  • Deciding what to log on Windows (Sysmon) vs Linux (auditd) hosts
  • Adding SQL-based, on-demand host inspection with Osquery for threat hunting
  • Tuning event volume so detections fire without drowning the SIEM in noise

๐Ÿ“‹ Table Of Contents


๐ŸŽฏ Overview

A SIEM is only as good as the telemetry it ingests. Endpoint visibility is the practice of instrumenting hosts so that security-relevant activity โ€” process creation, network connections, file writes, image loads, logons โ€” is recorded in a form you can search and alert on.

This sub-section covers the three sources that do most of the heavy lifting in a homelab or small SOC. They are complementary: Sysmon and auditd provide continuous event streams, while Osquery provides on-demand, point-in-time inspection of host state.

Tip

Deploy an event stream first (Sysmon on Windows, auditd on Linux), forward it to your SIEM, then layer Osquery on top for interactive hunting.


๐Ÿ—‚๏ธ Instrumentation Sources

Source Guide Platform Model Best For
๐ŸชŸ Sysmon Windows/sysmon.md Windows Continuous event stream Rich process/network/file/DNS tracing
๐Ÿง Auditd / Syslog Linux/auditd_syslog.md Linux Continuous event stream Kernel-level syscall & file/session auditing
๐Ÿ”Ž Osquery Linux/osquery.md Cross-platform On-demand SQL queries Interactive threat hunting & host state

๐Ÿ“š Deployment Guides

๐ŸชŸ Windows Sysmon

Deploy and configure Sysmon with community configs (SwiftOnSecurity, Olaf Hartong). Covers install/update, the configuration XML structure, and the critical event IDs โ€” 1 (process create), 3 (network), 7 (image load), 8 (CreateRemoteThread), 10 (process access), 11 (file create), 22 (DNS) โ€” plus hashing, SIEM forwarding, and a detection use case per event type. The single highest-value Windows telemetry source.

Harden Linux logging with auditd and rsyslog/syslog-ng. Covers auditd rule syntax (syscall auditing, file-access watches, user-session tracking), pre-built rule sets (STIG, CIS), log forwarding to a SIEM, parsing with ausearch/aureport, and common detection use cases.

๐Ÿ”Ž Osquery

Instrument hosts as a SQL-queryable surface. Covers installation (with the modern signed-by apt keyring), configuration, and queries for proactive threat hunting and monitoring โ€” ideal for asking ad-hoc questions ("which processes have a deleted binary on disk?") across a fleet.


Starred Companion Tools For One-time Windows Audits

  • DAT โ€” dag's Audit Tool โ€” PowerShell inventory of Windows hardware, accounts, services, networking, updates, Defender and event-log information. Check the script, permissions and sensitive output handling before using it on a client machine.
  • PNWC SystemTester โ€” your portable Windows/Sysinternals diagnostic and malware-triage toolkit; useful for technician baselines and pre/post-repair reports. A clean diagnostic run does not prove the absence of compromise.

These produce point-in-time observations; Sysmon, auditd, osquery and a SIEM still provide the continuous telemetry described below.

Post-assessment Workstation Provisioning (Different Phase)

PNWC DeployWorkstation automates Windows application provisioning, updates and removal of selected preinstalled software. It belongs in an approved deployment or rebuild workflow after investigation, required evidence preservation and recovery planningโ€”not in live malware triage. Test change lists on a disposable VM, obtain customer approval for removals and keep rollback/restore options available.

๐Ÿš€ Deployment Workflow

1. Instrument
   โ””โ”€> Windows: install Sysmon with a curated config (Olaf Hartong / SwiftOnSecurity).
   โ””โ”€> Linux:   load an auditd rule set (CIS/STIG) + configure rsyslog forwarding.

2. Forward
   โ””โ”€> Ship events to your SIEM (Winlogbeat/Filebeat, or the SIEM's own agent).
   โ””โ”€> Confirm events index correctly โ€” see ../SIEM/README.md.

3. Hunt on demand
   โ””โ”€> Add Osquery for interactive, SQL-based host inspection.

4. Tune
   โ””โ”€> Trim noisy events; keep the high-signal IDs. Map detections to MITRE ATT&CK.

โš ๏ธ Monitoring, Consent & Legal Warning

โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•
              โš ๏ธ  DEPLOY TELEMETRY ONLY WITH AUTHORIZATION  โš ๏ธ
โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•

โ–บ Only install agents/telemetry on systems you own or are explicitly
  authorized (in writing) to monitor. Endpoint monitoring can capture
  keystrokes, commands, and personal data.

โ–บ Covert monitoring of users/employees without proper notice can violate
  wiretap/interception, privacy, and labor laws โ€” coordinate with legal/HR.

โ–บ Forwarded logs often contain PII/credentials; protect the SIEM and
  transport (TLS) accordingly, and follow GDPR/HIPAA/CCPA where applicable.
โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•

๐Ÿค Contributing

Contributions from detection engineers and SOC analysts are welcome.

What we accept:

  • โœ… Sysmon config tweaks and per-event-ID detection notes
  • โœ… auditd rule sets and rsyslog/syslog-ng forwarding configs
  • โœ… Useful Osquery packs/queries for hunting
  • โœ… SIEM field-mapping notes

Guidelines:

  1. Sanitize sample events of real PII/credentials.
  2. Note the OS/tool version tested.
  3. Describe the detection value in your PR.

๐Ÿ“š Resources


๐Ÿ”— Quick Links


๐Ÿ›ก๏ธ Visibility is the foundation of defense โ€” instrument hosts ethically and legally.

Maintained by Pacific Northwest Computers (PNWC)


โฌ…๏ธ Back to Master Index | ๐ŸŽฏ Role Navigation | Legal Notice


๐Ÿ“„ Source: IncidentResponse/Endpoint-Visibility/README.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Incident Response

Clone this wiki locally