The Target of Evaluation (TOE) is webMethods Business Process Management Suite 8.2 SP2, which consists of Integration Server with Process Engine, webMethods Broker, My webMethods Server with Task Engine, and Designer. webMethods BPMS is part of the larger webMethods Product Suite. The BPMS product provides application services together with business process management (BPM) in a service-oriented architecture (SOA). The TOE encompasses the security functions of the BPMS. This section introduces the webMethods BPMS product and describes the parts of the product that make up the TOE.
","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 webMethods Business Process Management Suite 8.2 SP2 (BPMS) TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 3. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1, Revision 3.
\r\nLeidos, Inc., determined that the evaluation assurance level (EAL) for the product is EAL 2 augmented with ALC_FLR.1. The product, when delivered and configured as identified in the Installation Guide for BPMS 8.2 SP2 Common Criteria Configuration, satisfies all of the security functional requirements stated in the Software AG webMethods Business Process Management Suite 8.2 SP2 Security Target, Version 0.6, 11/08/13.
\r\nA validation team on behalf of the CCEVS Validation Body monitored the evaluation carried out by Leidos, Inc. The evaluation was completed in December 2013. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10483-2013), prepared by CCEVS.
","environmental_strengths":"Software AG webMethods Business Process Management Suite 8.2 SP2 provides a low to moderate level of independently assured security in a conventional TOE and is suitable for a cooperative non-hostile environment with good physical access security and competent administrators.
\r\nSoftware AG webMethods Business Process Management Suite 8.2 SP2 supports the following security functions:
\r\nThe TOE records security-relevant events in audit records. Integration Server, webMethods Broker, and My webMethods Server generate audit records, which are stored in distinct audit trails. Security-relevant events include TOE configuration changes made by administrators, business process changes made by business analysts and IT developers, and service access by users. The set of audited events is configurable. Each audit record contains information suitable for analysis including date and time of the event, type of event, responsible identity, and event outcome.
\r\nThe TOE provides tools to select Integration Server’s audit records by time or number of records and view the subset in chronological or reverse chronological order. The TOE limits access to these tools. The Integration Server stores the audit records in a database, which the operational environment protects.
\r\nThe TOE webMethods Broker and My webMethods Server store their audit trails in local operating system files, which the operating system protects. The TOE relies on the operational environment (for example, using a text editor) for review of webMethods Broker and My webMethods Server audit records. My webMethods Server also provides ability to view audit trails via its web interface.
\r\nIn addition, the TOE relies on the operational environment for reliable time stamps.
\r\nIntegration Server built-in services include services to digitally sign documents and verify digital signatures and to encrypt and decrypt documents. Business analysts and IT developers can use the built-in cryptographic services to present end users with digital signature and secure hash functions. These services rely on the operational environment, specifically JDK cryptographic providers and cryptographic functions of the Entrust FIPS 140-2 validated cryptographic module. The JDK cryptographic providers implement World Wide Web Consortium (W3C) XML standards. The cryptographic module provides cryptographic algorithms (RSA, AES, and Triple DES). The built-in services use the operational environment to make the cryptography capabilities available for use with documents.
\r\nThe TOE supports secure communication with users and between TOE components with TLS. The TOE configuration determines which ports require TLS. The TOE relies on the operational environment for key management and cryptographic functions, which are provided by the JDK (for example, TLS session establishment) and FIPS 140-2 validated cryptographic modules (for example, AES encryption and decryption). Cipher suites used by the TOE include Triple DES, AES, DSA, and RSA using common key sizes (192 bits, 128 to 256 bits, 1024 bits, and 1024 to 4096 bits, respectively).
\r\nBy default, JDK limits cryptographic key sizes. The defaults can be changed with a jurisdiction policy file. In order to allow use of longer keys (for example, 256-bit AES), the JVM in the operational environment must have an unlimited strength jurisdiction policy file.
\r\nThe TOE provides services to end users and provides development tools to business analysts and IT developers. The TOE enforces policies to limit access to services, tools, information, and resource to authorized users. The policy can limit service requests based on group membership, location (that is, source IP address), and service requested. It can limit access to other resources based on user name, group membership, role membership, owner of the resource, and operation requested. Administrators can configure access control policies and user permissions. Business analysts and IT developers may set user permissions on a limited basis (for example, on resources they own).
\r\nBoth access control policy enforcement and security audit depend on assured identity of users. The TOE provides password-based authentication and supports cryptographic authentication. In addition, the TOE supports use of an external LDAP server for authentication. The TOE enforces password composition rules. The TOE associates security attributes with each authenticated user. These attributes may include user name, group membership, role membership, password, and X.509 public key certificate. The TOE authentication policy is configurable so that some services and operations would require authentication while others would not.
\r\nThe TOE uses roles to manage privileges. Several Integration Server, webMethods Broker, and My webMethods Server roles have privilege to manage security functions. Collectively, these roles are identified with the Authorized Administrator role defined in this ST. The TOE also uses roles to enforce its access control policy.
\r\nThe TOE includes tools needed to manage its security functions and limits their use to Authorized Administrators. An Authorized Administrator can configure security audit, network port restrictions, user accounts, groups, roles, access control policy, and password policy rules.
\r\nThe TOE supports secure communication for service requests and responses. The TOE can be configured to use a FIPS 140-2 validated cryptographic module to present services through HTTPS and, for Integration Server, FTPS. In addition, the TOE can be configured to use TLS version 1.0 to protect communication among TOE components and between webMethods Broker and its clients. The TOE supports LDAPS (LDAP over TLS) for connections with LDAP directories in the operational environment. The TOE relies on the operational environment for secure communication with RDBMSs.
","features":[]}