Securing
CICS® uses an external security manager, such as RACF®, to make CICS systems, and the resources in those systems, secure against unauthorized access. Use this information to plan and implement security across your CICS systems.
- Introduction to CICS security with RACF
This part is an introduction to CICS security. It explains at a high level how you can use the facilities provided by RACF to make your CICS systems, and the resources in those systems, secure against unauthorized access. - Implementing RACF protection in a single CICS region
This part explains how to protect CICS resources in a single CICS region. - Identity propagation and distributed security
Identity propagation provides a mechanism to allow a user identity from an external security realm to be preserved, regardless of where the identity information was created, strengthening accountability across distributed environments. - Invoking an external security manager
CICS provides an interface to an external security manager (ESM), which can be the Resource Access Control Facility (RACF), a vendor product, or user-written. This information provides an overview of the CICS-ESM interface, and describes how you can use the MVS™ router exit to pass control to a user-written ESM. It describes how ESM exit programs can access CICS-related information. Finally, it lists the control points at which CICS invokes the ESM. - Security for CICSPlex SM
This part describes how to implement security for CICSPlex® SM. - Security for intercommunication
These topics tell you how to plan and implement security in an intersystem communication (ISC) environment using LU6.2 or LU6.1, in a multiregion operation (MRO) environment, and in an IP interconnectivity (IPIC) environment. - Security for TCP/IP clients
This part discusses how you can secure your applications when CICS participates in a client-server configuration, using TCP/IP communication protocols. - Security for data sources
- Security for external interfaces
- Security for Java applications
You can secure Java™ applications to ensure that only authorized users can deploy and install applications, and access those applications from the web or through CICS. You can also use a Java security manager to protect the Java application from performing potentially unsafe actions. - Security for CICS web support
When CICS is connected to the Internet, apply security measures to prevent unauthorized access to CICS applications and data and also to prevent third parties obtaining private information. - Support for securing web services
CICS Transaction Server for z/OS® provides support for a number of related technologies that you can use to secure SOAP and JSON messages. - Security in BTS
Security considerations for CICS business transaction services are the authority to access BTS resources, the user IDs under which a process and its constituent activities run, the authority to attach the process and its constituent activities and the authority to use BTS system programming commands. - Security for the CICS-WebSphere MQ adapter
The CICS-WebSphere® MQ adapter provides information to WebSphere MQ specifically for use in WebSphere MQ security. - Security for the CICS-WebSphere MQ bridge
When you start the CICS-WebSphere MQ bridge, you can specify the level of authentication. If requested, the bridge monitor checks the user ID and password extracted from the WebSphere MQ request message before running the CICS program named in the request message. - Kerberos support
CICS Transaction Server for z/OS provides support for Kerberos. - Configuring CICS for SAML
To configure CICS to use SAML, first configure the JVM server by customizing and installing the sample JVM server profile, then install the CSD group in the appropriate CICS regions. - Customizing security processing
This topic describes the interface between CICS and RACF interface, and how you can customize security processing using RACF exit programs.
security.html |
Last updated: Sunday, 4 June 2017