OpenControls Logo

STIG Viewer

STIGViewer Support

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.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94225SYMP-AG-000050SV-104179r2_ruleCCI-000068medium
Description
Private key data is used to prove that the entity presenting a public key certificate is the certificate's rightful owner. Compromise of private key data allows an adversary to impersonate the key holder. Private key data associated with software certificates, including those issued to an ALG, must be generated and protected in at least a FIPS 140-2 Level 1 validated cryptographic module. For Proxy SG, 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. Symantec HSM may be used; however, it may require an additional license.
STIGDate
Symantec ProxySG ALG Security Technical Implementation Guide2020-03-27

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-14.2Protection of Confidentiality / Integrity Using Encryption
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (33) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
CM-6Configuration Settings
1.00
CM-6(1)Automated Management, Application, and Verification
1.00
CM-7Least Functionality
1.00
CM-7(1)Periodic Review
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-3Device Identification and Authentication
1.00

+23 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.13
1.00
CCI1 mapping
CCI-000068
1.00

Details

Check Text (C-104179r2_chk)

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.

Fix Text (F-100341r2_fix)

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.