Network access: Restrict anonymous access to Named Pipes and Shares
|ID: oval:org.secpod.oval:def:40252||Date: (C)2017-04-25 (M)2018-07-10|
|Class: COMPLIANCE||Family: windows|
When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings. This policy setting controls null session access to shares on your computers by adding RestrictNullSessAccess with the value 1 in the HKLM\System
\CurrentControlSet\Services\LanManServer\Parameters registry key. This registry value toggles null session shares on or off to control whether the server service restricts unauthenticated clients' access to named resources. Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.
Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.
Configure the Network access: Restrict anonymous access to Named Pipes and Shares setting to Enabled.
You can enable this policy setting to restrict null session access for unauthenticated users to all server pipes and shared folders except those that are listed in the NullSessionPipes and NullSessionShares entries.
If you choose to enable this setting and are supporting Windows NT 4.0 domains, you should check if any of the named pipes are required to maintain trust relationships between the domains, and then add the pipe to the Network access: Named pipes that can be accessed anonymously:
- COMNAP -SNA session access
- COMNODE -SNA session access
- SQL\QUERY -SQL instance access
- SPOOLSS -Spooler service
- LLSRPC -License Logging service
- Netlogon -Net Logon service
- Lsarpc -LSA access
- Samr -Remote access to SAM objects
- browser -Computer Browser service
Previous to the release of Windows Server 2003 with Service Pack 1 (SP1) these named pipes were allowed anonymous access by default, but with the increased hardening in Windows Server 2003 with SP1 these pipes must be explicitly added if needed.
(1) GPO: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Restrict anonymous access to Named Pipes and Shares
(2) REG: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters!restrictnullsessaccess
|Microsoft Windows Server 2016|