CA IDMS must implement NIST FIPS 140-2 validated cryptographic modules to protect data-in-transit.
An XCCDF Rule
Description
<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards. For detailed information, refer to NIST FIPS Publication 140-2, Security Requirements for Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-251656r961857_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Contact the appropriate system administrators to make the needed changes to allow the use of AT-TLS and the associated software.
See Broadcom Techdocs for further information:
- Configure Secure Sockets
See IBM's z/OS Communications Server bookshelf for information on:
- Configuring AT-TLS
See IBM's z/OS Cryptographic Services System bookshelf for information on