The report artifact is the contract
MarlinSpike keeps the engine standalone and treats the generated report artifact as the handoff between packet analysis and downstream review.
The product takes packet captures in, sends no traffic back into the environment, and turns passive observations into topology, asset inventory, responder-grade findings, and portable JSON report artifacts. It is the open-source core behind Fathom and is intentionally built as a shared web workbench rather than a single-user thick client.
MarlinSpike keeps the engine standalone and treats the generated report artifact as the handoff between packet analysis and downstream review.
The preferred install path is a reverse-proxied Docker Compose deployment that multiple responders can share during an assessment, outage investigation, or tabletop.
The analysis pipeline stays intentionally legible: ingest and validation, protocol dissection, topology building, risk surfacing, and report generation.
MarlinSpike is built around industrial protocol visibility, then enriches that with network-discovery context so infrastructure relationships are not thrown away.
The public story stays bounded to what the platform actually exposes today. MarlinSpike supports standards-oriented review without pretending to be a broader compliance suite.
Stage 4 remediation guidance is framed around IEC 62443 SR-oriented remediation support for supported finding classes.
Selected ATT&CK mappings are published for current C2 and exfiltration-oriented findings and analyst context.
ISA-95 and Purdue-style zoning remain central to topology layout, asset placement, and cross-level communication review.
Continue with deployment, architecture, and package status documentation.