The TOE, IBM WebSphere MQ (WMQ) is message queuing middleware. It connects all business software together to form one enterprise by providing an open, scalable, industrial-strength messaging backbone.
\r\nThe TOE allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using WMQ.
\r\nMessages are used to transfer information from one application program to another (or between different parts of the same application). The applications can be running on the same platform, or on different platforms.
\r\nThe product has several features that were excluded from the target of evaluation boundary (TOE). The TOE does not support the administrator GUI interface. The command line administrator interface is only supported for the TOE. Also, the TOE does not reference or make any evaluation claims for JVM or cryptographic functionality.
","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 WebSphere MQ TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.1 and International Interpretations effective on 26 August 2003. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 1.0. 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 WebSphere MQ for (platform specific) Quick Beginnings Guide, satisfies all of the security functional requirements stated in the WebSphere EAL2 Security Target, Issue 2.8, 4 May 2004. The supported platforms are; AIX 5.1 & 5.2, HP-UX 11i, SUSE Linux Enterprise Server 8 (for Linux Intel and Linux zSeries), RedHat Enterprise Linux AS 2.1 (for Linux Intel), Sun Solaris 8, Sun Solaris 9, Microsoft Windows 2000 (this includes all combinations of Advanced Server, Server, Professional, Service Packs and hotfixes), and Microsoft Windows 2003 (this includes all combinations of Standard, Enterprise, Service Packs and hotfixes). One validator on behalf of the CCEVS Validation Body monitored the evaluation carried out by SAIC. The evaluation was completed in April 2004. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR—04-0059, dated 27 April 2004) prepared by CCEVS.
","environmental_strengths":"IBM WebSphere MQ was developed to connect all business software together to form one enterprise by providing an open, scalable, industrial-strength messaging backbone. WebSphere MQ supports the following three security functions:
\r\n\r\n","features":[]}Security Audit:
\r\n
\r\nIn the TOE, an instrumentation event is a logical combination of conditions that is detected by a queue manager. Such an event causes the queue manager to put a special message, called an event message, on an event queue. One type of instrumentation event is the Authority event. This event reports authorization failures, such as an application trying to open a queue for which it does not have the required authority, or a command being issued from a user ID that does not have the required authority. If an attempt to access an object has not been authorized then an audit event is generated. The type of event, the user identity and application ID data are gained from the process that attempted to access the object and recorded in the event message (audit record). The Event messages are stored in an event queue, which is protected in the same way as all other queues. Only the administrator (member of MQM group) is able to access the event queue.User Data Protection:
\r\n
\r\nThe TOE ensures that access to an object is only given to a process acting on behalf of a user, if the associated user and group IDs associated with the user, has been granted permission to access to that object. The user and group IDs are gained from the operating system and cached in memory for any subsequent access requests. Each process contains the user ID within the message descriptor part of the process, which is used to confirm the group permissions. Permission is confirmed by checking that either the UID or GID is contained within the object's Access Control List (ACL)Security Management:
\r\n
\r\nThe TOE is managed through a Command Line Interface (CLI). The command line interface is used to enable administrators to provide management of the queue manager. The CLI is used to administer and issue commands. The CLI provides the ability for the administrator to modify/delete event messages, update the ACLs to grant or revoke access to users/groups, viewing of the event queue contents for authorization failures and viewing of the default attributes assigned to an object upon creation. The administrator command line prevents unauthorized deletion and modifications of event messages by ensuring that only administrators (i.e. members of the mqm group) have access to the event queue.
\r\n