| V-224767 | | ISEC7 SPHERE must disable or delete local account created during application installation and configuration. | The ISEC7 local account password complexity controls do not meet DOD requirements; therefore, admins have the capability to configure the account out ... |
| V-225096 | | The ISEC7 Sphere server must be maintained at a supported version. | Versions of ISEC7 Sphere server are maintained by ISEC7 for specific periods of time. Unsupported versions will not receive security updates for new v... |
| V-224760 | | The ISEC7 SPHERE must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types. | Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allow... |
| V-224761 | | The ISEC7 SPHERE must initiate a session lock after a 15-minute period of inactivity. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-224762 | | The ISEC7 SPHERE must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access. | Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that explo... |
| V-224763 | | The ISEC7 SPHERE must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the ISEC7 SPHERE. | Display of the DOD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is cons... |
| V-224764 | | The ISEC7 SPHERE server must be configured to have at least one user in the following Administrator roles: Security Administrator, Site Administrator, and Help Desk User. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the ... |
| V-224765 | | The ISEC7 SPHERE must alert the information system security officer (ISSO) and system administrator (SA) (at a minimum) in the event of an audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-224766 | | The ISEC7 SPHERE must back up audit records at least every seven days onto a different system or system component than the system or component being audited, provide centralized management and configuration of the content to be captured in audit records generated by all ISEC7 SPHERE components, and offload audit records onto a different system or media than the system being audited. | Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate... |
| V-224768 | | When using PKI-based authentication for user access, the ISEC7 SPHERE must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly tru... |
| V-224770 | | Before establishing a local, remote, and/or network connection with any endpoint device, the ISEC7 SPHERE must use a bidirectional authentication mechanism configured with a FIPS-validated Advanced Encryption Standard (AES) cipher block algorithm to authenticate with the device. | Without device-to-device authentication, communications with malicious devices may be established. Bidirectional authentication provides stronger safe... |
| V-224771 | | The ISEC7 SPHERE must allow the use of DOD PKI established certificate authorities for verification of the establishment of protected sessions. | Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD syst... |
| V-224772 | | The ISEC7 SPHERE must protect the confidentiality and integrity of transmitted information during preparation for transmission and during reception using cryptographic mechanisms. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepte... |
| V-224773 | | The ISEC7 SPHERE must be configured to leverage the enterprise directory service accounts and groups for ISEC7 SPHERE server admin identification and authentication. | A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently an... |
| V-224774 | | The ISEC7 SPHERE must configure the timeout for the console to be 15 minutes or less. | A session time-out lock is a temporary action taken when a user (MDM system administrator) stops work and moves away from the immediate physical vicin... |
| V-224775 | | The ISEC7 SPHERE, Tomcat installation, and ISEC7 Suite monitor must be configured to use the Windows Trust Store for the storage of digital certificates and keys. | A trust store provides requisite encryption and access control to protect digital certificates from unauthorized access.... |
| V-224776 | | If cipher suites using pre-shared keys are used for device authentication, the ISEC7 SPHERE must have a minimum security strength of 112 bits or higher, must only be used in networks where both the client and server are government systems, must prohibit client negotiation to TLS 1.1, TLS 1.0, SSL 2.0, or SSL 3.0 and must prohibit or restrict the use of protocols that transmit unencrypted authentication information or use flawed cryptographic algorithm for transmission. | Pre-shared keys are symmetric keys that are already in place prior to the initiation of a Transport Layer Security (TLS) session (e.g., as the result ... |
| V-224777 | | The ISEC7 SPHERE must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (nonlegacy use). | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
To protect the integrity of the auth... |
| V-224778 | | The ISEC7 SPHERE must use a FIPS-validated cryptographic module to provision digital signatures. | Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. FIPS 140... |
| V-224779 | | The ISEC7 SPHERE must use a FIPS 140-2-validated cryptographic module to implement encryption services for unclassified information requiring confidentiality, generate cryptographic hashes, and to configure web management tools with FIPS-validated Advanced Encryption Standard (AES) cipher block algorithm to protect the confidentiality of maintenance and diagnostic communications for nonlocal maintenance sessions. | FIPS 140-2 precludes the use of invalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvali... |
| V-224780 | | The Apache Tomcat Manager Web app password must be cryptographically hashed with a DOD-approved algorithm. | The Apache Tomcat Manager Web app password is stored in plain text in CATALINA_HOME/conf/tomcat-users.xml and should be encrypted so it is not visible... |
| V-224781 | | All Web applications included with Apache Tomcat that are not required must be removed. | Removal of unneeded or nonsecure functions, ports, protocols, and services mitigate the risk of unauthorized connection of devices, unauthorized trans... |
| V-224782 | | LockOutRealm must not be removed from Apache Tomcat. | LockOutRealm prevents brute force attacks against user passwords. Removal of unneeded or nonsecure functions, ports, protocols, and services mitigate ... |
| V-224783 | | The LockOutRealm must be configured with a login failure count of 3. | LockOutRealm prevents brute force attacks against user passwords. Removal of unneeded or nonsecure functions, ports, protocols, and services mitigate ... |
| V-224784 | | The LockOutRealm must be configured with a login lockout time of 15 minutes. | LockOutRealm prevents brute force attacks against user passwords. Removal of unneeded or nonsecure functions, ports, protocols, and services mitigate ... |
| V-224785 | | The Manager Web app password must be configured as follows:
-15 or more characters.
-at least one lower case letter.
-at least one upper case letter.
-at least one number.
-at least one special character. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-224786 | | The ISEC7 SPHERE must configure Enable HTTPS to use HTTP over SSL in Apache Tomcat. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepte... |
| V-224788 | | Stack tracing must be disabled in Apache Tomcat. | The default error page shows a full stack trace, which is a disclosure of sensitive information. Removal of unneeded or nonsecure functions, ports, pr... |
| V-224789 | | The Apache Tomcat shutdown port must be disabled. | Tomcat uses a port (defaults to 8005) as a shutdown port. Someone could Telnet to the machine using this port and send the default command SHUTDOWN. T... |
| V-224790 | | The ISEC7 SPHERE must remove any unnecessary users or groups that have permissions to the server.xml file in Apache Tomcat. | Tomcat uses a port (defaults to 8005) as a shutdown port. Someone could Telnet to the machine using this port and send the default command SHUTDOWN. T... |
| V-224791 | | A manager role must be assigned to the Apache Tomcat Web apps (Manager, Host-Manager). | If a manager role is not assigned to the Apache Tomcat web apps, the system administrator will not be able to manage and configure the web apps and se... |
| V-224792 | | SSL must be enabled on Apache Tomcat. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepte... |
| V-224793 | | Tomcat SSL must be restricted except for ISEC7 SPHERE tasks. | Restricting the use of SSL helps ensure only authorized users and processes have access to Tomcat Web apps and reduces the attack surface of the ISEC7... |
| V-224769 | | The ISEC7 SPHERE must accept Personal Identity Verification (PIV) credentials. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
DOD has mandated the use of the CAC to support id... |
