A practical explanation of filesystem integrity baselines, scan cadence and investigation before rebaselining.

A baseline is a point of comparison

A host integrity scanner needs a reference to recognise subsequent changes. The important question is not whether baseline creation succeeded; it is whether the administrator understands and trusts the system state being recorded.

Create it during a controlled setup

One-Click exposes an IDS initialisation path in its audit commands. This makes sense early in the installation lifecycle, after reviewing the host and before uncontrolled application changes. Initialising a compromised host does not retroactively make it clean.

Changes are not automatically compromises

Operating-system updates, new services, certificate renewals and administrator work can legitimately modify binaries and configuration. A useful scanner reports changes and retains enough context for review. Detection and judgement remain separate responsibilities.

Treat remediation differently from scanning

Scheduled read-only scanning can give administrators earlier notice of drift. Automatic repair is a more consequential choice because the tool may not understand why a file changed. Scanner releases also differ: a standalone IDS version may offer extra flags not exposed by the One-Click wrapper.

Maintain an audit trail of decisions

Before rebuilding a baseline, document what changed, why it was allowed and which evidence was reviewed. This creates a better security practice than resetting the baseline every time an alert is inconvenient.

Continue with the practical guides for Rule Engine, Guard and Host IDS. Review the installed version before changing a production host.