This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Secure configuration: which baseline should your servers follow, and do they still match it?
This quarter, pick one published baseline per server platform, remove default and shared credentials and switch off the legacy protocols that relay attacks need, auditing each change before you enforce it. Then apply the baseline from code to every new and existing server and compare live settings with it every week, so drift becomes a finding with an owner.
If you only do five things
Switch off what relay attacks need.
After an audit, require SMB signing, LDAP signing and channel binding, and remove SMBv1, NTLMv1, LLMNR and NetBIOS. Microsoft saw NTLM-related security cases rise nearly sixfold in a decade, and more in the first half of 2026 than in all of 20255.
Apply it from code and check for drift.
Keep GPOs, OSConfig settings and playbooks in version control. Google calls hardening a state to maintain against drift: UNC3944 relied on changes such as enabling SSH24.
Roll out a baseline without breaking things
Measure before you change.
Pick the domain controller, member server or workgroup variant for each server3. Compare current GPOs with it in Policy Analyzer1, or run
oscap xccdf evalwith the profile on Linux20.Turn on the audit events and wait.
Log for two to four weeks, including a month end: SMB's Audit client does not support signing2, NTLM events 4020 to 4023 and 4030 to 40339, LSA protection events 3065 and 306614 and LDAP events 2889, 3074 and 3075, which need diagnostic logging and channel binding at When supported1112.
Enforce in rings, with an exception list.
Start with IT's own servers. Give each exception an owner, a reason and an end date; BSI asks you to document and justify settings you can't apply26.
Plan the rollback before you remediate.
Snapshot first: Red Hat has no automated way to revert hardening20, and removing an OSConfig baseline may not restore the old settings3.
Build new servers hardened.
Red Hat supports remediation only on systems in their default configuration, so install from a hardened Kickstart file or image20. Finish the configuration before a server reaches production or the internet26.
Windows Server settings that matter most
- SMB. Remove SMBv1, which Server 2019 and later don't install7. Server 2025 member servers require signing only outbound6: audit them, then require inbound signing or EPA2.
- LDAP signing and channel binding. New Active Directory deployments on Server 2025 require signing by default; channel binding defaults to When supported there and Never on 2022 and earlier1112. Once the audit events stop, set Require signing and Always.
- NTLMv1, LLMNR, NetBIOS and old TLS. The Server 2025 OSConfig baseline allows only NTLMv2, turns off LLMNR and NetBIOS and requires TLS 1.2 or later3. Set the same on older servers: Server 2022 and earlier enable TLS 1.0 and 1.1 by default13.
- LSA protection. Only new, domain-joined Windows 11 installs turn it on by default14; on Server 2025, the OSConfig baseline runs LSASS as a protected process3. Turn it on once the audit events are clean; with UEFI lock, as Microsoft's GPO baseline sets it, policy alone can't turn it off again14.
Every server, Linux, databases and hypervisors
- Unused roles and services. Remove what a server doesn't need, including firmware functions26. On Windows, start with the Print Spooler on domain controllers and servers that don't print15.
- Linux. RHEL 10's SCAP Security Guide has CIS, DISA STIG, PCI DSS and BSI SYS.1.1 and SYS.1.3 profiles20. Ubuntu's USG has CIS and STIG profiles for 20.04 to 24.04 and needs Ubuntu Pro, free only for personal use2122.
- Databases. Prefer Active Directory logins to SQL Server logins, keep
sadisabled, leavexp_cmdshelloff and enable only the features you use16. - ESXi. Google advises not joining hosts to Active Directory24; if you must, replace the default ESX Admins group with your own. Turn on audit records, off by default, and forward them23. Encrypt Tier 0 VMs24.
- Management controllers. Put iLO, iDRAC and other BMCs on an isolated network with local accounts, and disable IPMI Cipher 0 and unused services23.
What changed in 2026
- The Windows Server 2025 baseline turned on NTLM auditing in version 2602, published in February 2026. It says to audit SMB clients on member servers before requiring signing or EPA2.
- The 2011 Secure Boot certificates expired. Servers without the 2023 certificates still boot but get no new boot-level protections19.
- Broadcom's 9.1 hardening guide came out in June 2026, for VCF and vSphere Foundation 9.1, with PowerCLI audit and remediation scripts23.
- NTLM is going away in stages. October 2026 updates added enhanced NTLM auditing to Server 2019 and 20229 and block NTLMv1-derived single sign-on by default on Server 20258. Microsoft plans to disable network NTLM by default in the next major Windows Server release10.
What you can skip
- Every control at its strictest. Broadcom offers a reasonable baseline, not a catalog of every control, because the strictest settings often impede daily administration23. Use CIS Level 1 unless a rule requires Level 2.
- Buying CIS SecureSuite first. Microsoft's baselines come in the Security Compliance Toolkit1, RHEL ships CIS profiles20 and CIS Benchmark PDFs are free for non-commercial use28. CIS names hosting, consulting and security products as commercial use; membership starts at $2,400 a year27.
- Hardening the ESXi SSH daemon. Broadcom dropped that control: keep SSH stopped except for brief, supervised diagnostics23.
Mistakes that cost the most
- Enforcing signing before auditing. Once LDAP signing is required, domain controllers reject unsigned binds and simple binds without TLS11.
- Two tools managing one setting. If Group Policy and OSConfig set different values, the setting keeps flipping between them3.
- Weakening a whole server for one device. Turning off SMB signing for an old NAS7 or using RHEL's LEGACY crypto policy20 weakens every other connection.
- Leaving old VMs on the datastore. UNC3944 used an orphaned VM to read a domain controller's disk24. Delete retired disks.
What this looks like at your size
Small team, no security staff
- Test Microsoft's baseline GPOs, or OSConfig on Server 2025, on one server per role first.
- Ask your IT provider for every default or shared password on servers, NAS, hypervisors and BMCs, and turn on Windows LAPS.
- Find the tools that log in to ESXi hosts directly, then turn on lockdown mode in vCenter.
Growing, with IT or security staff
- Keep baselines and exceptions in version control and change them by pull request.
- Run the NTLM, SMB and LDAP audits this quarter, then enforce one ring a month.
- With Defender for Servers Plan 2, check Windows servers against CIS, or STIG on Server 2019, in its baselines assessment18.