Meridian
Runtime monitor
Patrol
Continuous monitoring of your production estate against the approved state. Detects drift before auditors do.
What it does
Patrol monitors deployed systems for drift — the gap between what production actually looks like and what it was approved to look like. When a configuration changes outside the normal deployment process, or when a system diverges from its approved architecture, Patrol detects it. It centralises alerts and telemetry in the evidence record and routes notifications to the relevant personnel through Meridian's alert manager.
Patrol's monitoring is continuous, not point-in-time. Rather than assessing compliance at audit time — when evidence must be reconstructed from memory and logs — Patrol maintains an ongoing record of the relationship between the approved state and the actual state, available for review at any moment.
Who it's for
Patrol is used by Security Engineers and SREs responsible for maintaining the integrity of the production estate and detecting unauthorised or unintended changes.
Works best with
-
Chancery
Chancery defines what the approved state is. The richer the policy in Chancery, the more precisely Patrol can define and detect drift.
-
Slipway
Slipway automatically onboards new services to Patrol as they're deployed. Patrol's monitoring coverage stays current with every release — no manual registration step required.
-
Admiralty
Patrol's continuous monitoring data feeds Admiralty's executive dashboard. Add Admiralty when CISO and board-level visibility into the live compliance posture is required.
How it fits the platform
Patrol closes the feedback loop between the approved state and production reality. Every other component in Meridian contributes to defining or reaching the approved state — Chancery defines it, Slipway implements it. Patrol is the component that verifies it is maintained. Its output is the continuous compliance record that Admiralty synthesises for reporting and that the rest of the platform builds on as evidence.