Nine points every project has to protect
Every system is assembled from parts with different origins: a widely used framework, our own building blocks, features built only for you, open-source components and outside services. Every place where parts meet, or where someone can send something in, is a point to protect.
Forms and input
Every field a visitor can fill in can be abused: spam, fake data or malicious input.
Logins
Passwords, two-factor authentication and limits on repeated attempts.
Permissions
Who can see and change what. A mistake here shows data to the wrong person.
New custom code
Every new feature is new code that has to be tested and reviewed.
Third-party libraries
A flaw found in any library affects every site that uses it, so updates must be continuous.
Personal data
What we store, for how long and who can see it: your obligations under data protection law.
File uploads
Uploaded files can carry harmful content, and private documents must stay private.
Keys and passwords
API keys and passwords must never be in the code or in an email.
External connections
Each outside service means keys, incoming notifications to verify, and a plan for when it is down.
Even a small request touches several of them. A booking form touches five at once.
Before anything goes live
Nothing irreversible may touch the running system until the new version has been proven good.
Every change, a big new feature or a one-line fix, passes the same gates. If any of them fails, your live site stays exactly as it was.
Secret scan
A password or key found in the code stops the build at once.
Tests
Syntax, code style, static analysis and automated tests.
Dependency audit
No package with a known vulnerability goes out.
Vulnerability scan
The finished build is scanned, and a critical flaw keeps it from being released.
Start-up check
The finished version has to start and prove it works before it goes anywhere near your site.
Health check
The new version starts beside the old one. If it is not healthy, the old one stays and the new one is rolled back.
Who can reach what
Most attacks begin by finding a door that was left open. So we keep the doors few, and we know who stands at each one.
One door to the internet
A visitor can reach exactly one point: the encrypted front door of the site.
Filtering in front of the server
Traffic passes through a filtering service that absorbs attacks before they reach the server, and the server has firewall rules of its own.
The workshop is closed
The systems we build and release with cannot be reached from the internet at all, only over a private, encrypted connection.
Maintenance access from known places only
Logging in to our servers for maintenance is allowed only from our own addresses, enforced by firewall rules on every server.
Every client in a space of their own
Each client runs in their own isolated space, with the test copy and the live site kept apart. Clients cannot see into each other’s data.
Security fixes arrive overnight
For systems under maintenance, updates are checked by a full build, go to a test copy first, and reach the live site a night later, only if they ran cleanly. Projects without their own tests are never released automatically.
What we won’t pretend
Custom code is reviewed by far fewer people than a platform like WordPress itself. That is why every change goes through the same checks, and why we keep third-party add-ons to a minimum.
A small team runs everything. The upside is that the people who built your system are the ones watching it.
No one can promise that a system will never be attacked. What we can promise is what we do, every time, before anything reaches your site.
Wondering what your system needs to protect?
Tell us how it works today. We’ll point out where the doors are.