Skip to main content
syscall analyze reads persisted process, filesystem, and network evidence and emits explainable findings linked to the original event row IDs. It does not execute recorded commands, assign a malware verdict, or calculate a probability of maliciousness. Findings describe recorded behavior and explain why it may matter.

Run analysis

Text output includes:
  • Session summary and collection status.
  • Evidence completeness and limitations.
  • Evaluated rules.
  • Findings grouped by severity.
  • Explanation, significance, supporting event IDs and details.
  • Related processes and time range.
  • Recommended next steps.
JSON output uses the versioned syscall-analysis/v1 report:
Write output to a mode 0600 file:
--output truncates an existing file. The default is stdout.

Filter findings

Severity levels: informational, low, medium, high, critical. The parser also accepts info. Confidence levels: low, medium, high. A disabled rule normally does not run. An explicit --rule RULE_ID intentionally overrides the disabled default while still applying bounds.

Rules

Full conditions, exclusions, false-positive notes, and severity rules are in Analysis rules.
Rules are contextual indicators. Shell chains, temporary execution, credential-file access, retries, and short-lived network tools are routinely benign. Temporal proximity in Rule E is not proof that data was transmitted.

Severity and confidence

Severity is investigative priority: Confidence describes the directness and quality of the evidence. It is not a calibrated probability. Incomplete sessions downgrade base confidence: high becomes medium, medium becomes low, and low remains low. The finding and report carry an explicit limitation.

Evidence completeness

The report’s evidence status is complete only when all of these hold:
  • Session status is completed.
  • Persisted counters do not indicate loss, drops, recovery, or incomplete identity.
  • The event scan was not truncated by max_events.
  • Read-only verification completed with assessment valid.
Otherwise the status is incomplete, with reasons in the evidence notes and report limitations.

Configuration

--config loads strict JSON. Unknown fields are rejected, and configuration is never executed.
Paths must be absolute and are lexically normalized. The loader rejects:
  • Unknown fields and unknown rule IDs.
  • Duplicate normalized paths or disabled rules.
  • Empty path lists.
  • Root / entries.
  • Zero thresholds or windows.
See Analysis rules for the full contract.

Bounds

When a bound truncates the work, the report marks it. A truncated analysis is not a complete negative result.

Investigative workflow

  1. Run stats and check collection completeness.
  2. Run analyze with default rules.
  3. Read the report limitations before the findings.
  4. Follow each finding’s event IDs into timeline or the workbench.
  5. Check the process tree and identity resolution behind the finding.
  6. Run Verification if integrity matters to the conclusion.
  7. Export the evidence package if the analysis must be shared.

Rule reference

Exact conditions, exclusions, and confidence rules for A–F.

Verification

Read-only consistency checks and assessment meanings.

Evidence export

Package findings with the recorded evidence and manifest.

Limitations

What the analysis cannot establish.