Back to Cybersecurity

Minimum Baseline Security Standard (MBSS): How to Write One, With Outline and Checklist

11 min read

Minimum baseline security standard document with hardening settings for servers, cloud accounts, databases and laptops

Short answer: A minimum baseline security standard (MBSS) is a documented set of required security settings for each technology you run, such as operating systems, cloud accounts, databases, network devices, laptops and SaaS admin consoles. Build it from CIS Benchmarks or vendor baselines, record exceptions, and monitor for drift so you can prove it to auditors and customers.

Related guides:

Key takeaways

  • An MBSS is a document, not a tool: one baseline per technology, listing each required setting, its value, the source it came from and how you check it.
  • You do not need to invent settings. Start from CIS Benchmarks, DISA STIGs or vendor baselines such as Microsoft's, then tailor and document what you changed.
  • One MBSS can provide evidence for several frameworks at once: ISO 27001 A.8.9, NIST SP 800-53 CM-2 and CM-6, SOC 2 CC7.1 and PCI DSS Requirement 2.2.
  • The baseline is only credible with an exceptions register and drift monitoring behind it. Auditors test whether systems actually match the document.

What is a minimum baseline security standard (MBSS)?

An MBSS is the written, approved minimum configuration that every instance of a given technology must meet before it goes into production and while it stays there.

Think of it as the "definition of hardened" for your company. Your configuration management process is how changes get made; the MBSS is the reference those changes are measured against. A typical SaaS company keeps separate baselines for server operating systems, cloud accounts, databases, network devices, laptops and SaaS admin consoles such as the identity provider and code hosting.

NIST uses a closely related term. Its National Checklist Program is the US government repository of security configuration checklists, and NIST SP 800-70 Rev. 4 defines a checklist as a document with instructions for configuring a product, verifying it was configured properly and identifying unauthorized changes. Your MBSS is the company-specific version: public checklists, tailored and approved for your environment. It also differs from MVSP, which describes the minimum security a software product should have rather than how your infrastructure is configured.

Why do customers and auditors ask for an MBSS?

They ask because a written baseline is the simplest proof that you configure systems deliberately rather than by default.

The request typically shows up in three places:

  1. Security questionnaires. Enterprise buyers ask "Do you maintain hardening standards for all system components?" and increasingly ask for the document itself.
  2. Vendor security requirements in customer contracts. Larger customers, particularly in regulated industries, may ask suppliers to share or attest to a documented hardening standard. Exact expectations vary by customer, so read the contract wording.
  3. Audits. ISO 27001, SOC 2 and PCI DSS assessors will ask for your configuration standards and then sample systems to see whether they match.

How does an MBSS map to ISO 27001, SOC 2, NIST and PCI DSS?

Each major framework has a control that asks you to define secure configurations and keep systems aligned to them, so one MBSS can provide evidence for all of them. Auditors will still test that the settings are implemented, monitored and reviewed.

Framework Reference What it asks for What your MBSS provides
ISO/IEC 27001:2022 Annex A 8.9 Configuration management Security configurations of hardware, software, services and networks are established, documented, implemented, monitored and reviewed. ISO describes the goal as ensuring configuration "is not altered by unauthorized or incorrect changes." The documented configurations, plus your monitoring and review records
NIST SP 800-53 Rev. 5 CM-2 Baseline Configuration Develop, document and maintain under configuration control a current baseline configuration, and review and update it The baseline itself and its version history
NIST SP 800-53 Rev. 5 CM-6 Configuration Settings Establish settings that reflect the most restrictive mode consistent with operational requirements; implement them; identify, document and approve deviations; monitor changes Settings tables, exceptions register, drift reports
SOC 2 Trust Services Criteria CC7.1 Detection and monitoring procedures to identify changes to configurations that introduce new vulnerabilities. Points of focus include using defined configuration standards The defined standard that monitoring compares against
PCI DSS v4.0.1 Requirement 2.2 2.2.1: configuration standards that cover all system components, address known vulnerabilities, are consistent with industry-accepted hardening standards or vendor recommendations, and are applied to new systems Configuration standards per component type, sourced from CIS or vendor guidance

