Repository navigation
Seraph
Seraph is Apex's SIEM: a suite for watching networks, built into standard Apex. It is a configuration, not a fork — the sensor edition of Apex (the shape PIA ships in) is the same system with the configuration preloaded.
Every seat has a Seraph role, set on the Seraph page (Nav → SIEM → Seraph):
- Console — holds the registry, receives sensors' pictures, shows detections. (Default.)
- Sensor — watches its own segment and reports to its console.
- Both — a seat that watches and consoles, the common single-box shape.
Seat settings: retention (days, default 30), collection cycle (seconds, default 300), the seat's sleep window (default 01:00–05:00, used by the impossible-hours detection), and the console node id a sensor reports to.
Collection is passive — Seraph reads what the box already knows:
- Inventory: the ARP table and DHCP leases — who is on the segment, by MAC, IP and lease name.
- Flows: the connection tables — which outside addresses the segment talks to, and how often. Metadata only; Seraph never captures payloads.
- Listeners: the segment's open doors, from the same tables.
- Sign-ins: sshd lines from the auth log — successes and failures, with their sources.
Every snapshot carries its gaps: the sources it could not read (an unreadable auth log blinds the sign-in picture, and the dashboard says so). The unit of sight is the segment the sensor sits on — Seraph never claims a wider view than its vantage.
- Watchlist — a flow or sign-in touches a watched term. Matching happens on the sensor, against the Wire's declared watchlist merged with Seraph-local terms; the list never leaves the machine — only matches travel.
- New face — a MAC the sensor has never inventoried.
- Beaconing — a remote called on a metronome: regular intervals over a sustained span.
- Impossible hours — a successful sign-in inside the seat's sleep window.
- Auth burst — a run of failed sign-ins from one source.
- Scan — one source knocking on many of the sensor's ports at once.
- New listener — a listening service that was not in the baseline.
Detections dedupe per sensor and kind; open and filed detections never age out — dismissed ones retire at the seat's retention.
An open detection rides the notification spine — tray, phone push, and Navi's own voice in chat — aimed at the Seraph view. From the page (or the sensor's dashboard) a detection can be filed as a case: the bridge computes the detection record's SHA-256 and carries it into the case's summary, so the case is born with custody of its evidence. Dismissing is one tap; both acts retire the alert.
A sensor is registered on its console's Seraph page (name, address, SSH user, Mesh node id, vantage — the segment it watches, in words). Registration is what lets its reports in: the Mesh door authenticates the caller as a paired peer, and the registry binds that peer to the sensor record. Unknown sensors, revoked sensors, and reports claiming a node that is not the sensor's own are refused by name.
Revocation is a tombstone: the record stays, marked revoked, and late reports are refused — a decommissioned sensor cannot quietly keep talking.
A sensor reports each collection pass to its console over the Mesh; when the uplink is dark it spools its envelopes on disk and drains them when the Mesh returns. Client sensors in a federation are limited citizens: they report their own network's picture to their operator and hold no borrow rights and no sight of any other network.
Each sensor's page carries Dashboard | SSH. The SSH tab rides the seat's shell-session machinery: opening it starts a shell on the console seat and runs ssh to the sensor's address with the operator's own key — operator-opened per session, never a standing connection. A sensor that is the seat needs no SSH; its tab says its shell is Chat's CLI mode.
- Passive by default. Anything active — a sweep, a probe — crosses the LOWC line, as with every Apex capability.
- The watchlist never leaves its machine (#314's law, kept by construction).
- Response is a human act. Seraph watches continuously; it does not act on a network.
Getting started
Talking to Navi
Navi Mesh
Chips
Knowledge & RAG
Settings & updates
- Settings & persona
- DHD — Apex from anywhere
- GitHub — the pulse, issues & backups
- Installing & updating
Help