Something changes
At Harbour Community Trust, a security setting on a finance application is relaxed late on a Friday.
It is observed, within scope
The change happens in a system the organisation connected deliberately, so it is visible rather than buried.
Context decides whether it matters
Who made the change, whether it was expected, what it affects, and whether it fits a known pattern of work.
It reaches a person, not a dashboard
The signal explains what changed, why it matters and the safe next step, and it goes to someone who can act.
The outcome is recorded
Reverted, accepted or escalated. Either way the decision is part of the record rather than a memory.
In development
See what changed. Act on what matters.
Most organisations already collect more security signal than anyone reads. Vigilance is about the few changes that deserve a person's attention, and making sure one gets it.
We are working with early design partners on first deployments.
Not another alert feed
Volume is not the problem. Working out which few changes deserve attention is.
Not unbounded monitoring
Visibility is limited to the systems and signals an organisation authorises. Scope is agreed, not assumed.
Ends with an owner
A signal that nobody owns is not a control. Each one that matters carries through to a person and an action.
Where would you like to start?
Three ways into the same idea, depending on what you are trying to work out.
Understand what a good signal is
What changed, why it matters and the safe next step — as opposed to another alert nobody reads.
See the modelSee what it would catch
The identity and access changes organisations most often wish they had noticed sooner.
See the examplesWork out where it fits
How Vigilance sits alongside your existing monitoring, and how it differs from DiligenceID and Delegance.
See the boundariesExample: a change that mattered
From a quiet configuration change to an owned response.
One signal followed the whole way, using a fictional organisation.
Questions people ask early
Does this replace our SIEM?
No. Where an organisation already collects telemetry, Vigilance is about what gets acted on rather than what gets stored. Where it fits.
What does it actually watch?
Only the systems and signals your organisation connects. Scope is agreed during design, and it is a privacy decision as much as a technical one.
How do you avoid more noise?
By starting from the changes that would matter to you and working backwards, rather than forwarding everything a platform can emit.
Can we start now?
Vigilance is in development. We are working with early design partners, which is the most useful stage to get involved. Talk to us.
Where it fits
One of three, each with its own job.
Vigilance watches what happens and carries meaningful risk through to a response.
DiligenceID carries provable facts about a person, such as a qualification or a current registration. Delegance governs who may act on whose behalf, and until when.
They connect where an organisation wants them to. None of them needs the others to be useful.
Is this your problem?
If a change in your environment would currently depend on someone happening to read a log, we would like to talk to you.