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?
What it does
Security monitoring is a crowded category. Here is what Vigilance is responsible for and what it deliberately leaves to the tools you already run.
Three separate propositions. They connect where an organisation wants them to, and none of them needs the others to be useful.
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?
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?
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.
Worth saying plainly, so nobody spends a quarter finding out.
A signal needs someone who will act on it. If nobody can take that, the first problem is organisational rather than technical.
Endpoint, network and malware detection are different disciplines with mature tools. This is not a replacement for them.
Vigilance is in development. If your need is immediate, MAITS does this work as a consulting engagement today.
If the issue is who should be allowed to do something rather than noticing that they did, that is Delegance.
Tell us the change you would want to catch, and we will tell you honestly whether this is the tool for it.