Operating System Not Hardened to a Recognised Baseline

The operating system largely keeps its default settings instead of following a recognised security baseline, leaving unnecessary features and weak settings in place.

SeverityMedium
CVSS 3.14.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Open in the calculator
CVSS 4.04.8 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1188: Initialization of a Resource with an Insecure Default
CategorySecurity Misconfiguration

Description

Operating systems ship with settings chosen largely for compatibility, and several protections are off or relaxed by default. Organisations close that gap by applying a recognised security baseline, such as the CIS Benchmarks, the Microsoft security baselines, the DISA Security Technical Implementation Guides (STIGs) or a vendor's hardening guide, and by keeping hosts compliant with it. The host reviewed does not follow such a baseline: comparing its configuration with one shows a significant number of settings that differ, with no documented reason.

Typical deviations include legacy protocols and authentication methods still enabled, such as SMBv1, LLMNR, NetBIOS name resolution or NTLMv1; unnecessary services, features and software installed; weak audit and logging settings; permissive local security policy and user rights; and, on Linux, permissive kernel parameters, unneeded network services and lax file permissions. No single deviation need be serious, but together they make attacks easier at every stage: they give an attacker more services to target, more ways to capture or relay credentials, more routes to escalate privileges and fewer records of what was done. A configuration that is not managed against a baseline also drifts over time and differs between hosts, so a weakness corrected on one system often remains on others.

Individual deviations with a significant impact are normally reported as findings of their own; this finding records that hardening is not managed as a whole, and its practical impact depends on the specific deviations found, which should be read alongside it. It is identified by comparing the configuration with a baseline, using tools such as CIS-CAT, OpenSCAP or those in Microsoft's Security Compliance Toolkit, or by reviewing the effective Group Policy and configuration files manually.

Remediation

Adopt a recognised baseline and manage hosts against it as a continuing process:

  • Choose a baseline for each operating system in use, such as the relevant CIS Benchmark Level 1 profile, the Microsoft security baselines or a DISA STIG, and record each setting the organisation deliberately departs from, with the reason and the risk owner.
  • Test the baseline on a representative group of systems, then apply it centrally: Group Policy or Intune security baselines for Windows (Windows Server 2025 can also apply Microsoft's baselines through OSConfig), and configuration management tools such as Ansible, Puppet or Chef, or hardened build profiles, for Linux.
  • Build new systems from hardened images or templates so that they are compliant from the start.
  • Remove features, services and software that are not needed, such as SMBv1 and PowerShell 2.0, and disable legacy name resolution and authentication protocols once their remaining dependencies have been dealt with.
  • Measure compliance regularly with a tool such as CIS-CAT, OpenSCAP or Microsoft's Security Compliance Toolkit, and treat deviations as defects to be corrected.

While the baseline is rolled out, prioritise the individual deviations reported elsewhere in the assessment. Confirm the fix by repeating the comparison against the chosen baseline and checking that any remaining differences are documented exceptions.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Windows and Linux Hosts Findings

Every Windows and Linux Hosts finding