Can I upload a raw .evtx file?
Yes, since 14 November 2026 — copy the file off the Windows machine and upload it, with no conversion step. The EvtxECmd CSV export (.evtx.csv) is still accepted as well, and was the only route before that date.
Is this a SIEM?
No, and it is not sold as a replacement for one. A SIEM ingests your events continuously, retains them and alerts on a live stream. This analyses one corpus you upload and keeps nothing afterwards. Teams that run a SIEM use this for the artefact that never reached it: a laptop with no agent, a file attached to a ticket, an export from a system outside the pipeline.
Are my logs stored?
No. The corpus and the report exist in memory for the life of the analysis and are then evicted — no database row, no file on disk, no history. The one stored record is an incident, once it is opened, which keeps its priority and its response clocks. The corpus it came from still is not.
Does it use Sigma rules?
Not for detection. The analysis runs 17 deterministic detections of its own, each showing its arithmetic. Sigma appears in two places: a Sigma or YARA pack you upload is recognised as rules rather than events, and, when the analysis engine is available, the report drafts an experimental detection rule for each finding in Sigma, KQL and SPL for your own SIEM.
What does a partial record mean on an .evtx upload?
The record was read and kept, with its channel, event ID and timestamp intact, but part of its EventData contains a BinXML token type the decoder flags instead of guessing. It still appears on the timeline, and the count of partial records is shown on every run so an incomplete read is visible rather than silent.
Does it work on Linux and cloud logs, or only Windows?
Both. Windows event logs are the format that needed binary decoding, but the accepted inputs include syslog, CEF, LEEF, Apache and nginx access logs, Zeek and Suricata output, Wazuh alerts, osquery results, and OCSF or ECS records from any source that emits them.
Do you hold a SOC 2 report?
No, and the name of this module is unrelated to that: a SOC here is a security operations centre, not the AICPA audit. We hold no SOC 2 report and no ISO 27001 certificate, the trust centre says so, and we answer security questionnaires in writing instead.