liveBook · Manning

Configuration baseline

As explained in Fundamentals of Cybersecurity

A secure configuration baseline is a documented set of approved security settings used as a reference for assessing and maintaining system configuration.

A configuration baseline is a documented set of minimum security requirements and approved settings. It gives an organization a clear reference for hardening systems consistently. It is a minimum, not a limit: a system may need stronger controls. section 15.3

Default settings often favor easy deployment. They may leave unnecessary services running, ports open, or permissions too broad. A baseline turns the goal of reducing those openings into settings that can be checked across systems. section 15.0 section 15.3

A baseline can specify settings such as:

  • Disable insecure or unnecessary services and close network ports that are not needed. section 15.3
  • Enforce strong password requirements. section 15.3

Organizations can start with CIS Benchmarks or the NIST National Checklist Program, then tailor the requirements to their business, operational, and regulatory needs. Policies state what security must achieve; the baseline specifies settings that put those goals into practice. section 15.3 section 15.2.1

Checking a proposed change

Suppose a proposed system change alters an approved setting. During impact analysis, compare the change with the baseline. After deployment, compare the system again to check that it has not drifted from its approved configuration. This makes the baseline useful after initial hardening, not just during setup. section 15.7

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines minimum requirements, illustrates settings, and explains change-review uses without giving a platform-specific configuration procedure.
Examples
Illustrates baselines through disabled services, strong password policies, closed ports, and checks during system changes.
What it assumes
Defines the baseline from minimum requirements before introducing frameworks or change checks; requires no named programming language.
What you can do after
Operate/configure it by choosing approved settings and checking whether proposed changes preserve them.
How it connects
Connects security policies and system hardening to vulnerability management and change management.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.