STIGQter STIGQter: STIG Summary: Symantec ProxySG ALG Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 24 Apr 2020:

Symantec ProxySG storing secret or private keys must use FIPS-approved key management technology and processes in the production and control of private/secret cryptographic keys.

DISA Rule

SV-104179r2_rule

Vulnerability Number

V-94225

Group Title

SRG-NET-000062-ALG-000092

Rule Version

SYMP-AG-000050

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

As long as the FIPS-compliant suite is configured for use and configured in compliance with the FIPS cert manual requirements, key management should be in compliance using the following instructions.

1. Log on to the Web Management Console.
2. Click Configuration >> SSL >> HSM.
3. Click the "HSM" and "HSM Keyring" tabs and configure these options per the guidance in the ProxySG Administration Guide, Chapter 9: Managing the SSL Proxy, Section G: Working with an HSM Appliance.
4. Click Configuration >> Proxy Settings >> SSL Proxy.
5. Select the HSM Keyring in the Issuer Keyring field and click "Apply".

Note: As long as the FIPS-compliant suite is being used and configured in compliance with the FIPS cert manual requirements, key management should be in compliance as part of this.

Check Contents

If the FIPS-compliant suite is configured for use, this is not a finding. If HSM is used, then verify that the ProxySG is using FIPS-approved key management.

1. Log on to the Web Management Console.
2. Click Configuration >> SSL >> HSM.
3. Click the "HSM" and "HSM Keyring" tabs and Verify that these options have been configured.
4. Verify with the ProxySG administrator that the HSM specified is FIPS 140-2 compliant.
5. Click Configuration >> Proxy Settings >> SSL Proxy.
6. Verify that the Issuer Keyring is set to the HSM Keyring from step 3.

If Symantec ProxySG storing secret or private keys does not use FIPS-approved key management technology and processes in the production and control of private/secret cryptographic keys, this is a finding.

Vulnerability Number

V-94225

Documentable

False

Rule Version

SYMP-AG-000050

Severity Override Guidance

If the FIPS-compliant suite is configured for use, this is not a finding. If HSM is used, then verify that the ProxySG is using FIPS-approved key management.

1. Log on to the Web Management Console.
2. Click Configuration >> SSL >> HSM.
3. Click the "HSM" and "HSM Keyring" tabs and Verify that these options have been configured.
4. Verify with the ProxySG administrator that the HSM specified is FIPS 140-2 compliant.
5. Click Configuration >> Proxy Settings >> SSL Proxy.
6. Verify that the Issuer Keyring is set to the HSM Keyring from step 3.

If Symantec ProxySG storing secret or private keys does not use FIPS-approved key management technology and processes in the production and control of private/secret cryptographic keys, this is a finding.

Check Content Reference

M

Target Key

3515

Comments