Standard |
Title |
Comment |
SSL V3.0 |
The SSL Protocol Version 3.0 (Nov 1996) |
Status: IETF Internet Draft |
PKCS #11 |
PKCS #11 v2.11: Cryptographic Token Interface Standard (November 2001) |
This is an "RSA Security Inc. Public-Key Cryptography Standards (PKCS)" |
PKCS #12 |
PKCS 12 v1.0: Personal Information Exchange Syntax Standard (June 1999) |
This is an "RSA Security Inc. Public-Key Cryptography Standards (PKCS)" |
RFC 2246 |
The TLS Protocol Version 1.0 |
Status: Proposed standard |
PKCS #11A |
PKCS #11 v2.11 Amendment 1 (August 2002) |
This is an "RSA Security Inc. Public-Key Cryptography Standards (PKCS)" |
PKCS #12TC |
PKCS #12 v1.0 Technical Corrigendum (February 2000) |
This is an "RSA Security Inc. Public-Key Cryptography Standards (PKCS)" |
FIPS 140-2 |
SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES |
CA Directory r12 and later utilizes an embedded cryptographic module that has been validated as meeting the Federal Information Processing Standards (FIPS) 140-2 Security Requirements for Cryptographic Modules. This module (RSA BSAFE® Crypto-C ME) provides all of the cryptographic services in the CA Product. The validation certificate number for this module is #608. |
FIPS 186-2 |
DIGITAL SIGNATURE STANDARD (DSS) 2000 January 27 |
CA Directory r12 and later utilizes an embedded cryptographic module (RSA BSAFE® Crypto-C ME) that has been validated as meeting FIPS 140-2 Security Requirements for Cryptographic Modules.
The validation for FIPS140-2 includes certification of DSA (Cert. #143); RNG (Cert. #130); ECDSA (Cert. #11). These algorithms are required by FIPS 186 and hence supports the implementation of a DSS solution. |
Copyright © 2009 CA. All rights reserved. | Email CA about this topic |