Company
Omvia builds GraphWalker
One product, built on one idea: a security claim is worth what its evidence is worth, and the evidence should be handed over rather than summarised.
What we are trying to do
Most security tooling tells you what is theoretically wrong. GraphWalker runs the technique and shows you what happened — the credential that worked, the file it read, the check that matched — and then asks the second question almost nobody answers: did anything in your estate notice?
Those two questions have separate answers and we keep them separate. A technique that is stopped but invisible and one that is visible but working are different problems, owned by different people, fixed in different ways. Merging them into a single score is how a report becomes decoration.
How we work
The rule we hold ourselves to is that a claim must be measured, not asserted, and that a measurement carries the date it was taken. It sounds like a slogan; in practice it is a chore. It means re-deriving numbers before publishing them, and it means writing down the ones that got worse.
Four of the figures on this site disagreed between our own internal documents before we built it — not because anyone was dishonest, but because the measurements grew while the sentences around them stood still. That is the ordinary way a company starts believing its own summary, and it is why every number here carries a date and a way to check it.
Who built Omvia and GraphWalker?
Omvia and GraphWalker are built by TR66 Training, Consulting, Software Ltd.