What this is

Maxuru is a hardening reference for servers, services and databases.

What every control page guarantees

The fix, first. The directive and the file it belongs in, at the top of the page. If you already know what you’re doing, you can copy it and leave.

Why it matters. The specific threat the control closes, in a sentence or two — enough to decide whether it applies to you.

Verification. The command that shows the setting is live in the running daemon. Setting a directive and having it take effect are different claims, and a reference that only tells you the first one is only half a reference.

The way back out. Hardening locks people out of their own hosts. Anything that can strand you says so, and says what to check first.

Reading the labels

Every control is tagged from its source data rather than by hand:

• Severity — critical, high, medium or low. This is about the exposure the control closes, not how hard it is to apply.
• Applies to — the versions and distributions the directive is known to hold for. If your version isn’t listed, treat the page as a starting point.
• CIS — the matching CIS Benchmark recommendation, where one exists.

What this isn’t

It isn’t a compliance certification, and following a checklist here doesn’t make a host audited. It’s the technical reference underneath that work.