Skip to content

Triage summary and counts

This page describes Antinomie 0.8.0, which is in development; the current release is 0.7.1.

Triage of a real run of /tmp/triage-sample on the Summary section: the run selector, Network route Internet (VM NAT, QEMU user networking), the tabs with IOC 15 and Export report…; Run overview with Refresh and Open properties; Detection evidence cards YARA, IDS and Sigma, each 0 rules matched, 0 occurrences, No rules enabled and Open results; Behavior & files with Syscalls 232, Observed task identities 4, Suspicious observations 5, Opened-file operations 16 and Read-file operations 11; Network evidence with the route, Capture frames 14, Destination IPs 2, Observed hostnames 1 and HTTP/1 requests 1.
The Summary of a real 0.8.0 run with no rule packs enabled. Antinomie 0.8.0, a recorded run.

Summary is the first Triage section. It gives whole-run counts. Click a count to open the evidence behind it.

Group Count Opens
Behavior & files Syscalls Process tree
Observed task identities Process tree
Suspicious observations Suspicious activity
Opened-file operations Opened files
Read-file operations Read files
Changed-file groups Changed files
Network evidence Capture frames URLs
Destination IPs Endpoints
Observed hostnames, DNS questions Domains
HTTP/1 requests URLs

From top to bottom the section has:

  • Run overview, with Refresh and Open properties, and a Network Unavailable badge when the run has no network evidence.
  • Detection evidence: a card per engine with its matched rules, occurrences, state and Open results.
  • The MITRE ATT&CK references of the matched rules (below).
  • Behavior & files and Network evidence, the counts above. Network evidence starts with the Network route the run used.
  • Main activity graph: the activity graph’s phases, severity curve and category heat strip for the whole run. A click opens Process → Graph without carrying a filter along, and the arrow icon opens the graph in its own window. The magnifier buttons, and Ctrl+wheel over the strip, make it larger or smaller (60 % to 300 %); the percentage takes it back to 100 %. When nothing is above LOW it is one line, such as No medium or high activity · 11 low · 340 info, and the arrow opens or closes it. It spaces findings equally, or by true time, following the Graph’s Events or Time choice.
  • Indicators (IOC): how many of the run’s indicators matched a dataset, such as 0 of 3 indicators matched, the dataset date or No datasets loaded, and Open IOC.
  • Observed activity: the worst four suspicious observations, HIGH first, with Open suspicious activity. Select one for Details, double-click it for its evidence.
The Triage Summary behind the Export report dialog: a Sigma card with No evaluated result, Not scanned and Open results; Network evidence with Network route Not recorded, Capture frames 5, Destination IPs 4, Observed hostnames 1, HTTP/1 requests 0 and DNS questions 3; the Indicators (IOC) card with 0 of 3 indicators matched, No datasets loaded and Open IOC; and Observed activity with a high memory.rwx row.
The lower part of the Summary: network counts, the IOC card and the worst observations. Antinomie 0.8.0, synthetic data.

Observed task identities counts tasks, including threads. It is not a process count.

A run that lived through a transport reconnect is counted whole: every recording segment of the run is read, oldest first.

The MITRE ATT&CK techniques that matched rules cite are listed under the detection cards by id and name, for example T1059 Command and Scripting Interpreter or T1059.004 Command and Scripting Interpreter: Unix Shell. The names come from a table of ATT&CK Enterprise v20.0 techniques bundled with the app, so nothing is looked up online; an id the table does not know stays bare. Up to 16 are shown, then +N in Detection. The Suspicious activity rules carry their own ATT&CK techniques in their Source column; see Processes.

The section tabs and the tabs under Process, Files and Network, and the Detection engines, carry a number badge. Counts are collected for the whole run, before any filter, sort or page, so they do not change when you type a filter or turn a toggle chip such as Hide stdio on or off. A badge reads … while it is being updated and — when no count is available; hover it to see which. The IOC tab counts the run’s indicators and turns red when one matched.

These are three different things:

  • Zero means the evidence was evaluated and nothing matched.
  • Preparing run evidence means whole-run counts are still being indexed. For a recording that is still being written the counts come from the part saved so far and grow with the next refresh.
  • Unavailable means there is nothing to count, for example network counts without a network capture, or a scan that never ran.

A detection card shows Queued while its scan waits for its turn and Scanning while it runs; otherwise Not scanned, Failed, Unavailable, No rules enabled, Evidence missing, Skipped, Partial or Complete, with the number of matched rules and occurrences. A card with no result says No evaluated result (or Waiting for its turn, Scan in progress). Open results opens the engine in Detection, where the inputs of the scan are listed. See Detection engines.

An activity graph of four processes: dropper 1201, sh 1202, curl 1203 and .x 1204, with markers for execution, persistence, C2, evasion and injection, an injection arrow from .x back to sh, a C2 phase band, a severity curve and the category heat strip; a break mark of 19.0 s on the time axis, Spacing Events selected.
The graph behind the Main activity graph strip: a long quiet stretch is squeezed and marked with its length. Antinomie 0.8.0, synthetic data.

Antinomie derives no malware verdict, score or vendor consensus from these counts. The sample window’s Highest suspicion is the highest tier any run reached, not a verdict either; see The sample window.