Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The CA API Gateway that stores secret or private keys must use FIPS-approved key management technology and processes in the production and control of private/secret cryptographic keys.
Description
Discussion Text
Private key data is used to prove 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, is required to be generated and protected in at least a FIPS 140-2 Level 1 validated cryptographic module.
By default, the CA API Gateway uses the SunJSSE PKCS#12 for key storage, which is not approved at FIPS 140-2. The Gateway must be configured to use a SafeNet Luna Hardware Security Module (HSM) that is approved at FIPS-140-2 Level 3.
Private key data associated with software certificates, including those issued to an ALG, is required to be generated and protected in at least a FIPS 140-2 Level 1 validated cryptographic module.
By default, the CA API Gateway uses the SunJSSE PKCS#12 for key storage, which is not approved at FIPS 140-2. The Gateway must be configured to use a SafeNet Luna Hardware Security Module (HSM) that is approved at FIPS-140-2 Level 3.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.