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

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.

DISA Rule

SV-224779r1013850_rule

Vulnerability Number

V-224779

Group Title

SRG-APP-000635

Rule Version

ISEC-06-002700

Severity

CAT II

CCI(s)

• CCI-002450 - Implement organization-defined types of cryptography for each specified cryptography use.

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 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.

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-224779

Documentable

False

Rule Version

ISEC-06-002700

Severity Override Guidance

Log in to the ISEC7 SPHERE Console.
Confirm that the browser session is secured using a DOD issued certificate.

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