Red Hat Certificate System 8.1 (RHCS 8.1) provides a security framework to guarantee the identity of users and ensure privacy of communications. RHCS 8.1 issues and manages X.509v3 certificates needed to handle strong authentication, single sign-on and secure communications. RHCS 8.1 handles all the major functions around the certificate lifecycle simplifying enterprise-wide deployment and adoption. Customizable registration allows RHCS 8.1 to adapt to virtually any enterprise security policy
\r\nRHCS 8.1 provides integrity controls to ensure data is not modified. RHCS 8.1,includes protections to protect against someone with physical access to the components and includes assurance requirements to ensure the CIMC is functioning securely.
\r\nRHCS 8.1 provides protection against malicious authorized users by requiring at least three distinct roles. At a minimum, one role will be responsible for account administration, key generation, and audit configuration; a second role will be responsible for issuing and revoking certificates; and a third role responsible for maintaining the audit logs. RHCS 8.1 provides two-party control of private key export and additional auditing of import and export of secret and private keys and requests for information. Cryptographic modules responsible for long-term private key protection or for signing certificates or certificate status information must be validated to FIPS 140-2 Level 3. Finally, there is increased public key protection and digital signatures are required on all messages.
","evaluation_configuration":null,"security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Red Hat Certificate System 8.1 TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 3. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 3. Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is EAL 4 augmented with ALC_FLR.2. The product, when delivered configured as identified in Implementing a Common Criteria Environment and Common Criteria Environment: A Walkthrough of the Preparation, Installation, and Configuration for a Certified PKI documents found on the Red Hat website at http://docs.redhat.com/docs/en-US/Red_Hat_Certificate_System_Common_Criteria_Certification/index.html, satisfies all of the security functional requirements stated in the Red Hat Certificate System 8.1 Security Target (Version 1.0). The project underwent Validation Oversight Review (VOR) panel reviews. The evaluation was completed in March 2012. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR-10359-2012, dated March 8, 2012) prepared by CCEVS.
","environmental_strengths":"The logical boundaries of RHCS 8.1 TOE are realized in the security functions that it implements. These security functions are realized at the network interfaces that service clients and via the administrator commands. Each of these security functions is summarized below.
\r\nIdentification & Authentication - RHCS 8.1 ensures that users are identified and authenticated before they can access any other security relevant services.
\r\nAccess Control - RHCS 8.1 provides the ability to define an access control list for each service it provides. These access control lists are used to ensure that users can only access services they have been authorized to use.
\r\nSecurity Management - RHCS 8.1 uses the access control functions to control the actions of administrative personnel. In order to accomplish this, predefined access control lists are assigned to the applicable services.
\r\nSecurity Audit - RHCS 8.1 has the capability to audit security relevant events. Audit records are generated when audit events occur, including the responsible user, date, time, and other details. Audit records are collected into audit buffers that are signed, to protect against possible tampering of the audit records, and then copied into non-volatile audit logs.
\r\nRemote Data Entry & Export - RHCS 8.1 protects data import and export operations using SSL sessions and secure channels in the case of TMS.
\r\nKey Management - RHCS 8.1 includes a number of key management functions. In particular, RHCS 8.1 protects security critical keys and other information by either encrypting it or storing it within a hardware cryptographic module. RHCS 8.1 also uses digital signatures when appropriate to ensure the integrity of key management related information.
\r\nCertificate Management - RHCS 8.1 includes a number of certificate management functions. In particular, RHCS 8.1 allows administrators to control, limit, or mandate values in certificates, certificate revocation lists (CRLs), and online certificate status protocol (OCSP) responses that are generated.
\r\nStrength of Functions - RHCS 8.1 is designed to make appropriate use of a FIPS 140-2 certified Hardware Security Module (HSM) for critical cryptographic operations
","features":[]}