WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page i i WebSphere Application Server for z/OS V7 Service level 7.0.0.19 with APAR PM55522 EAL4+ Security Target Date: May 17, 2012 Issue: V3.0 Reference: WAS/EAL4/ST/3.0 WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page ii ii This Page Intentionally Left Blank. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page iii iii Table of Contents TABLE OF CONTENTS....................................................................................................................III TRADEMARKS................................................................................................................................... V GLOSSARY AND TERMINOLOGY...............................................................................................VI 1 INTRODUCTION......................................................................................................................... 1 1.1 TOE OVERVIEW ...................................................................................................................... 1 1.2 SECURITY TARGET, TOE AND CC IDENTIFICATION................................................................ 1 1.3 CC CONFORMANCE ................................................................................................................. 1 1.3.1 PP Claims........................................................................................................................ 1 1.4 REFERENCES............................................................................................................................ 2 1.5 DOCUMENT CONVENTIONS ..................................................................................................... 2 1.6 STRUCTURE ............................................................................................................................. 3 2 TOE DESCRIPTION.................................................................................................................... 4 2.1 DESCRIPTION OF THE PRODUCT............................................................................................... 4 2.1.1 Product Application Server............................................................................................. 6 2.1.2 Product Tools and Applications...................................................................................... 7 2.1.3 Product Java 2 Software Development Kit (SDK) .......................................................... 7 2.1.4 Product Deployment Manager and Product Node Agent Servers................................... 7 2.2 TOE PHYSICAL COMPONENTS AND BOUNDARIES .................................................................. 8 2.2.1 TOE Components ............................................................................................................ 8 2.2.2 Components in the Environment during Evaluation ..................................................... 13 2.2.3 Excluded Functionality.................................................................................................. 15 2.3 DESCRIPTION OF THE TOE SECURITY FUNCTIONS................................................................ 15 2.3.1 Identification and Re-Identification .............................................................................. 17 2.3.2 Access Control............................................................................................................... 18 2.3.3 Security Management.................................................................................................... 18 2.3.4 Audit .............................................................................................................................. 18 3 SECURITY PROBLEM DEFINITION.................................................................................... 20 3.1 INTRODUCTION ...................................................................................................................... 20 3.2 THREATS................................................................................................................................ 20 3.2.1 Threats countered by the TOE....................................................................................... 20 3.2.2 Threats countered by the TOE Environment................................................................. 20 3.3 ORGANISATIONAL SECURITY POLICIES (OSPS).................................................................... 20 3.4 ASSUMPTIONS........................................................................................................................ 20 3.4.1 Operational environment aspects.................................................................................. 20 3.4.2 Physical aspects ............................................................................................................ 21 3.4.3 Personnel Aspects.......................................................................................................... 21 4 SECURITY OBJECTIVES........................................................................................................ 22 4.1 SECURITY OBJECTIVES FOR THE TOE................................................................................... 22 4.2 SECURITY OBJECTIVES FOR THE TOE ENVIRONMENT.......................................................... 22 5 SECURITY REQUIREMENTS................................................................................................. 23 5.1 TOE SECURITY FUNCTIONAL REQUIREMENTS ..................................................................... 24 5.1.1 Access Control (FDP) ................................................................................................... 28 WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page iv iv 5.1.2 Identification & Authentication (FIA)........................................................................... 47 5.1.3 Security Management (FMT) ........................................................................................ 49 5.1.4 Security Audit (FAU)..................................................................................................... 52 5.2 TOE SECURITY ASSURANCE REQUIREMENTS....................................................................... 52 6 TOE SUMMARY SPECIFICATION........................................................................................ 53 6.1 SECURITY FUNCTIONS (SF)................................................................................................... 53 6.1.1 Identification and Re-Identification (Ident)................................................................... 53 6.1.2 Access Control (AC)...................................................................................................... 61 6.1.3 Security Management (SM)........................................................................................... 68 6.1.4 Audit (Aud) .................................................................................................................... 72 7 RATIONALE............................................................................................................................... 73 7.1 CORRELATION OF THREATS, POLICIES, ASSUMPTIONS AND OBJECTIVES............................. 73 7.2 SECURITY OBJECTIVES RATIONALE ...................................................................................... 73 7.2.1 Threats........................................................................................................................... 74 7.2.2 Security Policy............................................................................................................... 75 7.2.3 Assumptions................................................................................................................... 75 7.3 SECURITY REQUIREMENTS RATIONALE ................................................................................ 77 7.3.1 Security Functional Requirements Rationale................................................................ 77 7.3.2 Security Assurance Requirements Rationale................................................................. 78 7.3.3 SFR Dependencies......................................................................................................... 80 7.4 TOE SUMMARY SPECIFICATION RATIONALE........................................................................ 82 7.4.1 TSF correspondence to SFRs ........................................................................................ 82 7.4.2 TSF correspondence Rationale ..................................................................................... 83 WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page v Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States and other countries, or both: AIX® DB2® Domino® IBM® Lotus® Power PC® Tivoli® WebSphere® z/OS® The following terms are trademarks of other companies: Java and all Java-based trademarks are registered trademarks of Oracle and/or its affiliates in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page vi Glossary and Terminology AllAuthenticatedUsers A value that is used by some of the TOE access control functions to determine authorization. The value of "AllAuthenticatedUsers" represents a special group consisting of all users that have been successfully identified (caller has presented its identity and the TOE has successfully authenticated the user through the environment). When the value of "AllAuthenticatedUsers" is mapped to a role with permission on a resource, the applicable TOE access control function grants access to the caller only if the caller has been successfully identified. In the evaluated configuration, all callers must be successfully identified by a TOE identification function before reaching a TOE access control function. Therefore, in the evaluated configuration, when the value of "AllAuthenticatedUsers" is mapped to a role with permission on a resource, the applicable TOE access control function always grants access to the resource. Note: AllAuthenticatedUsers is used interchangeably with AllAuthenticated. API Application Programming Interface CC Common Criteria CCIMB Common Criteria Interpretations Management Board CN Common Name (CN) is part of the Distinguished Name (DN) that uniquely identifies an entry in a directory. CORBA Common Object Request Broker Architecture (CORBA) is an architecture specification for distributed object-oriented computing that separates client and server programs with a formal interface definition. For additional information see the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rorb_r4lno.html COSNaming The CORBA Naming Service is also known as the Common Object Services Naming Service – COSNaming for short. For details, reference the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tnam_ovr2.html DB DataBase DN Distinguished Name is a set of attribute:value pairs that uniquely identifies an entry in a directory such as the LDAP directory. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page vii Distributed platforms All the WebSphere Application Server operating systems supported for the evaluation except for z/OS®. EAL Evaluation Assurance Level EJB Enterprise JavaBeans is a component architecture for Java Platform Enterprise Edition (Java EE) for the development and deployment of object-oriented, distributed enterprise-level applications. For details on EJB applications, reference the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/welc6tech_ejb. html Enterprise bean component A server application component that conforms to the JavaEE5 specification. The component contains one or more enterprise beans. The enterprise beans are packaged in a JAR file and configured with an ejb-jar.xml file. Enterprise application A server application that conforms to the JavaEE5 specification. The application consists of one or more web server application components, enterprise bean components, or both. The components optionally can be packaged in an EAR file and configured with an application.xml file. Enterprise bean A server module that is included in an enterprise bean component. The module is coded in the Java programming language and conforms to the EJB architecture identified in the JavaEE5 specification. Everyone A value that is used by some of the Target of Evaluation (TOE) access control functions to determine authorization. The value of "Everyone" represents a special group consisting of all users. When value of "Everyone" is mapped to a role with permission to access a resource, the applicable TOE access control function allows any caller to access the resource. In the evaluated configuration, for all identification functions except Ident.1, each caller must be successfully identified before the applicable access control function is processed. Therefore, in the evaluated configuration, for all identification functions except Ident.1, mapping "Everyone" to a resource has the same effect as mapping "AllAuthenticatedUsers" to a resource. (See "AllAuthenticatedUsers.") FIPS Federal Information Processing Standards (FIPS) are standards used by NIST for Federal Government Computer systems. For details, reference the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rovr_fips.html HA HA refers to High Availability as in the High Availability Manager component of the WebSphere Application Server. See HA Manager. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page viii HA Manager The High Availability (HA) Manager component of the WebSphere Application Server is provided to eliminate single points of failure by running key services on available application servers. For details, reference the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/crun_ha_haman ager.html HTML Hypertext Markup Language HTTP Hypertext Transfer Protocol (HTTP) an internet protocol that is used to transfer and display hypertext and XML documents on the Web. HTTPS Hypertext Transfer Protocol Secure (HTTPS) is an internet protocol that is used by Web servers and Web browsers to transfer and display hypermedia documents securely across the internet. HTTP/S Refers to both the HTTP and HTTPS protocols. IETF Internet Engineering Task Force IBM HTTP Server IBM HTTP Server. For details, see the IBM HTTP Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.ihs.doc/info/welcome_ihs.html IIOP Internet Inter-ORB Protocol (IIOP) is a protocol used for communication between Common Object Request Broker Architecture (CORBA) Object Request Brokers. For information on the IIOP protocol, reference Chapter 15 of the CORBA 2.3.1 specification at http://www.omg.org/spec/CORBA/2.3.1/ InfoCenter IBM WebSphere Application Server Information Center, which provided product documentation. See http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/ welcome_ndmp.html. IT Information Technology JAAS Java Authentication and Authorization Service (JAAS) is the package through which services can authenticate and authorized users while enabling the applications to remain independent from underlying technologies. For details see the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/csec_jaas.html JACC Java Authorization Contract for Containers (JACC) is a J2EE specification that enables third party security providers to manage authorization in the application server. For details, see the WebSphere Application Server Information Center at WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page ix http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/csec_jaccauthor ization.html JavaEE Java Enterprise Edition (JavaEE) 5 provides a standard for developing multi-tier, enterprise services. For information on Enterprise Applications (JavaEE Applications) see the WebSphere Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/crun_entapp.ht ml Java SE Java Standard Edition. WebSphere Application Server supports the Java Standard Edition (Java SE) 6 specification as described in the Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tovr_migratingj ava.html JAX-RPC Java API for XML-based RPC (JAX-RPC) is a specification that describes application programmer interfaces and conventions for supporting XML based remote procedure call (RPC) protocols in the Java platform. For more information, see http://jcp.org/en/jsr/detail?id=101 JCA J2EE Connector Architecture (JCA) is a standard architecture for connecting the J2EE platform to heterogeneous enterprise information systems (EIS). For information see the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tdat_jdbcconne ct.html JDBC Java Database Connectivity (JDBC) is an industry standard for database-independent connectivity between Java code and a wide range of databases. The JDBC provides a call-level application programming interface (API) for SQL-based database access. For information on creating and configuring a JDBC provider for WebSphere Application Server, see the Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tdat_tccrtprovd s.html JDK Java Development Kit JMS Java Message Service (JMS) is a Java API that supports the creation and communication of various messaging implementations. For more on messaging and WebSphere Application Server see the Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/co m.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6tech_m sg_intro.html WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page x JNDI Java Naming Directory Interface (JNDI) is a Java extension that provides an interface for various directory and naming services in an enterprise. For details on Naming and JNDI see the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/welc6tech_nam .html JSP JavaServer Page files, a server module that is included in a web server application component. The module is coded in the Java scripting language and conforms to the JSP architecture identified in the J2EE V1.4 specification. For information on JavaServer Pages and WebSphere Application Server, see the Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cweb_jov2.html JVM Java virtual machine (JVM) is a software implementation of a central processing unit that runs compiled Java code (applets and applications). LDAP Lightweight Directory Access Protocol (LDAP) is an open protocol that uses TCP/IP to provide access to information directories that support an X.500 model and it does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory. For information on configuring LDAP as the user registry with WebSphere Application Server, see http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_ldap.html LTPA Lightweight Third Party Authentication (LTPA) is a method that the product uses to generate and validate identification information. The method supports the use of an LTPA token for passing identification information. Note that the evaluated product uses LTPA 2.0. LTPA Token Lightweight Third Party Authentication (LTPA) Token 2.0 is a data structure containing the user ID of the caller, along with the caller‘s unique signature and date generated. The signature in the LTPA token is generated with the RSA algorithm using the TOE LTPA key. The TOE LTPA key is generated by the environment from a random number when the TOE is configured in the evaluated configuration. MBean Managed Bean (MBean). See the WebSphere Application Server Information Center Glossary at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=%2Fcom.ibm.websphere.help.glossary.doc%2Ftopics %2Fglossary.html . NIAP National Information Assurance Partnership WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page xi ORB Object Request Broker (ORB) in object-oriented programming, software that serves as an intermediary by transparently enabling objects to exchange requests and responses. For details, see the WebSphere Application Server Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/welc6tech_orb. html OS Operating System OSP Organisational Security Policy Permission Indicating that one has authorization to access a resource. Privilege and permission are used to mean the same thing. PP Common Criteria Protection Profile. PPC Power PC® Protected Resources Methods in enterprise beans, methods and HTML pages in web server applications, the Administration Service, the Naming Service, UDDI naming resources, and messaging resources. Remote Any entity outside the local network address. Role A logical grouping of users that are defined by an application component provider . RPC Remote procedure call (RPC) is a protocol that allows a program on a client computer to run a program on a server. SDK Software Development Kit Servlet A server module that is included in a web server application component. The module is coded in the Java programming language and conforms to the servlet architecture identified in the J2EE V1.4 specification. SF Security Function. A part or parts of the TOE that have been relied upon for enforcing a closely related subset of rules from the TSP. SFR Security Functional Requirement SOAP Simple Object Access Protocol (SOAP) is described in the specification at http://www.w3.org/TR/soap/ SSL Secure Sockets Layer (SSL) is a security protocol that provides transport layer security: authenticity, integrity, and confidentiality, for a secure connection between a client and a server. The protocol runs above TCP/IP and below application protocols. SSO Single signon (SSO is an authentication process in a client and server relationship in which the user can enter one name and password, and have access to more than one application. For more information on using single signon with WebSphere Application Server, see WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page xii http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_msso.html ST Security Target TCP Transmission Control Protocol TCP/IP Transmission Control Protocol/Internet Protocol (TCP/IP) is an industry-standard nonproprietary set of communication protocols that provide reliable end-to-end connections between applications over interconnected networks of different types. TLS Transport Layer Security (TLS) is an Internet Engineering Task Force (IETF) –defined security protocol that is based on Secure Sockets Layer (SSL). See the WebSphere Application Server Information Center for details at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twbs_secwsaatl. html TOE Target Of Evaluation. An IT product or system and its associated administrator and user guidance documentation that is the subject of the evaluation. Trusted applications, resource adapters, and providers Enterprise applications, resource adapters, and providers that have been written by a developer who adhered to all the guidelines described in the User Guidance document. TSF Scope of Control TSF TOE Security Function. A set consisting of all hardware, software and firmware of the TOE that must be relied upon for the correct enforcement of the TSP. TSP TOE Security Policy. A set of rules that regulate how assets are managed, protected and distributed within the TOE. UDB Universal Database UDDI Universal Description, Discovery, and Integration (UDDI) defines a way to publish and discover information about Web Services. Refer to the WebSphere Application Server Information Center for more details on the UDDI registry for WebSphere Application Server http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.js p?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cwsu_over.html URL Uniform Resource Locator (URL) is the unique address of a file that is accessible in a network such as the Internet. The URL includes the abbreviated name of the protocol used to access the information resource and the information used by the protocol to locate the information resource User Guidance document The document entitled "WebSphere Application Server AGD - Guidance". This document contains installation and configuration guidance as well as guidance for the administrator WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page xiii and developer. This document can be found at the following URL: http://www.ibm.com/support/docview.wss?uid=swg24030364 Web server application A servlet, JSP, or HTML page. Web server application component A server application component that conforms to the J2EE V1.4 specification. The component contains one or more web server applications. The web server applications are packaged in a WAR file and configured with a web.xml file. WS Web Services is often abbreviated as WS in this document. See the following for details on the Web Services for J2EE specification http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index. jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twbs_usew bs.html XML Extensible Markup Lanaguage. For information, see http://www.w3.org/XML/ z/OS platform The supported z/OS operating system. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page 1 1 Introduction This section identifies the Security Target (ST) and Target of Evaluation (TOE) identification, ST conventions, ST conformance claims, and the ST organization. 1.1 TOE Overview The TOE consists of an application server, deployment manager server, node agent server, and wsadmin tool, all components of the WebSphere® Application Server 7 product (hereafter referred to as the product) provided by IBM®. The primary purpose of the product is to provide an environment for running and managing the components of user-supplied enterprise applications. In addition to its primary purpose, the product provides tools for doing useful functions such as assembling and troubleshooting enterprise applications. 1.2 Security Target, TOE and CC Identification Security Target (ST) Title: WebSphere Application Server for z/OS V7, service level 7.0.0.19 with APAR PM55522 EAL4+ Security Target Version: 3.0 Version Date: 17 May 2012 Author: Dick Sikkema and Kristen Clarke TOE identification: WebSphere Application Server for z/OS V7, service level 7.0.0.19. Requires interim fix for APAR PM55522. Common Criteria Identification: Common Criteria for Information Technology Security Evaluation, CCMB-2009-07-002, Version 3.1, Revision 3, July 2009. Evaluated Assurance Level: EAL4, augmented with ALC_FLR.2 (Flaw Reporting Procedures). 1.3 CC Conformance This ST is [CC] Part 2 extended and Part 3 conformant to a claimed Evaluation Assurance Level of EAL4, augmented with ALC_FLR.2 (Flaw Reporting Procedures). 1.3.1 PP Claims This ST does not claim conformance to any PP for the TOE. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page 2 1.4 References [CC] Common Criteria for Information Technology Security Evaluation, CCMB- 2009-07-002, Version 3.1, Revision 3, July 2009. 1.5 Document Conventions Application Notes: An application note is additional informative and non-normative text that assists the intended audience to better understand the intent of the TOE and its security features. Application notes are identified as a footnote to the corresponding item requiring further clarification with a number in the upper-right position (e.g. FAU_GEN.1¹). The accompanying text of the application note is then displayed at the bottom of the page containing the corresponding item. Assignment: An assignment allows the specification of an identified parameter. Assignments are indicated using bold and are surrounded by brackets (e.g., [assignment]). Extended: An extended requirement is a requirement which is stated outside the scope of any predefined requirements within the Common Criteria. Extended requirements are often used for identifying specific capabilities, which are not common covered by the Common Criteria. Extended requirements are identified with ―.EXP‖ following by the component name (FIA_OBO.EXP.1). Interpretation: An interpretation is a clarification or further definition to a security functional or assurance requirement that has been reviewed and approved by CCIMB or the associated Common Criteria scheme representative as being acceptable to incorporate into a complying ST. CCIMB and NIAP interpretations are identified by inserting a footnote next to the corresponding security requirement component which indicates the interpretation affecting the component. Iteration: An iteration allows for the use of a component more than once with varying operations. Iterations are indicated with a lowercase alphabetic character (e.g. FAU_GEN.1a). WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012 All rights reserved. Page 3 Refinement: A refinement allows the addition of details. Refinements are indicated using bold, for additions, and strike- through, for deletions (e.g., ―… all objects …‖ or ―… some big things …‖). Refinements resulting from an interpretation are additionally indicated with a red font. Selection: A selection allows the specification of one or more elements from a list. Selections are indicated using bold italics and are surrounded by brackets (e.g., [selection]). 1.6 Structure The structure of this document is based on [CC] Part 1, Annex A:  Section 1 presents a brief introduction and conformance claims;  Section 2 continues the ST introduction with a TOE description;  Section 3 provides a security problem definition;  Section 4 provides the statement of security objectives;  Section 5 provides a statement of security requirements, including extended component definitions;  Section 6 provides the TOE summary specification, which includes the detailed specification of the IT functions; and  Section 7 provides the rationale for the security objectives, security requirements and TOE summary specification. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 4 2 TOE Description This section provides the following information:  Description of the product;  Description of the TOE Physical Components and Boundaries; and  Description of the TOE security functions. 2.1 Description of the Product The product is IBM‘s implementation of an application server, which is compliant with Java EE 5 specification. The primary purpose of the product is to provide an environment for running and managing user-supplied enterprise applications and their components. In particular, the product provides the capabilities to identify users and to control what resources a user can access through enterprise applications. In addition to its primary purpose, the product provides tools for doing useful functions such as assembling and troubleshooting enterprise applications. The product consists of the following components which are described in sections 2.1.1 to 2.1.4:  Product Application Server;  Product Tools and Applications;  Product Java 2 Software Development Kit (SDK);  Product Deployment Management Server;  Product Node Agent Server. The TOE was tested on the following operating systems. However, the operating system is outside the scope of the TOE. Note: Other operating systems are supported by the product, but those which are not listed below were not tested as part of the evaluation.  z/OS 1.11 It is assumed that all hardware used within the operating environment is secured such that no potential vulnerabilities could be introduced that would circumvent the functionality described within this ST. This protection is assumed to be both physical and logical (for example, appropriate use of network boundary protection devices). WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 5 Figure 1 illustrates the product and its interactions with the environment. The TOE components and interactions are described in more detail below. Application Server Java Client Web Container EJB Container JDBC Provider Naming Service UDDI Registry Tools and Applications Admin App Web Browser Java 2 SDK HTTP/S IIOP (ORB) Deployment Manager NodeAgent Figure 1 Product Overview WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 6 2.1.1 Product Application Server The Product Application Server component is a set of containers, services, and resources that provides an environment for running enterprise applications and their components and for programmatically managing enterprise applications and their components. This environment separates application logic from infrastructure. The enterprise application developer implements applications (for example, an EJB to containing business logic to access a legacy database). The Product Application Server implements infrastructure (for example, a container for the EJB) so that each application need only implement business logic. The infrastructure provides communication and security functions, which include, for example, user identification and authorization. It provides centralized mechanisms to deploy and manage enterprise applications within the infrastructure. Moreover, the physical and logical measures in the environment that protect the Product Application Server likewise protect the enterprise applications that reside with the server. The containers are runtime wrappers that handle system functions, such as communications and security, for enterprise application components and some types of resources. The following containers are included:  Enterprise bean container--handles system functions for enterprise beans.  Web server container (contains an embedded HTTP server)--handles system functions for web server applications.  Resource adapter container--handles system functions for resources that conform to the J2EE Connector Architecture (JCA). The services are Java API and remote interface implementations. They provide useful functions, such as directory and security that components of enterprise applications can use. A few of these services also are remotely available so that Java clients also can use them. The following services are included:  Administration service  Naming service  Messaging service, when the Product Application Server is configured to use the Built-In JMS Provider  UDDI Service  High Availability (HA) Manager The resources are software modules that are used by some of the services for back-end processing. The following resources are included:  A built-in Java Database Connectivity (JDBC) provider, which is sometimes referred to as the ―WebSphere Relational Resource Adapter‖-- handles back- end processing for the product JDBC API service and uses its own built-in database server for storing and retrieving storage.  A built-in Java Message Service (JMS) Provider, which is sometimes referred to as the ―Default Messaging Provider‖--handles back-end processing for the product messaging service. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 7  A naming resource--handles back-end processing for the product JNDI and COSNaming services.  The UDDI Registry Application, which provides a directory for storing web services endpoints.  Security resources--handles back-end processing for the product security services using a user registry in the environment. In this evaluation, it has been tested that when the TOE is in its evaluated configuration, the Product Application Server protects each remotely accessible resource through security checks for identification and access control. See the glossary for a definition of the term ―remote.‖ See Section 2.3 for a list of the protected resources. See Section 2.2 for a description of the TOE physical components and boundaries. 2.1.2 Product Tools and Applications The Product Tools and Applications consists of the Product wsadmin tool, system application for secure file transfer, and the UDDI registry application  The Product wsadmin tool, which provides a scripting interface for managing enterprise applications and their components.  Applications o System application for secure file transfer o UDDI Registry application 2.1.3 Product Java 2 Software Development Kit (SDK) The Product Java 2 SDK is provided with the product, but is part of the TOE operational environment. The Product Java 2 SDK component is software that implements all the Java APIs defined in the Java 2 Standard Edition (J2SE) V1.6 specification and provides a Java execution environment (Java Virtual Machine or JVM) for the rest of the TOE. The Product Java 2 SDK is sometimes referred to as the ―JDK.‖ 2.1.4 Product Deployment Manager and Product Node Agent Servers The Product Deployment Manager Server and Product Node Agent Server components provide additional functionality as a central point of administration for managing multiple Product Application Servers in a distributed environment. In this evaluation, it has been tested that when the TOE is in its evaluated configuration, the Node Agent Server and Deployment Manager Server protect each service they make available. Such services can be accessed remotely and can be used to access protected resources by authorized users. See the glossary for a definition of the term ―remote.‖ See Section 2.3 for a list of the protected resources. See 2.2 for a description of the TOE physical components and boundaries. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 8 2.2 TOE Physical Components and Boundaries 2.2.1 TOE Components The product components in the evaluated configuration (i.e., TOE) are:  Product Application Server - Required  Product wsadmin Tool - Required  Product Deployment Manager Server - Required  Product Node Agent Server - Required Note that the TOE also includes the set of evaluated Guidance documentation which can be downloaded from: http://www.ibm.com/support/docview.wss?uid=swg24030364 The ―WebSphere Application Server EAL4 AGD – Guidance‖ documentation includes  The Installation and Configuration Guide for the Certified System,  Administrator‘s Guide for the Certified System,  Developers Guide for the Certified System. The Guidance documentation includes links to pertinent on-line articles from the Information Center at http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.zseries.doc/inf o/zseries/ae/welcome_zseries.html The web pages at the Information Center link also include product information and operating environment information not necessarily specific to the TOE, which have not been evaluated, and should be considered for informational purposes only as they may contain instructions not suitable for use in the evaluated configuration. Only the Guidance documents identified above and the links to web pages within the Installation and Configuration, Administrator, and Developer’s Guides should be considered as specific guidance for the TOE. 2.2.1.1 Product Application Server The Product Application Server is included in the TOE. Multiple instances of the Product Application Server can be configured on the network and in a single operating system. Each instance of the Product Application Server runs in its own process and JVM. The Product Application Server is briefly described in the section 2.1.1 of this document. The following provides additional information about the Product Application Server and its required configuration. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 9 2.2.1.1.1 Description of the Product Application Server In the evaluated configuration, the Product Application Server performs the following functions:  Starts up  Loads local components  Accepts local and remote requests  Processes requests for services  Processes requests for mapped methods and HTML pages Starts up. The Product Application Server is started using the Java command provided by the Product Java 2 SDK. The Product Application Server is run in a single operating system process and JVM. Loads local components. The Product Application Server starts the following components:  User applications (that is, web server applications and enterprise beans), and  UDDI Registry Application. These components are run in the same operating system process and JVM that the Product Application Server is using. Therefore, these components are called "local components." For user applications, the TOE supports Enterprise JavaBean specifications 2.1 and lower. It supports Java Servlet specification 2.4 and lower. Accepts local and remote requests. The Product Application Server accepts requests over its local and remote interfaces. The requests over its local interfaces come from the local components (web server applications and enterprise beans). The Product Application Server receives these requests directly. The requests over its remote interfaces come from Java clients. The Product Application Server receives these requests indirectly by means of the Product Java 2 SDK. Processes requests for services. If the Product Application Server receives a request for a service, the Product Application Server first performs any actions required by the security configuration (for example, identification and access control). If actions are successful, the Product Application Server processes the requested service. In the evaluated configuration, the Product Application Server enforces the security checks for the following services:  Administration service  Naming service  Messaging service, when the Product Application Server is configured to use the Built-In JMS Provider  UDDI Service  High Availability (HA) Manager Processes requests for mapped methods and HTML pages. If the Product Application Server receives a request for a mapped method or HTML page in a user application or the WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 10 UDDI Registry Application, the Product Application Server first performs any actions required by the security configuration (for example, identification and access control). If the actions are successful, the Product Application server invokes the mapped method or HTML page. Web Services. The product supports two types of Web Services applications – JAX-WS and JAX-RPC. However, the evaluated configuration of the product includes only the support for JAX-RPC. As such, while the product includes a number of web services support features, specifically WS-ReliableMessaging, WS-SecureConversion, WS- Security, and WS-Kerberos, those features are excluded due their reliance on JAX-WS. The support for JAX-WS and these other specific features is excluded from the evaluated configuration due to very limited use by customers, reliance on external security products (e.g., a KDC), and some inherent limitations or conflicts among the available supporting functions. 2.2.1.1.2 Required configuration of the Product Application Server In the evaluated configuration, the Product Application Server must be configured as described in the document, ―WebSphere Application Server EAL4 – AGD Guidance‖. In particular, the TOE Single Signon (SSO) must be enabled in the evaluated configuration. In subsequent sections, this document will be referenced as the User Guidance document. Applications that the TOE hosts are not covered in the evaluation. This ST assumes that application developers follow guidance for a certified system in User Guidance and that administrators deploy only those applications. Consequently, some types of applications, services, and Web Services must not be used in the evaluated configuration. The following types of applications must not be deployed in the evaluated configuration:  Applications provided with WebSphere Application Server, except for the UDDI Registry Application 1  Session Initiation Protocol (SIP) applications,  Portlet applications,  Applications using request dispatching. The following types of services must not be used in the evaluated configuration:  Activity session service,  Data Replication service,  Compensation Scoping Service,  Event service, and  WS-Notification services (see Web Services above). The following types of web services must not be used in the evaluated configuration:  Web Services Gateway,  Web service endpoints using JMS transport (only HTTP is in the evaluated configuration),  Web Services JAX-WS applications (see Web Services above), and  JAX-RPC web services using Kerberos (see Web Services above). 1 The Secure File Transfer Servlet also is included in the evaluated configuration. It is not externally visible. The WebSphere Application Server uses this servlet internally. The Deployment Manager uses it to push files to nodes. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 11 The following types of external resources must not be used in the evaluated configuration:  External JACC provider, including Tivoli Access Manager Server  External Trust Association Interceptor (TAI) resource The following types of external resources are optional in the evaluated configuration:  External JAAS Login module  External resource adapters  Embedded WebSphere MQ client 2.2.1.2 Product wsadmin Tool The Product wsadmin Tool is included in the TOE. Multiple instances of wsadmin can be configured in the network or in a single node. Each instance of the wsadmin runs in its own operating system process and JVM. The Product wsadmin Tool is briefly described in section 2.1.2 of this document. The following provides additional information about the Product wsadmin Tool and how it is configured in the evaluated configuration. The Product wsadmin Tool is a Java client application. The administrator starts the Product wsadmin Tool by running a script (wsadmin.sh). After the Product wsadmin Tool starts, an administrator can use this tool to execute administrative scripting commands for the purpose of managing any or all of the following servers: Product Application Server, Product Node Agent Server, or Product Deployment Manager Server. The Product wsadmin Tool must be configured as described in the User Guidance document. 2.2.1.3 Product Deployment Manager Server and Product Node Agent Server The Product Deployment Manager Server and Product Node Agent Server are included in the TOE and provide a central point of administration for managing multiple Product Application Servers in a distributed environment . Multiple instances of Product Node Agent Server can be configured on the network. Each instance runs in its own operating system process and JVM. The Product Deployment Manager Server and Product Node Agent Server each contain one service, which is an administration service. The administration service of each server must be configured in a logical unit called a cell. Each cell consists of one Product Deployment Manager, one or more Product Node Agent Servers, and each Product Application Server residing on the same node as a Product Node Agent Server. Using this configuration, an entire cell can be managed from a single Java client using the Product wsadmin Tool, as shown in the following figure: WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 12 Product App Server Product Node Agent Server Product Deployment Manager Server Product App Server Product App Server Product Node Agent Server Product App Server Product App Server Product wsadmin Tool Cell Figure 1 : Cell Architecture WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 13 Each Product Deployment Manager Server and Product Node Agent Server accepts requests to its administration service, processes any required security as described for AC.3 in section 6.1.2.3, and processes the request only if security processing is successful. Each Product Deployment Manager Server and Product Node Agent Server must be configured as described in the User Guidance document. 2.2.2 Components in the Environment during Evaluation The following software components are not included in the TOE. They are part of the TOE operational environment in the evaluated configuration:  Operating system  Product Java 2 SDK  JDBC resource and any back-end servers The TOE has been designed to control access to the data it hosts and the associated management functions. This is accomplished by offering access to its objects and functions through interfaces carefully designed to ensure that the applicable security policies are enforced prior to allowing requested operations to succeed. However, the TOE is an application program that depends on the supporting products identified above and summarized below. As such, the TOE is dependent upon those products to enforce their respective policies to ultimately protect the TOE and its data both at rest and while in execution. 2.2.2.1 Operating System The TOE was evaluated with each of the operating systems listed in the section 2.1 ―Description of the Product.‖ The operating system was configured on each system unit in which a TOE component resides. The TOE components use the following resources of the operating system:  Process, threads, and mutex  User registry in a configuration in which the user registry from the operating system is used  File system (store, protect, and provide means to access data – such as audit records - in files)  TCP/IP network stack  Operating system APIs 2.2.2.2 Product Java 2 SDK The Product Java 2 SDK is included in the environment. When the TOE is configured as described in the User Guidance document, it is assumed the Java 2 SDK provides the functions described below to support the TOE. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 14 This component serves to provide a Java execution environment (Java Virtual Machine or JVM) for the rest of the TOE. The SDK is the IBM SDK for multiplatforms, Java Technology Edition, V6.0 on all platforms except for HP-UX and Solaris. For HP-UX, the SDK is HP JDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, Version 6.0. For Solaris, it is IBM SDK for Solaris, Java 2 Technology Edition, Version 6.0. The rest of the TOE uses the following resources of the Java 2 SDK: o APIs1 o Java launcher (distributed platforms only) The Java 2 SDK provides a layer of security for the TOE in two primary areas: Protection Domains and the Security Manager. Security Manager The Security Manager is involved in the secure loading and execution of Java programs. The JVM is configured such that the Security Manager is instantiated before the first application is loaded. This removes the possibility of the Security Manager being replaced by a malicious Java application and from accessing the file system. It also prevents applications from starting unsafe network connections. The main task of the Security Manager is to judge whether access requests for valuable system resources are to be allowed. The Security Manager first considers the Java class requesting the resource. The concerned Java class passes the control to the core Java classes, which, in turn, requests the resource. If the request is permitted, the program execution proceeds, otherwise an exception is thrown. The Java 2 security model ensures, for every JVM implementation, only a single instance of the SecurityManager class can be created. The default permission set for applications is the recommended permission set defined in the J2EE 1.4 Specification. The default is declared in a security policy file that grants defined permissions to everyone. However, applications are denied permissions that are declared in another file that serves to define access filters. Permissions that are declared in the filter file are filtered for applications during the permission check. Protection Domains The scope of a protection domain is applicable to the code source and permissions specified in the policy files. When a class is loaded, the class is mapped into a Protection Domain. The access permissions of the code are described through the grant entries in the policy file. If the classes have the same set of permissions but belong to different code sources, they are placed in different protection domains. Protection domains are of two types, application and system domains. An application domain constitutes the applets or applications that are given access permissions as defined by the security policy file. On the other hand, the system domain contains all the system code, which is granted all permissions. 1 The TOE is written in Java and leverages Java's Java Cryptography Extension (JCE) services such as when creating or reading certificates stored in keystore files. In addition, Java's Java Secure Sockets Extension (JSSE) leverages the JCE to handle Secure Sockets communications. The TOE makes no claims of these services as they do not contribute to satisfying TOE security functional requirements and were not evaluated. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 15 All the TOE system code such as the administrative subsystem, the Web container, and the EJB container code, are running as the system domain and are granted all permissions and can access all system resources. Application code running in the application security domain, which by default is granted with permissions according to J2EE specifications, can access only a restricted set of system resources. WebSphere Application Server run- time classes are protected by the class loader and are kept invisible to application code. 2.2.2.3 JDBC Provider and Back-end Servers The TOE was evaluated with the following JDBC provider, as well as the back-end server used by this provider: IBM DB2 UDB for z/OS v8. The provider was configured to run inside the Product Application Server component of the TOE and to access data stored in the back-end server. The UDDI and Built-in JMS Resource services of the TOE use the provider and back-end server to store UDDI and messaging data. 2.2.3 Excluded Functionality The Product Tools and Applications component has capabilities for product upgrading and migration. These capabilities are not applicable in the evaluated configuration and were excluded from evaluation. The following product components are excluded from evaluation:  Proxy Server  Admin Console  Admin Agent  Job Manager These components are not configured as part the TOE. Refer to the User Guidance document for specific configuration requirements. Product features that are not identified as part of the TOE and that are not explicitly excluded are available in the evaluated configuration but were not covered by the evaluation. These features do not contribute to meeting the security functional requirements claimed for the TOE. 2.3 Description of the TOE Security Functions The TOE provides a set of identification, access control, security management, and audit functions. These functions are designed to protect sensitive resources from malicious remote callers. A sensitive resource is defined as a resource that:  Resides in a server TOE component  Can be accessed by a remote caller, which is an entity residing outside the server TOE component in which the sensitive resource resides.  Could be used by a remote caller to compromise the security of a deployed web server application or deployed enterprise bean. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 16 The following are the sensitive resources of the TOE:  Methods and static web content of deployed user web server applications (user web server applications that are deployed in the TOE)  Methods of deployed user enterprise beans (user enterprise beans that are deployed in the TOE)  Transactions and activities of deployed user web server applications, deployed enterprise beans, and the TOE  The TOE naming directory  The TOE UDDI registry directory  TOE configuration data  TOE files  TOE runtime state  TOE local bus, queue destinations, temporary destinations, topic space, topic space root, and topics WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 17 2.3.1 Identification and Re-Identification The TOE provides functions that identify a remote caller when the caller requests access to a sensitive resource. These functions are:  Ident.1—This function identifies a remote caller that requests access to a sensitive resource using a remote HTTP/S Interface of the TOE.  Ident.2—This function identifies a remote caller that requests access to a sensitive resource using a remote ORB interface of the TOE.  Ident.3—This function identifies a remote caller that requests access to a sensitive resource using a remote JMS interface of the TOE.  Ident.4—This function re-identifies a remote caller that requests access to a sensitive resource using a remote web services interface of the TOE. The TOE does initial identification base on initiating request through Ident.1.  Ident.5—This function identifies a remote caller that requests access to a connection to the remote HA Manager interface of the TOE.  Ident.6—This function permits a method in a deployed user web server application or enterprise bean to assume the identity of another user.  Ident.7—This function identifies a remote caller when the remote caller attempts to access a sensitive transaction using the remote Web Services Transactions (WS-Transactions) interface of the TOE. The TOE relies on the operational environment and on the user IDs and group IDs maintained by the environment to authenticate claimed identities when TOE policy requires authentication. For authentication, the TOE accepts the user information (user ID/password, token, or certificate) and passes that information to the operational environment. The operational environment determines if the information is valid and returns that status to the TOE. If the information was valid the TOE creates a Subject that contains a credential with the user information. The TOE uses the Subject for subsequent identification and authorization checks. If the operational environment determines the identification information is not valid, then the TOE does not create a Subject and instead throws a login failure exception. See Section 6.1.1, "Identification and Re-Identification (Ident)‖ for more information. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 18 2.3.2 Access Control The TOE provides access control functions that allow only authorized remote callers to access to the sensitive resources. The following are the access control functions: o AC.1—This function controls access from remote callers to methods and HTML pages in deployed web server applications. o AC.2—This function controls access from remote callers to Methods in deployed enterprise beans (including methods that are deployed as web services endpoints). o AC.3—This function controls access from remote callers to TOE configuration data, TOE files, and TOE runtime state. o AC.4—This function controls access from remote callers to the TOE naming directory. o AC.5—This function controls access from remote callers to transactions and activities. o AC.6—This function controls access from remote callers to messaging resources (local bus, queue destinations, temporary destinations, topic space, topic space root, and topics). o AC.7—This function controls access from remote callers to UDDI resources. o AC.8 – This function is not applicable to this version of the product. o AC.9—This function controls access from remote callers to methods and attributes in user MBeans. The TOE bases access control decisions on identity and roles of the requestor and permissions required for the target resource. The TOE relies on the operational environment and on the user IDs and group IDs maintained by the environment to authenticate identity. Each resource‘s configuration determines the permissions required to access the resource. The TOE builds an authorization table based on information from the applications for EJBs and web resources, and admin policy files for the Application Server. Upon a request the TOE will use the credential from the Subject making the request and determine if the corresponding user (or group the user belongs to) is in the role definition required for that resource. If the user/group is in the required role, then the TOE grants access; otherwise, the TOE denies access. See Section 6.1.2, "Access Control (AC)" for more information. 2.3.3 Security Management The TOE provides security management functions that provide a mechanism for dynamically configuring some security attributes used by TOE access control functions See Section 6.1.3, "Security Management (SM)" for more information. 2.3.4 Audit The TOE provides audit functions that provide authorized administrators to associate users with security relevant actions for identification, access control and for enabling and disabling the audit function. The TOE relies on the operational environment for audit record storage. The following are the audit functions: WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 19 o Aud.1—The TOE provides an auditing function that provide a mechanism for auditing identification and access control events. o Aud.2—The TOE the capability to review audit records and limits that capability to authorized administrators. See Section 6.1.4, ―Audit (Aud) for more information. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 20 3 Security Problem Definition 3.1 Introduction The statement of TOE security environment describes the security aspects of the environment in which it is intended that the TOE will be used and the manner in which it is expected to be employed. The statement of TOE security environment therefore identifies the assumptions made on the operational environment and the intended method for the product, defines the threats that the product is designed to counter and the organisational security policies which the product is designed to comply. 3.2 Threats The assumed security threats are listed below: 3.2.1 Threats countered by the TOE [T.ACCESS_RES] A caller gains access to a resource without the correct authority to access that resource. [T.ACCESS_TOE] An unidentified caller gains access to a protected resource. [T.NETWORK] Data transferred between workstations is disclosed to, or modified by unidentified users or processes, either directly or indirectly. 3.2.2 Threats countered by the TOE Environment [T.APP] The misconfiguration, inappropriate installation, or inappropriate development of applications and operating system that the TOE interfaces with, compromises the TOE security policies or security functions used to protect sensitive resources from access by unauthorized remote callers. 3.3 Organisational Security Policies (OSPs) The TOE complies with the following OSP: [P.ACCESS] The right to access a resource is determined on the basis of association of user or group IDs to roles and of roles to resources. 3.4 Assumptions This section provides the minimum connectivity, physical, and procedural measures required to maintain security of the WebSphere Application Server product. 3.4.1 Operational environment aspects [A.AUTH] It is assumed that the operational environment supporting the TOE provides at least one of the supported authentication mechanisms identified within the evaluated configuration of the TOE. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 21 [A.APP] It is assumed that the applications and operating system that the TOE interfaces, will not compromise the security of the TOE and where applicable, that they have been configured in accordance with manufacturer‘s installation guides and/or its evaluated configuration. It also is assumed that the developers of all user applications (user web server applications and user enterprise beans), resource adapters, and providers will comply with all the guidelines and restrictions specified in the User Guidance document. [A.TIMESTAMP] It is assumed that the operational environment provides accurate timestamp information. [A.STORAGE] It is assumed that the operational environment supporting the TOE provides the means to store, protect, and access data within files. 3.4.2 Physical aspects [A.PROTECT] It is assumed that all software and hardware, including network and peripheral devices, have been approved for the transmittal of protected data. Such items are to be physically protected against threats to the confidentiality and integrity of the data. It is assumed that all hardware used in the operating environment is secured. 3.4.3 Personnel Aspects [A.ADMIN] It is assumed that there are one or more competent individuals that are assigned to manage the TOE and the security of the information it contains. Such personnel are assumed not to be careless, willfully negligent or hostile. It also is assumed that this individual will comply with all the guidelines specified in the User Guidance document. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 22 4 Security Objectives 4.1 Security Objectives for the TOE [O.ACCESS] The TOE must ensure that only those callers with the correct authority are able to access an object. [O.IDENTIFY] The TOE must ensure that all callers are identified and authenticated before they access a protected resource. [O.MANAGE] The TOE must allow administrators to effectively manage the TOE and that this can be performed remotely only by authorised callers. [O.AUDIT] The TOE must provide administrators with a mechanism for auditing access control decisions. 4.2 Security Objectives for the TOE Environment [O.ADMIN] Those responsible for the TOE and its environment are competent and trustworthy individuals, capable of managing the TOE and its environment, and the security of the information it contains. In addition, those responsible for the TOE and its environment must comply with the guidelines listed in the assumption A.ADMIN. [O.APP] Those responsible for the TOE must ensure that the interfacing applications do not compromise the security of the TOE and that they are installed and configured in accordance with the manufacturer‘s instructions and/or the evaluated configuration where applicable. In addition, those responsible for the TOE must ensure that the developers of the applications are trusted to comply with the Guidelines listed in the assumption A.APP. [O.ATTR] The operational environment shall maintain User and Group mappings for callers. [O.AUTH] The operational environment shall process authentication requests by remote callers. [O.TIMESTAMP] The operational environment shall provide accurate timestamp information. [O.FILES] The operational environment shall provide the means to store, protect, and retrieve data using files. [O.PROTECT] Those responsible for the TOE must ensure that procedures exist to ensure that data transferred between workstations is secured from disclosure, interruption or tampering. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 23 5 Security Requirements This section specifies the Security Functional Requirements (SFRs) for the TOE and organises the SFRs by class. Within the text of each SFR, the selection, assignment, and refinement operations (as defined within [CC]) are formatted according to the conventions specified in Section 1.6. The following requirements are extended components of the CC:  FIA_OBO.EXP.1 is an extended TOE security requirement, and although based on [CC], it has not been specified using CC Part 2 functional components. It was defined to address functionality for the ability of a user to perform an action on behalf of another user. It fits within the Identification and Authentication (FIA) class of CC requirements, but does not fit within an existing family of CC requirements. Rather, it fits within a new family of ‗On behalf of‘ (OBO) requirements. While other requirements could be devised to fit within that family, this ST only defines ‗Perform actions on behalf of another user‘ (FIA_OBO_EXP.1) which supports the specification of rules for a subject to perform actions on behalf of other users. The definition of FIA_OBO.EXP.1 is: FIA_OBO.EXP.1: Perform actions on behalf of another user Hierarchical to: No other components Dependencies: FIA_UID.1 Timing of Authentication FIA_OBO.EXP.1.1 The TSF shall provide a caller which has previously been successfully authenticated by the environment with the capability to perform operations on behalf of another user as follows: a) The caller shall obtain all privileges assigned to the claimed identity only if the user is successfully re- authenticated by the environment as the other user; or b) The caller shall obtain all privileges assigned to the TSF supplied identity only if specifically allowed by the TSF to operate with a TSF supplied identity. Recommendations for FIA_OBO.EXP.1 are: o Management – the management of user identities. Note: This general recommendation is realized in this ST by FMT_SMF.1.1 item e. o Audit – The following actions should be auditable if FAU_GEN.1 Security audit data generation is included in the PP/ST: Minimal: Unsuccessful use of the user identification mechanism, including the user identity provided; Basic: All use of the user identification mechanism, including the user identity provided. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 24  FIA_UAU.EXP.1 is an extended TOE security requirement, and although based on [CC], it has not been specified using CC Part 2 functional components. It was defined for the situation where a TOE invokes the operational environment to authenticate the identity claimed by a user. It fits within the User authentication (FIA_UAU) family of the Identification and Authentication (FIA) class of CC requirements. It is modelled after FIA_UAU.1, which specifies the same behaviour but with the TSF performing authentication. Consequently, CC operation guidance for FIA_UAU.1 applies to FIA_UAU.EXP.1. FIA_UAU.1 would be hierarchical to FIA_UAU.EXP.1. The definition of FIA_UAU.EXP.1 is: FIA_UAU.EXP.1 Timing of invoked authentication Hierarchical to: No other components. Dependencies: FIA_UID.1 Timing of identification FIA_UAU.EXP.1.1 The TSF shall allow [assignment: list of TSF mediated actions] on behalf of the user to be performed before the user is authenticated. FIA_UAU.EXP.1.2 The TSF shall require each user to be successfully authenticated before allowing any other TSF-mediated actions on behalf of that user. FIA_UAU.EXP.1.3 The TSF shall use authentication functions provided by the operational environment to perform authentication. Recommendations for FIA_UAU.EXP.1 are: o Management – managing the list of actions that can be taken before the user is authenticated. Note: The list of actions that can be taken before the user is authenticated is static in this ST. o Audit – The following actions should be auditable if FAU_GEN.1 Security audit data generation is included in the PP/ST: Minimal: Unsuccessful use of the user identification mechanism, including the user identity provided; Basic: All use of the user identification mechanism, including the user identity provided. The extended SFRs are modeled after Common Criteria requirements and as such the assurance requirements as identified in this document apply to the extended SFRs. No new assurance procedures are required to evaluate the extended SFRs. 5.1 TOE Security Functional Requirements The following table summarises the SFRs: Table 1 TOE Security Functional Requirements CLASS FAMILY COMPONENT ELEMENT WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 25 CLASS FAMILY COMPONENT ELEMENT FDP FDP_ACC FDP_ACC.1a FDP_ACC.1a.1 FDP_ACC.1a.2 FDP_ACC.1b FDP_ACC.1b.1 FDP_ACC.1b.2 FDP_ACC.1c FDP_ACC.1c.1 FDP_ACC.1c.2 FDP_ACC.1d FDP_ACC.1d.1 FDP_ACC.1d.2 FDP_ACC.1e FDP_ACC.1e.1 FDP_ACC.1e.2 FDP_ACC.1f FDP_ACC.1f.1 FDP_ACC.1f.2 FDP_ACC.1g FDP_ACC.1g.1 FDP_ACC.1g.2 FDP_ACC.1h (not applicable) FDP_ACC.1i FDP_ACC.1i.1 FDP_ACC.1i.2 FDP_ACF FDP_ACF.1a FDP_ACF.1a.1 FDP_ACF.1a.2 FDP_ACF.1a.3 FDP_ACF.1a.4 FDP_ACF.1b FDP_ACF.1b.1 FDP_ACF.1b.2 FDP_ACF.1b.3 WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 26 CLASS FAMILY COMPONENT ELEMENT FDP_ACF.1b.4 FDP_ACF.1c FDP_ACF.1c.1 FDP_ACF.1c.2 FDP_ACF.1c.3 FDP_ACF.1c.4 FDP_ACF.1d FDP_ACF.1d.1 FDP_ACF.1d.2 FDP_ACF.1d.3 FDP_ACF.1d.4 FDP_ACF.1e FDP_ACF.1e.1 FDP_ACF.1e.2 FDP_ACF.1e.3 FDP_ACF.1e.4 FDP_ACF.1f FDP_ACF.1f.1 FDP_ACF.1f.2 FDP_ACF.1f.3 FDP_ACF.1f.4 FDP_ACF.1g FDP_ACF.1g.1 FDP_ACF.1g.2 FDP_ACF.1g.3 FDP_ACF.1g.4 FDP_ACF.1h (not applicable) WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 27 CLASS FAMILY COMPONENT ELEMENT FDP_ACF.1i FDP_ACF.1i.1 FDP_ACF.1i.2 FDP_ACF.1i.3 FDP_ACF.1i.4 FIA FIA_ATD FIA_ATD.1 FIA_ATD.1.1 FIA_OBO.EXP FIA_OBO.EXP.1 FIA_OBO.EXP.1.1 FIA_UID FIA_UID.1 FIA_UID.1.1 FIA_UID.1.2 FIA_UAU FIA_UAU.EXP.1 FIA_UAU.EXP.1.1 FIA_UAU.EXP.1.2 FIA_UAU.EXP.1.3 FIA_USB FIA_USB.1 FIA_USB.1.1 FMT FMT_MOF FMT_MOF.1 FMT_MOF.1.1 FMT_MSA FMT_MSA.1a FMT_MSA.1a.1 FMT_MSA.1b FMT_MSA.1b.1 FMT_MSA.1c FMT_MSA.1c.1 FMT_MSA.3a FMT_MSA.3a.1 FMT_MSA.3a.2 FMT_MSA.3b FMT_MSA.3b.1 FMT_MSA.3b.2 FMT_MSA.3c FMT_MSA.3c.1 FMT_MSA.3c.2 FMT_MSA.3d FMT_MSA.3d.1 FMT_MSA.3d.2 FMT_SMF FMT_SMF.1 FMT_SMF.1.1 WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 28 CLASS FAMILY COMPONENT ELEMENT FMT_SMR FMT_SMR.1 FMT_SMR.1.1 FMT_SMR.1.2 FAU FAU_GEN FAU_GEN.1 FAU_GEN.1.1 FAU_GEN.1.2 FAU_GEN.2 FAU_GEN.2.1 FAU_SAR FAU_SAR.1 FAU_SAR.1.1 FAU_SAR.1.2 FAU_SAR.2 FAU_SAR.2.1 5.1.1 Access Control (FDP) FDP_ACC.1a: Subset access control FDP_ACC.1a.1 The TSF shall enforce the [web server applications access control policy] on [ a) Subjects a) Remote caller b) Objects a) Methods of web server applications designated by role as protected c) Operations a) Defined by the application developer]. FDP_ACC.1b: Subset access control FDP_ACC.1b.1 The TSF shall enforce the [enterprise beans access control policy] on [ a) Subjects a) Remote caller b) Objects a) Methods of enterprise beans designated by role as protected c) Operations a) Defined by the application developer]. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 29 FDP_ACC.1c: Subset access control FDP_ACC.1c.1 The TSF shall enforce the [configuration data, files, and runtime state access control policy] on [ a) Subjects a) Remote caller b) Objects a) TOE configuration data b) TOE files c) TOE runtime state c) Operations a) Read TOE configuration data b) Modify any attribute except attributes that that map user/group IDs to administration roles c) Modify attributes that map user/group IDs to administration roles d) Upload and download TOE files e) Read the TOE runtime state f) Modify the TOE runtime state]. FDP_ACC.1d: Subset access control FDP_ACC.1d.1 The TSF shall enforce the [naming directory access control policy] on [ a) Subjects a) Remote caller b) Objects a) TOE naming directory c) Operations a) Delete an entry from the TOE naming directory b) Create an entry into the TOE naming directory c) Write to an entry within the TOE naming directory d) Read an entry within the TOE naming directory]. FDP_ACC.1e: Subset access control WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 30 FDP_ACC.1e.1 The TSF shall enforce the [transactions and activities access control policy] on [ a) Subjects a) Remote caller b) Objects a) Transactions and activities c) Operations a) All transactions and activities operations]. FDP_ACC.1f: Subset access control FDP_ACC.1f.1 The TSF shall enforce the [messaging access control policy] on [ a) Subjects a) Remote caller b) Objects a) Protected resources of the built-in JMS Provider (the local bus, queue destination, temporary destination, topic space, topic space root and topics) c) Operations a) Browse b) Connect c) Create d) Receive e) Send]. FDP_ACC.1g: Subset access control FDP_ACC.1g.1 The TSF shall enforce the [UDDI access control policy] on [ a) Subjects a) Remote caller b) Objects a) Protected resources of the UDDI registry directory c) Operations a) All operations on the UDDI SOAP V1, V2 and V3 Publish API through the HTTP interface b) All operations on the UDDI SOAP V3 Custody Transfer API through the HTTP interface c) All operations on the UDDI SOAP V3 Security API through the HTTP interface WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 31 d) All operations on the V2 Publish API through the ORB interface]. FDP_ACC.1h: This SFR is not applicable to this version of the product. FDP_ACC.1i: Subset access control FDP_ACC.1i.1 The TSF shall enforce the [user MBean access control policy] on [ a) Subjects a. Remote caller b) Objects a) Protected methods and attributes of user MBeans c) Operations a) Invoke, read, write]. FDP_ACF.1a: Security attribute based access control FDP_ACF.1a.1 The TSF shall enforce the [web server applications access control policy] to objects based on the following: [information provided in Table 2]. Table 2: Mapping of Subjects/Objects to Security Attributes for the Web Server Applications Access Control Policy Subjects Objects Operations Security Attributes Remote caller2 Protected methods of Web Server Applications Defined by the application developer Application-Specific Role FDP_ACF.1a.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The user ID of the caller must be mapped to an application- specific role; or  A group ID of the caller must be mapped to an application- specific role; and  The application-specific role must have permission to access the protected resource.] FDP_ACF.1a.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. 2 A caller is a user from a remote JVM. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 32 FDP_ACF.1a.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1b: Security attribute based access control FDP_ACF.1b.1 The TSF shall enforce the [enterprise beans access control policy] to objects based on the following: [information provided in Table 3]. Table 3: Mapping of Subjects/Objects to Security Attributes for the Enterprise Beans methods Access Control Policy Subjects Objects Operations Security Attributes Remote caller3 Protected methods of enterprise beans Defined by the application developer Security attributes defined by Application-Specific Role FDP_ACF.1b.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The user ID of the caller must be mapped to an application- specific role; or  A group ID of the caller must be mapped to an application- specific role; and  The application-specific role must have permission to access the protected resource.]. FDP_ACF.1b.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1b.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1c: Security attribute based access control FDP_ACF.1c.1 The TSF shall enforce the [configuration data, files, and runtime state access control policy] to objects based on the following: [information provided in Table 4]. 3 A caller is a user from a remote JVM. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 33 Table 4: Mapping of Subjects/Objects to Security Attributes for the Configuration Data, Files, and Runtime State Access Control Policy Subjects Objects Operations Security Attributes4 Remote caller5 TOE configuration data Read Administrator role Configurator role Monitor role Operator role Deployer (configuration data for applications only) Modify Applies to all attributes except the attributes that map user/group IDs to administration roles. Note: This includes the attributes listed in SM 1.4 except for the runtime attribute that stores the list of registered UDDI publishers. Administrator role Configurator role Deployer (configuration data for applications only) Modify attributes that map user/group IDs to administration roles. AdminSecurityManage r role TOE files Upload and download files Administrator role Configurator role Monitor role Operator role Deployer role AdminSecurityManage r role 4 The security attributes to objects within the Configuration Data, Files, and Runtime State Access Control Policy consist of the pre-defined roles implemented in WebSphere Application Server. These pre-defined roles are hardcoded with a pre-defined set of privileges. Therefore, the only way a remote caller can inherit the appropriate permission to perform an operation is for the user ID or group ID of the remote caller to be mapped to a role that has sufficient permissions. See section 6.1.2.3 for further information. 5 A caller is a user from a remote JVM. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 34 TOE runtime state Read Administrator role Configurator role Monitor role Operator role Deployer(application runtime state only) Modify Note: this includes the runtime attribute that stores the list of registered UDDI publishers. Administrator role Operator role Deployer(application runtime state only) FDP_ACF.1c.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The requested resource must be TOE configuration data and: o The requested operation must be to read TOE configuration data and  The user ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, or Deployer (configuration for applications data only)); or  A group ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, or Deployer (configuration for applications data only)); or o The requested operation must be to modify any attributes except the attributes that map user/group IDs to administration roles.  The user ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, or, for application data only, Deployer); or  A group ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, or, for application data only, Deployer); WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 35 or o The requested operation must be to modify attributes that map user/group IDs to administration roles and  The user ID of the caller must be mapped to the following administration role (AdminSecurityManager); or  A group ID of the caller must be mapped to the following administration role (AdminSecurityManager); or  The requested resource must be TOE files and: o The requested operation must be to upload or download TOE files and  The user ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, Deployer, or AdminSecurityManager ); or  A group ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, Deployer, or AdminSecurityManager); or  The requested resource must be TOE runtime state and: o The requested operation must be read access to the TOE runtime state and  The user ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, or Deployer (for the runtime state of applications only) ); or  A group ID of the caller must be mapped to one of the following administration roles (Administrator, Configurator, Monitor, Operator, or Deployer (for the runtime state of applications only)); or o The requested operation must be to modify the TOE runtime state and WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 36  The user ID of the caller must be mapped to one of the following administration roles (Administrator, Operator, or Deployer (for the runtime state of applications only)); or  A group ID of the caller must be mapped to one of the following administration roles (Administrator, Operator, or Deployer (for the runtime state of applications only))]. FDP_ACF.1c.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1c.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1d: Security attribute based access control FDP_ACF.1d.1 The TSF shall enforce the [naming directory access control policy] to objects based on the following: [information provided in Table 5]. Table 5: Mapping of Subjects/Objects to Security Attributes for the Naming Directory Access Control Policy Subjects Objects Operations Security Attributes6 Remote caller7 TOE naming directory Delete access COSNamingDelete Role Create access COSNamingDelete Role COSNamingCreate Role Read access COSNamingDelete Role COSNamingCreate Role COSNamingRead Role COSNamingWrite Role Write access COSNamingDelete Role COSNamingCreate Role COSNamingWrite Role 6 The security attributes to objects within the Naming Directory Access Control Policy consist of the pre-defined roles implemented in WebSphere Application Server. These pre-defined roles are hardcoded with a pre-defined set of privileges. Therefore, the only way a remote caller can inherit the appropriate permission to perform an operation is for the user ID or group ID of the remote caller to be mapped to a role that has sufficient permissions. See section 6.1.2.4 for further information. 7 A caller is a user from a remote JVM. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 37 FDP_ACF.1d.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The requested operation must be to delete an entry from the TOE naming directory and o The user ID of the caller must be mapped to the following naming role (COSNamingDelete); or o A group ID of the caller must be mapped to the following naming role (COSNamingDelete); or  The requested operation must be to create an entry in the TOE naming directory and o The user ID of the caller must be mapped to one of the following naming roles (COSNamingDelete or COSNamingCreate); or o A group ID of the caller must be mapped to one of the following naming roles (COSNamingDelete or COSNamingCreate); or  The requested operation must be to write to an entry within the TOE naming directory and o The user ID of the caller must be mapped to one of the following naming roles (COSNamingDelete, COSNamingCreate, or COSNamingWrite); or o A group ID of the caller must be mapped to one of the following naming roles (COSNamingDelete, COSNamingCreate, or COSNamingWrite); or  The requested operation must be to read from an entry within the TOE naming directory and o The user ID of the caller must be mapped to one of the following naming roles (COSNamingDelete, COSNamingCreate, COSNamingRead, or COSNamingWrite); or WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 38 o A group ID of the caller must be mapped to one of the following naming roles (COSNamingDelete, COSNamingCreate, COSNamingRead, or COSNamingWrite)]. FDP_ACF.1d.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1d.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1e: Security attribute based access control FDP_ACF.1e.1 The TSF shall enforce the [transactions and activities access control policy] to objects based on the following: [information provided in Table 6]. Table 6: Mapping of Subjects/Objects to Security Attributes for the Transactions and Activities Access Control Policy Subjects Objects Operations Security Attributes8 Remote caller9 Transactions and activities All operations of transactions and activities Administrator Role FDP_ACF.1e.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The requested operation must be to perform an operation on a TOE transaction or activity and o The user ID of the caller must be mapped to the following administration role (Administrator); or o A group ID of the caller must be mapped to the following administration role (Administrator)]. FDP_ACF.1e.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. 8 The security attributes to objects within the Transactions and Activities Access Control Policy consists of the pre-defined role, Administrator, implemented in WebSphere Application Server. This pre-defined role is hardcoded with a pre-defined set of privileges. Therefore, the only way a remote caller can inherit the appropriate permission to perform an operation is for the user ID or group ID of the remote caller to be mapped to a role that has sufficient permissions. See section 6.1.2.5 for further information. 9 A caller is a user from a remote JVM. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 39 FDP_ACF.1e.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1f: Security attribute based access control FDP_ACF.1f.1 The TSF shall enforce the [messaging access control policy] to objects based on the following: [information provided in Table 7]. Table 7: Mapping of Subjects/Objects to Security Attributes for the Messaging Access Control Policy Subjects Objects Operations Security Attributes10 Remote caller Local Bus Connect to the local bus for messaging services. Bus connector Role Queue destination Create a queue destination. Creator Role Send a message to a queue destination. Sender Role Receive a message from a queue destination. Receiver Role Browse messages within a queue destination. Browser Role Temporary destination Create a temporary destination. Creator Role Send a message to a temporary destination. Sender Role Receive a message from a temporary destination. Receiver Role Browse messages within a temporary destination. Browser Role 10 The security attributes to objects within the Special Messaging Access Control Policy consist of the pre-defined roles implemented in WebSphere Application Server. These pre-defined roles are hardcoded with a pre-defined set of privileges. Therefore, the only way a remote caller can inherit the appropriate permission to perform an operation is for the user ID or group ID of the remote caller to be mapped to a role that has sufficient permissions. See section 6.1.2.6 for further information. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 40 Topic Space Send a message to a topic space Sender Role Receive a message from a topic space Receiver Role Topic Space Root Send a message to a topic space root Sender Role Receive a message from a topic space root Receiver Role Topics Send a message to a topic Sender Role Receive a message from a topic Receiver Role FDP_ACF.1f.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The Built-in JMS Provider must be installed and configured on the TOE; and  The requested resource must be Local Bus and: o The requested operation must be to connect to the local bus for messaging services. and  The user ID of the caller must be mapped to the Bus Connector messaging role; or  A group ID of the caller must be mapped to the Bus Connector messaging role; or  The requested resource must be protected Queue Destination and: o The requested operation must be to create a queue destination and  The user ID of the caller must be mapped to the Creator messaging role; or WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 41  A group ID of the caller must be mapped to the Creator messaging role; or o The requested operation must be to send a message to a queue destination and  The user ID of the caller must be mapped to the Sender messaging role; or  A group ID of the caller must be mapped to the Sender messaging role; or o The requested operation must be to receive a message from a queue destination and  The user ID of the caller must be mapped to the Receiver messaging role; or  A group ID of the caller must be mapped to the Receiver messaging role; or o The requested operation must be to browse messages within a queue destination and  The user ID of the caller must be mapped to the Browser messaging role; or  A group ID of the caller must be mapped to the Browser messaging role; or  The requested resource must be protected Temporary Destination and: o The requested operation must be to create a temporary destination and  The user ID of the caller must be mapped to the Creator messaging role; or  A group ID of the caller must be mapped to the Creator messaging role; or o The requested operation must be to send a message to a temporary destination and WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 42  The user ID of the caller must be mapped to the Sender messaging role; or  A group ID of the caller must be mapped to the Sender messaging role; or o The requested operation must be to receive a message from a temporary destination and  The user ID of the caller must be mapped to the Receiver messaging role; or  A group ID of the caller must be mapped to the Receiver messaging role; or o The requested operation must be to browse messages within a temporary destination and  The user ID of the caller must be mapped to the Browser messaging role; or  A group ID of the caller must be mapped to the Browser messaging role; or  The requested resource must be Topic Space and: o The requested operation must be to send a message to a topic space and  The user ID of the caller must be mapped to the Sender messaging role; or  A group ID of the caller must be mapped to the Sender messaging role; or o The requested operation must be to receive a message from a topic space and  The user ID of the caller must be mapped to the Receiver messaging role; or  A group ID of the caller must be mapped to the Receiver messaging role; or WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 43  The requested resource must be Topic Space Root and: o The requested operation must be to send a message to a topic space root and  The user ID of the caller must be mapped to the Sender messaging role; or  A group ID of the caller must be mapped to the Sender messaging role; or o The requested operation must be to receive a message from a topic space root and  The user ID of the caller must be mapped to the Receiver messaging role; or  A group ID of the caller must be mapped to the Receiver messaging role; or  The requested resource must be Topics and: o The requested operation must be to send a message to a topic and  The user ID of the caller must be mapped to the Sender messaging role; or  A group ID of the caller must be mapped to the Sender messaging role; or o The requested operation must be to receive a message from a topic and  The user ID of the caller must be mapped to the Receiver messaging role; or  A group ID of the caller must be mapped to the Receiver messaging role]. FDP_ACF.1f.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1f.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1g: Security attribute based access control WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 44 FDP_ACF.1g.1 The TSF shall enforce the [UDDI access control policy] to objects based on the following: [information provided in Table 8]. Table 8: Mapping of Subjects/Objects to Security Attributes for the UDDI Access Control Policy Subjects Objects Operations Security Attributes11 Remote caller Protected UDDI registry resources through the HTTP interface All operations on the SOAP V1, V2 and V3 Publish API SOAP_Publish_User or V3SOAP_Publish_User_Role, and List of registered UDDI Publishers All operations on the SOAP V3 Custody Transfer API V3SOAP_CustodyTransfer_User_Role, and List of registered UDDI All operations on the SOAP V3 Security API V3SOAP_Security_User_Role List of registered UDDI Publishers Protected UDDI registry resources through the ORB interface All operations on the V2 Publish API EJB_Publish_Role FDP_ACF.1g.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The UDDI Registry Application must be installed and configured on the TOE; and  The requested resource must be protected UDDI registry resources : o The requested operation must be an operation on the UDDI SOAP V1, V2, or V3 Publish API through the HTTP interface  The user ID of the caller must be mapped to one of the following UDDI roles (SOAP_Publish_User 11 The security attributes to objects within the Special UDDI Access Control Policy consists of the pre-defined UDDI Publisher roles, implemented in WebSphere Application Server. These pre- defined roles are hardcoded with a pre-defined set of privileges. Therefore, the only way a remote caller can inherit the appropriate permission to perform an operation is is for the user ID or group ID of the remote caller to be mapped to a role that has sufficient permissions. See section 6.1.2.7 for further information. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 45 or V3SOAP_Publish_User_Role) and is identified within the list of registered UDDI Publishers; or o The requested operation must be an operation on the UDDI SOAP V3 Custody Transfer API through the HTTP interface  The user ID of the caller must be mapped to one of the following UDDI roles (V3SOAP_CustodyTransfer_User_Role) and must be identified within the list of registered UDDI Publishers; or o The requested operation must be an operation on the UDDI V3SOAP Security User API through the HTTP interface  The user ID of the caller must be mapped to one of the following UDDI roles (V3SOAP_Security_User_Role) and must be identified within the list of registered UDDI Publishers; or o The requested operation must be an operation on the V2 Publish API through the ORB interface  The user ID of the caller must be mapped to the following UDDI role (EJB_Publish_Role)]. FDP_ACF.1g.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1g.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. FDP_ACF.1h: This SFR is not applicable to this version of the product. FDP_ACF.1i: Security attribute based access control FDP_ACF.1i.1 The TSF shall enforce the [user MBean access control policy] to objects based on the following: [information provided in Table 10]. Table 10: Mapping of Subjects/Objects to Security Attributes for the User MBean Access Control Policy Subjects Objects Operations Security Attributes WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 46 Remote caller12 Protected methods in user MBeans invoke One or more Administration roles13 Protected attributes in user MBeans read One or more Administration roles write One or more Administration roles FDP_ACF.1i.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [  The user ID of the caller must be mapped to an administration role; or  A group ID of the caller must be mapped to an administration role; and  The administration role must have permission to access the protected resource]. FDP_ACF.1i.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [no explicit authorization rules]. FDP_ACF.1i.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [no explicit denial rules]. 12 A caller is a user from a remote JVM. 13 The Administration roles are: AdminSecurityManager, Administrator, Configurator, Deployer, Operator, and Monitor. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 47 5.1.2 Identification & Authentication (FIA) FIA_ATD.1: User attribute definition FIA_ATD.1.1 The TSF shall maintain the following list of security attributes belonging to individual users: [roles]. FIA_OBO.EXP.1: Perform actions on behalf of another user FIA_OBO.EXP.1.1 The TSF shall provide a caller which has previously been successfully authenticated by the environment with the capability to perform operations on behalf of another user as follows: a) The caller shall obtain all privileges assigned to the claimed identity only if the user is successfully re-authenticated by the environment as the other user; or b) The caller shall obtain all privileges assigned to the TSF supplied identity only if specifically allowed by the TSF to operate with a TSF supplied identity. FIA_UID.1: Timing of identification FIA_UID.1.1 The TSF shall allow [access to a method or static web content that is not configured with a security constraint or access to a method or static web content that is configured with the security constraint of the “Everyone” role] on behalf of the user to be performed before the user is identified. FIA_UID.1.2 The TSF shall require each user to be successfully identified before allowing any other TSF-mediated actions on behalf of that user. FIA_UAU.EXP.1 Timing of invoked authentication FIA_UAU.EXP.1.1 The TSF shall allow [access to a method or static web content that is not configured with a security constraint or access to a method or static web content that is configured with the security constraint of the “Everyone” role] on behalf of the user to be performed before the user is authenticated. FIA_UAU.EXP.1.2 The TSF shall require each user to be successfully authenticated before allowing any other TSF-mediated actions on behalf of that user. FIA_UAU.EXP.1.3 The TSF shall use authentication functions provided by the operational environment to perform authentication. FIA_USB.1: User-subject binding FIA_USB.1.1 The TSF shall associate the following user security attributes with subjects acting on the behalf of that user: [roles]. FIA_USB.1.2 The TSF shall enforce the following rules on the initial association of user security attributes with subjects acting on the behalf of users: [when a subject is instantiated to act on behalf of a user, the subject is assigned the role associated with the identified user]. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 48 FIA_USB.1.3 The TSF shall enforce the following rules governing changes to the user security attributes associated with subjects acting on the behalf of users: [the role associated with a subject normally cannot change, however the “Run as” function can be exercised by an authorized administrator to change the identity and hence role of a subject]. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 49 5.1.3 Security Management (FMT) FMT_MOF.1: Management of security functions behaviour FMT_MOF.1.1 The TSF shall restrict the ability to [disable or enable] the functions [security audit] to [Auditors]. FMT_MSA.1a: Management of security attributes FMT_MSA.1a.1 The TSF shall enforce the [web server applications access control policy, the enterprise beans access control policy, the naming directory access control policy, and the messaging access control policy] to restrict the ability to [modify or delete] the security attributes  [Mappings of user/group IDs to application-defined roles,  Mappings of user/group IDs to messaging roles,  Mappings of user/group IDs to naming roles] to [only the callers that are mapped to either the Administrator role or Configurator role]. FMT_MSA.1b: Management of security attributes FMT_MSA.1b.1 The TSF shall enforce the [configuration data, files, and runtime state access control policy and transactions and activities access control policy and user MBean access control policy] to restrict the ability to [modify or delete] the security attributes  [Mappings of User/Group IDs to Administration Roles] to [only the callers that are mapped to the AdminSecurityManager role]. FMT_MSA.1c: Management of security attributes FMT_MSA.1c.1 The TSF shall enforce the [UDDI access control policy] to restrict the ability to [modify or delete] the security attributes  [Registered UDDI Publishers] to [only the callers that are mapped to either the Administrator role or Operator role]. FMT_MSA.3a: Static attribute initialization FMT_MSA.3a.1 The TSF shall enforce the [UDDI access control policy] to provide [restrictive] default values for security attributes that are used to enforce the SFP. FMT_MSA.3a.2 The TSF shall allow the [Administrator role or Operator role] to specify alternative initial values to override the default values when an object or information is created. FMT_MSA.3b: Static attribute initialization WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 50 FMT_MSA.3b.1 The TSF shall enforce the [web server application access control policy, enterprise bean access control policy, and messaging access control policy] to provide [restrictive] default values for security attributes that are used to enforce the SFPs. FMT_MSA.3b.2 The TSF shall allow the [Administrator role or Configurator role] to specify alternative initial values to override the default values when an object or information is created. FMT_MSA.3c: Static attribute initialization FMT_MSA.3c.1 The TSF shall enforce the [configuration data, files, and runtime state access control policy and transactions and activities access control policy] to provide [restrictive] default values for security attributes that are used to enforce the SFPs. FMT_MSA.3c.2 The TSF shall allow the [AdminSecurityManager role] to specify alternative initial values to override the default values when an object or information is created. FMT_MSA.3d: Static attribute initialization FMT_MSA.3d.1 The TSF shall enforce the [naming directory access control policy] to provide [permissive] default values for the security attributes that are used to enforce the SFP. FMT_MSA.3d.2 The TSF shall allow the [Administrator role or Configurator role] to specify alternative initial values to override the default values when an object or information is created. FMT_SMF.1: Specification of Management Functions FMT_SMF.1.1 The TSF shall be capable of performing the following management functions: [ a) Configuring the attributes that map user and group IDs to roles, b) Configuring the attribute that stores the list of registered UDDI publishers, c) Configuring the attribute that sets the inherit defaults flag for each Messaging queue, topic space, and topic, d) Configuring the attribute that sets the topic space access check flag for each Messaging topic space, e) Configuring the attribute that maps a user ID and password to a run-as role, f) Configuring the attribute that sets the inherit Sender flag for new topics, g) Configuring the attribute that sets the inherit Receiver flag for new topics, h) Enabling and disabling audit]. FMT_SMR.1: Security roles FMT_SMR.1.1 The TSF shall maintain the roles: [ o administration roles,  Administrator WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 51  Configurator  Monitor  Operator  Deployer  AdminSecurityManager  Auditor o application-defined roles, o messaging roles,  Browser  Bus Connector  Creator  Receiver  Sender o naming roles,  COSNamingCreate  COSNamingDelete  COSNamingRead  COSNamingWrite o UDDI roles  SOAP_Publish_User  V3SOAP_CustodyTransfer_User_Role  V3SOAP_Publish_User_Role  V3SOAP_Security_User_Role  EJB_Publish_Role]. FMT_SMR.1.2 The TSF shall be able to associate users with roles. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 52 5.1.4 Security Audit (FAU) FAU_GEN.1: Audit data generation FAU_GEN.1.1 The TSF shall be able to generate an audit record of the following auditable events:  Start-up and shutdown of the audit functions;  All auditable events for the [not specified] level of audit; and  [the access decisions per FDP_ACF.1a to FDP_ACF.1i  All use of the user identification mechanisms, including the user identity provided (FIA_UID.1, FIA_OBO.EXP.1)  Modifications to enable or disable the TOE security audit function (FMT_MOF.1)  ]. FAU_GEN.1.2 The TSF shall record within each audit record at least the following information:  Date and time of the event, type of event, subject identity (if applicable), and the outcome (success or failure) of the event; and  For each audit event type, based on the auditable event definitions of the functional components included in the PP/ST, [no other audit relevant information]. FAU_GEN.2: User identity association FAU_GEN.2.1 For audit events resulting from actions of identified users, the TSF shall be able to associate each auditable event with the identity of the user that caused the event. FAU_SAR.1: Audit review FAU_SAR.1.1 The TSF shall provide [Auditors] with the capability to read [all audit information] from the audit records. FAU_SAR.1.2 The TSF shall provide the audit records in a manner suitable for the user to interpret the information. FAU_SAR.2: Restricted audit review FAU_SAR.2.1 The TSF shall prohibit all users read access to the audit records, except those users that have been granted explicit read-access. 5.2 TOE Security Assurance Requirements The target evaluation assurance level for this product is EAL4, augmented with ALC_FLR.2 (Flaw Reporting Procedures) WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 53 6 TOE Summary Specification 6.1 Security Functions (SF) 6.1.1 Identification and Re-Identification (Ident) The following describes the TOE identification and re-identification security functions. 6.1.1.1 Remote HTTP/S Identification (Ident.1) This security function identifies a remote caller when the caller attempts to access a sensitive resource using a remote HTTP/S interface of the TOE. A remote caller can use the remote HTTP/S interface to access any of the following sensitive resources: Methods and static web content of deployed user web server applications that are configured with any security constraint except for the role of ―Everyone.‖ (The Ident.1 security function is not processed if a method or static web content is not configured with a security constraint or if the method or static web content is configured with the security constraint of the ―Everyone‖ role.) The behaviour of this security function depends on whether the TOE is configured for Single Signon (SSO) and whether a caller passes a valid LTPA 2.0 token with the request. In the evaluated configuration, Single Signon must be configured so the remaining description assumes that Single Signon is configured. For this security function, the TOE relies on user IDs and group IDs which are maintained by the environment. An LTPA token is valid if the token is signed by the TOE LTPA key and the date in the token has not expired. (The TOE relies on the environment to authenticate that the signature in the LTPA token was generated using the TOE LTPA key.) While the TOE does not perform the verification of an LTPA token‘s digital signature, the TOE makes its determination based on the response returned by the operational environment indicating whether the digital signature is valid or not valid.  Valid LTPA token passed. The TOE does one of the following, depending on whether the TOE is configured to use propagated attributes and propagated attributes are passed with the LTPA token: o Propagated attribute passed: The TOE gets the user ID from the token and any group IDs from the propagated attributes. The TOE then associates the user ID and any group IDs with the caller. o Propagated attributes not passed: The TOE gets the user ID from the token and then uses environment to get all group IDs of which the user ID is a member. The TOE then associates the user ID and any group IDs with the caller.  No valid LTPA token passed. The TOE does one of the following, depending on the configuration of the ―authentication method‖ attribute of the sensitive web resource. (In the evaluated configuration, a user web server application can be configured for BASIC, FORM, CLIENT CERTIFICATE, or no authentication method. The UDDI registry application is configured for no authentication method. The file transfer capability within the TOE, used to upload and download TOE files, is configured for BASIC authentication method.) WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 54 o FORM Authentication Method. The TOE queries the caller for a user ID and password using an HTML form. The TOE presents the caller with a customizable page with form fields for user name and password (for example, a company login page). The caller returns the contents of the fields. The TOE does not continue processing until it receives this content. The TOE then queries the environment using the content to determine whether the user ID and password is valid. (The user ID and password are valid if they are configured for a user in the user registry. The TOE relies on the environment to authenticate the user ID and password.) If invalid, the TOE does not process the caller request. Otherwise, the TOE uses the environment to get all group IDs of which the caller is a member and associates the user ID and any group IDs with the caller o CLIENT-CERT Authentication Method. The TOE gets the client certificate in one of the following ways:  If the caller passes a client certificate in the HTTP header and the Trusted property is configured in the environment, the TOE gets the client certificate from the HTTP header.  In all other cases (caller does not pass client certificate in HTTP header or Trusted property is not configured in the environment), the TOE uses the environment to get the client certificate from the SSL protocol and then uses the environment to authenticate the client certificate. (The TOE relies on the environment to authenticate that the client certificate belongs to the client and was signed by a trusted certificate authority.) If unsuccessful, the TOE returns and error to the caller and does not process the caller request. The TOE then uses the environment to map the identity in the certificate to a user ID. If no mapping exists, the TOE returns an error to the caller and does not process the caller request. Otherwise, the TOE uses the environment to get all group IDs of which the caller is a member and associates the user ID and any group IDs with the caller. o BASIC Authentication Method. The TOE queries the caller for a user ID and password using the BASIC Authentication Protocol. The TOE presents the caller with a dialog box containing fields for user name and password. The caller returns the contents of the fields. The TOE does not continue processing until it receives this content. The TOE then continues with the same processing as described previously for the ―Form Authentication Method.‖ WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 55 o No Authentication Method14 . The TOE allows processing of data without querying the caller for a user ID and password. 6.1.1.2 Remote ORB Identification (Ident.2) This security function identifies a remote caller when the caller attempts to access a sensitive resource of the TOE using a remote ORB interface of the TOE. The following sensitive resources can be accessed using a remote ORB interface of the TOE:  Methods of deployed user enterprise beans  Transactions and activities of deployed web server applications, deployed enterprise beans, or the TOE  The TOE naming directory  The TOE UDDI registry directory  TOE configuration data  TOE runtime state The function will attempt to receive and validate identification information from the remote caller. The specific way that the function will do this depends on the type of identification information that the remote caller passes and whether this information is supported in the TOE configuration. The following table lists the types of identification that could be passed and how the TOE will retrieve and validate each type of information. Identification Information How Identification Information is Validated User ID and password Must be a valid user ID and password stored in the user registry. (The TOE relies on the environment to authenticate the user ID and password. The user ID and password are valid if the reside in the user registry.) Client certificate For LDAP, must contain a subject DN that matches a subject DN that is stored in the LDAP user registry. For LocalOS, must contain a common name (CN) from a subject DN that matches a user ID in the user registry. (The TOE relies on the environment to authenticate that the client certificate belongs to the client and was signed by a trusted certificate authority.) LTPA token Must be a valid LTPA 2.0 token. An LTPA token is valid when it is signed with the configured LTPA key and the date in the token has not expired. (The TOE relies on the environment to authenticate the signature in the LTPA token was generated using the TOE LTPA key.) Propagated attributes Must be sent with a valid token (either an LTPA 2.0 token or an asserted identity token) Asserted identity Must be sent with server identification information (either user ID/password or X509Certificate) and the server’s ID must be present on a trusted ID list (the server 14 Although a ―No Authentication Method‖ option is available for certain cases such as access to the UDDI registry application, a remote caller is still subject to authentication via the BASIC Authentication Method, which is automatically enforced when application security is enabled. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 56 administrator IDs to which the server can support identity token submission) to establish trust in the sending server. The client’s asserted ID must be present in the target server’s user registry. (If sent with server ID/password, the TOE relies on the environment to authenticate the server ID and password. If sent with a server X509Certificate, the TOE relies on the environment to authenticate that the client certificate belongs to the server and was signed by a trusted certificate authority.) If the identification information is valid, the results of the identification function are successful. The TOE associates identification attributes with the caller. These attributes include the user ID of the caller and all groups ID of which the user is a member. If the remote caller does not provide identification information, the TOE returns an error to the caller. If the remote caller provides invalid identification information, the TOE returns an error to the caller. 6.1.1.3 Remote JMS Identification (Ident.3) This security function identifies a remote caller when the TOE is configured to use the Built-In JMS Provider Resource and the remote caller attempts to identify itself to the remotely accessible, proprietary messaging interface. The protocol used by this interface (JFAP) is used internally by:  The application Java client, to provide access to the sensitive JMS resources of the TOE to client applications.  Peer servers (messaging engines) belonging to the same ‗bus‘, to propagate the sensitive JMS resources around the messaging infrastructure. The TOE will not process requests that access the protected resources unless the remote caller has previously successfully identified itself, using an identification request. The following sensitive resources can be accessed using the remote JMS interface of the TOE: o Buses, queues, topic spaces and topics When the remote caller issues an identification request, it provides either a user ID and password, an LTPA 2.0 token, to the TOE. If the remote caller provides a user ID and password, the TOE then queries the environment to determine whether the user ID and password is valid. (The user ID and password are valid if they are configured for a user or are both null, indicating an anonymous login. If invalid, the TOE will reject the identification request. If the remote caller provides an LTPA token, the TOE determines if the LTPA token is valid. An LTPA token is valid when it is signed with the configured LTPA key and the date in the token has not expired. (The TOE relies on the environment to authenticate the signature in the LTPA token was generated using the TOE LTPA key.) If invalid, the TOE will reject the identification request. 6.1.1.4 Remote Web Services Re-Identification (Ident.4) This security function attempts to re-identify a remote caller when the remote caller attempts to access a sensitive resource using the remote web services interface of the WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 57 TOE. A remote caller can access only one type of sensitive resource using a remote web services interface, which is in a deployed enterprise bean that is configured as a web services endpoint. Before a request from a remote caller gets to a remote web services interface of the TOE, the request passes through a remote HTTP/S (Ident.1) of the TOE. Therefore, the caller already has been identified by the Ident.1 identification function of the TOE before being processed by this security function (Ident.4). This security function attempts to re- identify the caller. Re-identification occurs using an identification token, and optionally also a trust token. An identification token is a data structure that is used to pass a username token, x.509 token, or LTPA 2.0 token.  A username token is a data structure that contains a user name and password.  An x.509 token is a data structure that contains an x.509 certificate. Note that x.509 tokens are cached by default to avoid certificate path validation to improve performance.  An LTPA token is a data structure that contains a user id. A trust token is a data structure used to pass a username token. A username token contains a user name and password. The specific behaviour of this security function depends on the configuration of the web services endpoint for this security function. In the evaluated configuration, five configurations are supported. The following table defines the five configurations. The meanings of the columns are as follows:  Configuration Identifier—an identifier number that is referenced in the next table.  Identification Token Required—indicates whether the Java client is required to send an identification token with the request.  Identification Token Type—indicates the type and contents of the identification token.  Asserted Identity—indicates whether the identification token contains an asserted identity.  Trust Token Required—indicates whether the Java client is required to send a trust token, in addition to the Identification Token, with the request.  Trust Token Type—indicates the type and contents of the trust token Configuration Identifier Identification token required? Identification token type Asserted identity? Trust token required? Trust token type 1 No not applicable not applicable not applicable not applicable 2 Yes username token containing user ID yes yes user name token containing user ID and WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 58 password 3 Yes user name token containing user ID and password no no not applicable 4 Yes X509 token containing client certificate no no not applicable 5 Yes LTPA token no no not applicable For configuration 1, the TOE does not attempt to re-identify the remote caller, so the identification attributes inserted by the Ident.1 security function are not replaced. For all other configurations (configurations 2-5), the TOE attempts to obtain new identification information from the caller, determine whether the information is valid, and, if valid, replace the identification attributes of the caller with new identification attributes. The following table defines how the TOE does this. The meanings of the columns are as follows:  Configuration identifier—a reference to a configuration identifier number in the previous table.  Logic for determining if information is valid—the logic that the TOE uses to determine whether the information in the identification token is valid.  Associated IDs if valid—the IDs that are associated with the Java client connection if the TOE determines that the information in the identification token is valid. Configuration Identifier Logic for determining if information is valid Associated IDs if valid 2 (1)User registry must contain an entry with a user ID and password that matches the user ID and password in the trust token. (The TOE relies on the environment to authenticate the user ID and password.) (2) The user ID from the trust token must be in the trusted list of the target server.15 * the user ID contained in the username identification token * all group IDs that are configured in the user registry with the user ID as a member. 3 User registry must contain an entry with a user ID and password * the user ID contained in the username 15 The case (1) for user ID and password check will generate an audit event for both positive and negative input. The case (2) for testing whether a user ID from the trust token is in the trusted list will not generate an audit event. This check does not indicate if user information provided is correct, but instead tests whether a validated user is in a list of trusted users. If the case (2) fails, the attempted invocation will also fail, thereby preventing untrusted calls WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 59 that matches the user ID and password in the identification token. (The TOE relies on the environment to authenticate the user ID and password.) identification token * all group IDs that are configured in the user registry with the user ID as a member. 4 * If the user registry is in LDAP, the client certificate must contain a subject DN that matches a DN in the LDAP user registry. * If the user registry is in the local OS, the client certificate must contain a common name (CN) from a subject DN that matches a user ID in the user registry. (The TOE relies on the environment to authenticate that the client certificate belongs to the Java client and was signed by a trusted certificate authority.) * the user ID contained in the user registry that is mapped to the client certificate in the x509 identification token * all group IDs that are configured in the user registry with the user ID as a member. 5 (1) Signature of token must be valid and (2) Token must not have an expired date. (The TOE relies on the environment to authenticate that the signature in the token was generated using the TOE LTPA key.) * user ID contained in the LTPA identification token * all group IDs that are configured in the user registry with the user ID as a member. If the TOE is unable to obtain the required identification attributes from the caller or if the identification attributes are not valid, the TOE returns an error and does not process the caller request. 6.1.1.5 Remote HA Manager Identification (Ident.5) This security function determines whether a remote caller has a trusted identity when the remote caller attempts to access a sensitive resource by means of a remote High Availability (HA) Manager interface. The remote caller can access only one sensitive resource by means of a remote HA Manager interface, which is a remote HA Manager connection. When a remote caller issues a connection request to the remote HA Manager interface, first, the interface validates the LTPA token. (The TOE relies on the environment to authenticate that the signature in the LTPA token was generated using the TOE LTPA key.) If the LTPA token is invalid, the security function terminates the connection. 6.1.1.6 Run-As Identification (Ident.6) This security function is processed each time the TOE invokes a method in a deployed web server application or enterprise bean on behalf of a remote caller. Before a request from a remote caller gets to invoke the Run-As Identification function, the request passes through a remote HTTP/S (Ident.1) or Remote ORB Identification function (Ident.2) of the TOE. Therefore, the caller already has been identified by the Ident.1 or Ident.2 identification function of the TOE before being processed by this security function WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 60 (Ident.6). This security function associates identification attributes with the invoke method. To determine which identification attributes to associate with the method, the TOE uses the configured ―Run-As‖ identity or, if no Run-As identity is configured, the identification attributes of the remote caller. The configured Run-As identity can be configured for any of the following: o Client o System (applicable only for a method in an enterprise bean) o Specified Identity If Client is configured, the TOE associates with the method the identification attributes of the remote caller that requested the method. If System is configured, the TOE associates with the method the identification attributes of the TOE component in which the method resides. If Specified Identity is configured, the user ID and password of this specified user must also be configured. The TOE uses the environment to determine whether the user ID and password are valid. If the user ID and password are valid, the TOE uses the environment to get the identification attributes of the user and associates with the method these attributes (which include the user ID of the user and all group IDs of which the user is a member). If not valid, the identification attributes of the remote caller are used. 6.1.1.7 Remote WS-Transactions Identification (Ident.7) This security function attempts to identify a remote caller when the remote caller attempts to access a sensitive transaction using the remote Web Services Transactions (WS- Transactions) interface of the TOE. When the remote caller uses this interface, the TOE requires the remote caller to identify itself using an LTPA 2.0 token. The TOE then determines whether the LTPA token is valid based on the response returned by the operational environment. The LTPA token is valid if it is signed by the LTPA key of WebSphere Application Server and the date in the token has not expired. If not valid, the TOE does not process the caller request. Otherwise, the TOE uses the environment to get all group IDs of which the caller is a member and associates the user ID and any group IDs with the caller. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 61 6.1.2 Access Control (AC) The following describes the TOE access control security functions. 6.1.2.1 Protection of Methods and HTML pages in Deployed Web Server Applications (AC.1) This function controls access to the following sensitive resources: o Methods and HTML pages in deployed web server applications This protects a method or HTML page in a deployed web server application from being invoked by an unauthorized remote caller. When a remote caller issues a request to a method or HTML page in a deployed web server application, the TOE invokes the method or HTML page on behalf of the caller if one of the following conditions are true:  A user or group ID of the user is mapped to a role that has permission to access the method or HTML page.  The special group ID of ―Everyone‖ is mapped to a role that has permission to access the method or HTML page.  The special group ID of ―AllAuthenticatedUsers‖ is mapped to a role that has permission to access the method or HTML page and the remote caller has been successfully identified.  The method is not configured with a permission (security constraint). If none of these conditions are true, the TOE does not invoke the method or HTML page. The application roles and permissions (if any) are configured before the Web Server application is deployed into the evaluated configuration. An application developer specifies application roles and permissions through deployment descriptors, a standard Java EE construct. Typically, a developer uses an assembly tool from an integrated development environment for the specification. The application mappings are described in the System Management functions. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 62 6.1.2.2 Protection of Methods in Deployed Enterprise Beans (AC.2) This function controls access to the following sensitive resources: o Method in deployed enterprise beans (including methods that are deployed as web services endpoints) This protects a method in deployed enterprise bean (including a method that has been deployed as a web services endpoint) from being invoked by an unauthorized remote caller. When a remote caller issues a request to a method in a deployed enterprise bean (including a method that has been deployed as a web services endpoint), the TOE invokes the method on behalf of the caller if one of the following conditions are true:  A user or group ID of the user is mapped to a role that has permission to access the method.  The special group ID of ―Everyone‖ is mapped to a role that has permission to access the method  The special group ID of ―AllAuthenticatedUsers‖ is mapped to a role that has permission to access the method and the remote caller has been successfully identified.  The method is not configured with a permission. If none of these conditions are true, the TOE does not invoke the method. The application roles and permissions (if any) are configured before the Enterprise Beans is deployed into the evaluated configuration. An application developer specifies application roles and permissions through deployment descriptors, a standard Java EE construct. Typically, a developer uses an assembly tool from an integrated development environment for the specification. The application mappings are described in the System Management functions. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 63 6.1.2.3 Protection of TOE Configuration Data, Files, and TOE Runtime State (AC.3) This function controls access to the following sensitive resources: o TOE configuration data o TOE files o TOE runtime state This protects the TOE configuration data and TOE runtime state from a read or write operation that is initiated by an unauthorized remote caller. When a remote caller requests the TOE to read or write configuration data or runtime state, the TOE performs the operation only if one of the following conditions is true:  A user or group ID of the user is mapped to a role that has permission to perform the operation.  The special group ID of ―Everyone‖ is mapped to a role that has permission to perform the operation.  The special group ID of ―AllAuthenticatedUsers‖ is mapped to a role that has permission to perform the operation and the remote caller has been successfully identified.  The special group ID of ―PrimaryAdmin‖ is mapped to a role that has permission to perform the operation and the remote caller is the primary administrator ID.  The special group ID of ―Server ID‖ is mapped to a role that has permission to perform the operation and the remote caller is the server ID. If none of these conditions are true, the TOE does not perform the operation. The following are the administration roles and permissions. Administration Role Permission Monitor Permission to read configuration attributes and runtime state, and to manage TOE files. Operator Monitor permission plus permission to affect runtime state, and to manage TOE files. Permission to modify the attribute that stores the list of registered UDDI publishers. Configurator Monitor permission plus permission to: Modify attributes that map user/group IDs to application-defined roles, messaging roles, naming roles, and UDDI roles. Modify the attribute that sets the inherit defaults flag for each Messaging queue, topic space, and topic. Modify the attribute that sets the topic space WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 64 access check flag for each Messaging topic space. Modify the attribute that maps a user ID and password to a run-as role. Modify the attribute that sets the inherit Sender flag for new topics. Modify the attribute that sets the inherit Receiver flag for new topics. Administrator Operator and Configurator permission. Deployer Operator plus Configurator permission on applications. AdminSecurityManager Permission to modify attributes that map user/group IDs to administration roles. Auditor Permission to: Enable/Disable audit sub-system and Review audit records. The administration mappings are described in the SM functions. 6.1.2.4 Protection of TOE Naming Directory (AC.4) This function controls access to the following sensitive resources: o TOE naming directory This protects the TOE naming data from a read or write operation that is initiated by an unauthorized remote caller. When a remote caller requests the TOE to read from or write to the TOE naming directory, the TOE performs the operation only if one of the following conditions is true:  A user or group ID of the user is mapped to a role that has permission to perform the operation.  The special group ID of ―Everyone‖ is mapped to a role that has permission to perform the operation.  The special group ID of ―AllAuthenticatedUsers‖ is mapped to a role that has permission to perform the operation and the remote caller has been successfully identified.  The special group ID of ―PrimaryAdmin‖ is mapped to a role that has permission to perform the operation and the remote caller is the primary administrator ID.  The special group ID of ―Server ID‖ is mapped to a role that has permission to perform the operation and the remote caller is the server ID. If none of these conditions are true, the TOE does not perform the operation. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 65 The following are the naming roles and permissions: Naming Role Permission COSNamingRead Permission to read from the naming directory COSNamingWrite COSNamingRead permission plus permission to write to the naming directory COSNamingCreate COSNamingWrite permission plus permission to insert entries in the naming directory COSNamingDelete COSNamingCreate permission plus permission to delete entries in the naming directory The naming mappings are described in the SM functions. 6.1.2.5 Protection of Transactions and Activities (AC.5) This function allows a remote caller to invoke a TOE operation that affects a transaction or activity only if the TOE has identified the remote caller, this identity has been validated, and the authenticated identity of the remote caller is mapped to the administrator role. Transactions and activities are invoked via the Transactions interface, which is accessible through the remote ORB or HTTP/S interface. 6.1.2.6 Protection of Messaging Destinations (AC.6) Note: The product documentation describes an additional messaging role, identity adopter, which is not mentioned in this document. The reason the identity adopter role is not mentioned in this document is because this role is not permitted to be configured in the evaluated configuration (as specified in the User Guidance document) and, therefore, this role is not relevant to the evaluation. This security function protects the messaging resources (local bus, queue destination, temporary destination, topic space, topic space root, and topics) of the Built-in JMS Provider from a connect, send, receive, browse, or create operation that is initiated by an unauthorized remote caller. When a remote caller requests the TOE to perform a connect, send, receive, browse, or create, operation on messaging resource of the Built-in JMS Provider, the TOE evaluates the following conditions and performs the operation only if one of them is true (the conditions are evaluate in the order below, until one is discovered to be true, if any): 1. The special group ID of ―Everyone‖ is mapped to a role that has permission to perform the operation. Use of this group for any messaging role is not permitted in the TOE. (In the User Guidance document, the administrator is instructed not to map the special group of ―Everyone‖ to a role that has permission to a Messaging operation, so this condition should never occur in the evaluated configuration. If ―Everyone‖ is mapped to a role with permission, any caller will be allowed to perform the requested operation.) 2. The user ID is mapped to a role that has permission to perform the operation. 3. The special group ID of ―AllAuthenticated‖ is mapped to a role that has permission to perform the operation and the remote caller has been successfully identified. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 66 4. At this point the user ID to group ID mappings are determined. A group ID to which the user belongs is mapped to a role that has permission to perform the operation. In addition to these conditions, the TOE also takes into consideration any flags set that will require additional access checks or to inherit permissions. As such, if the inheritsDefaults flag is set, then the above conditions also take into account any User/Group ID to messaging role mappings that are inherited from the Default values. The inheritsDefaults flag is independently settable for each Queue and Topic Space destination. It informs the TOE to take into account all mappings configured for the Defaults values as well as for the target destination. For example, if the caller requests an operation on a target destination, the inheritsDefault flag is set, and the Defaults values contains a mapping between the user ID of the caller and a role with permission to the requested operation, the TOE will perform the requested operation. If the inheritSender flag is set, then the above conditions also take into account any User/Group ID to the Sender messaging role mappings that are inherited from the parent topic. The inheritSender flag is independently settable for each topic destination. It informs the TOE to take into account all mappings configured for Send role of the parent destination as well as the mappings configured for the target destination. For example, if the caller requests a send operation on a target destination, the inheritSender flag is set, and the parent destination contains a mapping between the user ID of the caller and the Send role, the TOE will perform the requested operation. If the inheritReceiver flag is set, then the above conditions also take into account any User/Group ID to the Receiver messaging role mappings that are inherited from the parent topic. The inheritReceiver flag is independently settable for each topic destination. It informs the TOE to take into acocunt all mappings configured for the Receive role of the parent destination as well as the mappings configured for the target destination. For example, if the caller requests a receive operation on a target destination, the inheritReceiver flag is set, and the parent destination contains a mapping between the user ID of the caller and the Receive role, the TOE will perform the requested operation. If the topicAccessCheck flag is set, then the above conditions also take into account any User/Group ID to messaging role mappings configured for each topic within a topic space, in addition to the role mappings configured on the Topic Space. The topicAccessCheck flag is independently settable for each topic space destination. For example, if the caller requests an operatoin on a topic and the topicAccessCheck flag is set, the TOE will take into account the mappings configured for the topic as well as the topic space. If none of these conditions are true, the TOE does not perform the operation. 6.1.2.7 Protection of UDDI Registry (AC.7) The UDDI Registry can be accessed by two remote interfaces: HTTP/S and ORB. This security function protects the UDDI Registry so that it can be accessed by remote callers only by means of the remote HTTP/S interface and so that only remote callers that the TOE has identified using the Ident.1 security function can perform a protected UDDI registry operation. The protected UDDI registry operations are: o All operations over HTTP on the o UDDI SOAP V1, V2, and V3 Publish API WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 67 o UDDI SOAP V3 Custody Transfer API o UDDI SOAP V3 Security API o All operations over the ORB interface on the o UDDI V2 Publish API When a remote caller issues a request to the TOE to access the UDDI registry by means of the remote ORB interface, the TOE always denies the request. When a remote caller issues a request to the TOE to access the UDDI registry by means of the remote HTTPS interface, the TOE will accept the request but if the request is to perform a protected UDDI registry operation, the TOE will perform the operation only if both of the following conditions are true: o The TOE has identified the user and validated this identity o The user is registered as a UDDI publisher. This means that the user is configured on the list of registered UDDI publishers. If all of these conditions are not true, the TOE will not perform the operation. The configuration of the user to role mappings are part of the evaluated configuration and are restricted to only those mappings defined within the evaluated configuration guidance. The configuration of users that are registered as UDDI publishers is also part of the evaluated configuration and may be configured as desired. 6.1.2.8 Protection of Location Service (AC.8) This function is not applicable to this version of the product. 6.1.2.9 Protection of Methods and Attributes in User MBeans (AC.9) This function controls access to the following sensitive resources: o Methods and Attributes in User MBeans This protects a method and attributes in User MBeans from being invoked by an unauthorized remote caller. When a remote caller issues a request to a method in a User Mbean, the TOE invokes the method on behalf of the caller if one of the following conditions are true:  A user or group ID of the user is mapped to a role that has permission to access the method.  The special group ID of ―Everyone‖ is mapped to a role that has permission to access the method  The special group ID of ―AllAuthenticatedUsers‖ is mapped to a role that has permission to access the method and the remote caller has been successfully identified.  The method is not configured with a permission. If none of these conditions are true, the TOE does not invoke the method. The application roles and permissions (if any) are configured before the User Mbean is deployed into the evaluated configuration. The Administration role mappings are described in the System Management functions. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 68 6.1.3 Security Management (SM) The following describes the TOE security management security functions. 6.1.3.1 Management of the Product Application Server (SM.1) SM.1.1 The TOE maintains the following roles: Administration roles:  Administrator  Configurator  Monitor  Operator  Deployer  AdminSecurityManager  Auditor Messaging roles:  Browser  Bus Connector  Creator  Receiver  Sender Naming roles:  COSNamingCreate  COSNamingDelete  COSNamingRead  COSNamingWrite UDDI roles:  SOAP_Publish_User  V3SOAP_CustodyTransfer_User_Role  V3SOAP_Publish_User_Role  V3SOAP_Security_User_Role  EJB_Publish_Role SM.1.2 The TOE maintains the security attributes:  Mappings of user/group IDs to application-defined roles WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 69  Mappings of user/group IDs to messaging roles  Mappings of user/group IDs to naming roles  Mappings of User/Group IDs to Roles Mapping to Administration Roles  Registered UDDI publishers  Audit On/Off SM.1.3 On initiation of the TOE by default, the following is configured for each of the security attributes defined in SM.1.2:  Mappings of user/group IDs to application-defined roles: Application-Defined Role Default user/group IDs to role mappings Each application-defined role None or defined by application developer  Mappings of user/group IDs to administration roles: Administration Role Default user/group IDs to role mappings Administrator16 Server ID, PrimaryAdmin User:WSADMIN,Group:CBCFG1 Configurator None Monitor None Operator None Deployer None Auditor17 Server ID, PrimaryAdmin 16 The default mapping for the Administrator role does not associate any users to the Administrator role. However, an internal mapping is defined which assigns each server identity (Server ID and PrimaryAdmin) to the administrator role so that server operations have sufficient privileges to execute. Yet, these internal mappings are not externally visible within the configuration for mapping users to the Administrator role. (The server ID and PrimaryAdmin are externally visible with the configuration, but the mapping of the server identity and PrimaryAdmin to the Administration role is not externally visible.) 17 The default mapping for the Auditor role does not associate any users to the Auditor role. However, an internal mapping is defined which assigns each server identity (Server ID and PrimaryAdmin) to the auditor role so that server operations have sufficient privileges to execute. Yet, these internal mappings are not externally visible within the configuration for mapping users to the Auditor role. (The server ID and PrimaryAdmin are externally visible with the WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 70 User:WSADMIN,Group:CBCFG1 AdminSecurityManager18 Server ID, PrimaryAdmin User:WSADMIN,Group:CBCFG1  Mappings of user/group IDs to naming roles: Naming Role Default user/group IDs to role mappings19 COSNamingCreate Server ID COSNamingDelete Server ID COSNamingRead Server ID, Everyone group ID COSNamingWrite Server ID  Mappings of user/group IDs to messaging roles: Messaging Role Default user/group IDs to role mappings Browser None Bus Connector None Creator None Receiver None Sender None  Registration of UDDI publishers: None  Audit: Off configuration, but the mapping of the server identity and PrimaryAdmin to the Auditor role is not externally visible.) 18 The default mapping for the AdminSecurityManager role does not associate any users to the AdminSecurityManager role. However, an internal mapping is defined which assigns each server identity (Server ID and PrimaryAdmin) to the AdminSecurityManager role so that server operations have sufficient privileges to execute. Yet, these internal mappings are not externally visible within the configuration for mapping users to the AdminSecurityManager role. (The server ID and PrimaryAdmin are externally visible with the configuration, but the mapping of the server identity and PrimaryAdmin to the AdminSecurityManager role is not externally visible.) 19 The default mapping for the Naming roles has the internal mapping defined which assigns each server identity (Server ID) to the naming role so that server operations have sufficient privileges to execute. Yet, this internal mappings is not externally visible within the configuration for mapping users to the Naming role. (The server ID is externally visible with the configuration, but the mapping of the server identity to the Naming role is not externally visible.) WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 71 SM.1.4 A caller in the Administrator or Configurator role can configure, via the Product wsadmin Tool, the following security attributes:  The attributes that map user/group IDs to messaging roles, and naming roles.  The attribute that sets the inherit defaults flag for each Messaging queue and topic space (inheritsDefaults).  The attribute that sets the topic space access check flag for each Messaging topic space (topicAccessCheck).  The attribute that sets the inherit Sender flag for new topics (inheritSender).  The attribute that sets the inherit Receiver flag for new topics (inheritReceiver). A caller in the Administrator, Configurator or Deployer role can configure, via the Product wsadmin Tool, the following security attributes:  The attributes that map user/group IDs to application-defined roles, messaging roles, and naming roles.  The attribute that maps a user ID and password to a run-as role. A caller in the Monitor role can view the attributes that map users and groups to naming roles. A caller in the Administrator or Operator role can configure, via the Product wsadmin Tool, the following security attribute:  The attribute that stores the list of registered UDDI publishers. A caller in the AdminSecurityManager role can configure, via the Product wsadmin Tool, the following security attribute:  The attributes that map user/group IDs to administration roles.  The attribute that turns audit On and Off. A caller in the Auditor role can enable and disable the security audit function. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 72 6.1.4 Audit (Aud) AUD.1 The TOE audits each of the following events:  Startup of the audit function  Shutdown of the audit function  Each use of user identification mechanisms defined in Section 2.3.1 of this document  Each attempt to access one of the sensitive resources defined in Section 2.3.2 of this document. Each audit record generated by the TOE contains the following information:  A timestamp containing the date and time of the event  Type of event (the object and operation being requested)  Subject (the user ID of the caller)  Outcome (Success or failure and an indication of whether the failure occurred because the user is not authorized) The generated audit records are written into a file in the hosting operating system. The contents of the file can be reviewed through the TOE (see AUD.2) or using tools available within the operating system. AUD.2 The TOE includes audit services that are accessible only by an Auditor. Using these services, the Auditor can review (in human-readable form) all stored audit records and can also elect to enable or disable the security audit function. The TOE relies on the operational environment for audit record storage. The operating system files containing audit records are assumed to be protected to prevent unauthorized or inappropriate access by means provided by other than the TOE. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 73 7 Rationale This chapter presents the evidence used in the ST evaluation and supports the claims that the ST is a complete and cohesive set of requirements. 7.1 Correlation of Threats, Policies, Assumptions and Objectives The following matrix provides a correspondence of the threats, policies, assumptions and objectives: Objectives: O.ACCESS O.IDENTIFY O.MANAGE O.AUDIT O.ADMIN O.APP O.ATTR O.AUTH O.TIMESTAMP O.FILES O.PROTECT T.ACCESS_RES x x x x x T.ACCESS_TOE x x x x x T.APP x x x T.NETWORK x x x P.ACCESS x x x x x A.ADMIN x A.APP x x A.AUTH x A.PROTECT x A.TIMESTAMP x A.STORAGE x 7.2 Security Objectives Rationale This section demonstrates that the security objectives stated in Section 4 of this ST are traceable to all of the aspects identified in the TOE security environment and are suitable to cover them. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 74 7.2.1 Threats This section provides evidence demonstrating coverage of the threats by both the IT and non-IT security objectives. [T.ACCESS_RES] A caller gains access to a resource without the correct authority to access that resource. The objective O.ACCESS counters this directly by ensuring that only those callers with the correct authority can access an object. This is supported by O.MANAGE, which ensures that privileged actions are performed effectively. The following environmental objectives support O.ACCESS in countering the threat:  O.ATTR – ensures that the correct user to group association is maintained, thus assisting in enforcing resource access restrictions since the TOE assigns roles to both users and groups.  O.PROTECT – ensures that no objects can be accessed by the cabling between the workstations.  O.AUDIT – ensures that all events relevant to O.PROTECT are audited. [T.ACCESS_TOE] An unidentified caller gains access to a protected resource. O.IDENTIFY is the primary objective that counters this threat, by ensuring that all callers are identified and authenticated before they can access a protected resource. O.MANAGE also supports this by ensuring effective management of the TOE. The following environmental objectives support O.IDENTIFY in countering the threat:  O.ATTR – ensures that a UID is maintained thus allowing correct operation of the identification functionality;  O.PROTECT – ensures that an unidentified caller cannot gain access to the TOE via the cabling between the workstations;  O.AUDIT – ensures that all events relevant to O.PROTECT are audited. [T.APP] The applications and operating system that the TOE interfaces compromises the TOE. It is essential that the administrator manages the applications interfacing to the TOE in a secure manner, so that vulnerabilities do not exist, which may lead to compromise of the TOE. The objectives O.APP, O.PROTECT, and O.AUDIT all ensure that the operating system is managed in a secure manner. [T.NETWORK] Data transferred between workstations is disclosed to, or modified by unidentified callers or processes, either directly or indirectly. Administrators must ensure that data transferred between workstations i.e. along network cabling, is suitably protected against physical or other (e.g. Sniffing) attacks that may result in the disclosure, modification or delay of information transmitted between workstations. Objective O.PROTECT and O.AUDIT ensures that this is achieved. O.APP WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 75 ensures that the protocols used in the transmission of data have been correctly configured within the operating systems. 7.2.2 Security Policy This section provides evidence demonstrating coverage of the organisational security policy by both the IT and non-IT security objectives. [P.ACCESS] The right to access a resource is determined on the basis of association of user or group IDs to roles and of roles to resources. This policy is implemented through the objective O.ACCESS, which provides the means of controlling access to objects by users and processes. O.MANAGE supports this policy by the administrators ensuring that the policy is maintained. The environmental objectives O.ADMIN and O.APP further support the policy by ensuring that the interfacing applications are configured in a secure manner so that no vulnerability may exist that enables an unauthorised caller to gain an authorised identity. O.ATTR ensures that the association of roles to resources is maintained, and thus supporting this policy. 7.2.3 Assumptions This section provides evidence demonstrating coverage of the assumptions by both the IT and non-IT security objectives. [A.ADMIN] It is assumed that there are one or more competent individuals that are assigned to manage the TOE and the security of the information it contains. Such personnel are assumed not to be careless, willfully negligent or hostile. It also is assumed that this individual will comply with all the guidelines specified in the User Guidance document. O.ADMIN is the primary objective that meets this assumption, which ensures that the administrator is a competent and trustworthy person whom is capable of managing the TOE in a secure manner. [A.APP] It is assumed that the applications and operating system that the TOE interfaces, will not compromise the security of the TOE and where applicable, that they have been configured in accordance with manufacturer’s installation guides and/or its evaluated configuration. It also is assumed that the developers of all trusted user applications (user web server applications and user enterprise beans), resource adapters, and providers will comply with all the guidelines and restrictions specified in the User Guidance document. O.APP is the primary environmental objective that satisfies the assumption. This ensures that the administrator installs and configures the supporting operating systems in accordance with:  The manufacturers instructions; and  Any evaluated configurations were applicable. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 76 This also ensures that the developers of the applications comply with the guidelines defined in this document. O.ADMIN supports this by ensuring that the Administrator is a competent and trustworthy person and that the users have been set up appropriately. [A.AUTH] It is assumed that the operational environment supporting the TOE provides at least one of the supported authentication mechanisms identified within the evaluated configuration of the TOE. O.AUTH is the primary environmental objective that satisfies the assumption. This ensures that at least one or more authentication mechanisms are present within the environment to authenticate remote callers needing to access the TOE resources. Section 6.1.1 Identification and Re-Identification (Ident) lists TOE identification functions. For each identification function, the section describes corresponding authentication services provided by the operational environment that the TOE may invoke. The authentication services used in a particular instance depend on which services are available in the operational environment and how the TOE is configured. [A.TIMESTAMP] It is assumed that the operational environment provides accurate timestamp information. O.TIMESTAMP is the environmental objective that satisfies the assumption. This ensures the availability of accurate timestamp information. [A.STORAGE] It is assumed that the operational environment supporting the TOE provides the means to store, protect, and access data within files. O.FILES is the environmental objective that satisfies the assumption. This ensures that the operational environment will provide the means to store, protect, and retrieve data using files. [A.PROTECT] It is assumed that all software and hardware, including network and peripheral devices, have been approved for the transmittal of protected data. Such items are to be physically protected against threats to the confidentiality and integrity of the data. The environmental objective O.PROTECT ensures that the network cabling is suitably protected against threats of modification, tampering or interruption of the data transmitted via this medium. Also, it is assumed that all hardware used within the operating environment is secured. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 77 7.3 Security Requirements Rationale 7.3.1 Security Functional Requirements Rationale This section demonstrates that the functional components selected for the TOE provide complete coverage of the defined security objectives. The mapping of components to security objectives is illustrated in the table below. Security Objective Functional Component O.ACCESS Subset Access Control (FDP_ACC.1a, FDP_ACC.1b, FDP_ACC.1c, FDP_ACC.1d, FDP_ACC.1e, FDP_ACC.1f, FDP_ACC.1g, FDP_ACC.1i) Security Attribute Based Access Control (FDP_ACF.1a, FDP_ACF.1b, FDP_ACF.1c, FDP_ACF.1d, FDP_ACF.1e, FDP_ACF.1f, FDP_ACF.1g, FDP_ACF.1i) User-subject binding (FIA_USB.1) Management of Security Attributes (FMT_MSA.1(a)(b)(c)) Static Attribute Initialisation (FMT_MSA.3(a)(b)(c)(d)) O.IDENTIFY Perform Actions On Behalf Of Another User (FIA_OBO.EXP.1) Timing of Identification (FIA_UID.1) Timing of Invoked Authentication (FIA_UAU.EXP.1) O.MANAGE Management of Security Attributes (FMT_MSA.1(a)(b)(c)) Static Attribute Initialisation (FMT_MSA.3(a)(b)(c)(d)) Specification of Management Functions (FMT_SMF.1) Security Roles (FIA_ATD.1, FMT_SMR.1) O.AUDIT Audit data generation (FAU_GEN.1, FAU_GEN.2, FAU_SAR.1, FAU_SAR.2, FMT_MOF.1) [O.ACCESS] The TOE must ensure that only those callers with the correct authority are able to access an object. Association [FIA_USB.1] of user security attributes must be performed in order that the access control mechanism can operate. The access control mechanism must have a defined scope of control [FDP_ACC.1a, FDP_ACC.1b, FDP_ACC.1c, FDP_ACC.1d, FDP_ACC.1e, FDP_ACC.1f, WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 78 FDP_ACC.1g, and FDP_ACC.1i] with defined rules [FDP_ACF.1a, FDP_ACF.1b, FDP_ACF.1c, FDP_ACF.1d, FDP_ACF.1e, FDP_ACF.1f, FDP_ACF.1g, and FDP_ACF.1i]. Authorised callers [FMT_SMR.1] must be able to control who has access to the objects [FMT_MSA.1 (a) (b) (c)]. Protection of these objects must be continuous, starting from object creation [FMT_MSA.3 (a) (b) (c) (d)]. [O.IDENTIFY] The TOE must ensure that all callers are identified and authenticated before they access a protected resource. The TOE provides a user the ability to be identified as another user to perform a specific action on behalf of that user [FIA_OBO.EXP.1]. Before callers can access a protected resource, they need to be identified [FIA_UID.1] and authenticated [FIA_UAU.EXP.1]. The TSF invokes authentication services provided by the operational environment to authenticate user identities. [O.MANAGE] The TOE must allow administrators to effectively manage the TOE and that this is only performed by authorised callers. The TSF must restrict the ability to manage the TOE to authorised administrators [FMT_MSA.1 (a) (b) (c)] with default values [FMT_MSA.3 (a) (b) (c) (d)] and the security attributes [FMT_MSA.1 (a) (b) (c)]. [FMT_SMF.1] specifies the management functions provided by the TOE. [FMT_SMR.1] defines roles, and [FIA_ATD.1] associates roles with users, in order that the TOE is managed effectively. [O.AUDIT] The TOE must provide administrators with a mechanism for auditing access control decisions. The TOE provides an audit data generation function for identification and access control decisions [FAU_GEN.1 and FAU_GEN.2]. The TOE provides the means for an Auditor, and only an Auditor, to review the generated audit records [FAU_SAR.1 and FAU_SAR.2]. The audit function can be enabled and disabled, but only by an Auditor [FMT_MOF.1]. 7.3.2 Security Assurance Requirements Rationale This ST contains assurance requirements from the CC EAL4, augmented with ALC_FLR.2 (Flaw Reporting Procedures) assurance package. The EAL chosen is based on the impact that the statements of the security environment and objectives within this ST have on the assurance level. The administrator shall be capable of managing the TOE such that the security is maintained (O.ADMIN) particularly within the operating system that the TOE relies (O.APP), and that the physical environment protects the TOE from any potential vulnerability (O.PROTECT). This EAL level also provides a moderate to high level of independently assured security through analysis of the functional specification, guidance documentation, the high-level and low-level design of the TOE, and a subset of the implementation to understand the security behaviour of the TOE. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 79 While the TOE includes extended security functional requirements, the assurance requirements selected provide adequate assurance to ensure that the design and implementation details of these extended security functionalities are documented and tested. The assurance requirements selected also ensure that the extended security functional requirements are stated in a manner in which compliance can be demonstrated. Given the amount of assurance required to meet the TOE environment and the intent of EAL4, this assurance level was considered most applicable for the TOE described within this ST. EAL4, augmented with ALC_FLR.2 (Flaw Reporting Procedures), was chosen to provide further assurance in the flaw remediation procedures provided by the developers. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 80 7.3.3 SFR Dependencies The matrix below identifies all of the dependencies of the SFRs included in the ST. Only those SFRs that have a dependency, or are depended upon are shown in the table. FAU_GEN.1 FAU_SAR.1 FDP_ACC.1a FDP_ACC.1b FDP_ACC.1c FDP_ACC.1d FDP_ACC.1e FDP_ACC.1f FDP_ACC.1g FDP_ACC.1i FDP_ACF.1a FDP_ACF.1b FDP_ACF.1c FDP_ACF.1d FDP_ACF.1e FDP_ACF.1f FDP_ACF.1g FDP_ACF.1i FIA_ATD.1 FIA_UID.1 FMT_MSA.1a FMT_MSA.1b FMT_MSA.1c FMT_MSA.3a FMT_MSA.3b FMT_MSA.3c FMT_MSA.3d FMT_SMF.1 FMT_SMR.1 FPT_STM.1 FAU_GEN.1 o FAU_GEN.2 x x FAU_SAR.1 x FAU_SAR.2 x FDP_ACC.1a x FDP_ACC.1b x FDP_ACC.1c x FDP_ACC.1d x FDP_ACC.1e x FDP_ACC.1f x FDP_ACC.1g x FDP_ACC.1i x FDP_ACF.1a x x FDP_ACF.1b x x FDP_ACF.1c x x FDP_ACF.1d x x FDP_ACF.1e x x FDP_ACF.1f x x FDP_ACF.1g x x x FDP_ACF.1i x x FIA_OBO.EXP.1 x FIA_UAU.EXP.1 x FIA_USB.1 x FMT_MOF.1 x x FMT_MSA.1a x x x x x x FMT_MSA.1b x x x x x FMT_MSA.1c x x x FMT_MSA.3a x x FMT_MSA.3b x x FMT_MSA.3c x x FMT_MSA.3d x x FMT_SMR.1 x The key to the symbols used, are: x required dependency WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 81 o unfulfilled dependency All dependencies are satisfied by the TOE, with the exception for the following SFRs: o FAU_GEN.1 is dependent on the availability of reliable time information for its audit records (i.e., FPT_STM.1). However, this information is obtained from the TOE environment rather than from the TOE itself and as such FPT_STM.1 is omitted from this ST. The TOE environment objective O.TIMESTAMP is intended to address this dependency. Note that while not an identified CC dependency the TOE environment objective O.FILES is intended to address the need for files used to store and potential access generated audit data. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 82 7.4 TOE Summary Specification Rationale This section demonstrates that the TOE security functions and assurance measures are suitable to meet the TOE security requirements. 7.4.1 TSF correspondence to SFRs This section demonstrates that the combination of the specified TSFs works together so that the SFRs are satisfied. The matrix below shows the TOE security functions, which together satisfy each SFR element. AC.1 AC.2 AC.3 AC.4 AC.5 AC.6 AC.7 AC.9 Ident.1 Ident.2 Ident.3 Ident.4 Ident.5 Ident.6 Ident.7 SM.1.1 SM.1.2 SM.1.3 SM.1.4 Aud.1 Aud.2 FAU_GEN.1 X FAU_GEN.2 X FAU_SAR.1 X FAR_SAR.2 X FDP_ACC.1a X FDP_ACC.1b X FDP_ACC.1c X FDP_ACC.1d X FDP_ACC.1e X FDP_ACC.1f X FDP_ACC.1g X FDP_ACC.1i X FDP_ACF.1a X FDP_ACF.1b X FDP_ACF.1c X FDP_ACF.1d X FDP_ACF.1e X FDP_ACF.1f X FDP_ACF.1g X FDP_ACF.1i X FIA_ATD.1 X FIA_OBO.EXP.1 X FIA_UID.1 X X X X X X FIA_UAU.EXP.1 X X X X X X X FIA_USB.1 X X X X X X FMT_MOF.1 X FMT_MSA.1(a)(b)(c) X FMT_MSA.3(a)(b)(c)(d) X FMT_SMF.1 X FMT_SMR.1 X WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 83 7.4.2 TSF correspondence Rationale This section provides rationale describing how the combination of the specified TSFs works together so that the SFRs are satisfied. SFRs TSFs FAU_GEN.1 AUD.1 is suitable to meet FAU_GEN.1 by ensuring that the TOE audits the startup and shutdown of the audit function and all attempts to access resources protected by the TOE and that each record contains date and time of the event, the subject of the event, and the outcome of the event. FAU_GEN.2 AUD.1 is suitable to meet FAU_GEN.2 by ensuring that each audit record is traceable back to the user responsible for that event. FAU_SAR.1 AUD.2 is suitable to meet FAU_SAR.1 by ensuring that the Auditor can review the generated audit records in human-readable form. FAU_SAR.2 AUD.2 is suitable to meet FAU_SAR.2 by ensuring that access to audit records is limited to Auditors. FDP_ACC.1a AC.1 is suitable to meet FDP_ACC.1a by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to protected methods of web server applications using operations defined by an application developer. However the operations must conform to the application developer guidance supplied for the evaluated configuration. FDP_ACC.1b AC.2 is suitable to meet FDP_ACC.1b by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to protected methods of enterprise beans using operations defined by an application developer. However the operations must conform to the application developer guidance supplied for the evaluated configuration. FDP_ACC.1c AC.3 is suitable to meet FDP_ACC.1c by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to TOE configuration data, TOE files, or TOE runtime state using the set of operations defined. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 84 SFRs TSFs FDP_ACC.1d AC.4 is suitable to meet FDP_ACC.1d by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to TOE naming directory using the set of operations defined. FDP_ACC.1e AC.5 is suitable to meet FDP_ACC.1e by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to transaction and activities using the set of operations defined. FDP_ACC.1f AC.6 is suitable to meet FDP_ACC.1f by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to the local bus, queue destination, temporary destination, topic space, topic space root, and topics using the set of operations defined. FDP_ACC.1g AC.7 is suitable to meet FDP_ACC.1g by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to protected resources of the UDDI registry directory using the set of operations defined. FDP_ACC.1i AC.9 is suitable to meet FDP_ACC.1i by ensuring that the TOE enforces an access control security function policy for remote callers requesting access to user MBeans using the set of operations defined. FDP_ACF.1a AC.1 is suitable to meet FDP_ACF.1a by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to protected methods of web server applications using operations defined by an application developer, based on security attributes also defined by an application developer. However the operations and security attributes defined must conform to the application developer guidance supplied for the evaluated configuration. FDP_ACF.1b AC.2 is suitable to meet FDP_ACF.1b by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to protected methods of enterprise beans using operations defined by an application developer, based on security attributes also defined by an application developer. However the operations and security attributes defined must conform to the application developer guidance supplied for the evaluated configuration. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 85 SFRs TSFs FDP_ACF.1c AC.3 is suitable to meet FDP_ACF.1c by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to TOE configuration data, TOE files, or TOE runtime state using the set of defined operations, based on the security attributes identified. The security attributes of the TOE configuration data, TOE files, or TOE runtime state are identified as the roles belonging to the Administration roles group. These roles defined are hard-coded with a specific level of access which can only be granted by being mapped to the role. The security attributes of the remote callers include the User/Group ID to role mapping. FDP_ACF.1d AC.4 is suitable to meet FDP_ACF.1d by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to the TOE naming directory using the set of defined operations, based on the security attributes identified. The security attributes of the TOE naming directory are identified as the roles belonging to the Naming roles group. These roles defined are hard-coded with a specific level of access which can only be granted by being mapped to the role. The security attributes of the remote callers include the User/Group ID to role mapping. FDP_ACF.1e AC.5 is suitable to meet FDP_ACF.1e by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to transactions and activities using the set of defined operations, based on the security attributes identified. The security attributes of the transactions and activities are identified as the Administrator role. This role is hard-coded with a specific level of access which can only be granted by being mapped to the role. The security attributes of the remote callers include the User/Group ID to role mapping. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 86 SFRs TSFs FDP_ACF.1f AC.6 is suitable to meet FDP_ACF.1f by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to the local bus, queue destination, temporary destination, topic space, topic space root, and topics using the set of defined operations, based on the security attributes identified. The security attributes of the local bus, queue destination, temporary destination, topic space, topic space root, and topics are identified as the roles belonging to the Messaging roles group. These roles defined are hard- coded with a specific level of access which can only be granted by being mapped to the role. The security attributes of the remote callers include the User/Group ID to role mapping. FDP_ACF.1g AC.7 is suitable to meet FDP_ACF.1g by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to protected resources of the UDDI registry directory using the set of defined operations, based on the security attributes identified. The security attributes of the protected resources of the UDDI registry directory are identified as the list of registered UDDI publishers and the role belonging to the UDDI roles group. This role is hard- coded with a specific level of access which can only be granted by being mapped to the role. The security attributes of the remote callers include the User/Group ID to role mapping. FDP_ACF.1i AC.9 is suitable to meet FDP_ACF.1i by ensuring that the TOE enforces an access control policy which permits or denies remote callers requesting access to protected methods and attributes in user MBeans using the set of defined operations, based on the security attributes identified. The security attributes are identified as the roles belonging to the Administration roles group. These roles are configured for MBean methods and attributes by the application developer. The application developer must conform to the guidance supplied for the evaluated configuration. FIA_ATD.1 SM.1.2 is suitable to meet FIA_ATD.1 by ensuring that roles are associated with users (directly or via their assigned groups). WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 87 SFRs TSFs FIA_OBO.EXP.1 Ident.6 is suitable to meet FIA_OBO.EXP.1 by ensuring that the TOE provides a means for a remote caller or application to be associated with an additional authenticated identity, in which operations may be performed on behalf of the additional authenticated identity. FIA_UID.1 Ident.1 is suitable to meet FIA_UID.1 by ensuring that the TOE uniquely identifies remote callers by the user ID associated with the remote caller when accessing the TOE through the remote HTTP/S interface for all methods or static web content is configured with a security constraint or for method or static web content not configured with the security constraint of the ―Everyone‖ role. Ident.2 is suitable to meet FIA_UID.1 by ensuring that the TOE uniquely identifies remote callers by the user ID associated with the remote caller when accessing the TOE through the remote ORB interface. Ident.3 is suitable to meet FIA_UID.1 by ensuring that the TOE uniquely identifies remote callers by the user ID associated with the remote caller when accessing the TOE through the remote JMS interface. Ident.4 is suitable to meet FIA_UID.1 by ensuring that the TOE re-identifies a remote caller‘s user ID from either a username token, x509 token, or LTPA 2.0 token when accessing the TOE through either the remote HTTP/S interface. Ident.5 is suitable to meet FIA_UID.1 by ensuring that the TOE uniquely identifies remote callers by the user ID associated with the remote caller as it is supplied within the LTPA token, when accessing the TOE through the remote HA manager interface. Ident.7 is suitable to meet FIA_UID.1 by ensuring that the TOE uniquely identifies remote callers by the user ID associated Ident with the remote caller as it is supplied within the LTPA token, when accessing the TOE through the remote WS-Transactions interface. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 88 SFRs TSFs FIA_UAU.EXP.1 Ident.1 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified through the remote HTTP/S interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity Ident.2 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified through the remote ORB interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity Ident.3 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified through the remote JMS interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity Ident.4 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is re-identified through either remote HTTP/S interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity Ident.5 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified through the remote HA manager interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity. Ident.6 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified for change in identity (that is, Run As identification) through the either the remote HTTP/S or remote ORB interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity Ident.7 is suitable to meet FIA_UAU.EXP.1 by ensuring that when a remote caller is identified through the remote WS-Transactions interface, the TOE invokes appropriate services in the operational environment to authenticate the claimed identity WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 89 SFRs TSFs FIA_USB.1 Ident.1 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is identified through the remote HTTP/S interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. Ident.2 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is identified through the remote ORB interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. Ident.3 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is identified through the remote JMS interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. Ident.4 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is re-identified through either the remote HTTP/S interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. Ident.5 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is identified through the remote HA manager interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. Ident.7 is suitable to meet FIA_USB.1 by ensuring that when a remote caller is identified through the remote WS- Transacations interface, the TOE properly maps any roles associated to the remote callers authenticated user and/or group ID. FMT_MOF.1 AUD.2 is suitable to meet FMT_MOF.1 by ensuring that only an Auditor can enable and disable the security audit function. FMT_MSA.1a SM.1 is suitable to meet FMT_MSA.1a by ensuring that the TOE enforces the web server applications access control policy, the enterprise beans access control policy, the naming directory access control policy, and the messaging access control policy to restrict access to write or delete the mapping of user and group IDs to an application-defined role, messaging role, and naming role to either the Administrator or Configurator role. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 90 SFRs TSFs FMT_MSA.1b SM.1 is suitable to meet FMT_MSA.1b by ensuring that the TOE enforces the configuration data, TOE files, and runtime state access control policy and the transaction and activities access control policy to restrict access to write or delete the mapping of user and group IDs to an administration role to the Administrator role. FMT_MSA.1c SM.1 is suitable to meet FMT_MSA.1c by ensuring that the TOE enforces the UDDI access control policy to restrict access to write or delete the registered UDDI publishers to the Administrator role or Operator role. FMT_MSA.3a SM.1 is suitable to meet FMT_MSA.3a by ensuring that the TOE enforces the UDDI access control policy to provide restrictive default values for the registered UDDI publishers. SM.1 also ensures that only the Administrator role or Operator role can define alternative registered UDDI publishers. FMT_MSA.3b SM.1 is suitable to meet FMT_MSA.3b by ensuring that the TOE enforces the web server applications access control policy, the enterprise beans access control policy, and the messaging access control policy to provide restrictive default values for mapping a user or group ID to an application-defined role, or messaging role. SM.1 also ensures that only a remote caller associated with either the Administrator role or Configurator role can define alternative role mappings to override the default role mappings. FMT_MSA.3c SM.1 is suitable to meet FMT_MSA.3c by ensuring that the TOE enforces the configuration data, TOE files, and runtime state access control policy, and the transactions and activities access control policy to provide restrictive default values for the user/group IDs to administration roles. SM.1 also ensures that only a remote caller associated with the Administrator role can define alternative role mappings to override the default administration role mappings. WebSphere Application Server EAL4+ Security Target Issue: v3.0 © Copyright IBM 2005, 2012. All rights reserved. Page 91 SFRs TSFs FMT_MSA.3d SM.1 is suitable to meet FMT_MSA.3d by ensuring that the TOE enforces the naming directory access control policy to provide permissive default values for the mapping of user/group IDs to naming roles. SM.1 also ensures that only a remote caller associated with either the Administrator role or Configurator role can define alternative role mappings to override the default role mappings. FMT_SMF.1 SM.1 is suitable to meet FMT_SMF.1 by ensuring that the TOE provides the capability for a remote caller to configure the attribute that stores the list of registered UDDI publishers, the attribute that sets the inherit defaults flag for each Messaging queue, topic space, and topic, the attribute that sets the topic space access check flag for each Messaging topic space, the attribute that maps a user ID and password to a run-as role, the attribute that sets the inherit Sender flag for new topics, the attribute that sets the inherit Receiver flag for new topics, the attribute that maps user and group IDs to roles, and also to enable and disable the security audit function. FMT_SMR.1 SM.1 is suitable to meet FMT_SMR.1 by ensuring that the TOE maintains administration roles (Administrator, Configurator, Monitor, Operator, Deployer, AdminSecurityManager, and Auditor), application- defined roles, messaging roles (Browser, Bus Connector, Creator, Receiver, Sender), naming roles (COSNamingCreate, COSNamingDelete, COSNamingRead, COSNamingWrite), and UDDI roles ( SOAP_Publish_User, V3SOAP_CustodyTransfer_User_Role, V3SOAP_Publish_User_Role,V3SOAP_Security_User_ Role, EJB_Publish_Role). End of Document