Skip to main content
Free plan, no cardStart free

SOCSOC Analyst · updated 2026-11-15

SOC log analysis and Windows event log (.evtx) triage

Upload one log corpus, including a raw Windows .evtx, and get a MITRE-mapped assessment with the arithmetic behind every finding. Your logs are never stored.

For: Security analysts, incident responders and engineering teams without a SOC who have one log file, one machine and one question — and no ingest pipeline to point at it.

acme-shop / checkout-flow.recIllustrative
1 selector healed#pay-now-btn[data-test="pay"]

Capabilities

Raw binary .evtx, no export step

Copy a Windows event log off the machine and upload it. The decoder reads the file, chunk and record headers and the BinXML inside them; a record it cannot fully read is marked partial rather than quietly shortened. Validated on 1,961 records from four real Windows channels.

Read more: Raw binary .evtx, no export step

Reads the tools you already run

Zeek logs with their #fields schema and conn_state outcomes, Suricata EVE JSON with severity translated, Wazuh alerts with rule.level and rule.mitre, Sysmon and osquery exports with quote-aware command lines, OCSF and ECS where class_uid and event.outcome are authoritative, Volatility 3 and Sleuth Kit bodyfiles with MACB timestamps preserved.

17 deterministic detections, mapped to ATT&CK

Credential brute force, password spraying, a success straight after repeated failures, C2 beaconing, port scanning, DGA-like domains, outbound volume outliers, living-off-the-land binaries, log tampering, web attack payloads, plaintext credentials in log data, account enumeration, rare activity, off-hours activity, impossible travel, error spikes and malware indicators. Each hit carries its MITRE ATT&CK technique, and the hits are assembled into a kill chain.

The arithmetic behind every finding

Each finding shows the metric, the value, the threshold and the method that produced it, and a confidence computed as a Bayesian posterior from the rule’s prior, sensitivity and false-positive rate, not set by hand, so an analyst can overturn it instead of trusting it.

A rule pack is not an event

A Sigma or YARA pack you upload is classified as rules and never swept into the event stream; a STIX 2.1 or MISP bundle is classified as intel, with to_ids honoured. Your detection rules are never counted as suspicious activity.

What this corpus can and cannot support

The report grades what the uploaded file can support and, when the analysis engine is available, lists in its shift handoff what the file cannot answer, so a thin log reads as thin rather than as clean. A missing data source is reported as a gap, never as a finding of no harm.

Detection drafts for your own SIEM (experimental)

When the analysis engine is available, the report drafts a detection rule for each finding in Sigma, KQL for Microsoft Sentinel and Defender, and SPL for Splunk, with its false-positive risk and tuning notes. The drafts are labelled experimental: review one before you deploy it.

Your assets set the priority

Criticality comes from the asset inventory a team owner or a single-user account maintains, so the same event on a build agent and on a domain controller do not arrive at the same priority. Until the estate is inventoried, every priority band is labelled provisional.

An incident register with response clocks

An incident is the one stored record: the register lists open incidents worst band first with their acknowledge targets and moves each one only through the states the server allows (Triaged, Escalated, Contained, Resolved, or Closed as a false positive), each button saying what the move does to the clocks. There is no button yet that opens an incident from a finding; incidents are opened through the API.

How it works

  1. Upload one logOne file up to 64 MB, in any of the accepted formats. A raw .evtx needs no conversion first. The file is scanned for malware before anything reads it.
  2. The platform classifies what is in itEvents, rules or intel; which tool produced it; which schema it follows. A misread format is reported, not guessed at.
  3. Read the assessmentThe verdict, the findings ranked by computed risk with the arithmetic behind each one, the kill chain, the MITRE ATT&CK coverage, the evidence grade, the blast radius and the escalation decision.
  4. Export what you needExport JSON saves the report to your machine. It cannot be retrieved once you leave the page, because it was never stored.

What you receive, and what we do not do

Evidence ledger
Per finding
The records behind it (card numbers redacted in place), the rule and its arithmetic, a Bayesian confidence, the MITRE ATT&CK technique, the affected entities and a recommended action.
Per corpus
The format and schema detected, the engines that contributed and those that declined, and an evidence grade for what the corpus can support.
Per .evtx upload
Records read, records decoded in full, and the count decoded only partially, so an incomplete read is a number you can see, not an assumption.
Per analysis
The retention statement: the corpus and this report were not stored, and an incident, if one is opened, is.

Limits we state

  • This is not a SIEM and does not replace one. There is no continuous ingest, no retention of your events and no alerting on a live stream; it is one corpus, analysed on upload.
  • One file per analysis, up to 64 MB. A larger log is split, or the relevant window uploaded.
  • Decoding a raw .evtx is not complete: the rare CDATA, entity-reference and processing-instruction BinXML tokens are flagged partial rather than guessed, and the record count affected is shown on every run. On our own validation corpus 86.9% of records decoded in full.
  • The report is not stored, so it cannot be re-opened later. Use Export JSON before you leave the page.
  • Detection drafts are experimental and appear only when the analysis engine is available; review a draft before deploying it.
  • There is no button yet that opens an incident from a finding; the page lists and moves incidents opened through the API.
  • Priority bands are provisional until the asset inventory is populated, and the page says so rather than implying the criticality was known.
  • Analysis runs on local models and deterministic rules inside the platform.

Plans: SOC Analyst carries the existing security-scanning entitlement: not included on Free (the entitlement is off, not merely small); Solo Pro and above, including Team and Enterprise. See the metering table.

Questions buyers ask

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.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial. Or bring one flow from your product and we record it live.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India