Security
Software that is closed, and stays closed
Secure because it was built that way, not because something was laid over it afterwards. We check what you are running now, test where somebody would get in, and keep an eye on it.
Why now
Things are built faster than ever. That is not the same as better.
Putting software together has become a great deal easier in recent years, partly because AI takes over some of the writing. That is a gain. But getting something working quickly and closing it properly are two different things, and only the first one shows on the outside.
The result is all over the internet by now: forms that give back more than they should, connections with no lock on them, admin screens that can be found with a bit of patience. Nobody notices, until somebody does.
On the other side stands that same toolkit. Looking for weak spots is scaling up just as fast, and no human does that by hand any more. A site that stayed under the radar five years ago because it was small will not stay there now.
What we do
Checking, closing, and keeping it that way
This goes for what we build and for what is already running. You do not have to be a customer of ours to have it looked at.
Securing your systems
Closed properly, not patched over afterwards.
Who gets to see what, updates that keep running, and connections that give back no more than they need to. We check what you are running now and repair what is open — even if somebody else built it. What we make ourselves comes out that way; it is not a separate product you buy on the side.
Security test (pen test)
Somebody looking at it with bad intentions, before anybody else does.
We try to get into your site, your webshop or your internal system, and write down what worked and how you close it — in plain language, the most important thing at the top. No list of a thousand alerts that nobody can do anything with. If we find nothing serious, that is in there too.
Monitoring & backups
Noticing that something is wrong before your customer does.
We keep an eye on whether everything is running and whether odd things are happening, and there are backups ready that we have actually restored at least once — a backup that has never been tried is an assumption. If something does go wrong, we pick it up and you hear from us what happened.
GDPR & NIS2
Knowing where your data is, and why.
Which personal data you keep, where it is, who can get to it and how long you hold on to it. We map it out and make it right in the systems themselves, and think along about what NIS2 means for your business. We are not lawyers: for paperwork that needs a signature underneath it, we refer you on.
Phishing & awareness training
The weakest point is usually not the software.
An explanation for your team in plain language: what a fake email looks like, why that one invoice added up and was false anyway, and what you do if you did click after all. Want to know where you stand first, then we send a practice email ourselves — the outcome is about the company, not about who fell for it.
How it works
Look first, repair afterwards
There is deliberately no lead time and no response time here: those differ from one situation to the next, and on this subject an invented promise is worse than no promise at all.
01
We look at what is there
Which systems are running, what talks to what, who can get where, and what data is in it. Often that list on its own is already a surprise.
02
We try to get in
The way an outsider would. What works is in the report; what does not work is in there too, because that tells you just as much about where you stand.
03
You get it in order of importance
No list of a thousand alerts that nobody can do anything with, but what really matters, at the top, with what it will cost you to repair it.
04
We close it, or you do
Either one works. The report is written so your own people can carry on with it — you are not tied to us for this.
Said honestly
What we do not promise
Nobody can say that something is unbreakable, and anyone who does say it should not be believed. Security is not a switch you flip, it is keeping up — and it can still go wrong.
So there is no seal of approval hanging here and no percentage. What we do do: write down what is open, put it in order of importance, and be honest about what is worth repairing and what is not. Sometimes the answer is that the risk is small enough to leave alone.
And for paperwork that needs a signature underneath it — data processing agreements, legal advice on NIS2 — we refer you on. We are builders, not lawyers.
And the rest?
It is already in what we build
If we build your system, it comes out that way: permissions per user, nothing that gives away more than it needs to, and updates that keep running for as long as we keep it going. You do not have to buy anything extra for that.
Is something running that somebody else built, or are you not sure what is all out there — then checking it over is where it starts. That is a separate piece of work and commits you to nothing.
Curious how secure your systems are?
Send one sentence about what you are running. Then you will hear what we would look at, what already looks right — and whether an investigation is worth it in your case.