Security for inbound ports
A TCPIPSERVICE resource definition defines each port used for CICS® web support. The TCPIPSERVICE definition specifies security options for the port, including whether SSL is used and the level of authentication that is requested from clients. Ports must be guarded against unauthorized or malicious access.
Creating TCPIPSERVICE resource definitions for CICS web support explains how to create definitions for ports.
- Specify the MAXDATALEN attribute on every TCPIPSERVICE definition. This option limits the maximum amount of data that CICS accepts for a single request, and it helps to defend CICS against denial of service attacks involving the transmission of large amounts of data.
- Use Secure Sockets Layer (SSL) wherever you want to ensure that your interaction with the web client remains confidential and cannot be intercepted by a third party. The use of SSL is particularly important when confidential data is being transmitted or when authorization such as a user ID and password are being passed to the server. Refer to SSL with CICS web support.
If you do experience unusual activity on one or more of your CICS web support ports, use CICS system commands to shut down CICS web support at different levels (a single request, a virtual host, a port, or the whole of CICS web support), without shutting down the CICS system. Refer to Rejecting HTTP requests.
URIMAP resource definitions name either HTTP or HTTPS as the scheme for the request. A URIMAP specifying HTTP accepts web client requests made using either HTTP or the more secure HTTPS. A URIMAP specifying HTTPS accepts only web client requests that are made using HTTPS.
When a URIMAP definition with HTTPS matches a request from a web client, CICS checks that the inbound port used by the request is using SSL. If SSL is not specified for the port, the request is rejected with a 403 (Forbidden) status code. When the URIMAP definition applies to all inbound ports, this check ensures that a web client cannot use an unsecured port to access a secured resource. No check is carried out for a URIMAP definition that specifies HTTP, so web clients can use either unsecured or secured (SSL) ports to access these resources.