| V-206390 | | The web server must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when encrypting stored data. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified, and cannot be relied up... |
| V-206399 | | The web server must generate a unique session identifier for each session using a FIPS 140-2 approved random number generator. | Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. In order to maintain a connection... |
| V-206431 | | The web server must encrypt user identifiers and passwords. | When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb... |
| V-206434 | | The web server must employ cryptographic mechanisms (TLS/DTLS/SSL) preventing the unauthorized disclosure of information during transmission. | Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in orde... |
| V-206350 | | The web server must limit the number of allowed simultaneous session requests. | Web server management includes the ability to control the number of users and user sessions that utilize a web server. Limiting the number of allowed ... |
| V-206351 | | The web server must perform server-side session management. | Session management is the practice of protecting the bulk of the user authorization and identity information. Storing of this data can occur on the cl... |
| V-206352 | | The web server must use encryption strength in accordance with the categorization of data hosted by the web server when remote connections are provided. | The web server has several remote communications channels. Examples are user requests via http/https, communication to a backend database, or communic... |
| V-206353 | | The web server must use cryptography to protect the integrity of remote sessions. | Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even whe... |
| V-206354 | | The web server must generate information to be used by external applications or entities to monitor and control remote access. | Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to... |
| V-206355 | | The web server must enforce approved authorizations for logical access to hosted applications and resources in accordance with applicable access control policies. | To control access to sensitive information and hosted applications by entities that have been issued certificates by DoD-approved PKIs, the web server... |
| V-206356 | | The web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events. | Log records can be generated from various components within the web server (e.g., httpd, plug-ins to external backends, etc.). From a web server persp... |
| V-206357 | | The web server must initiate session logging upon start up. | An attacker can compromise a web server during the startup process. If logging is not initiated until all the web server processes are started, key in... |
| V-206359 | | The web server must produce log records containing sufficient information to establish what type of events occurred. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206360 | | The web server must produce log records containing sufficient information to establish when (date and time) events occurred. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206361 | | The web server must produce log records containing sufficient information to establish where within the web server the events occurred. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206362 | | The web server must produce log records containing sufficient information to establish the source of events. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206363 | | A web server, behind a load balancer or proxy server, must produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206364 | | The web server must produce log records that contain sufficient information to establish the outcome (success or failure) of events. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206365 | | The web server must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-206366 | | The web server must use a logging mechanism that is configured to alert the ISSO and SA in the event of a processing failure. | Reviewing log data allows an investigator to recreate the path of an attacker and to capture forensic data for later use. Log data is also essential t... |
| V-206367 | | The web server must use the internal system clock to generate time stamps for log records. | Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysi... |
| V-206368 | | Web server log files must only be accessible by privileged users. | Log data is essential in the investigation of events. If log data were to become compromised, then competent forensic analysis and discovery of the tr... |
| V-206369 | | The log information from the web server must be protected from unauthorized modification. | Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not h... |
| V-206370 | | The log information from the web server must be protected from unauthorized deletion. | Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not h... |
| V-206371 | | The log data and records from the web server must be backed up onto a different system or media. | Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up log records to an unrelated system or onto separate ... |
| V-206372 | | All web server files must be verified for their integrity (e.g., checksums and hashes) before becoming part of the production web server. | Being able to verify that a patch, upgrade, certificate, etc., being added to the web server is unchanged from the producer of the file is essential f... |
| V-206373 | | Expansion modules must be fully reviewed, tested, and signed before they can exist on a production web server. | In the case of a production web server, areas for content development and testing will not exist, as this type of content is only permissible on a dev... |
| V-206374 | | The web server must not perform user management for hosted applications. | User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user man... |
| V-206375 | | The web server must only contain services and functions necessary for operation. | 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 DoD sy... |
| V-206376 | | The web server must not be a proxy server. | A web server should be primarily a web server or a proxy server but not both, for the same reasons that other multi-use servers are not recommended. ... |
| V-206377 | | The web server must provide install options to exclude the installation of documentation, sample code, example applications, and tutorials. | Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server because this type of code has ... |
| V-206378 | | Web server accounts not utilized by installed features (i.e., tools, utilities, specific services, etc.) must not be created and must be deleted when the web server feature is uninstalled. | When accounts used for web server features such as documentation, sample code, example applications, tutorials, utilities, and services are created ev... |
| V-206379 | | The web server must provide install options to exclude installation of utility programs, services, plug-ins, and modules not necessary for operation. | Just as running unneeded services and protocols is a danger to the web server at the lower levels of the OSI model, running unneeded utilities and pro... |
| V-206380 | | The web server must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled. | Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more function... |
| V-206381 | | The web server must allow the mappings to unused and vulnerable scripts to be removed. | Scripts allow server side processing on behalf of the hosted application user or as processes needed in the implementation of hosted applications. Rem... |
| V-206382 | | The web server must have resource mappings set to disable the serving of certain file types. | Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client... |
| V-206383 | | The web server must have Web Distributed Authoring (WebDAV) disabled. | A web server can be installed with functionality that, just by its nature, is not secure. Web Distributed Authoring (WebDAV) is an extension to the HT... |
| V-206384 | | The web server must protect system resources and privileged operations from hosted applications. | A web server may host one too many applications. Each application will need certain system resources and privileged operations to operate correctly. ... |
| V-206385 | | Users and scripts running on behalf of users must be contained to the document root or home directory tree of the web server. | A web server is designed to deliver content and execute scripts or applications on the request of a client or user. Containing user requests to files... |
| V-206386 | | The web server must be configured to use a specified IP address and port. | The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utili... |
| V-206387 | | The web server must encrypt passwords during transmission. | Data used to authenticate, especially passwords, needs to be protected at all times, and encryption is the standard method for protecting authenticati... |
| V-206388 | | The web server must perform RFC 5280-compliant certification path validation. | A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path vali... |
| V-206389 | | Only authenticated system administrators or the designated PKI Sponsor for the web server must have access to the web servers private key. | The web server's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt commun... |
| V-206391 | | The web server must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon... |
| V-206392 | | A web server utilizing mobile code must meet DoD-defined mobile code requirements. | Mobile code in hosted applications allows the developer to add functionality and displays to hosted applications that are fluid, as opposed to a stati... |
| V-206393 | | Web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts. | As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require acco... |
| V-206394 | | Anonymous user access to the web server application directories must be prohibited. | In order to properly monitor the changes to the web server and the hosted applications, logging must be enabled. Along with logging being enabled, eac... |
| V-206395 | | The web server must separate the hosted applications from hosted web server management functionality. | The separation of user functionality from web server management can be accomplished by moving management functions to a separate IP address or port. ... |
| V-206396 | | The web server must invalidate session identifiers upon hosted application user logout or other session termination. | Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and continuing to employ previo... |
| V-206397 | | Cookies exchanged between the web server and client, such as session cookies, must have security settings that disallow cookie access outside the originating web server and hosted application. | Cookies are used to exchange data between the web server and the client. Cookies, such as a session cookie, may contain session information and user c... |
| V-206398 | | The web server must accept only system-generated session identifiers. | Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. In order to maintain a connection... |
| V-206400 | | The web server must generate unique session identifiers that cannot be reliably reproduced. | Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. In order to maintain a connection... |
| V-206401 | | The web server must generate a session ID long enough that it cannot be guessed through brute force. | Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowin... |
| V-206402 | | The web server must generate a session ID using as much of the character set as possible to reduce the risk of brute force. | Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing... |
| V-206403 | | The web server must generate unique session identifiers with definable entropy. | Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing... |
| V-206404 | | The web server must augment re-creation to a stable and known baseline. | Making certain that the web server has not been updated by an unauthorized user is always a concern. Adding patches, functions, and modules that are u... |
| V-206405 | | The web server must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail. | Determining a safe state for failure and weighing that against a potential DoS for users depends on what type of application the web server is hosting... |
| V-206406 | | The web server must provide a clustering capability. | The web server may host applications that display information that cannot be disrupted, such as information that is time-critical or life-threatening.... |
| V-206407 | | Information at rest must be encrypted using a DOD-accepted algorithm to protect the confidentiality and integrity of the information. | Data at rest is inactive data stored physically in any digital form (e.g., databases, data warehouses, spreadsheets, archives, tapes, off-site backups... |
| V-206408 | | The web server document directory must be in a separate partition from the web servers system files. | A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted applica... |
| V-206409 | | The web server must restrict the ability of users to launch Denial of Service (DoS) attacks against other information systems or networks. | A web server can limit the ability of the web server being used in a DoS attack through several methods. The methods employed will depend upon the hos... |
| V-206410 | | The web server must limit the character set used for data entry. | Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared... |
| V-206411 | | The web server must display a default hosted application web page, not a directory listing, when a requested web page cannot be found. | The goal is to completely control the web user's experience in navigating any portion of the web document root directories. Ensuring all web content d... |
| V-206412 | | Warning and error messages displayed to clients must be modified to minimize the identity of the web server, patches, loaded modules, and directory paths. | Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server, backend... |
| V-206413 | | Debugging and trace information used to diagnose the web server must be disabled. | Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug... |
| V-206414 | | The web server must set an absolute session timeout value of eight hours or less. | Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted applicat... |
| V-206415 | | The web server must set an inactive timeout for sessions. | Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted applicat... |
| V-206416 | | Remote access to the web server must follow access policy or work in conjunction with enterprise tools designed to enforce policy requirements. | Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to... |
| V-206417 | | The web server must restrict inbound connections from nonsecure zones. | Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to... |
| V-206418 | | The web server must provide the capability to immediately disconnect or disable remote access to the hosted applications. | During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to st... |
| V-206419 | | Non-privileged accounts on the hosting system must only access web server security-relevant information and functions through a distinct administrative account. | By separating web server security functions from non-privileged users, roles can be developed that can then be used to administer the web server. Forc... |
| V-206421 | | The web server must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the web server. | In order to make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mec... |
| V-206422 | | The web server must not impede the ability to write specified log record content to an audit log server. | Writing events to a centralized management audit system offers many benefits to the enterprise over having dispersed logs. Centralized management of a... |
| V-206423 | | The web server must be configurable to integrate with an organizations security infrastructure. | A web server will typically utilize logging mechanisms for maintaining a historical log of activity that occurs within a hosted application. This info... |
| V-206424 | | The web server must use a logging mechanism that is configured to provide a warning to the ISSO and SA when allocated record storage volume reaches 75% of maximum log record storage capacity. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process logs as required. Log processing failures includ... |
| V-206425 | | The web server must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple device... |
| V-206426 | | The web server must record time stamps for log records to a minimum granularity of one second. | Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records.
Time stamps generated ... |
| V-206427 | | The web server application, libraries, and configuration files must only be accessible to privileged users. | A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes... |
| V-206428 | | The web server must prohibit or restrict the use of nonsecure or unnecessary ports, protocols, modules, and/or services. | Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or ... |
| V-206430 | | The web server must only accept client certificates (user and machine) issued by DOD PKI or DOD-approved PKI Certificate Authorities (CAs). | Non-DOD approved PKIs have not been evaluated to ensure that they have security controls and identity vetting procedures in place which are sufficient... |
| V-206432 | | The web server must be protected from being stopped by a non-privileged user. | An attacker has at least two reasons to stop a web server. The first is to cause a DoS, and the second is to put in place changes the attacker made to... |
| V-206433 | | The web server must be tuned to handle the operational requirements of the hosted application. | A Denial of Service (DoS) can occur when the web server is so overwhelmed that it can no longer respond to additional requests. A web server not prope... |
| V-206435 | | Web server session IDs must be sent to the client using SSL/TLS. | The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used... |
| V-206436 | | Web server cookies, such as session cookies, sent to the client using SSL/TLS must not be compressed. | A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client return... |
| V-206437 | | Cookies exchanged between the web server and the client, such as session cookies, must have cookie properties set to prohibit client-side scripts from reading the cookie data. | A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side script... |
| V-206438 | | Cookies exchanged between the web server and the client, such as session cookies, must have cookie properties set to force the encryption of cookies. | Cookies can be sent to a client using TLS/SSL to encrypt the cookies, but TLS/SSL is not used by every hosted application since the data being display... |
| V-206439 | | A web server must maintain the confidentiality of controlled information during transmission through the use of an approved TLS version. | Transport Layer Security (TLS) is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidenti... |
| V-206440 | | The web server must remove all export ciphers to protect the confidentiality and integrity of transmitted information. | During the initial setup of a Transport Layer Security (TLS) connection to the web server, the client sends a list of supported cipher suites in order... |
| V-206441 | | The web server must maintain the confidentiality and integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during agg... |
| V-206442 | | The web server must maintain the confidentiality and integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protoc... |
| V-206443 | | The web server must install security-relevant software updates within the configured time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). | Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovere... |
| V-206444 | | All accounts installed with the web server software and tools must have passwords assigned and default passwords changed. | During installation of the web server software, accounts are created for the web server to operate properly. The accounts installed can have either no... |
| V-206445 | | The web server must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. | Configuring the web server to implement organization-wide security implementation guides and security checklists guarantees compliance with federal st... |
| V-239371 | | The web server must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when encrypting data that must be compartmentalized. | Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data.
Use of weak or untested encryption algorithms unde... |
| V-264337 | | The web server must disable accounts when the accounts have expired. | Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality which reduce the attack ... |
| V-264338 | | The web server must disable accounts when the accounts are no longer associated to a user. | Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality which reduce the attack ... |
| V-264339 | | The web server must implement the capability to centrally review and analyze audit records from multiple components within the system. | Automated mechanisms for centralized reviews and analyses include security information and event management products.... |
| V-264340 | | The web server must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information. | Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and... |
| V-264341 | | The web server must automatically generate audit records of the enforcement actions. | Organizations log system accesses associated with applying configuration changes to ensure that configuration change control is implemented and to sup... |
| V-264342 | | The web server must require users to be individually authenticated before granting access to the shared accounts or resources. | Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.... |
| V-264343 | | The web server must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access. | The purpose of requiring a device separate from the system to which the user is attempting to gain access for one of the factors during multifactor au... |
| V-264344 | | The web server must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements. | The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multif... |
| V-264345 | | The web server must, for password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264346 | | The web server must, for password-based authentication, update the list of passwords on an organization-defined frequency. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264347 | | The web server must, for password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264348 | | The web server must, for password-based authentication, verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a). | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264349 | | The web server must, for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264350 | | The web server must, for password-based authentication, require immediate selection of a new password upon account recovery. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264351 | | The web server must, for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264352 | | The web server must, for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264353 | | The web server must, for password-based authentication, enforce organization-defined composition and complexity rules. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-264354 | | The web server must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation. | Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certific... |
| V-264355 | | The web server must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths. | Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through either an external or internal network. Communicat... |
| V-264356 | | The web server must include only approved trust anchors in trust stores or certificate stores managed by the organization. | Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the inter... |
| V-264357 | | The web server must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. | A Trusted Platform Module (TPM) is an example of a hardware-protected data store that can be used to protect cryptographic keys.... |
| V-264358 | | The web server must synchronize system clocks within and between systems or system components. | Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication proc... |
| V-264359 | | The web server must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source. | Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and ... |
| V-264360 | | The web server must restrict a consistent inbound source IP for the entire management session. | Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
... |
| V-264361 | | The web server must restrict a consistent inbound source IP for the entire user session. | Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
... |
| V-264362 | | The web server must use HTTP/2, at a minimum. | HTTP/2, like HTTPS, enhances security compared to HTTP/1.x by minimizing the risk of header-based attacks (e.g., header injection and manipulation).
... |
| V-264363 | | The web server must disable HTTP/1.x downgrading. | HTTP/2 is backward compatible with HTTP/1.x, so it is possible to configure the architecture to implement a front-end server for HTTP/2 while communic... |
| V-264364 | | The web server must interpret and normalize ambiguous HTTP requests or terminate the TCP connection. | Request smuggling attacks involve placing both the Content-Length header and the Transfer-Encoding header into a single HTTP/1 request and manipulatin... |
| V-264365 | | The web server must terminate the connection if server-level exceptions are triggered when handling requests to prevent HTTP request smuggling attacks. | The web server defines a set of exceptions for every HTTP status code. Each exception class has a status code according to RFC 2068: Codes with 100-30... |
| V-264366 | | The web server must only use forward proxies that route HTTP/2 requests upstream. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepte... |
