Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-3338 | 3.063 | SV-6274r1_rule | ECSC-1 | High |
Description |
---|
This is a Category 1 finding because the potential for gaining unauthorized system access. Pipes are internal system communications processes. They are identified internally by ID numbers that vary between systems. To make access to these processes easier, these pipes are given names that do not vary between systems. This setting controls which of these pipes anonymous users may access. |
STIG | Date |
---|---|
Windows XP Security Technical Implementation Guide | 2012-08-22 |
Check Text ( C-154r1_chk ) |
---|
Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network access: Named pipes that can be accessed anonymously” contains entries besides “COMNAP, COMNODE, SQL\QUERY, SPOOLSS, LLSRPC, browser”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: NullSessionPipes Value Type: REG_MULTI_SZ Value: As defined in the policy above Note: Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the IAO this would not be a finding. Documentation should contain supporting information from the vendor's instructions. Note: Windows XP 64-Bit is based on Windows 2003. An XP 64-bit system will include the following by default: COMNAP, COMNODE, SQL\QUERY, SPOOLSS, NETLOGON, LSARPC, SAMR, BROWSER |
Fix Text (F-28868r1_fix) |
---|
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network access: Named pipes that can be accessed anonymously” as defined in the Check section. |