| Telemetry | Windows | Linux | macOS |
|---|---|---|---|
| Process start and exit | ✓ | ✓ | ✓ |
| Network connections | ✓ | ✓ | ✓ ¹ |
| File create, modify, rename, delete | ✓ | ✓ | ✓ |
| DNS queries | ✓ | ✓ ² | ✓ ² |
| DNS answers | ✓ | ✓ ² | |
| Registry | ✓ | ||
| Image (DLL) load | ✓ ⁴ | ||
| PowerShell script blocks and modules | ✓ ³ | ||
| WMI activity | ✓ | ||
| Service installs, scheduled tasks | ✓ | ||
| Security audit events | ✓ ³ | ||
| Microsoft Defender Operational events | ✓ | ||
| Application channel events | ✓ | ||
| Driver loads | ✓ |
- Captured from the network and matched to a process on a best-effort basis.
- Plain DNS on port 53 only. DNS over HTTPS or TLS is not visible.
- Needs host policy, see Windows host logging.
- Image-load rules receive live DLL loads. This is a dense event stream, so enabling a broad rule corpus can increase CPU and memory use during DLL-heavy workloads.
macOS support is experimental. Detailed gaps are in Limitations.
A blank cell in the table above is one of three things.
| Gap | Status | Platform | Why |
|---|---|---|---|
Named pipes (pipe_created) |
Unavailable without a driver | Windows | Kernel-File ETW records no pipe name or creator for a pipe exchange. |
| Process tampering | Unavailable without a driver | Windows | The only source is the Threat Intelligence provider, which is closed to a process that is not a protected process light. |
| Process access | Planned | Windows | Kernel-Audit-API-Calls gives the access, but not the true GrantedAccess, see Limitations. |
| Remote threads | Planned | Windows | Thread starts give the source and target process, with field gaps for rules that need module or function names. |
| File reads of sensitive paths | Planned | Windows, Linux | Bounded to sensitive paths, not every read. |
| Alternate data streams | Planned | Windows | Stream names come from ETW, but contents and hashes need a bounded read. |
| Raw device reads | Planned | Windows | Raw reads of physical drives. |
Anything else not in the table is not collected today and has no decision recorded.
These are deliberate boundaries, not gaps to close.
- Other platforms. Rustinel runs on Windows, Linux, and macOS hosts. ESXi and other hypervisors, network and edge devices, and mobile devices are not platforms.
- Per-host correlation. Correlation state lives in one agent. Correlating across hosts belongs to the SIEM that receives the alerts.
- Inventory and exposure. Rustinel collects no software inventory and no vulnerability exposure data.
- Blocking. Linux (BPF LSM) and macOS (Endpoint Security AUTH events) could block an action before it happens. Rustinel does not use them: detection stays passive by decision, see Security model.
CI loads every rule from SigmaHQ commit da9bb07 (3,783 rules) and checks the result against a pinned baseline.
Rules that load against a collector on each platform:
| Platform | Rules |
|---|---|
| Windows | 2,709 |
| Linux | 178 |
| macOS | 86 |
The rest are skipped: they target another platform, a cloud or network product, or a Linux log service Rustinel does not read, such as auditd.
A rule can load without error and still never fire, in two ways:
- No collector.
The platform does not collect the rule's logsource.
rustinel doctorcounts these rules assigma_rules_inert. - A field is never filled. The rule needs a field listed in Field availability.
rustinel sigma doctor --platform <platform> gives a verdict for each rule, taking or branches and negation into account, see Compatibility diagnostics.
!!! note "Rule count is not coverage" A 3,000-rule pack on Linux does not give 3,000 detections: most SigmaHQ rules are written for Windows. Judge a pack by what its rules reference.
Generated from FIELD_AVAILABILITY.
These count fields, not rules: a rule that references a Never field inside an or branch can still fire.
| View | Platform | Always | Conditional | Never |
|---|---|---|---|---|
sysmon |
windows | 217 | 1139 | 65 |
sysmon |
linux | 19 | 51 | 15 |
sysmon |
macos | 27 | 28 | 28 |
auditd |
linux | 15 | 23 | 47 |
The complete machine-readable baseline is compatibility/field-availability.json.