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
- 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.
syscall-analysis/v1 report:
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.
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 iscomplete 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.
incomplete, with reasons in the evidence notes and report limitations.
Configuration
--config loads strict JSON. Unknown fields are rejected, and configuration is never executed.
- Unknown fields and unknown rule IDs.
- Duplicate normalized paths or disabled rules.
- Empty path lists.
- Root
/entries. - Zero thresholds or windows.
Bounds
When a bound truncates the work, the report marks it. A truncated analysis is not a complete negative result.
Investigative workflow
- Run
statsand check collection completeness. - Run
analyzewith default rules. - Read the report limitations before the findings.
- Follow each finding’s event IDs into
timelineor the workbench. - Check the process tree and identity resolution behind the finding.
- Run Verification if integrity matters to the conclusion.
- Export the evidence package if the analysis must be shared.
Related pages
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.