Servers configured to resist attack and stay that way
We review how your servers are set up, close the openings attackers rely on, and write down every change. You end up with a known baseline your team can check against.
What is included
- Baseline review
- We compare each server against a published benchmark such as CIS and record every gap.
- Access control
- We tighten SSH, remove unused accounts, enforce key-based login and limit administrative rights.
- Service reduction
- We stop and remove services, packages and open ports the workload does not need.
- Network filtering
- We set host firewall rules so only expected traffic reaches each service.
- Logging and time
- We turn on audit logging, central log shipping and reliable time synchronisation.
- Patch policy
- We set up regular security updates and a schedule for applying them.
How it works
Assess. We agree the scope and the benchmark, then scan the current configuration.
What you receiveA gap list ranked by risk and operational impact.
Plan. We mark which changes are safe and which need testing, and agree any exceptions with you.
What you receiveA written change plan with a reason for each exception.
Apply. We make changes in stages, test the application after each one and keep a rollback path.
What you receiveHardened servers and a change log.
Verify. We rescan, compare the result with the baseline and check for drift at agreed intervals.
What you receiveA before-and-after report and the configuration as code.
Right for you if
Your servers were built quickly and nobody has reviewed them since.
An auditor or customer has asked how your servers are configured.
You are taking over servers from another provider.
Questions
Will hardening break our application?
Some changes can, so we test in stages and keep a rollback for each step. Changes that conflict with the application become recorded exceptions.
Is CIS alignment the same as compliance?
No. It is good evidence of sound configuration, but compliance frameworks also cover processes and people.
Can you harden servers already in production?
Yes. We plan changes into maintenance windows and apply them gradually.
How often should hardening be rechecked?
We suggest a drift check every 3 months and after every major system change.