Course contentsShow
← Security
Lesson 1503 of 3,05230. Operating System Security - MonitoringFree lesson

Baseline Creation and Management

Establishing trusted file baselines, determining what to monitor, and maintaining baseline accuracy through controlled updates.

Baseline Creation and Management

What you'll learn: How to create, maintain, and update trusted file baselines so your integrity monitoring remains accurate and trustworthy.

What Is a Baseline?

A baseline is your snapshot of "known good" – a cryptographic record of all files you want to monitor in their legitimate state. Think of it as taking a photograph of your file system when everything is clean and correct. Future scans compare against this photograph to detect changes.

The baseline contains file metadata (permissions, ownership, timestamps) and cryptographic hashes that uniquely identify each file's contents. Without an accurate baseline, your FIM tool can't distinguish legitimate changes from malicious ones.

Creating the Initial Baseline

Timing matters critically. Create your baseline immediately after:

  • Fresh OS installation and hardening
  • All approved software is installed
  • Security configurations are complete
  • Before the system goes into production
  • Verified malware scans show clean

Creating a baseline on a compromised system means you're documenting the attacker's presence as "normal" – a catastrophic mistake.

What to Monitor

Don't monitor everything (performance nightmare) or too little (security gaps). Focus on:

  • System binaries and libraries (/bin, /usr/bin, /lib)
  • Configuration files (/etc)
  • Boot files and kernel modules
  • Critical application binaries
  • Web server document roots

Exclude high-change directories like /tmp, /var/log, and user home directories unless specifically required.

Maintaining Baseline Accuracy

Baselines become stale. Every legitimate system change requires a controlled update:

  1. Document the change (patch number, change ticket)
  2. Verify the change is authorized
  3. Update the baseline with new hashes
  4. Archive the old baseline for audit trails

Neglected baselines generate false positives that train staff to ignore alerts – the "boy who cried wolf" problem.

Key Takeaway: A baseline is only trustworthy if created on a clean system and maintained through documented, controlled updates – otherwise your integrity monitoring protects nothing.