The CM-6 discussion in SP 800-53 names common secure configurations such as STIGs as inputs, which supports building from public benchmarks. PCI SSC states that PCI DSS v4.0.1 is the only active version since v4.0 was retired on 31 December 2024.

How do you write an MBSS for a small company?

Pick your in-scope technologies, adopt a published benchmark for each, tailor it, and get it approved.

  1. List your technologies. Group your asset inventory by technology, not by host: "Ubuntu 24.04 servers," not 40 server names.
  2. Choose a source per technology. Good public options:
    • CIS Benchmarks: prescriptive, consensus-based configuration recommendations for 25+ vendor product families, covering operating systems, cloud providers and network devices. The CIS FAQ says they are distributed free in PDF format and describes Level 1 as a base recommendation with limited performance impact, and Level 2 as defense in depth.
    • DISA STIGs, published through the DoD Cyber Exchange. Written for US Department of Defense systems and generally stricter, so most SMBs use them selectively or as a cross-check.
    • Vendor baselines such as the Microsoft security baselines, which Microsoft describes as groups of Microsoft-recommended configuration settings with their security implications.
  3. Start at CIS Level 1. For most SMBs, Level 1 plus a few targeted Level 2 items is a sensible floor.
  4. Tailor and record why. Remove settings that do not apply or would break production, and write down each removal with a reason. Auditors accept tailoring; they do not accept silence.
  5. Decide how each setting is checked. Mark it automated (CSPM, MDM, configuration scanner) or manual (quarterly review). If you are choosing a cloud scanner, see our CSPM tools comparison.
  6. Assign owners and approve. Each baseline needs a technical owner and an approver, typically your security lead.
  7. Set a review cadence. Review at least annually, and whenever the source benchmark releases a new version or you adopt a new platform version.

MBSS template: what sections should it have?

Use the same structure for every technology so auditors and engineers know where to look.

Section Fields to include
Document control Baseline ID, technology, version, owner, approver, effective date, next review date
Scope Technology and versions covered, environments (production, staging), systems explicitly excluded
Sources Benchmark name and version (for example, CIS benchmark for the platform, Level 1), vendor guidance used
Settings table Setting ID, setting, required value, rationale, source reference, check method (automated or manual), severity
Tailoring log Source recommendations not adopted, with reason and approver
Exceptions Link to exceptions register entries that apply to this baseline
Build and deployment How the baseline is applied: golden image, infrastructure as code module, MDM profile
Monitoring Tool, frequency, alert route, drift remediation SLA
Evidence Which reports are retained, where, and for how long
Change history Date, version, change summary, approver

MBSS checklist: sample settings by technology

The table below shows illustrative examples only. Your actual settings should come from the current benchmark for your platform version, tailored to your environment.

Technology Example settings
Linux servers SSH root login disabled; SSH key authentication only; automatic security updates enabled; audit logging on and shipped to central logs; unused services removed
Cloud account (for example AWS) MFA on the root user and no root access keys; audit logging enabled in all regions; account-level block on public storage access; default encryption for storage and volumes
Databases Not publicly accessible; encryption at rest; TLS required for connections; automated backups with tested restore; connection and admin activity logging
Network devices and firewalls Default credentials changed; management interfaces not exposed to the internet; insecure management protocols such as Telnet disabled; configuration backed up
Endpoints Full-disk encryption; screen lock after inactivity; host firewall on; EDR or antivirus running; OS updates enforced (see our endpoint baseline guide)
SaaS admin settings MFA or SSO enforced for all users; limited number of super admins; external sharing restricted; branch protection on default code branches

Several of these line up directly with PCI DSS 2.2, which also requires vendor default accounts to be managed, only necessary services to be enabled, and non-console administrative access to be encrypted.

How should you handle exceptions to the baseline?

Every deviation should be requested, risk-assessed, approved, time-limited and recorded, which is exactly what CM-6 means by identifying, documenting and approving deviations.

