We look from outside, from inside and into the code, within an agreed window. The duty shift knows about the work in advance.
Two lines of work, one logic. Find what is already open in your defences, and close it inside the process so that the decision stays with a human.
THE WHOLE PAGE ADAPTS: THE LIST, THE STEPS, THE EXAMPLES. YOU CAN SWITCH AT ANY TIME FROM THE HEADER.
These are classes, not your network. Click a row and the breakdown appears: where this usually sits and what we do about it.
THE SCALE IS OUR ESTIMATE FROM PAST ASSESSMENTS, NOT A MEASUREMENT IN YOUR NETWORK.
THE BREAKDOWN DESCRIBES A CLASS, NOT YOUR SYSTEM. WHAT IS OPEN AT YOUR END BECOMES VISIBLE ONLY AFTER A CONTRACT AND ACCESS.
A finding is closed inside a process, and the process lives with people: in email, in logs, in tickets, in a policy read once a year. The second half of our work is to connect those tools and leave the last word to a human.
We look from outside, from inside and into the code, within an agreed window. The duty shift knows about the work in advance.
For every finding we write down the class, where it sits, what it threatens and what happens if it is left until the next assessment.
A plan by priority, help with the fix, and a repeat check of the same places.
THESE ARE NOT PROMISES ON A WEBSITE. WE PUT ALL FOUR IN WRITING BEFORE THE WORK STARTS, AND THEY DO NOT CHANGE ALONG THE WAY.
The first step is the same either way: a conversation with no access to your systems. What comes next depends on what you choose.
A conversation, then a short risk note, then a proposal with scope and timing.
[email protected]A conversation, then we choose one decision point, then a pilot on your own texts, lasting [DURATION].
[email protected]