The target of evaluation (TOE) is the Global Security ToolKit (GSKit) Version 8.0.14.21. GSKit is a set of tools and C/C++ programming interfaces that can be integrated in software applications to add secure channels to consuming application using the SSLv3.0, TLSv1.0, TLSv1.1, and TLSv1.2 protocols. It provides the cryptographic functions, the protocol implementation, and key generation and management functionality for this purpose. The TOE is a software only component; the operating system and hardware platform are part of the TOE environment. Consumers of the TOE are software products that need to establish SSLv3.0,TLSv1.0, TLSv1.1, or TLSv1.2 secure channels and developers of such products.
\r\nThe functionality provided comprises:
\r\nSSL and TLS functionality accessible via an API (called SSL API) for SSLv3.0 and TLSv1.0, TLSv1.1, and TLSv1.2.
\r\nKey and certificate generation and management functionality via an API (called Key Management API) and a command line interface (CLI).
\r\nFurthermore, GSKit encapsulates the IBM Crypto for C (ICC) cryptographic software module. ICC Version 8.0 has been validated under the Federal Information Processing Standard (FIPS) 140-2 [FIPS140-2] for an overall Security level 1 [FIPS140-2], with certificate number 1433. The module provides a variety of FIPS 140-2 validated cryptographic algorithms, as well as some algorithms that are not standardized by the cryptographic algorithm validation program.
","evaluation_configuration":"AIX 5.3,6.1,7; Solaris 9,10,11; Windows NT,XP,2003,2008,Vista,7;RHEL 5,6;SLES 10,11
\r\n(for specific versions and patch levels see Section 1.3.4.4 in the Security Target)
","security_evaluation_summary":"The evaluation was conducted by atsec information security corporation within the Common Criteria Evaluation and Validation Scheme (CCEVS) against the Common Criteria for Information Technology Security Evaluation. Part 1-3. July 2009. Version 3.1 Revision 3 for all assurance classes, applying the respective versions of the Common Methodology for Information Technology Security Evaluation. The evaluation demonstrated that the target of evaluation (TOE), IBM Global Security Kit (GSKit) Version 8.0.14 with IBM Crypto for C (ICC) 8.0.0.0, conforms to the functional and assurance claims in “IBM Global Security Kit Version 8.0.14 Security Target, Version 3.4” as of December 6, 2011, when operated as specified in “Global Security Kit Common Criteria Mode Operating Guidance, Version 8.0” as of January 11, 2012. The evaluation assurance level is EAL4, Part 3 conformant, Part 2 extended.
","environmental_strengths":"The purpose of GSKit, is to provide a secure channel between itself and a remote IT product. The TOE is intended to be incorporated into a product (software application), which is part of the TOE environment. The TOE is a software library and as such does not offer self-protection; corresponding assumptions on the IT and operational environment are defined in the Security Target and reflected in the guidance provided to consumers. The TOE provides a secure trusted channel to protect information transmitted over SSL and TLS against loss of confidentiality and integrity, and protection of cryptographic key material permanently stored in files in the underlying operating system.
\r\nGSKit is implemented by IBM for numerous operational platforms. This evaluation covers GSKit Version 8.0.14.21 on the platforms and operating systems specified in the Security Target.
\r\nThe following security functions are implemented by GSKit Version 8.0.14.21 and have been assessed as part of this evaluation:
\r\nSecure Channel
\r\nThe TOE allows consuming applications to implement TLS functionality. (The SSL protocol versions supported by GSKit are not available in the evaluated configuration). GSKit supports both TLS client and server functionality. The TLS functionality is offered via an API (called SSL API) for TLSv1, 1.1, and 1.2 and with certain TLS extensions from RFC6066.
\r\nThe TOE supports a wide variety of cipher suites including optional Suite B Conformance. The TOE enforces server authentication, and optionally can enforce client authentication; including certificate validation with optional revocation checking via CRLs and/or OCSP.
\r\nThe TOE can query OCSP responders in the operational environment using OCSP as defined in RFC2560 and RFC6277, or using the lightweight OCSP profile defined in RFC5019. The TOE can also retrieve and validate X.509 version 1 and 2 CRLs from the operational environment using LDAP, flat files or HTTP.
\r\nCryptographic Operations
\r\nThe TOE offers generation of symmetric keys, generation of asymmetric key pairs, symmetric encryption/decryption, asymmetric encryption/decryption, generation/verification of digital signatures, data authentication, secure message digest algorithms, and random number generation. The majority of the implemented cryptographic algorithms are FIPS-approved, and the majority of implementations have been FIPS 140-2 validated. Detailed information is provided in the Security Target.
\r\nSelf-tests and failure handling
\r\nGSKit offers self-tests for the ICC component: some of ICC’s cryptographic functions and the integrity of ICC can be tested. The self-tests have been analyzed as part of the FIPS 140-2 level 1 validation. GSKit provides the preservation of a secure state during normal operation and in case of SSL/TLS communication errors.
\r\nKey Management
\r\nThe TOE implements both a key management API and command line interface (CLI) to generate keys and certificate requests, and manage (import, export, define the trust status, etc.) keys and certificates. Key data (i.e. keys, certificates, and related information) is stored in a so-called keystore, a file stored in the operational environment. The TOE ensures by cryptographic means that the integrity and, where appropriate, the confidentiality of the data stored in the keystore is protected. Alternatively, PKCS#11 devices or MSCAPI/MSCNG cryptographic service providers can be used for key and certificate storage and for performing cryptographic primitives.
\r\nThe TOE is capable of certificate generation, but not of certificate management (including the issuance of CRLs, management of revocation status, etc.) for PKIs in any larger scale. The evaluated configuration assumes that the operational environment will manage (and provide, where appropriate) certificates for the operation of GSKit within a proper and trustworthy certificate management infrastructure.
","features":[]}