PRODUCT DESCRIPTION

The Target of Evaluation (TOE) is IBM WebSphere Business Integration Message Broker, Version 5.0, Fix Pack 4.  The WebSphere Business Integration (WBI) Message Broker (WMB) enables information, packaged as messages to flow between different business applications, ranging from large legacy systems through to unmanned devices such as sensors on pipelines.

The TOE is comprised of the WMB components created by IBM. The TOE architecture consists of five subsystems functional components, which are placed at key points within the Enterprise architecture:  Message Brokers Toolkit, Broker, Configuration Manager, User Name Server, and Application (client).

The Message Brokers Toolkit

The Message Brokers Toolkit is an integrated development environment and graphical user interface used for management. The Message Brokers Toolkit also communicates with one or more Configuration Managers, and is used to manage broker domains.

The Broker

A broker is a system service on Windows platforms or a daemon process on UNIX platforms that controls processes that run message flows.
Applications send messages to the broker using WebSphere MQ queues and connections. The broker routes each message using the rules defined in message flows and message sets, and transforms the data into the structure required by the receiving application.

Configuration Manager

The Configuration Manager is the runtime component that acts as an intermediary between the toolkit and the runtime broker domain. It is able to police which Windows users are able to perform actions within the domain. The Configuration Manager is only supported on Windows 2000.

User Name Server

The User Name Server is a runtime component that provides authentication of users and groups performing publish/subscribe operations.
If the operating environment has applications that use the publish/subscribe services of a broker, an additional level of security can be applied to the topics on which messages are published and subscribed. This additional security, known as topic-based security, is managed by the User Name Server that provides administrative control over who can publish and who can subscribe.

Applications (Clients)

Applications send messages to the broker using WebSphere MQ queues and connections. The broker routes each message using the rules defined in message flows and message sets, and transforms the data into the structure required by the receiving application.

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 IBM WebSphere Business Integration Message Broker TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.2 and International Interpretations effective on 29 July 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.  Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is EAL3 family of assurance requirements.  The product, when configured as specified in the WebSphere Business Integration Message Broker Configuration, Administration, and Security, satisfies all of the security functional requirements stated in the IBM WebSphere Business Integration Message Broker Security Target, Version 1.0, 21 November 2005.  The supported platforms are; Windows 2000 (this includes all combinations of Advanced Server and Server with recommended Service Pack and hotfixes) or Windows Server 2003 (this includes all combinations of Standard and Enterprise with recommended Service Pack and hotfixes); AIX Version 5.1 (maintenance level 3) or AIX Version 5.2 (maintenance level 2); HP-UX, V11.11 (December 2002 Quality Pack); Sun Solaris 2.8 ( with the SunSolve recommended patch level); Red Hat Enterprise Linux AS 3.0 (for Linux Intel); SuSE Linux Enterprise Server (SLES) 8 (for Linux Intel).  The TOE also requires a database that uses the ODBC protocol and WebSphere MQ.  One Validator on behalf of the CCEVS Validation Body monitored the evaluation carried out by SAIC.  The evaluation was completed in November 2005.  Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR-05-0087, dated 5 December 2005) prepared by CCEVS.

ENVIRONMENTAL STRENGTHS

IBM WebSphere Business Integration (WBI) Message Broker (WMB) enables information, packaged as messages to flow between different business applications, ranging from large legacy systems through to unmanned devices such as sensors on pipelines.  WMB supports the following six security functions:
Authentication
WMB provides authentication services between client applications that use the WebSphere MQ Real-Time Transport and WebSphere MQ Message Broker Real-Time Input and Real-time Optimized Flow nodes.  The WMB identification and authentication services verify that a broker and a client application are who they claim they are, and can participate in a publish/subscribe session; where each participant uses an authentication protocol to prove to the other that they are who they say they are and are not an intruder impersonating a valid participant.
The WMB supports the following three protocols:

• M – Mutual challenge-response password authentication;
• S – Asymmetric Secure Socket Layer (SSL); and,
• R – Symmetric SSL.

Communication

WMB provides the ability to verify the sender and receiver of messages.  Support for the authenticity of the sender and/or receiver is proved through the use of SSL.

Access Control

WMB uses topic-based security to control which applications in the environments publish/subscribe system can access information on which topics.  Access control lists can be created to determine which principals (i.e. userids and groups of userids) have permission to publish and subscribe on a given topic.  Principals can also be specified on persistent messages (i.e., stored messages).  WMB also has an access policy to control who can create the topology of the domain where access decisions are based on groups IDs.

Security Audit

WMB performs security auditing for all authentication attempts made to the TOE.  Audit records are generated when audit events occur, including the responsible user, date, time, and other details. The audit data is recorded into the operating system for protection.

Security Management

WMB provides security management functionality for the management of the access control policies.  Management is performed from the Broker Toolkit and the command line.

Protection of the TSF

WMB protects itself and ensures that its policies are enforced in a number of ways. First, WMB interacts with users through well-defined interfaces designed to ensure that the WMB security policies are always enforced.  Next, WMB encrypts all communications between physically separate parts of the TOE to ensure that no data is disclosed or modified.

Vendor Information

IBM Corporation
Sally Whittingham
+44 (0) 1962 816521
whittis.uk.ibm.com

http://www.ibm.com