https://documentation.opengate.es/edge_products/axiom_border/presenting/index.html The product in seven readings: what it is, the ingest-observe-decide-act loop, the four probes, how passive and active analysis hand over to each other, how an event becomes an actionable alarm, the models that run on the probe, and the security posture it deploys with. Hugo en-us https://documentation.opengate.es/edge_products/axiom_border/presenting/what_it_is/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/what_it_is/index.html The thesis behind the product: an autonomous edge node that observes, decides and acts on its own, and centralises into OpenGate only if you ask it to — plus the deployment specification in one table. https://documentation.opengate.es/edge_products/axiom_border/presenting/the_full_loop/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/the_full_loop/index.html The four stages a single observation travels through — ingest, observe, decide, act — each with its own clock, all writing to the same local state, and none of them sending anything off the machine by default. https://documentation.opengate.es/edge_products/axiom_border/presenting/the_four_probes/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/the_four_probes/index.html One probe listens and three ask. What each of them produces, how often it runs, and the execution contract the three active ones share — including what happens to a scan the probe was in the middle of when it restarted. https://documentation.opengate.es/edge_products/axiom_border/presenting/passive_and_active/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/passive_and_active/index.html Passive and active analysis are two kinds of claim, not two views of the same data: why the passive probe decides whether an active scan means anything, why neither inventory contains the other, and why a scan that finds nothing does not retract what listening established. https://documentation.opengate.es/edge_products/axiom_border/presenting/alarms/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/alarms/index.html Three things can raise an alarm and all three go through one gate: coalescing by identity, which is what keeps both the history and the operator's attention intact. Plus acknowledgement that reopens, rules that already know what changed, and the live feed behind the console's counter. https://documentation.opengate.es/edge_products/axiom_border/presenting/ai/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/ai/index.html Anomaly detection that runs on the node itself, in local containers, with no call to any external service: the training and inference circuit end to end, why an inferred anomaly enters through the same gate as any other alarm, and the platform limit to know about. https://documentation.opengate.es/edge_products/axiom_border/presenting/posture_and_storage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://documentation.opengate.es/edge_products/axiom_border/presenting/posture_and_storage/index.html A probe that watches an industrial network has an attack surface of its own, so the installation deploys a posture rather than offering one: transport, sessions, the message bus, ingestion, configuration secrets and cloud egress — plus where each kind of data ends up.