The TOE is a software IT management tool that provides an organization the ability to consistently manage servers on multiple end hosts, through the establishment of best-practices. The TOE is designed to simplify and expedite the administration of servers and the deployment and maintenance of software across a heterogeneous environment. The TOE implements the following features:
\r\nThere are two primary modes of operation for the Opsware System, stand-alone and multimaster. Multimaster mode allows the organization to be spread over several sites all acting in coordinated fashion. The differences between the installation modes relate solely to the requirements necessary for multiple Model Repository servers. However, in the evaluation configuration only stand-alone mode is allowed.
\r\nCommunication between hosts is secured via OpenSSL, a cryptography module that is FIPS-approved but has not been evaluated further during this evaluation.
","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 Opsware System 4.5 Patch 1 TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.1, August 1999, ISO/IEC 15408 and International Interpretations effective on 29 April 2004. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 1.0, August 1999. Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is EAL2 family of assurance requirements. The product, when configured as specified in the Opsware System 4.5 Installation Guide, satisfies all of the security functional requirements stated in the Opsware System 4.5 Security Target, Version 1.0. One Validator on behalf of the CCEVS Validation Body monitored the evaluation carried out by SAIC. The evaluation was completed in October 2005. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR-05-0133, dated December 12, 2005) prepared by CCEVS.
","environmental_strengths":"The TOE is a commercial product whose users require a low to moderate level of independently assured security. Opsware System 4.5 Patch 1 is targeted at a relatively benign environment with good physical access security and competent TOE administrators and users. Within such environments, it is assumed that attackers will have a low attack potential. Opsware System 4.5 Patch 1 supports the following four security functions:
\r\nUser Data Protection
\r\nThe TOE enforces a Management Access Control policy, which restricts access to the management functions of the TOE. This protection requires that users of the TOE be authenticated before any access to the management functions is granted. Once access is granted, user access to management functions is controlled by the assigned user privileges.
Identification and Authentication
\r\nThe TOE requires users to provide unique identification and authentication data before any administrative access to the system is granted. The TOE provides the ability to define levels of authority for users, providing administrative flexibility. Full administrators have the ability to define groups and their authority and they have complete control over the TOE. Security privileges are associated with Groups, and it is by assigning users to one or more groups that users get access to features within the TOE.
Security Management
\r\nThe TOE is managed through the Opsware Command Center, a web-based interface. Through this interface TOE management can be performed by providing the administrators the ability to manage user attributes and privileges, as well as assign roles for different levels of administrative access.
Protection of Security Functions
\r\nThe TOE provides protection of all data that is transferred internally between disparate TOE components. The TOE protection ensures that modifications to the transferred data between disparate TOE components can be detected, preventing unauthorized data from being transferred into the TOE. All components, except for the Agent, are installed on the same platform. The Agent must be installed on each server that is managed by the TOE. Therefore, the only disparate communication is between the Agent and the core components (e.g. Command Engine, Software Repository).