Skip to content

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

An XCCDF Rule

Description

<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. This requirement applies only to ALGs that provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC). The CA API Gateway meets NIST FIPS-validated cryptography for digital signatures by using the built-in "Sign XML Element" and "Sign Element" Assertions within Registered Services policies, along with registered keypairs configured in accordance with organizational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID
SV-86099r1_rule
Severity
Medium
References
Updated



Remediation - Manual Procedure

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