STIGQter STIGQter: STIG Summary:

Application Server Security Requirements Guide

Version: 3

Release: 1 Benchmark Date: 23 Oct 2020

CheckedNameTitle
☐SV-204708r508029_ruleThe application server must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types.
☐SV-204709r508029_ruleThe application server must use encryption strength in accordance with the categorization of the management data during remote access management sessions.
☐SV-204710r508029_ruleThe application server must implement cryptography mechanisms to protect the integrity of the remote access session.
☐SV-204711r508029_ruleThe application server must ensure remote sessions for accessing security functions and security-relevant information are logged.
☐SV-204712r508029_ruleThe application server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
☐SV-204713r508029_ruleThe application server management interface must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
☐SV-204714r508029_ruleThe application server management interface must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.
☐SV-204715r508029_ruleThe application server must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.
☐SV-204716r508029_ruleFor application servers providing log record aggregation, the application server must compile log records from organization-defined information system components into a system-wide log trail that is time-correlated with an organization-defined level of tolerance for the relationship between time stamps of individual records in the log trail.
☐SV-204717r508029_ruleThe application server must generate log records for access and authentication events.
☐SV-204718r508029_ruleThe application server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which logable events are to be logged.
☐SV-204719r508029_ruleThe application server must generate log records when successful/unsuccessful attempts to access subject privileges occur.
☐SV-204720r508029_ruleThe application server must initiate session logging upon startup.
☐SV-204721r508029_ruleThe application server must produce log records containing information to establish what type of events occurred.
☐SV-204722r508029_ruleThe application server must produce log records containing sufficient information to establish when (date and time) the events occurred.
☐SV-204723r508029_ruleThe application server must produce log records containing sufficient information to establish where the events occurred.
☐SV-204724r508029_ruleThe application server must produce log records containing sufficient information to establish the sources of the events.
☐SV-204725r508029_ruleThe application server must produce log records that contain sufficient information to establish the outcome of events.
☐SV-204726r508029_ruleThe application server must generate log records containing information that establishes the identity of any individual or process associated with the event.
☐SV-204727r508029_ruleThe application server must generate log records containing the full-text recording of privileged commands or the individual identities of group account users.
☐SV-204728r508029_ruleThe application server must alert the SA and ISSO, at a minimum, in the event of a log processing failure.
☐SV-204729r508029_ruleThe application server must shut down by default upon log failure (unless availability is an overriding concern).
☐SV-204730r508029_ruleThe application server must be configured to fail over to another system in the event of log subsystem failure.
☐SV-204731r508029_ruleThe application server must use internal system clocks to generate time stamps for log records.
☐SV-204732r508029_ruleThe application server must protect log information from any type of unauthorized read access.
☐SV-204733r508029_ruleThe application server must protect log information from unauthorized modification.
☐SV-204734r508029_ruleThe application server must protect log information from unauthorized deletion.
☐SV-204735r508029_ruleThe application server must protect log tools from unauthorized access.
☐SV-204736r508029_ruleThe application server must protect log tools from unauthorized modification.
☐SV-204737r508029_ruleThe application server must protect log tools from unauthorized deletion.
☐SV-204738r508029_ruleThe application server must back up log records at least every seven days onto a different system or system component than the system or component being logged.
☐SV-204739r508029_ruleThe application server must use cryptographic mechanisms to protect the integrity of log information.
☐SV-204740r508029_ruleThe application server must prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.
☐SV-204741r508029_ruleThe application server must limit privileges to change the software resident within software libraries.
☐SV-204742r508029_ruleThe application server must be capable of reverting to the last known good configuration in the event of failed installations and upgrades.
☐SV-204743r508029_ruleThe application server must adhere to the principles of least functionality by providing only essential capabilities.
☐SV-204744r508029_ruleThe application server must prohibit or restrict the use of nonsecure ports, protocols, modules, and/or services as defined in the PPSM CAL and vulnerability assessments.
☐SV-204745r508029_ruleThe application server must use an enterprise user management system to uniquely identify and authenticate users (or processes acting on behalf of organizational users).
☐SV-204746r508029_ruleThe application server must use multifactor authentication for network access to privileged accounts.
☐SV-204747r508029_ruleThe application server must use multifactor authentication for local access to privileged accounts.
☐SV-204748r508029_ruleThe application server must authenticate users individually prior to using a group authenticator.
☐SV-204749r508029_ruleThe application server must provide security extensions to extend the SOAP protocol and provide secure authentication when accessing sensitive data.
☐SV-204750r508029_ruleThe application server must disable identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.
☐SV-204751r508029_ruleThe application server must store only encrypted representations of passwords.
☐SV-204752r508029_ruleThe application server must transmit only encrypted representations of passwords.
☐SV-204753r508029_ruleThe application server must utilize encryption when using LDAP for authentication.
☐SV-204754r508029_ruleThe application server must perform RFC 5280-compliant certification path validation.
☐SV-204755r508029_ruleOnly authenticated system administrators or the designated PKI Sponsor for the application server must have access to the web servers private key.
☐SV-204756r508029_ruleThe application server must map the authenticated identity to the individual user or group account for PKI-based authentication.
☐SV-204757r508029_ruleThe application server must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
☐SV-204758r508029_ruleThe application server must utilize FIPS 140-2 approved encryption modules when authenticating users and processes.
☐SV-204759r508029_ruleThe application server must provide a log reduction capability that supports on-demand reporting requirements.
☐SV-204760r508029_ruleThe application server must identify prohibited mobile code.
☐SV-204761r508029_ruleThe application server must separate hosted application functionality from application server management functionality.
☐SV-204762r508029_ruleThe application server must be configured to mutually authenticate connecting proxies, application servers or gateways.
☐SV-204763r508029_ruleThe application server must invalidate session identifiers upon user logout or other session termination.
☐SV-204764r508029_ruleThe application server must generate a unique session identifier for each session.
☐SV-204765r508029_ruleThe application server must recognize only system-generated session identifiers.
☐SV-204766r508029_ruleThe application server must generate a unique session identifier using a FIPS 140-2 approved random number generator.
☐SV-204767r508029_ruleThe application server must be configured to perform complete application deployments.
☐SV-204768r508029_ruleThe application server must provide a clustering capability.
☐SV-204769r508029_ruleThe application server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
☐SV-204770r508029_ruleThe application server must protect the confidentiality and integrity of all information at rest.
☐SV-204771r508029_ruleThe application server must employ cryptographic mechanisms to ensure confidentiality and integrity of all information at rest when stored off-line.
☐SV-204772r508029_ruleThe application server must check the validity of all data inputs to the management interface, except those specifically identified by the organization.
☐SV-204773r508029_ruleThe application server must identify potentially security-relevant error conditions.
☐SV-204774r508029_ruleThe application server must only generate error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs and administrative messages.
☐SV-204775r508029_ruleThe application server must restrict error messages only to authorized users.
☐SV-204776r508029_ruleThe application server must use cryptographic mechanisms to protect the integrity of log tools.
☐SV-204777r508029_ruleThe application server must automatically terminate a user session after organization-defined conditions or trigger events requiring a session disconnect.
☐SV-204778r508029_ruleThe application server management interface must provide a logout capability for user-initiated communication session.
☐SV-204779r508029_ruleThe application server management interface must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.
☐SV-204780r508029_ruleThe application server must associate organization-defined types of security attributes having organization-defined security attribute values with information in process.
☐SV-204781r508029_ruleThe application server must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.
☐SV-204782r508029_ruleThe application server must control remote access methods.
☐SV-204783r508029_ruleThe application server must provide the capability to immediately disconnect or disable remote access to the management interface.
☐SV-204784r508029_ruleThe application server must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
☐SV-204785r508029_ruleThe application server must provide access logging that ensures users who are granted a privileged role (or roles) have their privileged activity logged.
☐SV-204787r508029_ruleThe application server must provide centralized management and configuration of the content to be captured in log records generated by all application components.
☐SV-204788r508029_ruleThe application server must allocate log record storage capacity in accordance with organization-defined log record storage requirements.
☐SV-204789r508029_ruleThe application server must off-load log records onto a different system or media from the system being logged.
☐SV-204790r508029_ruleThe application server must provide an immediate warning to the SA and ISSO, at a minimum, when allocated log record storage volume reaches 75% of maximum log record storage capacity.
☐SV-204791r508029_ruleThe application server must provide an immediate real-time alert to authorized users of all log failure events requiring real-time alerts.
☐SV-204792r508029_ruleThe application server must compare internal application server clocks at least every 24 hours with an authoritative time source.
☐SV-204793r508029_ruleThe application server must synchronize internal application server clocks to an authoritative time source when the time difference is greater than the organization-defined time period.
☐SV-204794r508029_ruleThe application server must record time stamps for log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
☐SV-204795r508029_ruleThe application server must record time stamps for log records that meet a granularity of one second for a minimum degree of precision.
☐SV-204796r508029_ruleThe application server must enforce access restrictions associated with changes to application server configuration.
☐SV-204797r508029_ruleThe application server must log the enforcement actions used to restrict access associated with changes to the application server.
☐SV-204798r508029_ruleThe application server must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.
☐SV-204799r508029_ruleThe application server must require devices to re-authenticate when organization-defined circumstances or situations require re-authentication.
☐SV-204800r508029_ruleThe application server must accept Personal Identity Verification (PIV) credentials to access the management interface.
☐SV-204801r508029_ruleThe application server must electronically verify Personal Identity Verification (PIV) credentials for access to the management interface.
☐SV-204804r508029_ruleThe application server must prohibit the use of cached authenticators after an organization-defined time period.
☐SV-204805r508029_ruleThe application server, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.
☐SV-204806r508029_ruleThe application server must accept Personal Identity Verification (PIV) credentials from other federal agencies to access the management interface.
☐SV-204807r508029_ruleThe application server must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies to access the management interface.
☐SV-204808r508029_ruleThe application server must accept FICAM-approved third-party credentials.
☐SV-204809r508029_ruleThe application server must conform to FICAM-issued profiles.
☐SV-204811r508029_ruleThe application server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
☐SV-204812r508029_ruleThe application server must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components.
☐SV-204813r508029_ruleThe application must implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined information system components.
☐SV-204814r508029_ruleThe application server, when a MAC I system, must be in a high-availability (HA) cluster.
☐SV-204815r508029_ruleThe application server must protect against or limit the effects of all types of Denial of Service (DoS) attacks by employing organization-defined security safeguards.
☐SV-204816r508029_ruleThe application server must protect the confidentiality and integrity of transmitted information through the use of an approved TLS version.
☐SV-204817r508029_ruleThe application server must remove all export ciphers to protect the confidentiality and integrity of transmitted information.
☐SV-204818r508029_ruleThe application server must employ approved cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission.
☐SV-204819r508029_ruleThe application server must maintain the confidentiality and integrity of information during preparation for transmission.
☐SV-204820r508029_ruleThe application server must maintain the confidentiality and integrity of information during reception.
☐SV-204821r508029_ruleThe application server must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.
☐SV-204822r508029_ruleThe application server must remove organization-defined software components after updated versions have been installed.
☐SV-204823r508029_ruleThe application server must install security-relevant software updates within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
☐SV-204824r508029_ruleThe application server must generate log records when successful/unsuccessful attempts to modify privileges occur.
☐SV-204825r508029_ruleThe application server must generate log records when successful/unsuccessful attempts to delete privileges occur.
☐SV-204826r508029_ruleThe application server must generate log records when successful/unsuccessful logon attempts occur.
☐SV-204827r508029_ruleThe application server must generate log records for privileged activities.
☐SV-204828r508029_ruleThe application must generate log records showing starting and ending times for user access to the application server management interface.
☐SV-204829r508029_ruleThe application server must generate log records when concurrent logons from different workstations occur to the application server management interface.
☐SV-204830r508029_ruleThe application server must generate log records for all account creations, modifications, disabling, and termination events.
☐SV-204831r508029_ruleApplication servers must use NIST-approved or NSA-approved key management technology and processes.
☐SV-204832r508029_ruleThe application server must use DoD- or CNSS-approved PKI Class 3 or Class 4 certificates.
☐SV-204833r508029_ruleThe application server must, at a minimum, transfer the logs of interconnected systems in real time, and transfer the logs of standalone systems weekly.
☐SV-204834r508029_ruleThe application 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.
☐SV-220326r508029_ruleThe application server must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.