We define security settings suited to the operating system role and version in Windows, Linux and virtualization environments. We test the recommended settings in a pilot and record the exceptions that don’t fit the application. Day-to-day operation and maintenance of servers fall within our server and cloud management service.
We use CIS Benchmarks and vendor security baselines as references. Applying these settings doesn’t mean certification.
01
Should CIS Level 1 or Level 2 be applied?
For most enterprise servers, Level 1 is a good start. Level 2 is more restrictive; it should be chosen for high-risk systems and after application testing.
02
Will hardening break our applications?
It can. That’s why a test group, phased rollout and a rollback method are part of the plan; exceptions for incompatible applications are recorded with a justification.
03
What should we do with old operating systems?
For an out-of-support system, the priority is upgrading or replacing it. If that’s not possible, risk is reduced with network isolation, access restrictions and extra monitoring, and the remaining risk is recorded.
04
How do we ensure continuity?
Periodic compliance scans, a template (golden image) for new servers and change management make it possible to track settings drifting over time.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Inventory
A list of servers, roles, operating systems and critical applications is compiled.
02 / PLAN
Baseline and measurement
A suitable baseline is selected and a drift scan is run.
03 / EXECUTION
Test and implementation
Settings are validated in a test group and rolled out in phases.
04 / HANDOVER
Sustain
Periodic compliance scanning and a new-server build standard come into effect.