STIGQter: STIG Summary: ISEC7 Sphere Security Technical Implementation Guide Version: 3 Release: 1 Benchmark Date: 24 Oct 2024:

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.

DISA Rule

SV-224770r1013824_rule

Vulnerability Number

V-224770

Group Title

SRG-APP-000395

Rule Version

ISEC-06-001760

Severity

CAT II

CCI(s)

• CCI-001967 - Authenticate organization-defined devices and/or types of devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.

Weight

10

Fix Recommendation

Submit a CSR for a DOD-issued certificate with the private key.
Retrieve the approved certificate from the issuing Certificate Authority.
Set the friendly name on the certificate to https.

Windows-MY:
Open the Microsoft Management Console.
Add the Certificates Snap-In for the ISEC7 Service Account.
Navigate to the Personal Certificates Store.
Import the certificate with Private key.
Log in to the ISEC7 SPHERE Console.
Navigate to Administration >> Configuration >> Apache Tomcat Settings.
Set the Keystore Type to Windows-MY.
Restart the ISEC7 SPHERE Web service.

JavaKeystore:
Using a Keystore browser such as Portecle, open the ISEC7 SPHERE Suite keystore.
Enter the Keystore password when prompted.
Delete the self-signed certificate in the keystore.
Import the DOD-issued certificate with the private key.
Enter the key password when prompted.
Enter the certificate alias as "https" when prompted.
Save the keystore with the same keystore password.
Log in to the ISEC7 SPHERE Console.
Navigate to Administration >> Configuration >> Apache Tomcat Settings.
Verify the Keystore type is set to JavaKeystore PKCS12.
Restart the ISEC7 SPHERE Web service.

Check Contents

Log in to the ISEC7 SPHERE Console.
Confirm that the browser session is secured using a DOD issued certificate.
Internet Explorer:
Click the Padlock icon at the end of the url field.
Select "View Certificates".
Confirm that the Issued By is a valid DOD Certificate Authority.

Google Chrome:
Click the Padlock icon at the front of the url field.
Select "Certificate".
Confirm that the Issued By is a valid DOD Certificate Authority.

Alternately, log in to the ISEC7 SPHERE Console.
Navigate to Administration >> Configuration >> Apache Tomcat Settings.
Identify which type of Keystore is being used.

Windows MY:
Open the Microsoft Management Console.
Add the Certificates Snap-In for the ISEC7 Service Account.
Navigate to the Personal Certificates Store.
Verify the certificate is issued by a DOD Trusted Certificate Authority.

JavaKeystore PKCS12:
Using a Keystore browser such as Portecle, open the ISEC7 SPHERE keystore.
Enter the Keystore password when prompted.
Open the installed certificate and verify it was issued by a DOD Trusted Certificate Authority.

If certificates used by the server are not DOD-issued certificates, this is a finding.

Vulnerability Number

V-224770

Documentable

False

Rule Version

ISEC-06-001760

Severity Override Guidance

Log in to the ISEC7 SPHERE Console.
Confirm that the browser session is secured using a DOD issued certificate.
Internet Explorer:
Click the Padlock icon at the end of the url field.
Select "View Certificates".
Confirm that the Issued By is a valid DOD Certificate Authority.

Google Chrome:
Click the Padlock icon at the front of the url field.
Select "Certificate".
Confirm that the Issued By is a valid DOD Certificate Authority.

Alternately, log in to the ISEC7 SPHERE Console.
Navigate to Administration >> Configuration >> Apache Tomcat Settings.
Identify which type of Keystore is being used.

Windows MY:
Open the Microsoft Management Console.
Add the Certificates Snap-In for the ISEC7 Service Account.
Navigate to the Personal Certificates Store.
Verify the certificate is issued by a DOD Trusted Certificate Authority.

JavaKeystore PKCS12:
Using a Keystore browser such as Portecle, open the ISEC7 SPHERE keystore.
Enter the Keystore password when prompted.
Open the installed certificate and verify it was issued by a DOD Trusted Certificate Authority.

If certificates used by the server are not DOD-issued certificates, this is a finding.

Check Content Reference

M

Target Key

4200