STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to STIGs

z/OS IBM CICS Transaction Server for ACF2 Security Technical Implementation Guide

Version

V7R2

Release Date

Sep 23, 2025

SCAP Benchmark ID

zOS_IBM_CICS_Transaction_Server_for_ACF2

Total Checks

12

Tags

other
CAT I: 0CAT II: 12CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (12)

V-224302MEDIUMCICS system datasets are not properly protected.V-224303MEDIUMSensitive CICS transactions are not protected in accordance with security requirements.V-224304MEDIUMCICS System Initialization Table (SIT) parameter values must be specified in accordance with proper security requirements.V-224305MEDIUMCICS region logonid(s) must be defined and/or controlled in accordance with the security requirements.V-224306MEDIUMCICS default logonid(s) must be defined and/or controlled in accordance with the security requirements.V-224307MEDIUMCICS logonid(s) must be configured with proper timeout and signon limits.V-224308MEDIUMACF2/CICS parameter datasets are not protected in accordance with the proper security requirements.V-224309MEDIUMIBM CICS Transaction Server SPI command resources must be properly defined and protected.V-224310MEDIUMCICS startup JCL statement is not specified in accordance with the proper security requirements.V-224311MEDIUMKey ACF2/CICS parameters must be properly coded.V-224312MEDIUMSensitive CICS transactions are not protected in accordance with the proper security requirements.V-224313MEDIUMSensitive CICS transactions are not protected in accordance with the proper security requirements.