SVO — software verification & operations

The whole scope, flow by flow. The code and the server it runs on.

The attention

Whoever builds a system spends the day with one question in mind: does this work? It is the right question for building — and it is a different question from ours.

Ours is: what else does this path accept?

Whoever wrote the code was assembling the behaviour, and the intelligence that helped write it was on the same task. The audit arrives afterwards, with its whole attention turned the other way: what happens when the system is used in a way nobody planned for.

It is the same intelligence, pointed at the opposite question.

The reach

A test is born from expected behaviour — that is what it exists for. Data flow goes wherever the code lets it go.

That is why the entry points are enumerated before the reading starts, and each path is read all the way to the place where it decides something.

The two halves

The software

Every entry point of the system, every guard that decides who may do what, every path that carries data from outside to a place that decides something. Read in full: the entry points are enumerated before the reading starts, and the report says how many there were.

The infrastructure

The server it runs on: what is listening, what starts on its own, who can get in, what was left open by an old configuration, what the backup actually takes.

Inside and outside

The difference is in what can be seen.

From the outside, you see what the system answers. From the inside, you see what it does when nobody is watching.

The scope is yours

What you list is what gets audited.

It is the contract you wrote, and the audit does not step outside it.

In the end, every path that accepts what it should not shows up in the report, with its address.

See the report →