What it does

Where Vigilance fits.

Security monitoring is a crowded category. Here is what Vigilance is responsible for and what it deliberately leaves to the tools you already run.

Alongside your existing tooling

Log collection and retention
Your SIEM or logging platform keeps doing this. Vigilance is about which changes get acted on, not which get stored.
Endpoint and network detection
Different domain. Vigilance concentrates on identity, access and digital trust, where the signal is often organisational rather than technical.
Identity governance
Access reviews are periodic by nature. Vigilance covers what happens between them, when a change occurs and nobody is scheduled to look.
Incident response tooling
Where you have a response process, Vigilance feeds it. The aim is a signal that arrives ready to act on, not a parallel process.

Alongside our other products

Three separate propositions. They connect where an organisation wants them to, and none of them needs the others to be useful.

Provable facts

DiligenceID

Carries verifiable facts about a person — a qualification, a licence, a current registration — that another organisation can check.

Answers: what is true about this person?

diligence.id

Authority to act

Delegance

Governs who may act on behalf of whom, for what purpose, under whose approval, and until when.

Answers: may this person do this, and on whose authority?

delegance.id

What happened

Vigilance

Observes identity, access and digital trust signals within an authorised boundary, and carries what matters through to a response.

Answers: what changed, and does anyone need to act?

In development

Each product keeps its own purpose and data boundary. Connecting them is a decision an organisation takes deliberately, for a stated reason — not something that happens because they came from the same place.

When Vigilance is not the answer

Worth saying plainly, so nobody spends a quarter finding out.

You have no owner to route to

A signal needs someone who will act on it. If nobody can take that, the first problem is organisational rather than technical.

You need broad threat detection

Endpoint, network and malware detection are different disciplines with mature tools. This is not a replacement for them.

You need it in production this quarter

Vigilance is in development. If your need is immediate, MAITS does this work as a consulting engagement today.

Your question is about authority

If the issue is who should be allowed to do something rather than noticing that they did, that is Delegance.

Still the right fit?

Tell us the change you would want to catch, and we will tell you honestly whether this is the tool for it.