STIGViewer Support

CICS region logonid(s) must be defined and/or controlled in accordance with the security requirements.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-224732ZCIC0040SV-224732r1146380_ruleCCI-000764medium
Description
CICS is a transaction-processing product that provides programmers with the facilities to develop interactive applications. Improperly defined or controlled CICS userids (i.e., region, default, and terminal users) may provide an exposure and vulnerability within the CICS environment. This could result in the compromise of the confidentiality, integrity, and availability of the CICS region, applications, and customer data.
STIGDate
z/OS IBM CICS Transaction Server for TSS Security Technical Implementation Guide2025-09-28

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-04Identification & Authentication for Devices
1.00
IAC-05Identification & Authentication for Third-Party Technology Assets, Applications and/or Services (TAAS)
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (71) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-11Device Lock
1.00
AC-11(1)Pattern-hiding Displays
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00

+61 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.5.1
1.00
3.5.2
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Who does this work

7 NICE work roles and 5 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-224732r1146380_chk)

Refer to the following report produced by the z/OS Data Collection: - EXAM.RPT(CICSPROC). Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(@ACID). - TSSCMDS.RPT(#STC). Refer to the CICS Systems Programmer Worksheets filled out from previous vulnerability ZCIC0010. If the following items are in effect for each CICS region ACID, this is not a finding. A unique ACID is associated with the CICS region. No access to interactive online facilities (e.g., TSO) other than CICS. CICS region ACID does not have any BYPASS privilege. EXCEPT: NOSUBCHK - REQUIRED FOR CICS REGIONS TO SUBMIT BATCH PROCESSING/JOBS OF THE USER WHO IS LOGGED INTO CICS. Ensure that each CICS region ACID is associated with a TSS CICS facility. For example: TSS ADD(CICS region ACID) MASTFAC(CICS facility) CICS region is defined in the STC table. For example: TSS ADD(STC) PROCNAME(CICS region) ACID(CICS ACID)

Fix Text (F-26411r1146380_fix)

Review all CICS region, default, and end-user userids to ensure they are defined and controlled as required. Ensure the following items are in effect for each CICS region ACID: A unique ACID is associated with the CICS region. No access to interactive online facilities (e.g., TSO) other than CICS. CICS region ACID does not have any BYPASS privilege. CICS region ACID is associated with a TSS CICS facility. (The ISSO will determine the MASTFAC used.) CICS region is defined in the STC table. For example: TSS ADD(STC) PROCNAME(CICS region) ACID(CICS ACID)