Solutions · IT & Security

Hardening: from 2 years to 6 weeks.

A continuous view of which settings, permissions and patches deviate, with the impact of every fix visible up front. You close digital doors and windows in a targeted way, with 85-95% less effort.

Measures against: CIS Benchmarks · NIS2 · ISO 27001/27002 · BIO2 · NEN 7510 · DORA

Sound familiar?

Why hardening stays undone.

FEAR OF BREAKAGE Nobody dares to turn the dials

Hundreds of settings per operating system, and no view of what a change does to production.

NO BASELINE Patching is not hardening

Without a shared baseline, hardening gets confused with patch management, and the configuration stays untouched.

NO PROOF Work without a trace

What does get done is not demonstrable. At an audit or claim, the searching starts all over.

The approach

Biggest impact first.

You harden against the Easy2audit Baseline: comparable to CIS Level 1, but chosen so your systems stay reachable. Rolled out in phases, with continuous re-measurement.

Impact up frontper setting you see what the fix does, before you apply it
Phased, with rollbacktighten in steps, with rollback as a basic principle
Continuous drift detectionre-measure and see immediately what changed since the last scan

The journey

From baseline scan to holding the line.

01Baseline scan

Scan against the Easy2audit Baseline: per system you see which settings deviate and what the impact is.

02Prioritise

Biggest risk reduction first. Settings with possible impact on workability are flagged up front.

03Test group, then wide

Apply to a test group, re-measure, then roll out in phases across the rest.

04Hold the line

Re-measure periodically: drift becomes visible as soon as a system deviates from the baseline.

In practice · Water Authority Aa en Maas

Water Authority Aa en Maas had to comply with the Dutch BIO baseline and faced some 400 security settings to check per operating system, with the requirement that availability and performance stayed intact. With Easy2audit they configured their systems more securely and became demonstrably compliant at the same time.

"For every security setting you see the possible impact on performance. That gave our administrators the confidence to apply measures without workability suffering."
FC
Frank Coppens
Information security · Water Authority Aa en Maas

full customer case as PDF (in Dutch)

Frequently asked questions

Will something break when we start hardening?

That is exactly what the process prevents: per setting you see the possible impact up front, you start on a test group and roll out in phases. Rollback is a basic principle, not an emergency measure.

What is the Easy2audit Baseline?

A set of secure settings per platform, proven in practice, comparable to CIS Level 1 but chosen so systems stay reachable and workable. You measure against it, harden towards it and use it to prove where you stand.

Do we have to apply everything at once?

No. You prioritise by risk reduction and work in steps; every re-measurement shows what is in place and what is still open.

See how you make hardening demonstrable.

30 minutes · online · no obligations