{"product_id":2006,"v_id":2006,"product_name":"BMC Software PATROL®, Version 3.4.11 ","certification_status":"Not Certified","certification_date":"2002-09-30T00:09:00Z","tech_type":"Network Management","vendor_id":{"name":"BMC Software, Inc.","website":"http://www.bmc.com"},"vendor_poc":"Blakeley Bleidt","vendor_phone":"713.918.1221","vendor_email":"blakelely_bleidt@bmc.com","assigned_lab":{"cctl_name":"DXC.technology"},"product_description":"<p>BMC Software PATROL&reg; Version 3.4.11 is a systems application and event management tool. It provides an environment by which the status of every vital resource in the distributed environment being managed can be monitored. The Target of Evaluation (TOE) is PATROL&Ograve; version 3.4.11, as a suite of products consisting of:</p>\r\n<ul>\r\n    <li>PATROL<strong>&reg;</strong> Console, </li>\r\n    <li>PATROL<strong>&reg;</strong> Agents, </li>\r\n    <li>PATROL<strong>&reg;</strong> Event Manager (PEM), and </li>\r\n    <li>PATROL<strong>&reg;</strong> Knowledge Modules (KMs)<br />\r\n    (only PATROL<strong>&reg;</strong> KM for UNIX V8.3 and PATROL<strong>&reg;</strong> KM for NT V.3.5 are included in the TOE) </li>\r\n</ul>\r\n<p>There were two evaluated TOE configurations, one a SUN platform, the other a PC platform. Specifically these consisted of a Sun Ultra 5 running Solaris 2.7, and a Dell GX1 running Windows NT 4.0 SP6a. Each platform had the corresponding TOE binaries installed and configured, per Installation, Generation and Startup (IGS), by a BMC engineer.</p>","evaluation_configuration":null,"security_evaluation_summary":"<p>The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The evaluation demonstrated that the product meets the security requirements contained in the Security Target. The criteria against which the BMC Software PATROL&reg; Version 3.4.11 was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.1. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 1.0. Computer Sciences Corporation determined that the target evaluation assurance level (EAL) for the product is EAL 2. The product, configured as installed by the BMC Software technician, satisfies all of the security functional requirements stated in the Security Target (ST). A validator, on behalf of the CCEVS Validation Body, monitored the evaluation carried out by Computer Sciences Corporation. The ST conforms to CC part 2 extended and is CC part 3 conformant at the EAL 2 level of assurance. The evaluation was completed in September 2002. Results of the evaluation can be found in the Validation Report BMC Software PATROL&reg; Version 3.4.11 prepared by National Information Assurance Partnership (NIAP) Common Criteria Evaluation and Validation Scheme (CCEVS).</p>","environmental_strengths":"<p>The TOE provides the following security features<br />\r\nAuditing - PATROL&reg; has the capability to generate audit logs. Audit information generated by the system is based on PATROL&reg; Agent audit logs. Audit functionality provided by the IT Environment is outside the scope of this evaluation. The PATROL&reg; Agent audit log feature permits the recording of various security-related aspects of PATROL&reg; operation. </p>\r\n<p>User Data Protection - PATROL&reg; provides discretionary access control restrictions, inter-TSF user data confidentiality, and data exchange integrity. PATROL&reg; uses access control lists (ACLs) to restrict access to PATROL&reg; Agents.</p>\r\n<p>Identification and Authentication - PATROL&reg; provides for identification and authentication of users on PATROL&reg; Consoles and Agents.</p>\r\n<p>Security Management - PATROL&reg; includes access control lists (ACLs) and security role definitions/assignments to assist in the management of security policy implementation. The PATROL System Administrator can define the following:</p>\r\n<ul>\r\n    <li>Which users have access to the Agent, </li>\r\n    <li>Which hosts have access to the Agent, </li>\r\n    <li>Which type of PATROL&reg; consoles and utilities have access to the agent, and </li>\r\n    <li>Any combination of the above three types of control. </li>\r\n</ul>\r\n<p>The tasks controlled through user roles include:</p>\r\n<ul>\r\n    <li>Committing PATROL&reg; KM changes to a PATROL&reg; Agent, </li>\r\n    <li>Issuing operating system commands at the PATROL&reg; system output window, </li>\r\n    <li>Modifying the PATROL&reg; Agent's parameter attributes, </li>\r\n    <li>Launching a PATROL&reg; Console in developer mode. </li>\r\n</ul>","features":[]}