EAOS · Cyber Security Platform

EAOS SpiderNet — Active Cyber Defense

Inspired by how a spider hunts: a web of deception, the vibration of events, analyst spiders, wrapping the attacker, and inspecting the prey.

SpiderNet product visual
16+industrial & IT protocols
5hunter agents

The attacker believes they entered a real industrial network, but they are actually trapped in a controlled, resettable, learning decoy environment. With virtual OT/IT equipment and dozens of industrial protocols, SpiderNet draws the attacker into engagement, isolates them, and gathers evidence and threat intelligence — aligned with MITRE Engage and under EAOS human control.

Capabilities

Deception fabric: virtual RTU, HMI, Historian, AD, VPN, and SCADA
Industrial protocol support: Modbus, IEC 60870-5-104, IEC 61850, DNP3, S7, OPC UA
Hunter agents: Detection, Engagement, Malware, Attribution, and Evidence
Attacker isolation and containment engine
Decision kernel with a human-approval policy gate
Spider-web dashboard with real-time attacker movement and risk level
Integration with SIEM/SOAR, network control (FW/NAC/DNS), and a CERT portal

EAOS · ARCHITECTURE

System architecture

The attacker believes they entered a real industrial network, but they are caught in a controlled, resettable, learning web of deception — aligned with MITRE Engage.

EAOS SpiderNet macro architecture
EAOS SpiderNet macro architecture

EAOS · CATALOGUE

Product catalogue

DĀMTĀR — industrial and enterprise cyber deception platform · version 1.0, 6 Mordad 1405

Page 1 of 13 — Cover — DĀMTĀR, the industrial and enterprise cyber deception platform
Page 2 of 13 — 01 Why DĀMTĀR exists — an attacker already inside goes unseen for months with today's tools
Page 3 of 13 — 02 The product at a glance — nine capability domains, from the deception factory to the policy engine and human approval
Page 4 of 13 — 03 The deception factory — what is faked, at which interaction level, and the boundary that is not configurable
Page 5 of 13 — 04 OT safety — two containment dimensions, one floor, and the evidence demanded before deployment
Page 6 of 13 — 05 Reference architecture — four layers, fourteen components, and a boundary that is never crossed
Page 7 of 13 — 06 From interaction to decision — seven steps, and the metrics that must be baselined in the customer's environment
Page 8 of 13 — 07 AI as adviser, not decision-maker — every model output carries a confidence and a reference to evidence
Page 9 of 13 — 08 Standards and integration — fourteen references with matching evidence, and the seams DĀMTĀR does not own
Page 10 of 13 — 09 What has been built so far — the design and delivery package, measured with tools rather than asserted in prose
Page 11 of 13 — 10 Roadmap — eight phases, twelve parallel work packages, and an order that parallel teams cannot parallelise
Page 12 of 13 — 12 Next step and declared boundaries — what is needed to start, and what this product explicitly does not do
Page 13 of 13 — Back cover — what is offered is not one more sensor
Download the PDF · 1.8 MB

Click a page edge to turn it, or step forward and back with the ← and → keys.