SIS CLI
Report Guide
This guide explains when to use sis report instead of sis scan --format json or sis query.
When to use report
Use sis report when you need:
- a durable human-readable investigation summary
- a report file for analyst hand-off
- a curated view of findings, chains, and verdict context
Use sis scan --format json when you need machine-stable raw analysis output. Use sis query when you
need one specific slice rather than a full narrative report.
Command shape
sis report <input> [options]
Common examples:
sis report sample.docx
sis report sample.hta --deep --format markdown --out report.md
sis report sample.one --deep --format json --out report.json
sis report sample.pdf --format yaml
Output formats
markdown: best for analyst review and hand-offjson: best when downstream tooling wants full report structure as a structured report objectyaml: useful for ad hoc inspection and configuration-adjacent workflows
Key controls
--deepto align the report with deep-analysis triage--report-verbosity compact|standard|verboseto tune detail level--report-chain-summary minimal|events|fullto control chain expansion--out <path>to write the report to disk--config <path>on the scan surface if a specific runtime policy or config must be reproduced
Choosing between scan, query, and report
scan: canonical detector pipeline and machine outputquery: one forensic slice, count, or filtered viewreport: full operator-facing summary
Typical sequence:
sis scan <sample> --deep --format jsonsis query findings <sample> --format jsonsis report <sample> --deep --format markdown --out report.mdsis explain finding <sample> <finding-id>for the most important findings
Investigation notes
reportreanalyses; it is not a projection of a saved scan. It has no explicit--configflag. Usequery --from-reportfor supported saved-result projections.- Prefer
markdownfor hand-offs and case-study drafting. - Prefer
jsonif another tool needs the report body but not the scan wrapper.
Related guides
sis docs investigatesis docs explainsis docs query