\r\n
Red Hat Enterprise Linux is a general purpose, multi-user, multi-tasking Linux based operating system. It provides a platform for a variety of applications in the governmental and commercial environment. Red Hat Enterprise Linux is available on a broad range of computer systems, ranging from departmental servers to multi-processor enterprise servers and small server type computer systems.
\r\nThe TOE Security Functions (TSF) consist of functions of Red Hat Enterprise Linux that run in kernel mode plus some trusted processes. These are the functions that enforce the security policy as defined in this Security Target. Tools and commands executed in user mode that are used by an administrative user need also to be trusted to manage the system in a secure way. But as with other operating system evaluations they are not considered to be part of this TSF.
\r\nSystem administration tools include the standard Linux commands. A graphical user interface for system administration or any other operation is not included in the evaluated configuration.
","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 RHEL5 TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.3 and National and International Interpretations effective on 2005-12-15. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 2.3.
\r\nThe CCTL (atsec) determined that the evaluation assurance level (EAL) for the product is EAL 4, augmented with the CC ACL_FLR.3 Flaw Remediation assurance requirements. The product, when configured as specified in the Evaluated Configuration Guide satisfies all of the security functional requirements stated in the Red Hat Enterprise Linux Version 5 Security Target for CAPP, RBAC, and LSPP Compliance, Version 1.11 and is conformant to the CAPP, RBACPP, and LSPP. The evaluation was completed in May 2007. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"The functionality of Red Hat Enterprise Linux is consistent with the requirements set forth by the Protection Profiles it complies with, on the platforms specified in the Security Target.
\r\nIdentification and Authentication: The identification and authentication mechanism identifies and authenticates users and assigns the configured group definition. An administrator configurable audit subsystem is able to record system events and user actions. It stores the audit records on disk and appropriate access control configurations are in place to protect them from unauthorized access. The Discretionary Access Control Policy is enforced on processes running on behalf of users as subjects and file system objects as well as IPC objects. This mechanism allows only administrators and object owners to modify the access control attributes of named objects. Access Control Lists (ACLs) can be used for a more fine grained control for file system objects. The Mandatory Access Control Policy is enforced on processes running on behalf of users as subjects and all objects known to the system. This mechanism allows only administrators to modify the access control attributes. Access is determined based on labels maintained for subjects and objects according to the Bell-LaPadula model. Labeled networking as well as labeled printing is also provided. The Role-based Access Control Policy is enforced on processes running on behalf of users as subjects and file system objects as well as IPC objects. This mechanism allows only administrators and object owners to modify the access control attributes of named objects.The TOE ensures that residual data is made unavailable prior to allocation of resources to subjects and objects.
\r\nSecurity Audit: An administrator configurable audit subsystem is able to record system events and user actions. It stores the audit records on disk and appropriate access control configurations are in place to protect them from unauthorized access.
Discretionary Access Control: The Discretionary Access Control Policy is enforced on processes running on behalf of users as subjects and file system objects as well as IPC objects. This mechanism allows only administrators and object owners to modify the access control attributes of named objects. Access Control Lists (ACLs) can be used for a more fine grained control for file system objects.
Mandatory Access Control: The Mandatory Access Control Policy is enforced on processes running on behalf of users as subjects and all objects known to the system. This mechanism allows only administrators to modify the access control attributes. Access is determined based on labels maintained for subjects and objects according to the Bell-LaPadula model. Labeled networking as well as labeled printing is also provided.
Role-based Access Control: The Role-based Access Control Policy is enforced on processes running on behalf of users as subjects and file system objects as well as IPC objects. This mechanism allows only administrators and object owners to modify the access control attributes of named objects.
Object reuse: The TOE ensures that residual data is made unavailable prior to allocation of resources to subjects and objects.
Security Management: The security management mechanism provides a set of administrative management tools to create, delete and modify users, groups and their authentication data. In addition, management tools for the audit subsystem are provided.
Secure Communication: The TOE provides SSHv2 and SSLv3 communication to ensure confidentiality and integrity of data transmitted.
\r\nProtection of TOE Security Functions: The protection mechanisms ensure that the execution between domains of trusted components and untrusted processes is separated to protect against interference. The separation mechanism allows communication between processes through well-defined interfaces only.
","features":[]}