Telemetry requirements and ATT&CK¶
The optional Manager module compares a proposed filtering/routing change with declared requirements from a versioned pack. It shows whether supplied sample events retain the required fields and are routed to the selected Sentinel destination.
ATT&CK mappings provide reference context. They do not prove that your detections are enabled or effective. The module does not configure collectors or execute playbooks.
Enable¶
Set SLIMSTREAM_TELEMETRY_ENABLED=true for Manager, or Helm manager.telemetry.enabled=true. The feature is disabled by default. Sign in through the existing Manager authentication and choose Telemetry requirements.
Viewer can read catalogs/reports. Operator can assess samples. Admin imports data/packs, creates bindings, records review and creates draft configuration versions. Existing rollout permissions continue to apply.
Workflow¶
- Import a local Enterprise ATT&CK STIX JSON artifact and record its intended release. The checksum identifies the artifact; independently verify its source. Import does not download external URLs.
- Import a declarative JSON pack against the selected dataset. Review its version, provenance, source schema, technique mappings and requirement tree. The UI explicitly binds the imported pack to the selected dataset.
- Create a binding for the declared source/schema and actual Sentinel emitter name. Field mappings refer to top-level event keys. Table/source settings are declarations and are not checked against a live tenant.
- Select an existing baseline config version. Paste candidate Manager JSON, or copy the current builder settings. Upload/paste a representative sample array.
- Assess and review baseline/candidate findings. Distinguish newly introduced violations, existing gaps and unknown dependencies.
- Record an Admin review reason and decision. An approved current report can create a draft config version. Rollout is a separate action.
Bindings and pack versions are immutable. Create a new binding/version and rerun assessment when mappings or requirements change. A newly created latest config version makes older assessment reviews stale; saving the same draft twice is rejected.
Understand the evidence¶
| Finding | Meaning |
|---|---|
| satisfied_on_sample | Declared requirements held for matching supplied events |
| violated_on_sample | At least one matching sample violated a declared requirement |
| unknown | There was insufficient evidence or an unsupported dependency |
| not_applicable | Explicit requirement-tree outcome; absence of matching events is unknown |
No matching samples do not mean data can be discarded. All-of and any-of checks retain child evidence. A report may remain partial even if a parent alternative succeeds. Detection evidence remains not_tested because no real detection execution is performed.
Preview supports KEEP, DROP and RENAME and bounded scalar comparisons/Boolean conditions. Grok, masking, enrichment, arbitrary expressions and unsupported baseline YAML produce unknown results. KEEP/DROP/RENAME use the runtime's collected top-level field semantics. Conflicting renames resolve by sorted source keys, with the last source winning.
Archiving an event does not satisfy a requirement for immediate SIEM delivery. Retaining a field name while changing its value fails an unchanged requirement. Collection prerequisites, retention, table mapping and live delivery require separate validation.
Privacy and limits¶
Assessment samples are sent to Manager for request-time evaluation. Raw event values are omitted from stored reports, audit logs and errors. They remain transient in process/browser memory; secure erasure is not promised. Candidate configuration is stored for draft creation, following existing secret-reference rules. Do not put literal secrets in configurations or review notes.
Limits: 2 MiB assessment request, 1000 events, 64 KiB/event, 16 bindings, JSON depth 32, two concurrent evaluations and five-second evaluation context. STIX uploads are bounded at 128 MiB/100k objects; pack uploads at 1 MiB. Catalog/report API pages contain at most 50 items and support offset pagination. Limits are currently fixed.
Local demonstration¶
Use a disposable Manager database. From the monorepo:
cd slimstream-manager
SLIMSTREAM_ALLOW_UNAUTHENTICATED_LOOPBACK=true \
SLIMSTREAM_TELEMETRY_ENABLED=true \
go run ./cmd/manager -listen 127.0.0.1:8090 -db /tmp/logstrm-telemetry-demo.db
In another terminal, from slimstream-manager:
python3 examples/telemetry/demo.py
The script creates local catalog/binding/config/report records and should report new_violation after dropping CommandLine. It creates no rollout and sends no events to Sentinel. Open Manager to inspect the report. To use local OIDC instead, provide LOGSTRM_MANAGER_TOKEN with an Admin token to the script.
The shipped process-context pack, events and STIX reference are synthetic demonstrations. They are not a validated PowerShell detection, a native Windows collector, or a production routing policy. The technique reference is PowerShell T1059.001.
Production use requires reviewed rule dependencies, representative source schemas, collector prerequisites and real SIEM validation in your environment. See MITRE's official ATT&CK data and tools page for data sources and verify applicable attribution/redistribution terms before distributing upstream content.