What changes for the organisation
You learn where regulated data actually lives, and who can reach it who should not.
Finds regulated data where it should not be, and access that should not exist.
What changes for the organisation
You learn where regulated data actually lives, and who can reach it who should not.
How it works
Approved file shares, document repositories, database exports and records systems are scanned to locate regulated or confidential data and suggest classification. AD and application entitlement data are joined to surface dormant accounts, excessive privilege and toxic combinations.
The mechanism, not the marketing. If a step below would not survive an engineer's scrutiny, it should not be on this page.
Operating path
The finding is about a folder. It is deliberately not about a person.
An approved scan of one departmental file share, agreed in advance with the data owner.
11,400 files containing regulated personal data. 3,900 of them older than the retention schedule permits — an over-retention exposure that exists whether or not anyone ever misuses it.
One folder inherits permissions from a security group with 340 members, of whom 12 are actually in the department. Deterministic graph analysis, not an inference.
The model ranks this above roughly 200 other findings and explains why: regulated content, excessive reach, no named owner, and retention already breached.
The data owner reviews, confirms, assigns ownership, corrects inheritance, and applies the retention schedule.
What it came to
No individual was scored, profiled or flagged at any point. The exposure was structural, the remedy was structural, and the record shows a folder being fixed rather than a person being investigated.
The authority ladder. Green rungs are authoritative — a rule, a scanner, a sandbox, or a person. Blue is where the model contributes. Amber is where a human decides.
Prioritisation and explanation across a signal volume no reviewer could read — and the hypothesis that makes a case worth opening.
It cannot conclude intent. An inference about a person is a hypothesis with evidence attached, never a determination.
We will not show you a scripted demonstration of something that does not exist. What we publish instead is the workflow specification, held to the same standard as shipped work: actor, trigger, happy path, exceptions, terminal state, and the audit evidence it must leave. When it is built, this section becomes a demonstration.
Roadmap discovery. Promotion requires named document repositories and identity sources, case-precision targets, and a documented fairness review.