A lightweight exceptions process:

  1. Request. The system owner names the baseline setting, affected systems and business reason.
  2. Assess. Security rates the risk and defines compensating controls, such as network isolation for a legacy host.
  3. Approve. Higher risk needs a more senior approver.
  4. Expire. Each exception has an end date (for example, 6 months), then is renewed or closed.
  5. Record. Log it in an exceptions register that links to the baseline ID and setting ID, and suppress the known finding in your scanner so real drift stands out.

If the same exception keeps getting renewed, update the baseline instead.

How do you monitor drift and prove it to auditors?

Scan systems against the baseline continuously or on a fixed schedule, fix drift within a defined window, and keep the reports.

  • Cloud accounts: a CSPM or native provider rules, mapped to baseline IDs.
  • Servers and containers: configuration scanners or policy-as-code checks in CI, plus golden images so new systems start compliant, as PCI DSS 2.2.1 expects.
  • Endpoints and SaaS: MDM compliance reports and periodic admin-setting reviews.

Evidence auditors typically ask for:

Evidence Shows
Approved MBSS with version history The standard exists and is reviewed
Tailoring log and exceptions register Deviations are controlled
Scan or compliance reports over the audit period Systems actually match the baseline
Tickets showing drift remediated Monitoring leads to action
Build templates (images, IaC modules, MDM profiles) New systems start hardened

For a Type 2 SOC 2 or an ISO 27001 surveillance audit, expect the auditor to sample dates across the period, so keep reports from the whole window, not just the week before fieldwork.

How SecureSlate helps

SecureSlate helps you turn an MBSS into a control you can evidence:

  • Custom frameworks and controls: MBSS is not a built-in framework, so you set it up as a custom framework, with each baseline or key setting as a control. Multi-framework control mapping then links those controls to built-in frameworks including ISO 27001, SOC 2, PCI DSS and NIST CSF.
  • Agentless read-only cloud integrations surface cloud configuration findings you can compare against your baseline.
  • Device agent reports endpoint settings such as disk encryption, screen lock and firewall status.
  • Risk management gives exceptions a home, with owners, compensating controls and review dates.
  • Audit management keeps baseline documents, scan reports and remediation evidence in one place.
  • Security questionnaire automation helps you answer hardening questions consistently.

Start your free SecureSlate trial and map your first baseline as a custom framework.

FAQ

What does MBSS stand for?

MBSS stands for minimum baseline security standard. It is a documented set of minimum required security settings for each technology an organization runs, used as the reference point for hardening, monitoring and audits.

Is an MBSS the same as CIS Benchmarks?

No. CIS Benchmarks are public, generic configuration recommendations. An MBSS is your organization's approved standard, which often adopts a CIS Benchmark as its source and then records your tailoring, exceptions, owners and monitoring.

How many baselines does a small SaaS company need?

Usually one per major technology in scope: your cloud account, server OS, database, laptops and key SaaS admin consoles. The exact number depends on how many distinct technologies you run. Start with the systems that store or process customer data.

How often should an MBSS be reviewed?

At least annually, and when the source benchmark publishes a new version, when you adopt a new platform version, or after an incident caused by misconfiguration. NIST SP 800-53 CM-2 also calls for review when components are installed or upgraded.

Disclaimer (legal note)

This article is for general information only and is not legal, regulatory or professional advice. Requirements vary by framework, industry and jurisdiction. Consult qualified advisors for your specific obligations.

Need compliance without the complexity?

SecureSlate automates ISO 27001, SOC 2, GDPR, HIPAA, and more. Built for growing teams. See it in action.

Find compliance gaps in 30 seconds

Keep reading

Oct 1, 2026 · Cybersecurity

German IT Security Act 2.0 and NIS2: What SaaS and HealthTech Suppliers Need to Know

Jun 17, 2026 · Cybersecurity

Security Posture Best Practices: How to Assess and Improve It

Jun 20, 2026 · Cybersecurity

Cyber Security Report Example: Types, Template and Sample

View more posts