Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Security Baseline
Cyber Security

Security Baseline

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

A security baseline is the control set used to judge whether a cloud environment is meeting expectations. It may come from a benchmark, a framework, a customer questionnaire, or a regulated standard. In practice, the baseline determines what evidence is collected, how findings are scored, and what must be fixed.

What a security baseline does

A security baseline is the reference point that turns a broad policy expectation into a testable control set. In cloud and platform environments, it is usually the minimum configuration standard that evidence, scoring and exception handling are measured against. That makes the baseline both a security standard and a practical assessment tool.

Baselines are useful because they reduce ambiguity. Instead of asking whether a system is “secure enough” in the abstract, teams can compare actual settings against an agreed benchmark, framework, customer requirement or regulated standard. The baseline therefore becomes the shared language between engineering, security, audit and risk owners.

Where security baselines come from

A baseline can be derived from different sources depending on the environment and the assurance goal. Some baselines are benchmark-driven, such as a hardened operating system profile. Others are built from framework requirements, customer questionnaires or regulatory obligations, especially when the organisation must prove a minimum control posture to a third party.

That source matters because it shapes the scope of the check. A benchmark may focus on technical hardening settings, while a customer-driven baseline may emphasise logging, account controls or encryption evidence. In many programmes, the baseline is an overlap of several authorities rather than a single document.

For cloud teams, widely used baselines such as ISO/IEC 27002:2022 Information Security Controls and CIS Benchmarks often shape what “good” looks like, even when the final control set is customised for the organisation.

How baselines shape scoring and evidence

Once a baseline exists, it drives the assessment workflow. Evidence collection is no longer random because the baseline defines which settings, artifacts and control outcomes must be verified. Findings can then be scored consistently, which helps teams compare estates, prioritise remediation and track change over time.

This is why baselines are more than documentation. They influence what the scanner looks for, what analysts accept as proof and what the organisation treats as a deviation. In practice, a strong baseline gives security teams a repeatable way to separate normal variation from control failure.

That repeatability is especially important in platforms where configurations drift quickly. NHIMG’s Configuration Drift and Baseline Enforcement Guide explains how drift detection and enforcement connect the baseline to real operational state, while the CIS Control 4 Secure Configuration of Enterprise Assets and Software Guide shows how baseline choice and implementation are linked to secure configuration outcomes.

Why baseline management is an ongoing control problem

Security baselines are not “set and forget”. Systems change, vendors update defaults, business teams request exceptions and new services introduce new settings. If the baseline is not maintained, it can become detached from the estate it is meant to judge, which weakens both security and assurance.

The practical challenge is keeping the baseline current without turning it into a moving target. Teams usually need a controlled way to version baselines, approve exceptions and decide when a change is a legitimate policy update versus an uncontrolled deviation. NHIMG’s Secure Configuration and Hardening Policy Template and Hardening Exceptions and Compensating Controls Template reflect that governance reality: the baseline only works when deviations are visible and time-bound.

Different environments also need different baseline expressions. A server baseline, browser baseline, endpoint baseline or cloud tenant baseline may all serve the same security objective, but each has its own control surface and evidence pattern. NHIMG’s Cloud Security Guide is a useful parent reference for understanding how cloud guardrails, logging and posture checks sit around that broader baseline model.

How practitioners use baselines well

Why practitioners should care: A baseline is only valuable if it is both strict enough to reduce risk and clear enough to measure. If it is too vague, different teams will interpret it differently; if it is too rigid, exceptions will accumulate outside governance and the baseline will stop reflecting reality.

Common misunderstanding: A benchmark is not automatically a baseline, and a baseline is not automatically a benchmark. The useful version is the one that has been adapted to the organisation’s actual systems, evidence sources and remediation process. NHIMG’s Microsoft Cloud Security Benchmark Guide illustrates how a vendor benchmark can be translated into a working control baseline.

Practitioner takeaway: Treat the baseline as an operational control contract, not just a checklist, and make sure the exception process is as deliberate as the baseline itself.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareSecurity baselines operationalise secure configuration expectations.
CIS-7 — Continuous Vulnerability ManagementBaseline drift and weak settings are often detected through ongoing assessment and verification.
Recommendation — Use CIS-4 to define hardened settings, measure drift, and remediate deviations from the approved baseline. Use CIS-7 to continuously identify and prioritise baseline-related exposure.
NIST SP 800-53 Rev 5CM-2 — Baseline ConfigurationBaseline selection and comparison are central to configuration-management governance.
CM-6 — Configuration SettingsSecurity baselines specify required settings and acceptable deviations.
Recommendation — Establish CM-2 baselines and compare system state against approved configurations. Use CM-6 to define, enforce, and review required secure configuration settings.
ISO/IEC 27001:2022A.8.9 — Configuration managementBaselines are the practical artefact of controlled secure configuration management.
Recommendation — Apply A.8.9 to govern configuration baselines, approval, and change control.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org