IIS6 Server
Pick two releases to diff their requirements.
Open a previous version of this STIG.
- RMF Control
- Severity
- M
- CCI
- Version
- WG050 IIS6
- Vuln IDs
-
- V-2232
- Rule IDs
-
- SV-38188r1_rule
Checks: C-37623r1_chk
The reviewer should make a note of the name of the account being used for the web service. NOTE: There may also be other server services running related to the web server in support of a particular web application, these passwords must be entrusted to the SA or Web Manager as well. Query the SA or Web Manager to determine if they have the web service password(s). If the web services password(s) are not entrusted to the SA or Web Manager, this is a finding. NOTE: For IIS installations that use the LocalSystem account, the password is OS generated. In this case, the SA or Web Manager having an Admin account on the system would meet the intent of this check.
Fix: F-32865r1_fix
Ensure the SA or Web Manager is entrusted with the web service(s) password.
- RMF Control
- Severity
- M
- CCI
- Version
- WG040 IIS6
- Vuln IDs
-
- V-2234
- Rule IDs
-
- SV-38175r1_rule
Checks: C-37557r1_chk
1. From a command prompt, type "net share" and press Enter to provide a list of available shares (including printers). 2. To display the permissions assigned to the shares type "net share" followed by the share name found in the previous step. If any private assets are assigned permissions to the share, this is a finding. If any printers are shared, this is a finding.
Fix: F-32803r1_fix
Configure the public web server to not have a trusted relationship with any system resource that is not accessible to the public.
- RMF Control
- Severity
- M
- CCI
- Version
- WG060 IIS6
- Vuln IDs
-
- V-2235
- Rule IDs
-
- SV-38189r1_rule
Checks: C-37627r1_chk
1. Go to Start > Administrative Tools > Services. 2. Right click on service name World Wide Web Publishing Service > Select Properties > Select Log On tab. 3. The username next to “This account” is the web service account ID. 4. Open a command prompt and enter “Net User [service account ID]” > Press Enter 5. Verify the values for Password last set and Password expires to ensure the password has been changed in the past year, and will be required to change within the coming year. If the service account ID is not configured according to the guidelines in step 5, this is a finding. NOTE: For IIS installations that are running as localsystem, the password is changed automatically by the OS every 7 days, so this should be marked as N/A.
Fix: F-32869r1_fix
Configure the service account ID used to run the web site to have its password changed at least annually.
- RMF Control
- Severity
- M
- CCI
- Version
- WG080 IIS6
- Vuln IDs
-
- V-2236
- Rule IDs
-
- SV-38190r1_rule
Checks: C-37633r1_chk
Using Windows Explorer, search the system for the existence of known compilers such as msc.exe, msvc.exe, Python.exe, javac.exe, Lcc-win32.exe, or equivalent. If a compiler is found on the production server, this is a finding. NOTE: This check does not prohibit the use of the .Net Framework. This does not prohibit the use of the java compiler for Oracle. NOTE: ColdFusion would not be considered a compiler as long as the site is not using the tools for development work.
Fix: F-32874r1_fix
Remove any compiler programs found on the production web server.
- RMF Control
- Severity
- M
- CCI
- Version
- WA060 IIS6
- Vuln IDs
-
- V-2242
- Rule IDs
-
- SV-38169r1_rule
Checks: C-37550r1_chk
Determine where the public web server is logically located on the sites LAN. Visually check the web server hardware connections to see if it conforms to the site’s network diagram. If the web server is not isolated in accordance with the DoD Enclave and Internet-NIPRNet DMZ STIGs, this is a finding. NOTE: If there is a Network Reviewer available, they should be able to provide much of the information needed to validate this check.
Fix: F-32796r1_fix
Relocate the public web servers to be isolated from internal systems. In addition, ensure the public web servers do not have trusted connections with assets outside the confines of the Demilitarized Zone (DMZ) or isolated separate public enclave (subnet).
- RMF Control
- Severity
- M
- CCI
- Version
- WA070 IIS6
- Vuln IDs
-
- V-2243
- Rule IDs
-
- SV-38170r1_rule
Checks: C-37551r1_chk
Perform a check of the site’s network diagram and a visual check of the web server. The private web server must be located on a separate controlled access subnet and not part of the public DMZ that houses the public web servers. In addition, the private web server needs to be isolated via a controlled access mechanism from the local general population LAN. If the web server is not located inside the premise router, switch, or firewall, and is not isolated via a controlled access mechanism from the general population LAN, this is a finding. NOTE: If there is a Network Reviewer available, they should be able to provide much of the information needed to validate this check.
Fix: F-32797r1_fix
Isolate the private web server from the public DMZ and separate it from the internal general population LAN. This separation must have access control in place to protect the web server from internal threats.
- RMF Control
- Severity
- H
- CCI
- Version
- WG190 IIS6
- Vuln IDs
-
- V-2246
- Rule IDs
-
- SV-38193r1_rule
Checks: C-37643r1_chk
1. Using Explorer, find the inetinfo.exe file or move to the file %systemroot%\system32\inetsrv\inetinfo.exe. 2. Right-click on inetinfo.exe and select properties. 3. Select the version tab. The file version field should be 6.0.xx. 4. If the current version of the web server software is not installed and running, this is a finding.
Fix: F-32884r1_fix
Upgrade to the current version of the web server software and maintain appropriate service packs and patches.
- RMF Control
- Severity
- H
- CCI
- Version
- WG200 IIS6
- Vuln IDs
-
- V-2247
- Rule IDs
-
- SV-38194r1_rule
Checks: C-37648r1_chk
Search all of the system’s hard drives for the command.com and cmd.exe files. The allowed permissions on these files are: System Full Control Administrators Full Control Examine account access and any group membership access to these files. If any non-administrator account, group membership, or service ID has any access to any command.com or cmd.exe files and the access is documented as mission critical, this is not a finding. Examine access to operating system configuration files, scripts, utilities, privileges, and functions. If any non-administrator account, group membership, or service ID has any access to any of these operating system components and the access is documented as mission critical, this is not a finding. If any non-administrator account, group membership, or service ID has undocumented access to any listed file or operating system component, this is a finding. NOTE: Examine the list of user accounts and determine the group affiliations for the user account in question. Verify with the SA, Web Manager or IAO that the non-administrator accounts are mission essential. If they are mission essential, and this is documented locally, this would not be a finding. NOTE: CREATOR OWNER would not be a finding if the CREATOR OWNER is an administrative account. If it is not, this is a finding.
Fix: F-32889r1_fix
Ensure non-administrators are not allowed access to the directory tree, the shell, or other operating system functions and utilities.
- RMF Control
- Severity
- M
- CCI
- Version
- WG220 IIS6
- Vuln IDs
-
- V-2248
- Rule IDs
-
- SV-38326r1_rule
Checks: C-37716r1_chk
1. Open the Microsoft Management Console (MMC). 2. Expand the applicable policy > Windows Settings > Security Settings > Local Policies 3. Click on User Rights Assignment. 4. Double click Allow log on locally. 5. The Allow log on locally must be limited to accounts owned by the SA, Web Manager, or Web Manager designees. 6. Navigate to %systemroot%\system32\inetsrv\. 7. Right click inetmgr.exe and select properties. 8. Select the security tab. 9. The Internet Services Manager (i.e. inetmgr.exe) must be limited to accounts owned by the SA, Web Manager, or Web Manager’s designees. If accounts other than the System, SA, Web Manager, or Web Manager designees have access to the web administration tool or equivalent, this is a finding.
Fix: F-32963r1_fix
Restrict access to the web administration tool to only the Web Manager and the Web Manager’s designees.
- RMF Control
- Severity
- L
- CCI
- Version
- WG130 IIS6
- Vuln IDs
-
- V-2251
- Rule IDs
-
- SV-38191r1_rule
Checks: C-37637r1_chk
Query the Information Assurance Officer (IAO) SA, Web Manager, Webmaster, and/or developers to determine if the web server is configured with unnecessary software. Query the SA to determine if processes other than those supporting the web server are loaded and/or run on the web server. Examples of software that should not be on the web server are all web development tools, office suites, (unless the web server is a private web development server) compilers, and utilities that are not part of the web server suite or the basic operating system. 1. Check the directory structure of the server and ensure additional, unintended or unneeded applications are not loaded on the system. 2. Select Start > Control Panel > Add or Remove Programs 3. Check for programs services such as: Front Page (as evident by directories which begin _vti ) MS Access MS Excel MS Money MS Word Third party text editors Graphics editors If, after review of the application on the system, the SA cannot provide justification for the requirement of the identified software, this is a finding. NOTE: If the site requires the use of a particular piece of software, the IAO will need to maintain documentation identifying this software as necessary for operations and the software will be maintained to meet any and all released security patches. In addition, if the software is unsupported, it is not acceptable for use. If this is the case, this should be marked as not a finding.
Fix: F-32878r1_fix
Install only web support software on the web server. When other processes are supported by the web server, ensure a risk assessment has been performed and documented. If a database server is installed on the same platform as the web server, it must be on a separate drive or partition. Remove all unnecessary applications and programs.
- RMF Control
- Severity
- L
- CCI
- Version
- WA120 IIS6
- Vuln IDs
-
- V-2257
- Rule IDs
-
- SV-38171r1_rule
Checks: C-37552r1_chk
1. Using User Manager, User Manager for Domains, or Local Users and Groups examine user accounts. 2. Determine if the local sites documentation matches the accounts with access privileges on the server. If documentation does not exist for users and/or groups with access privileges to the web server, this is a finding.
Fix: F-32798r1_fix
Document the administrative users and groups which have access rights to the web server in the web site SOP or an equivalent document.
- RMF Control
- Severity
- M
- CCI
- Version
- WG300 IIS6
- Vuln IDs
-
- V-2259
- Rule IDs
-
- SV-38327r1_rule
Checks: C-37717r1_chk
The default server root is %system%\system32\inetsrv. The anonymous web user is IUSR_computername, which is created by default when IIS is installed. This account should be part of a group named Guests or WebUsers (IIS Lockdown creates the Web Applications and Web Anonymous Users Groups) and have read and execute permissions only to web content directories. Other permissions are as follows: \inetpub Administrators (Full Control) System (Full Control) Authenticated Users (Read) \inetpub\AdminScripts Administrators (Full Control) System (Full Control) \inetpub\ftproot Administrators (Full Control) System (Full Control) Authenticated Users (Read) Web Anonymous Users (Deny Write) Web Applications (Deny Write) IIS_WPG (Deny Write) \inetpub\ftproot\ftpfiles Administrators (Full Control) System (Full Control) WebAdmins (Modify) Authenticated Users (Read) Web Anonymous Users (Read) Web Applications (Read) IIS_WPG (Read) IIS Permissions: Read and None FTP Uploads (if required) \inetpub\ftproot\dropbox Administrators (Full Control) WebAdmins or FTPAdmins (Read,Write,Delete) SpecifiedUsers (Write) IIS Permissions: Write and None \inetpub\mailroot Administrators (Full Control) System (Full Control) Authenticated Users (Read) Web Anonymous Users (Deny Write) Web Applications (Deny Write) IIS_WPG (Deny Write) \inetpub\wwwroot Administrators (Full Control) System (Full Control) Authenticated Users (Read) Web Anonymous Users (Deny Write) Web Applications (Deny Write) IIS_WPG (Deny Write) \inetpub\wwroot\docs Administrators (Full Control) System (Full Control) WebAdmins (Modify) Authenticated Users (Read) Web Anonymous Users (Deny Write) Web Applications (Deny Write) IIS_WPG (Deny Write) IIS Permissions: Read and None \inetpub\wwwroot\images Administrators (Full Control) System (Full Control) WebAdmins (Modify) Authenticated Users (Read) Web Anonymous Users (Deny Write) Web Applications (Deny Write) IIS_WPG (Deny Write) IIS Permissions: Read and None \inetpub\wwwroot\scripts Administrators (Full Control) System (Full Control) WebAdmins(Modify) IIS_WPG (Traverse Folder/Execute) Web Anonymous Users (Traverse Folder/Execute) Web Applications (Traverse Folder/Execute) IIS Permissions: Script NOTE: There may be additional application specific content directories associated with this web server and they should follow the same guidance as the wwwroot and associated sub-directories for permissions. \WINNT\system32\inetsrv Administrators (Full Control) System (Full Control) Users (Read & Execute) \WINNT\system32\inetsrv\data Administrators (Full Control) System (Full Control) Users (Read & Execute) \WINNT\system32\inetsrv\ASP Compiled Templates Administrators (Full Control) System (Full Control) \WINNT\system32\inetsrv\History Administrators (Full Control) System (Full Control) \WINNT\system32\inetsrv\iisadmin Administrators (Full Control) System (Full Control) \WINNT\system32\inetsrv\iisadmpwd Administrators (Full Control) System (Full Control) \WINNT\system32\inetsrv\inetmgr.exe Administrators (Full Control) System (Full Control) Web Admins (Read & Execute) Web Anonymous Users (Deny ALL) Web Applications (Deny ALL) IIS_WPG (Deny ALL) \WINNT\system32\inetsrv\MetaBack Administrators (Full Control) System (Full Control) \WINNT\system32\inetsrv\urlscan Administrators (Full Control) System (Full Control) LocalService (Read / Execute) NetworkService (Read/Execute) FILE SPECIFIC PERMISSIONS: \WINNT\system32\inetsrv\*.exe \WINNT\system32\inetsrv\*.bat \WINNT\system32\inetsrv\oblt-log.log \WINNT\system32\inetsrv\oblt-rep.log \WINNT\system32\inetsrv\oblt-undo.log \WINNT\system32\inetsrv\oblt-undone.log Administrators (Full Control) System (Full Control) Users (Read & Execute) Web Anonymous Users (Deny ALL) Web Applications (Deny ALL) IIS_WPG (Deny ALL) \WINNT\system32\inetsrv\metabase.bin \WINNT\system32\inetsrv\metabase.xml \WINNT\system32\inetsrv\MBSchema.xml \WINNT\system32\inetsrv\ MBSchema.bin.00000000h Administrators (Full Control) System (Full Control) If the file permissions do not meet the minimum file permissions listed above, this is a finding. More restrictive file permissions would not be a finding. NOTE: If there is a "Windows\SysWOW64\Inetsrv" present on the system, this check applies to that directory as well. NOTE: To check the file permissions, navigate to the directories or files using a tool such as Windows Explorer, right click on the directory or file being reviewed > Select properties > Select security tab. The permissions will then be displayed for your review. To check the IIS Permissions, use the Internet Services Manager, navigate to the web site being reviewed > Select properties > Select the Home Directory tab. From here review the assigned IIS permissions for this web site.
Fix: F-32964r1_fix
Set file permissions on the web server system files to meet minimum file permission requirements.
- RMF Control
- Severity
- M
- CCI
- Version
- WG330 IIS6
- Vuln IDs
-
- V-2261
- Rule IDs
-
- SV-38328r1_rule
Checks: C-37718r1_chk
1. Open the Services window > look for the Simple Mail Transfer Protocol (SMTP) service. 2. If the service is running, then this is a finding. 3. Open Add/Remove Programs to see if there are any e-mail programs installed. 4. Search the system to determine if other e-mail programs are running. If there is an e-mail program installed and that program has been configured to accept inbound e-mail, this is a finding. NOTE: If available, telnet to the server under review on port 25. If a response is received, this is a finding.
Fix: F-32965r1_fix
Disable the SMTP service. If other e-mail programs are running, remove them.
- RMF Control
- Severity
- M
- CCI
- Version
- WG470 IIS6
- Vuln IDs
-
- V-2264
- Rule IDs
-
- SV-38332r1_rule
Checks: C-37722r1_chk
1. Select Start > Search > Search for instances of Wscript.exe and Cscript.exe. 2. If found, navigate to these files > right click on them to view their properties. 3. Permissions should only exist for the System, the SA, and Web Manager (i.e. Full Control). 4. User accounts with access to these files that are unknown or unintended to the SA or Web Manager should be removed. If these files have permissions for accounts other than the System, SA, or Web Manager, this is a finding.
Fix: F-32969r1_fix
Remove Wscript.exe and Cscript.exe files from the server, or restrict access to these files to the SA, the Web Administrator, and the system account.
- RMF Control
- Severity
- M
- CCI
- Version
- WG440 IIS6
- Vuln IDs
-
- V-2271
- Rule IDs
-
- SV-38331r1_rule
Checks: C-37721r1_chk
Request to see the template file or configuration file of the software being used to accomplish this security task. The monitoring program should provide constant monitoring for these files, and instantly alert the Web Admin of any unauthorized changes. Examples of CGI file extensions include, but are not limited to cgi, asp, aspx, class, vb, php, pl, and c. If the monitoring product configuration does not monitor changes to CGI program files, this is a finding.
Fix: F-32968r1_fix
Configure the monitoring tool to include CGI type files or equivalent programs directory.
- RMF Control
- Severity
- L
- CCI
- Version
- WA140 IIS6
- Vuln IDs
-
- V-6485
- Rule IDs
-
- SV-38172r1_rule
Checks: C-37554r1_chk
The reviewer should query the Information Assurance Officer (IAO) SA, Web Manager, Webmaster or developers as necessary to determine whether or not a tested and verifiable backup strategy has been implemented for web server software as well as all web server data files. Proposed Questions: Who maintains the backup and recovery procedures? Do you have a copy of the backup and recovery procedures? Where is the off-site backup location? Is the contingency plan documented? When was the last time the contingency plan was tested? Are the test dates and results documented? If there is not a backup and recovery process for the web server, this is a finding. NOTE: Backup media containing sensitive data needs to be compliant with DoD Memorandum: "Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage Media", dated 3 Jul 2007.
Fix: F-32800r1_fix
Document the backup procedures.
- RMF Control
- Severity
- H
- CCI
- Version
- WG195 IIS6
- Vuln IDs
-
- V-6537
- Rule IDs
-
- SV-29351r2_rule
Checks: C-37646r1_chk
The reviewer should review the privileges assigned to the "IUSR_Account". Any group the IUSR_Account is assigned to must not provide authenticated access to the external users. The use of another group created for anonymous access is the acceptable solution for group assignment. 1. Select Start > Control Panel > Administrative Tools > Computer Management > Local Users and Groups > Users. 2. Double click the IUSR_Account > Select “Member of:” tab. If the IUSR_Account is assigned to any group other than a local anonymous group, this is a finding. NOTE: Any associations with the authenticated users group or everyone group would not make this a finding. NOTE: The group created for the anonymous account needs to be restricted to the web directories, and not have access to the entire system.
Fix: F-32887r1_fix
Remove the anonymous access account from all privileged accounts and all privileged groups.
- RMF Control
- Severity
- M
- CCI
- Version
- WG204 IIS6
- Vuln IDs
-
- V-6577
- Rule IDs
-
- SV-38196r1_rule
Checks: C-37654r1_chk
Request a copy of and review the web server’s installation and configuration plan. Ensure the server is in compliance with this plan. If the server is not in compliance with the plan, this is a finding. Query the SA to ascertain if and where the additional services are installed. Confirm the additional service or application is not installed on the same partition as the operating systems root directory or the web document root. If it is, this is a finding.
Fix: F-32895r1_fix
Move or install additional services and applications to partitions that are not the operating system root or the web document root.
- RMF Control
- Severity
- L
- CCI
- Version
- WG520 IIS6
- Vuln IDs
-
- V-6724
- Rule IDs
-
- SV-38333r1_rule
Checks: C-37723r1_chk
Query the SA regarding the publishing of the web server or operating system information. The SA should be able to show that the web server is configured to not display the host operating system of the web server. The reviewer should review the following registry key using the registry editor: HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\DisableServerHeader (REG_DWORD) If the value is not set to 1, this is a finding.
Fix: F-32970r1_fix
Set the following registry key to 1: HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\DisableServerHeader (REG_DWORD)
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI080 IIS6
- Vuln IDs
-
- V-6754
- Rule IDs
-
- SV-38150r1_rule
Checks: C-37520r1_chk
1. Open IIS Manager > expand the applicable server > select "Web Service Extensions". 2. In the right pane, the Internet Printing extension should be displayed. 3. If the Internet Printing extension is set to "Allowed", this is a finding.
Fix: F-32768r1_fix
Set the Internet Printing Extension to “Prohibited”.
- RMF Control
- Severity
- H
- CCI
- Version
- WA155 IIS6
- Vuln IDs
-
- V-13591
- Rule IDs
-
- SV-38173r1_rule
Checks: C-37555r1_chk
Interview the IAO, the SA, the Web Administrator, or developers as necessary to determine if a classified web server is afforded physical security commensurate with the classification of its content (i.e., is located in a vault or a room approved for classified storage at the highest classification processed on that system). Ask what the classification of the web server is, and based on the classification, evaluate the location of the web server. Determine if it is approved for storage of that classification level. If there is a traditional reviewer available, work with them to address specific conditions or questions. If the web server is not appropriately physically protected based on its classification, this is a finding.
Fix: F-32801r1_fix
Relocate the web server to a location appropriate to classified devices.
- RMF Control
- Severity
- M
- CCI
- Version
- WA230 IIS6
- Vuln IDs
-
- V-13613
- Rule IDs
-
- SV-38174r1_rule
Checks: C-37556r1_chk
Query the Web Administrator to determine if the site has a detailed process as part of its configuration management plan to stay compliant with all security-related patches. Proposed Questions: How does the SA stay current with web server vendor patches? How is the SA notified when a new security patch is issued by the vendor? What is the process followed for applying patches to the web server (excluding IAVM)? If the site is not in compliance with all applicable security patches, this is a finding.
Fix: F-32802r1_fix
Establish a detailed process as part of the configuration management plan to stay compliant with all web server security-related patches.
- RMF Control
- Severity
- H
- CCI
- Version
- WG385 IIS6
- Vuln IDs
-
- V-13621
- Rule IDs
-
- SV-38330r1_rule
Checks: C-37720r1_chk
Query the SA to determine if all directories that contain samples and any scripts used to execute the samples have been removed from the server. Each web server has its own list of sample files and folders. These may change with the software versions and features utilized on the web server. The following are some examples of what to look for, and should not be considered the definitive list of sample files and folders. If present, remove the following directories: %systemdrive%\inetpub\AdminScripts %systemdrive%\inetpub\scripts\IISSamples If present, remove the following virtual directories: http://localhost/iissamples http://localhost/IISHelp If any sample files or folders are found on the web server, this is a finding. NOTE: The presence of the AdminScripts directory would not be a finding if the permissions are restricted to administrators and Web Admins.
Fix: F-32967r1_fix
Remove sample code and documentation from the web server.
- RMF Control
- Severity
- H
- CCI
- Version
- WA000-WI035 IIS6
- Vuln IDs
-
- V-13698
- Rule IDs
-
- SV-38148r1_rule
Checks: C-37517r1_chk
1. Select Start > Run. 2. Enter %systemroot%\system32\inetsrv into the run dialog box and press OK. 3. Look for the presence of the iisadmpwd directory. 4. If the directory is present and is capable of being removed, this is a finding. NOTE: If the iisadmpwd directory does not exist, this is NOT a finding and the check procedure can stop here. NOTE: There have been numerous reports of sites not being able to delete this directory without Windows File Protection automatically restoring it. The work around for this will be to ensure the virtual directory is removed from all web sites associated with the server and restrict access to this directory and files to the system and administrators. 5. If the iisadmpwd directory exists on the server due to a technical inability to delete it, review the permissions on this directory and its files. The permissions should be as follows: Administrators - Full Control System - Full Control 6. If any other user or group has permissions to this directory, this is a finding. 7. If the permissions are set correctly, use the IIS Services Manager and review the web sites to see if there is a virtual directory associated with any of the sites pointing to the iisadmpwd directory. A virtual directory will be a child directory to a web site. 8. If any of these directories point to the iisadmpwd directory, this is a finding, even if the permissions are set correctly. NOTE: There is a possibility the automated check will result in a false positive condition. This could occur if the Administrators account has been renamed. If the account causing the finding has access to this directory is in the Administrators group, this would not be a finding.
Fix: F-32766r1_fix
If possible, ensure the iisadmpwd directory has been removed from the web server. If removal is not possible ensure the virtual directory is removed from all web sites associated with the server, and restrict access to this directory and it files, to the system and administrators. NOTE: There have been numerous reports of sites not being able to delete this directory without Windows File Protection automatically restoring it. The work around for this will be to ensure the virtual directory is removed from all web sites associated with the server and to restrict access for this directory and files to the system and administrators. NOTE: The .dll in the IISADMPWD folder may be able to be deleted by going into safe mode and deleting it. This will not work for the folder. If the IISADMPWD directory cannot be deleted set the permissions as follows: Administrators - Full Control System - Full Control
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI100 IIS6
- Vuln IDs
-
- V-13700
- Rule IDs
-
- SV-38151r1_rule
Checks: C-37521r1_chk
Query the SA or Web Manager to determine if the File System Object is required. If it is, the IAO will need to document this requirement. Check for the existence of the following registry keys. If either of the following keys exists, the FileSystemObject is enabled: HKEY_CLASSES_ROOT\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228} HKEY_CLASSES_ROOT\Scripting.FileSystemObject If the File System Object is registered and is not required for operations, this is a finding. NOTE: This vulnerability can be documented locally by the IAM/IAO if the site is running an application requiring the registration of this object if the site has operational reasons for the use of this object and if the IAM/IAO has approved this change in writing, this should be marked as not a finding.
Fix: F-32769r1_fix
Unregister the File System Object using the following command: regsvr32 scrrun.dll /u.
- RMF Control
- Severity
- H
- CCI
- Version
- WA000-WI110 IIS6
- Vuln IDs
-
- V-13701
- Rule IDs
-
- SV-38159r1_rule
Checks: C-37540r1_chk
Check the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters for the following value: SSIEnableCmdDirective REG_DWORD 0. If the key does not exist or if the value is not a REG_DWORD= 0, this is a finding.
Fix: F-32786r1_fix
Set the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters to the following value: SSIEnableCmdDirective REG_DWORD 0
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6080 IIS6
- Vuln IDs
-
- V-13714
- Rule IDs
-
- SV-38160r1_rule
Checks: C-37541r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the AllowRestrictedChars key is set to REG_DWORD 0. If the registry key is not set to 0 or does not exist, this is a finding.
Fix: F-32787r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the AllowRestrictedChars key to REG_DWORD 0 or add the key and set it to REG_DWORD 0.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6082 IIS6
- Vuln IDs
-
- V-13715
- Rule IDs
-
- SV-38161r1_rule
Checks: C-37542r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters EnableNonUTF8. 3. Ensure the value for the EnableNonUTF8 key is REG_DWORD 0. If the registry key is not set to 0 or does not exist, this is a finding.
Fix: F-32788r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the EnableNonUTF8 key to REG_DWORD 0 or add the key and set it to REG_DWORD 0.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6084 IIS6
- Vuln IDs
-
- V-13716
- Rule IDs
-
- SV-38162r1_rule
Checks: C-37543r1_chk
To verify this setting, use the registry editor and navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters FavorUTF8 REG_DWORD 1 If the registry value is not set to 1, this is a finding. NOTE: If check WA000-WI6082 is set correctly to 0, this registry key is optional and would not be a finding if it is not present.
Fix: F-32789r1_fix
Use the registry editor and navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Set the " FavorUTF8" key to REG_DWORD 1, add the key if it does not exist.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6086 IIS6
- Vuln IDs
-
- V-13717
- Rule IDs
-
- SV-38163r1_rule
Checks: C-37544r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the MaxFieldLength key is REG_DWORD 16384 (or less). If the registry value is not set to 16384 (or less) or missing, this is a finding. NOTE: This vulnerability can be documented locally by the IAM/IAO if the site has operational reasons for an increased value. If the IAM/IAO has approved this change in writing, this should be marked as not a finding.
Fix: F-32790r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the MaxFieldLength key to REG_DWORD 16384 (or less) or add the key and set it to REG_DWORD 16384.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6088 IIS6
- Vuln IDs
-
- V-13718
- Rule IDs
-
- SV-38164r1_rule
Checks: C-37545r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the MaxRequestBytes key is set to REG_DWORD 16384 (or less). If the registry key is not set to 16384 (or less) or is missing, this is a finding. NOTE: This vulnerability can be documented locally by the IAM/IAO if the site has operational reasons for an increased value. If the IAM/IAO has approved this change in writing, this should be marked as not a finding.
Fix: F-32791r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the MaxRequestBytes key to REG_DWORD 16384 (or less) or add the key and set it to REG_DWORD 16384.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6090 IIS6
- Vuln IDs
-
- V-13719
- Rule IDs
-
- SV-38165r1_rule
Checks: C-37546r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the UrlSegmentMaxLength key is set to REG_DWORD 260 (or less). If the registry key is not set to 260 (or less) or is missing, this is a finding.
Fix: F-32792r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the UrlSegmentMaxLength key to REG_DWORD 260 (or less) or add the key and set it to REG_DWORD 260.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6092 IIS6
- Vuln IDs
-
- V-13720
- Rule IDs
-
- SV-38166r1_rule
Checks: C-37547r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the PercentUAllowed key is set to REG_DWORD 0. If the registry value is not set to 0 or is missing, this is a finding.
Fix: F-32793r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the PercentUAllowed key to REG_DWORD 0 or add the key and set it to REG_DWORD 0.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6094 IIS6
- Vuln IDs
-
- V-13721
- Rule IDs
-
- SV-38167r1_rule
Checks: C-37548r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Ensure the value for the UriMaxUriBytes key is set to REG_DWORD 262144 (or less). If the registry value is not set to 262144 (or less) or is missing, this is a finding.
Fix: F-32794r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the UriMaxUriBytes key to REG_DWORD 262144 or add the key and set it to REG_DWORD 262144.
- RMF Control
- Severity
- M
- CCI
- Version
- WA000-WI6096 IIS6
- Vuln IDs
-
- V-13722
- Rule IDs
-
- SV-38168r1_rule
Checks: C-37549r1_chk
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the UrlSegmentMaxCount key is set to REG_DWORD 255 (or less). If the registry value is not set to 255 (or less) or is missing, this is a finding.
Fix: F-32795r1_fix
1. Open the registry editor. 2. Navigate to the following location in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters. 3. Set the value for the UrlSegmentMaxCount key to REG_DWORD 255 (or less) or add the key and set it to REG_DWORD 255.