STIGQter: STIG Summary: CA API Gateway ALG Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 28 Apr 2017:

The CA API Gateway providing encryption intermediary services must implement NIST FIPS-validated cryptography for digital signatures.

DISA Rule

SV-86099r1_rule

Vulnerability Number

V-71475

Group Title

SRG-NET-000510-ALG-000040

Rule Version

CAGW-GW-000890

Severity

CAT II

CCI(s)

• CCI-002450 - The information system implements organization-defined cryptographic uses and type of cryptography required for each use in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

Weight

10

Fix Recommendation

Open the CA API Gateway - Policy Manager.

Double-click each of the Registered Services that requires NIST-FIPS-validated cryptography for digital signatures to be enabled.

Add the following Assertion(s) in accordance with organizational need: "Sign XML Element" and/or "Sign Element".

Verify that the Signature Digest Algorithm is set to SHA-256 or above to meet organizational requirements.

Verify/install an approved public-private keypair in Tasks >> Manage Private Keys.

Also, right-click on the aforementioned Assertions, whenever used, chose "Select Private Key", and verify the appropriate private key is assigned to be used for the signature.

If the "security.fips.enabled" Cluster-Wide Property is not enabled, select "Manage Cluster-Wide Properties" from the "Tasks" menu. Click "Add" and select "security.fips.enabled" from the "Key:" drop-down list.

Set the value to "True" and click "OK".

Check Contents

Open the CA API GW - Policy Manager.

Double-click each of the Registered Services that has the "Sign XML Element” or “Sign Element” Assertions, or require NIST-FIPS-validated cryptography for digital signatures be enabled. Verify that the Signature Digest Algorithm is SHA-256 or above to meet organizational requirements.

Verify that an approved public-private keypair exists in Tasks >> Manage Private Keys. Right-click on the aforementioned Assertions; whenever used, chose "Select Private Key" and verify the appropriate private key is assigned to be used for the signature. Additionally verify that the "security.fips.enabled" Cluster Wide Property is enabled.

If any of the above steps are not met, this is a finding.

Vulnerability Number

V-71475

Documentable

False

Rule Version

CAGW-GW-000890

Severity Override Guidance

Open the CA API GW - Policy Manager.

Double-click each of the Registered Services that has the "Sign XML Element” or “Sign Element” Assertions, or require NIST-FIPS-validated cryptography for digital signatures be enabled. Verify that the Signature Digest Algorithm is SHA-256 or above to meet organizational requirements.

Verify that an approved public-private keypair exists in Tasks >> Manage Private Keys. Right-click on the aforementioned Assertions; whenever used, chose "Select Private Key" and verify the appropriate private key is assigned to be used for the signature. Additionally verify that the "security.fips.enabled" Cluster Wide Property is enabled.

If any of the above steps are not met, this is a finding.

Check Content Reference

M

Target Key

3049

Comments