What changed in Apache Server 2.4 UNIX Site STIG V2R7V2R7 changes

Apache Server 2.4 UNIX Site STIG V2R7 (2026-07-01) replaced V2R6 (2025-04-02): 11 checks removed, 2 updated. It has 16 checks, against 27 in V2R6.

  • 0 added
  • 11 removed
  • 2 updated

Updated fields: Check text 2CCIs 1Title 1Discussion 1

Removed since V2R6 (11)

  • V-214277CAT IIThe Apache web server must perform server-side session management.
  • V-214278CAT IIThe Apache web server must use encryption strength in accordance with the categorization of data hosted by the Apache web server when remote connections are provided.
  • V-214279CAT IIThe Apache web server must produce log records containing sufficient information to establish what type of events occurred.
  • V-214281CAT IIThe Apache web server must have Multipurpose Internet Mail Extensions (MIME) that invoke operating system shell programs disabled.
  • V-214283CAT IIThe Apache web server must have resource mappings set to disable the serving of certain file types.
  • V-214285CAT IIThe Apache web server must be configured to use a specified IP address and port.
  • V-214291CAT IIThe Apache web server must be tuned to handle the operational requirements of the hosted application.
  • V-214293CAT IIWarning and error messages displayed to clients must be modified to minimize the identity of the Apache web server, patches, loaded modules, and directory paths.
  • V-214294CAT IIDebugging and trace information used to diagnose the Apache web server must be disabled.
  • V-214295CAT IIThe Apache web server must set an absolute timeout for sessions.
  • V-214299CAT IIThe Apache web server application, libraries, and configuration files must only be accessible to privileged users.

Updated in V2R7 (2)

V-214288CAT IICookies exchanged between the Apache web server and client, such as session cookies, must have security settings that disallow cookie access outside the originating Apache web server and hosted application.Check text

Check text

Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: # apachectl -V | egrep -i 'httpd_root|server_config_file' -D HTTPD_ROOT="/etc/httpd" -D SERVER_CONFIG_FILE="conf/httpd.conf" Note: The apachectl front end is the preferred method for locating the Apache httpd file. For some Linux distributions, "apache2ctl -V" or "httpd -V" can also be used. Search for the "Set-Cookie Header" directive: # cat /&ltpath_to_file>/httpd.conf | grep -i "Header.*Set-Cookie" If "HttpOnly" "secure" is not configured, this is a finding. "Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;secure" Review the code. If, when creating cookies, the following is not occurring, this is a finding: function setCookie() { document.cookie = "ALEPH_SESSION_ID = $SESS; path = /; secure"; }

V-214304CAT IIIThe Apache web server must prohibit or restrict the use of nonsecure or unnecessary ports, protocols, modules, and/or services.Title, Check text, Discussion, CCIs

Title

The Apache web server must beprohibit configuredor inrestrict accordance with the securityuse configurationof settingsnonsecure based on DoD security configuration or implementationunnecessary guidanceports, including STIGsprotocols, NSA configuration guidesmodules, CTOs, and/or DTMsservices.

Check text

Review the website to determine if HTTP and HTTPsHTTPS are used in accordance with well-known ports (e.g., 80 and 443) or those ports and services as registered and approved for use by the DoDDOD PPSM. Verify that any variation in PPS is documented, registered, and approved by the PPSM. If well-known ports and services are not approved for useduse by PPSM, this is a finding.

Discussion

ConfiguringWeb theservers Apacheprovide webnumerous serverprocesses, tofeatures, implementand organization-widefunctionalities securitythat implementationuse guidesTCP/IP andports. securitySome checklistsof guaranteesthese complianceprocesses withmay federalbe standardsdeemed andunnecessary establishesor too unsecure to run on a commonproduction securitysystem. The baselineweb acrossserver must provide the DoDcapability thatto reflectsdisable theor mostdeactivate restrictivenetwork-related securityservices posturethat consistentare withdeemed operationalnonessential requirements.to the Configurationserver settingsmission, are too unsecure, or are prohibited by the setPorts, ofProtocols, parametersand thatServices canManagement be(PPSM) changedCategory thatAssurance affectList (CAL) and vulnerability assessments. Configuring the web server to implement organizationwide security postureimplementation guides and/or functionalitysecurity ofchecklists theguarantees system.compliance Security-relatedwith parametersfederal arestandards parametersand impactingestablishes thea common security statebaseline ofacross the ApacheDOD webthat server,reflects including the parametersmost requiredrestrictive tosecurity satisfyposture otherconsistent securitywith controloperational requirements. Satisfies: SRG-APP-000516-WSR-000174, SRG-APP-000383-WSR-000175

CCIs

CCI-000366CCI-001762,CCI-000366

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 V2R7 no longer has.

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