A baseline configuration is a reviewed record of how a system is intended to be built and operated at a particular point in time. It can include approved operating-system versions, network connections, services, accounts, application settings and security controls. The record is useful only when a team can compare it with the deployed system, authorize legitimate exceptions and keep it current after changes. NIST SP 800-53’s CM-2 control requires developing, documenting and maintaining a current baseline under configuration control; it does not say that possessing a template automatically makes every device secure.
Baseline configuration versus secure configuration settings
A configuration baseline describes the approved, versioned state of a particular system or class of systems. A security-hardening standard is related but not identical: NIST CM-6 addresses configuration settings, while CM-2 addresses the system baseline and its maintenance. A device may match its baseline perfectly while that baseline still contains an excessive permission or obsolete service. Consistency is evidence of control, not proof that the chosen configuration was safe.
For a small business application, the baseline might name the operating system, authorized packages, server purpose, ports permitted by the firewall, local administrative group, backup settings, log destinations and upstream identity provider. It should also specify the owner, review date, source of each required setting and how the configuration is restored. Do not embed passwords, private keys or live tokens in the baseline document.
A practical baseline for one test server
Imagine a disposable application server whose approved state includes a supported OS version, one web process, no directly reachable database port from the internet, forwarding of security logs, and an encrypted backup with a tested restore procedure. Record these requirements in a version-controlled configuration file, then deploy through a reviewed automation tool if one is available. Ensure the example contains fake hostnames and test-only secrets.
Take a second observation of the running server and compare it with the approved baseline. If a new open port appears, do not close it blindly. Establish whether it was authorized for a documented change, whether another service depends on it, and how the change can be reversed safely. A drift detector reports a difference; it does not automatically know whether the difference is malicious, accidental or required by the business.
How to manage exceptions and version changes
Someone must own the baseline and approve changes. Record the reason, expected impact, affected systems, authorizing person, validation plan and rollback mechanism for each proposed change. A security team may demand a stricter setting that breaks a legacy application; the right answer is a controlled decision with compensating safeguards, not a silent exception left permanently in production.
After an operating-system upgrade, verify the default services, permission models, drivers and network paths. Then revise the baseline to reflect the accepted state. NIST CM-2 explicitly calls for review when components are installed or upgraded and at defined intervals. Retain enough older versions to reconstruct a meaningful previous configuration, but do not assume that reverting files restores databases, identities or external resources changed by the same operation.
Use evidence to handle a configuration incident
Suppose a security scan shows that a management endpoint is now reachable from a guest subnet. The baseline states that only a designated administration network should have access. Gather the current firewall policy, route observations, change records and service logs. Identify whether the exposure comes from the host firewall, a network security rule or an intentional emergency exception that was never removed.
Test a corrected rule on a controlled path, verify legitimate administration still works, and check the unauthorized route is blocked. Record the observation rather than relying on a successful configuration command. If enforcement spans cloud and on-premises components, collect evidence from both boundaries. It is possible for the host to match its local baseline while a separate network gateway has an incorrect rule.
Security, compliance and the limits of a baseline
Baselines can support audits by showing an approved standard, its owners, exceptions and measured deviations. Compliance also requires evidence that controls actually operate and that the relevant regulation applies. An approved baseline cannot guarantee regulatory compliance, uninterrupted availability or freedom from vulnerabilities. Scanners miss some exposures and can report false positives; a baseline review should connect automated checks with accountable human decisions.
Different groups may need different baselines. A laptop, domain controller, test database and cloud gateway serve different functions. Reusing one identical checklist for all four can disable necessary services or overlook system-specific risks. Organize baselines by role and risk, document justified deviations, and keep a measured schedule for reassessment.
What a useful baseline record contains
A reviewable baseline answers six questions: which assets and versions it covers; which settings are required; why those settings matter; who approves changes; what evidence shows compliance; and what happens when a deployment deviates. Keep the record short enough for operators to use during incidents. Pair each important requirement with a test—such as a denied connection, a service-status check or a restore result—rather than a vague assertion that security is already ensured.
Baseline management is a recurring operational discipline, not a one-time installation checklist. Its value lies in finding meaningful deviations, controlling changes and enabling reproducible recovery when systems evolve. The team’s evidence, exception handling and maintenance process make the baseline useful; the document alone cannot keep an application available or a network secure.