Trust

Governance.

Monitoring without governance is surveillance. These are the controls that keep the difference clear, and the design principles we are building to.

Controls in the model

Authorisation

Each system and signal source is connected deliberately by the organisation. Availability of data is not a reason to collect it.

Purpose

A connected source maps to a change someone would act on. Sources that cannot be tied to a response are a reason to narrow scope.

Minimisation

Credential monitoring, for example, can work from issuance, verification and status activity without collecting credential contents.

Ownership

Every signal that matters has someone expected to respond, and that expectation is agreed before the signal is switched on.

Separation

Each MAITS product keeps its own purpose and data boundary. Connecting them is a deliberate decision with a stated reason.

Evidence

What was observed, what was decided and who decided it, so a later review has something better than recollection.

Stated directly, for reviewers who need it on the record.

Product status: In development. Vigilance is not generally available, and there is no production service to assess today. We will say so in any procurement conversation before it goes further.
Certification: Vigilance does not hold independent certification. Security and governance design is documented under the MAITS information management system and available to design partners.
Available today: Identity and access monitoring design work is available now as a MAITS consulting engagement, using the platforms you already run.
Design partner material: Architecture, data handling and governance design documents are shared with organisations working with us on first deployments. Ask for them.

We will share the design material and answer a security questionnaire in writing, including where the honest answer is "not yet".