The problem
Where it usually hurts
Nobody can say with certainty which ports are reachable from the internet. The firewall was set up once, and since then containers have published ports that nobody approved.
Security is checked once a year, in an audit or a penetration test. The report lists findings, the findings become tickets, and the tickets wait behind feature work.
Secrets sit in repositories and in environment files on servers. Everyone knows it should be different. Nobody has had the week to change it.
Scope
What you get
- An exposure report per host: what is reachable from the internet, and what should be
- Hardened hosts: firewall rules, SSH access and updates, written as code so they can be applied again
- Secret scans and image scans in the pipeline that stop a release with critical findings
- Secrets moved out of repositories into a secret store, and the exposed ones rotated
- A prioritised list of findings, each with its fix and the person who has to make it
- A documented baseline, so the next audit starts from evidence and not from interviews
Process
How an engagement runs
Four steps. You decide after each one whether there is a next one.
- 01
Book a call
Tell us what hurts: the release process, an audit finding, a slow database, a cloud account nobody fully understands. We ask questions and say plainly whether we can help.
- 02
Get a written proposal
Scope, steps and price in writing. You decide with the facts on the table.
- 03
Work in your systems
We work in your repositories, your pipelines and your cloud accounts, alongside your team. Our changes go through review like any other change.
- 04
Keep everything
Code, configuration and documentation stay in your repositories. Your team runs the result without us.
FAQ
Questions we get before the first call
Is this a penetration test?
No. A penetration test attacks your systems to find out what an attacker could do. We check configuration and exposure, fix what we find and build checks that keep it fixed. The two complement each other: a penetration test tells you whether the hardening holds.
Will the checks slow down our releases?
A scan adds time to a pipeline run, and a failed gate stops a release. That is what a gate is for. We tune which findings block and which only report, so the pipeline stops for what matters and the team does not learn to ignore it.
Do you certify us for ISO 27001 or a similar standard?
No. We are not a certification body and we issue no certificates. What we deliver is the technical evidence auditors ask for: what is exposed, how the hosts are hardened, and which checks run on every release.
Do you need access to production?
For the exposure check, no: it looks at your servers from the outside. For hardening we need access to the hosts or to the code that configures them. We work with the least access the task needs, and you can revoke it at any time.
We already had an audit. What do you add?
An audit report says what is wrong. We fix it, put the fix into code and add a check that fails when the problem comes back.
Talk to us about DevSecOps
Describe where you stand today. We tell you plainly whether we can help and what a first step would look like.
The first call is free and without commitment.