Hello !
We have an LDAP account that is member of local administrator via a LDAP group.
After applying the CIS 2019 lvl1 GPO we are getting partial credential succes on port 445. When I view the best practise following Rapid7 Authentication on Windows: best practices | InsightVM Documentation (rapid7.com) the best practise of Rapid7 is going against the CIS compliance on point 18.3.1.
Why is the credential best practise going against CIS compliance and are there workarounds ?
18.3.1 (L1) Ensure ‘Apply UAC restrictions to local accounts on network
logons’ is set to ‘Enabled’ (MS only) (Automated)
Profile Applicability:
Level 1 - Member Server
Description:
This setting controls whether local accounts can be used for remote administration via
network logon (e.g., NET USE, connecting to C$, etc.). Local accounts are at high risk for
credential theft when the same account and password is configured on multiple systems.
Enabling this policy significantly reduces that risk.
Enabled: Applies UAC token-filtering to local accounts on network logons. Membership in
powerful group such as Administrators is disabled and powerful privileges are removed
from the resulting access token. This configures the LocalAccountTokenFilterPolicy
registry value to 0. This is the default behavior for Windows.
Disabled:Allows local accounts to have full administrative rights when authenticating via
network logon, by configuring the LocalAccountTokenFilterPolicy registry value to 1.
For more information about local accounts and credential theft, review the “Mitigating
Pass-the-Hash (PtH) Attacks and Other Credential Theft Techniques” documents.
For more information about LocalAccountTokenFilterPolicy, see Microsoft Knowledge
Base article 951016: Description of User Account Control and remote restrictions in
Windows Vista.
The recommended state for this setting is: Enabled.
474 | P a g e
Rationale:
Local accounts are at high risk for credential theft when the same account and password is
configured on multiple systems. Ensuring this policy is Enabled significantly reduces that
risk.
Impact:
None - this is the default behavior.
Audit:
Navigate to the UI Path articulated in the Remediation section and confirm it is set as
prescribed. This group policy setting is backed by the following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System:
LocalAccountTokenFilterPolicy
Remediation:
To establish the recommended configuration via GP, set the following UI path to Enabled:
Computer Configuration\Policies\Administrative Templates\MS Security
Guide\Apply UAC restrictions to local accounts on network logons
Note: This Group Policy path does not exist by default. An additional Group Policy template
(SecGuide.admx/adml) is required - it is available from Microsoft at this link.
Default Value:
Enabled. (UAC token-filtering is applied to local accounts on network logons. Membership
in powerful groups such as Administrators and disabled and powerful privileges are
removed from the resulting access token.