This document describes the installation and deployment guide for IBM Security zSecure CARLa-Driven Components Version 2.2.1.
This IBM publication (SC27-5638-03, December 2016) is the Installation and Deployment Guide for IBM Security zSecure CARLa-Driven Components version 2.2.1. The edition applies to version 2, release 2, modification 1 of IBM Security zSecure Admin (5655-N16), zSecure Audit (5655-N17), zSecure Visual (5655-N20), zSecure Alert (5655-N21), and IBM Security zSecure Adapters for QRadar SIEM (5655-AD8).
The guide walks through an installation road map, preparation and space planning, the fast installation method and the supplied installation jobs, activation and APF authorization, deployment of configuration data sets, and verification. Later chapters cover setup for production and capacity planning, the zSecure Server for remote data access and command routing, Access Monitor, RACF-Offline, zSecure Alert, the zSecure Visual Server, Change Tracking, and data preparation for QRadar SIEM and Guardium Vulnerability Assessment, followed by appendixes on the site module, security setup, restricted mode, configuration parameters and the ISPF interface.
| Publication number | SC27-5638-03 |
|---|---|
| Edition | December 2016 |
| Version covered | 2.2.1 (version 2, release 2, modification 1) |
| zSecure Admin product number | 5655-N16 |
| zSecure Audit product number | 5655-N17 |
| zSecure Visual product number | 5655-N20 |
| zSecure Alert product number | 5655-N21 |
| Adapters for QRadar SIEM product number | 5655-AD8 |
It applies to zSecure Admin, zSecure Audit, zSecure Visual, zSecure Alert, and zSecure Adapters for QRadar SIEM, all at version 2, release 2, modification 1.
The installation parameters are updated in the CKRZUPDI member, and job CKRZUPDZ is then run to update the CKRINST library members.
Verification covers base ISPF interface functions and menu configuration, the zSecure Collect function and base batch operation, report display functions, and the CKGRACF command for security resources.
The process uses SMF records for data collection, which must be generated and made available to QRadar, with procedures for near real-time or for file polling.