What changed in Microsoft IIS 10.0 Server STIG V3R8V3R8 changes

Microsoft IIS 10.0 Server STIG V3R8 (2026-09-30) replaced V3R7 (2026-04-01): 4 checks updated. It has 40 checks, against 40 in V3R7.

  • 0 added
  • 0 removed
  • 4 updated

Updated fields: Discussion 4Check text 1Title 1

Updated in V3R8 (4)

V-218793CAT IIThe IIS 10.0 web server must only contain functions necessary for operation.Discussion

Discussion

A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DoDDoW system. The web server must provide the capability to disable, uninstall, or deactivate functionality and services deemed non-essentialnonessential to the web server mission or that adversely impact server performance.

V-218801CAT IIJava software installed on a production IIS 10.0 web server must be limited to .class files and the Java Virtual Machine.Discussion

Discussion

Mobile code in hosted applications allows the developer to add functionality and displays to hosted applications that are fluid, as opposed to a static web page. The data presentation becomes more appealing to the user, is easier to analyze, and is less complicated to navigate through the hosted application and data. Some mobile code technologies in use in today's applications are: Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. The DoDDoW has created policies that define the usage of mobile code on DoDDoW systems. The usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. Source code for a Java program is often stored in files with either .java or .jpp file extensions. From the .java and .jpp files the Java compiler produces a binary file with an extension of .class. The .java or .jpp file could therefore reveal sensitive information regarding an application's logic and permissions to resources on the server.

V-218812CAT IIThe IIS 10.0 web server must restrict inbound connections from non-secure zones.Discussion

Discussion

Remote access to the web server is any access that communicates through an external, nonnonorganization-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. A web server can be accessed remotely and must be capable of restricting access from what the DoDDoW defines as non-secure zones. Non-secure zones are defined as any IP, subnet, or region defined as a threat to the organization. The non-secure zones must be defined for public web servers logically located in a DMZ, as well as private web servers with perimeter protection devices. By restricting access from non-secure zones through internal web server access lists, the web server can stop or slow denial -of -service (DoS) attacks on the web server.

V-228572CAT IIAn IIS Server must be configured to be a SMTP relay must require authentication.Title, Check text, Discussion

Title

An IIS Server must be configured to be a SMTP relay must require authentication.

Check text

Interview the Systemsystem Administratoradministrator (SA) about the role of the IIS 10.0 web server. If the IIS 10.0 web server is running SMTP relay services, have the SA provide supporting documentation on how the server is hardened. A DoDDoW-issued certificate, and specific allowed IP address should be configured. This requirement applies to the existence of a third-party SMTP relay as well. If the IIS web server is not running SMTP relay services, this is Not Applicable. If the IIS web server running SMTP relay services without TLS enabled, this is a finding. If the IIS web server running SMTP relay services is not configured to only allow a specific IP address, from the same network as the relay, this is a finding.

Discussion

Anonymous SMTP relays are strictly prohibited. An anonymous SMTP relay can be a vector for many types of malicious activity not limited to server exploitation for the sending of SPAM mail, access to emails, phishing, denial-of-service (DoS) attacks, etc. Enabling TLS, authentication, and strictly assigning IP addresses that can communicate with the relay greatly reduce the risk of the implementation.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V3R8 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.