Outdated Domain Functional Level

The domain or forest runs at an old functional level, which keeps legacy behaviour and prevents the use of security features that require a newer level.

SeverityInformational
CVSS 3.10 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N Open in the calculator
CVSS 4.00 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-693: Protection Mechanism Failure
OWASP Top 10A06:2025 Insecure Design
CategorySecurity Misconfiguration

Description

The domain and forest functional levels determine which Active Directory features are available, and cannot be higher than the oldest Windows Server version run by any domain controller in the domain or forest. A domain or forest left at an old level cannot use features introduced since, even when every domain controller has been upgraded. This does not expose the domain to a specific attack, and the finding is therefore rated as informational: its effect is to withhold protections that limit credential theft and the misuse of privileged accounts. An old level often indicates, however, that domain controllers running unsupported versions of Windows Server remain, or did until recently, and legacy domain controllers that no longer receive security updates are a more serious issue in their own right.

Security-related features that depend on the domain functional level include AES encryption for Kerberos and fine-grained password policies (Windows Server 2008); the domain controller options that always provide claims and require Kerberos armouring, also called FAST (Windows Server 2012); the domain controller protections of the Protected Users group, and authentication policies and silos (Windows Server 2012 R2); and the automatic rolling of NTLM secrets for accounts that require smart card sign-in (Windows Server 2016). The Active Directory Recycle Bin, which helps recovery, needs the Windows Server 2008 R2 forest functional level.

The levels are shown by the domainFunctionality and forestFunctionality attributes of the rootDSE, which can be read without authentication, by Get-ADDomain and Get-ADForest, and by most directory assessment tools.

Remediation

  • Upgrade or replace every domain controller running a Windows Server version that is out of support or older than the target level, then demote the old ones and remove any that no longer exist from the directory.
  • Raise the domain functional level, then the forest functional level, to the highest level that all domain controllers support, with Active Directory Domains and Trusts or the Set-ADDomainMode and Set-ADForestMode cmdlets, as a member of Domain Admins and Enterprise Admins respectively.
  • Plan the change: a raised level can only be lowered in limited cases, so confirm with application owners that nothing depends on legacy behaviour, and check that no domain controller runs an older version.
  • After raising the level, adopt the features it allows, such as Protected Users for administrators and authentication policy silos for Tier 0 accounts.

Confirm the fix with (Get-ADDomain).DomainMode and (Get-ADForest).ForestMode, or by reading the rootDSE attributes again.

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 Active Directory Findings

Every Active Directory finding