| Checked | Name | Title |
|---|
| ☐ | SV-204708r960735_rule | The application server must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types. |
| ☐ | SV-204709r960759_rule | The application server must use encryption strength in accordance with the categorization of the management data during remote access management sessions. |
| ☐ | SV-204710r960762_rule | The application server must implement cryptography mechanisms to protect the integrity of the remote access session. |
| ☐ | SV-204711r960765_rule | The application server must ensure remote sessions for accessing security functions and security-relevant information are logged. |
| ☐ | SV-204712r1137578_rule | The application server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-204713r960843_rule | The application server management interface must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
| ☐ | SV-204714r960846_rule | The 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-204715r960864_rule | The 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-204716r960873_rule | For 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-204717r960879_rule | The application server must generate log records for access and authentication events. |
| ☐ | SV-204718r960882_rule | The 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-204719r960885_rule | The application server must generate log records when successful/unsuccessful attempts to access subject privileges occur. |
| ☐ | SV-204720r960888_rule | The application server must initiate session logging upon startup. |
| ☐ | SV-204721r960891_rule | The application server must produce log records containing information to establish what type of events occurred. |
| ☐ | SV-204722r960894_rule | The application server must produce log records containing sufficient information to establish when (date and time) the events occurred. |
| ☐ | SV-204723r960897_rule | The application server must produce log records containing sufficient information to establish where the events occurred. |
| ☐ | SV-204724r960900_rule | The application server must produce log records containing sufficient information to establish the sources of the events. |
| ☐ | SV-204725r960903_rule | The application server must produce log records that contain sufficient information to establish the outcome of events. |
| ☐ | SV-204726r960906_rule | The application server must generate log records containing information that establishes the identity of any individual or process associated with the event. |
| ☐ | SV-204727r960909_rule | The application server must generate log records containing the full-text recording of privileged commands or the individual identities of group account users. |
| ☐ | SV-204728r960912_rule | The application server must alert the SA and ISSO, at a minimum, in the event of a log processing failure. |
| ☐ | SV-204731r960927_rule | The application server must use internal system clocks to generate time stamps for log records. |
| ☐ | SV-204732r960930_rule | The application server must protect log information from any type of unauthorized read access. |
| ☐ | SV-204733r960933_rule | The application server must protect log information from unauthorized modification. |
| ☐ | SV-204734r960936_rule | The application server must protect log information from unauthorized deletion. |
| ☐ | SV-204735r960939_rule | The application server must protect log tools from unauthorized access. |
| ☐ | SV-204736r960942_rule | The application server must protect log tools from unauthorized modification. |
| ☐ | SV-204737r960945_rule | The application server must protect log tools from unauthorized deletion. |
| ☐ | SV-204738r960948_rule | The 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-204739r960951_rule | The application server must use cryptographic mechanisms to protect the integrity of log information. |
| ☐ | SV-204740r981678_rule | The 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 recognized and approved by the organization. |
| ☐ | SV-204741r960960_rule | The application server must limit privileges to change the software resident within software libraries. |
| ☐ | SV-204742r960960_rule | The application server must be capable of reverting to the last known good configuration in the event of failed installations and upgrades. |
| ☐ | SV-204743r960963_rule | The application server must adhere to the principles of least functionality by providing only essential capabilities. |
| ☐ | SV-204744r1043177_rule | The 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-204745r1051118_rule | The application server must use an approved DOD enterprise identity, credential, and access management (ICAM) solution to uniquely identify and authenticate users (or processes acting on behalf of organizational users). |
| ☐ | SV-204746r960972_rule | The application server must use multifactor authentication for network access to privileged accounts. |
| ☐ | SV-204747r981679_rule | The application server must use multifactor authentication for local access to privileged accounts. |
| ☐ | SV-204748r981680_rule | The application server must authenticate users individually prior to using a group authenticator. |
| ☐ | SV-204749r960993_rule | The application server must provide security extensions to extend the SOAP protocol and provide secure authentication when accessing sensitive data. |
| ☐ | SV-204750r981681_rule | The application server must disable identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. |
| ☐ | SV-204751r981682_rule | The application server must for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash. |
| ☐ | SV-204752r1207648_rule | The application server must transmit only encrypted representations of passwords. |
| ☐ | SV-204753r1207649_rule | The application server must utilize encryption when using LDAP for authentication. |
| ☐ | SV-204754r961038_rule | The application server must perform RFC 5280-compliant certification path validation. |
| ☐ | SV-204755r961041_rule | Only authenticated system administrators or the designated PKI Sponsor for the application server must have access to the web servers private key. |
| ☐ | SV-204756r961044_rule | The application server must map the authenticated identity to the individual user or group account for PKI-based authentication. |
| ☐ | SV-204757r961047_rule | The application server must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-204758r961050_rule | The application server must utilize FIPS 140-2 approved encryption modules when authenticating users and processes. |
| ☐ | SV-204759r961056_rule | The application server must provide a log reduction capability that supports on-demand reporting requirements. |
| ☐ | SV-204760r961083_rule | The application server must identify prohibited mobile code. |
| ☐ | SV-204761r1137579_rule | The application server must separate hosted application functionality from application server management functionality. |
| ☐ | SV-204762r1043178_rule | The application server must be configured to mutually authenticate connecting proxies, application servers or gateways. |
| ☐ | SV-204763r1043179_rule | The application server must invalidate session identifiers upon user logout or other session termination. |
| ☐ | SV-204764r1043180_rule | The application server must generate a unique session identifier for each session. |
| ☐ | SV-204765r1043180_rule | The application server must recognize only system-generated session identifiers. |
| ☐ | SV-204766r1043181_rule | The application server must generate a unique session identifier using a FIPS 140-2 approved random number generator. |
| ☐ | SV-204767r961122_rule | The application server must be configured to perform complete application deployments. |
| ☐ | SV-204768r961122_rule | The application server must provide a clustering capability. |
| ☐ | SV-204769r961122_rule | The application server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-204770r961128_rule | The application server must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-204771r961128_rule | The application server must employ cryptographic mechanisms to ensure confidentiality and integrity of all information at rest when stored off-line. |
| ☐ | SV-204772r961158_rule | The application server must check the validity of all data inputs to the management interface, except those specifically identified by the organization. |
| ☐ | SV-204773r961167_rule | The application server must identify potentially security-relevant error conditions. |
| ☐ | SV-204774r961167_rule | The 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-204775r961170_rule | The application server must restrict error messages only to authorized users. |
| ☐ | SV-204776r961206_rule | The application server must use cryptographic mechanisms to protect the integrity of log tools. |
| ☐ | SV-204777r1043182_rule | The application server must automatically terminate a user session after organization-defined conditions or trigger events requiring a session disconnect. |
| ☐ | SV-204778r961224_rule | The application server management interface must provide a logout capability for user-initiated communication session. |
| ☐ | SV-204779r961227_rule | The application server management interface must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions. |
| ☐ | SV-204780r961272_rule | The application server must associate organization-defined types of security attributes having organization-defined security attribute values with information in process. |
| ☐ | SV-204781r961275_rule | The application server must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission. |
| ☐ | SV-204782r961278_rule | The application server must control remote access methods. |
| ☐ | SV-204783r961281_rule | The application server must provide the capability to immediately disconnect or disable remote access to the management interface. |
| ☐ | SV-204784r961353_rule | The application server must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-204785r961362_rule | The application server must provide access logging that ensures users who are granted a privileged role (or roles) have their privileged activity logged. |
| ☐ | SV-204788r961392_rule | The application server must allocate log record storage capacity in accordance with organization-defined log record storage requirements. |
| ☐ | SV-204789r961395_rule | The application server must off-load log records onto a different system or media from the system being logged. |
| ☐ | SV-204790r961398_rule | The 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-204791r961401_rule | The application server must provide an immediate real-time alert to authorized users of all log failure events requiring real-time alerts. |
| ☐ | SV-204792r981685_rule | The application server must compare internal application server clocks at least every 24 hours with an authoritative time source. |
| ☐ | SV-204793r981686_rule | The 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-204794r961443_rule | The application server must record time stamps for log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
| ☐ | SV-204795r961446_rule | The application server must record time stamps for log records that meet a granularity of one second for a minimum degree of precision. |
| ☐ | SV-204796r961461_rule | The application server must enforce access restrictions associated with changes to application server configuration. |
| ☐ | SV-204797r981687_rule | The application server must log the enforcement actions used to restrict access associated with changes to the application server. |
| ☐ | SV-204798r1050785_rule | The application server must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-204800r961494_rule | The application server must accept Personal Identity Verification (PIV) credentials to access the management interface. |
| ☐ | SV-204801r961497_rule | The application server must electronically verify Personal Identity Verification (PIV) credentials for access to the management interface. |
| ☐ | SV-204804r961521_rule | The application server must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-204805r981694_rule | The 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-204806r961527_rule | The application server must accept Personal Identity Verification (PIV) credentials from other federal agencies to access the management interface. |
| ☐ | SV-204807r961530_rule | The application server must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies to access the management interface. |
| ☐ | SV-204808r981695_rule | The application server must accept Federal Identity, Credential, and Access Management (FICAM)-approved third-party credentials. |
| ☐ | SV-204809r981696_rule | The application server must conform to Federal Identity, Credential, and Access Management (FICAM)-issued profiles. |
| ☐ | SV-204811r961596_rule | The application server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions. |
| ☐ | SV-204812r1067567_rule | The application server must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-204813r1067568_rule | The application must implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-204814r961620_rule | The application server, when a MAC I system, must be in a high-availability (HA) cluster. |
| ☐ | SV-204815r961620_rule | The 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-204816r961632_rule | The application server must protect the confidentiality and integrity of transmitted information through the use of an approved TLS version. |
| ☐ | SV-204817r961632_rule | The application server must remove all export ciphers to protect the confidentiality and integrity of transmitted information. |
| ☐ | SV-204818r1137581_rule | The application server must employ approved cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission. |
| ☐ | SV-204819r961638_rule | The application server must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-204820r961641_rule | The application server must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-204821r961656_rule | The application server must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. |
| ☐ | SV-204822r961677_rule | The application server must remove organization-defined software components after updated versions have been installed. |
| ☐ | SV-204823r1137612_rule | The application server must install security-relevant software updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs). |
| ☐ | SV-204824r961800_rule | The application server must generate log records when successful/unsuccessful attempts to modify privileges occur. |
| ☐ | SV-204825r961812_rule | The application server must generate log records when successful/unsuccessful attempts to delete privileges occur. |
| ☐ | SV-204826r961824_rule | The application server must generate log records when successful/unsuccessful logon attempts occur. |
| ☐ | SV-204827r961827_rule | The application server must generate log records for privileged activities. |
| ☐ | SV-204828r961830_rule | The application must generate log records showing starting and ending times for user access to the application server management interface. |
| ☐ | SV-204829r961833_rule | The application server must generate log records when concurrent logons from different workstations occur to the application server management interface. |
| ☐ | SV-204830r961842_rule | The application server must generate log records for all account creations, modifications, disabling, and termination events. |
| ☐ | SV-204831r1137582_rule | Application servers must use NIST-approved or NSA-approved key management technology and processes. |
| ☐ | SV-204832r1137585_rule | The application server must use DOD- or CNSS-approved PKI Class 3 or Class 4 certificates. |
| ☐ | SV-204833r961860_rule | The application server must, at a minimum, transfer the logs of interconnected systems in real time, and transfer the logs of standalone systems weekly. |
| ☐ | SV-204834r961863_rule | The 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-240925r1117186_rule | The application server must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
| ☐ | SV-263549r981699_rule | The application server must disable accounts when the accounts are no longer associated to a user. |
| ☐ | SV-263550r981702_rule | The application server must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information. |
| ☐ | SV-263551r981705_rule | The application 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. |
| ☐ | SV-263552r981708_rule | The application 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. |
| ☐ | SV-263553r981711_rule | The application server must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths. |
| ☐ | SV-263554r981714_rule | The application server must include only approved trust anchors in trust stores or certificate stores managed by the organization. |
| ☐ | SV-263555r981717_rule | The application server must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. |
| ☐ | SV-263556r981720_rule | The application server must synchronize system clocks within and between systems or system components. |
| ☐ | SV-278959r1137588_rule | The application server must dynamically associate security attributes with organization-defined subjects in accordance with organization-defined security policies as information is created and combined. |
| ☐ | SV-278960r1137591_rule | The application server must uniquely identify and authenticate source by organization, system, application, and/or individual for information transfer. |
| ☐ | SV-278961r1227257_rule | The application server must enforce attribute-based control access over defined subjects and objects based upon organization-defined attributes to assume access permissions. |
| ☐ | SV-278962r1227258_rule | The application server must attach data tags containing organization-defined authorized processing to organization-defined elements of personally identifiable information. |
| ☐ | SV-278963r1227259_rule | The application server must attach data tags containing organization-defined processing purposes to organization-defined elements of personally identifiable information. |
| ☐ | SV-278964r1227260_rule | The application server must employ automated mechanisms to integrate intrusion detection mechanisms into access control mechanisms. |
| ☐ | SV-278965r1137606_rule | The application server must dynamically associate security attributes with organization-defined objects in accordance with organization-defined security policies as information is created and combined. |
| ☐ | SV-278966r1137609_rule | The application server must enforce a role-based access control (RBAC) policy over defined subjects and objects. |
| ☐ | SV-278967r1137615_rule | The application server must be a version supported by the vendor. |
STIGQter: STIG Summary: