STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub·STIGs updated 2 days ago
Powered by Pylon·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS CA 1 Tape Management for ACF2 Security Technical Implementation Guide

V-224258

CAT II (Medium)

CA 1 Tape Management installation datasets must be properly protected.

Rule ID

SV-224258r1141350_rule

STIG

z/OS CA 1 Tape Management for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499CCI-002234

Discussion

CA 1 Tape Management installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

Check Content

Refer to the following report produced by the dataset and Resource Data Collection:

- SENSITVE.RPT(CA1PROD).

Automated Analysis
Refer to the following report produced by the dataset and Resource Data Collection:

- PDI(ZCA10000).

Verify that the accesses to the CA 1 Tape Management installation datasets are properly restricted. If the following guidance is true, this is not a finding.

The ACF2 dataset rules for the datasets restrict READ access to all authorized users.

The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel.

The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix Text

Ensure that WRITE and/or greater access to CA 1 Tape Management installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users.

The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure that they are properly  restricted to the ACP (Access Control Program) active on the system.

The following is an example of the type of datasets to be protected:

SYS2.CA1.
SYS2A.CA1.*.CAILIB
SYS2A.CA1.*.CAILPA
Or
SYS2A.CA1.*.CTAPLINK
SYS3.CA1.
SYS3A.CA1.*.CAILIB
Or
SYS3A.CA1.*.CTAPLINK
SYS3A.CA1.*.CTAPLPA

The following commands are provided as a sample for implementing dataset controls:

$KEY(S2C)
$PREFIX(SYS2)
CA1.V-.- UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-.- UID(authorized users/*) R(A) E(A)

SET RULE
COMPILE 'ACF2.MVA.DSNRULES(S2C)' STORE

$KEY(SYS2A0C)
$MODE(ABORT)
$PREFIX(SYS2A)
CA1.V-.CAILIB UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-.CAILIB UID(authorized users/*) R(A) E(A)
CA1.V-.CAILPA UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-.CAILPA UID(authorized users/*) R(A) E(A)
Or
CA1.V-. CTAPLINK UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-. CTAPLINK UID(authorized users/*) R(A) E(A)

SET RULE
COMPILE 'ACF2.MVA.DSNRULES(SYS2A0C)' STORE

$KEY(S3C)
$PREFIX(SYS3)
CA1.V-.- UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-.- UID(authorized users/*) R(A) E(A)

SET RULE
COMPILE 'ACF2.MVA.DSNRULES(S3C)' STORE

$KEY(SYS3A0C)
$MODE(ABORT)
$PREFIX(SYS3A)
CA1.V-.CAILIB UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-.CAILIB UID(authorized users/*) R(A) E(A)
Or
CA1.V-. CTAPLINK UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-. CTAPLINK UID(authorized users/*) R(A) E(A)
CA1.V-. CTAPLPA UID(syspaudt) R(A) W(L) A(L) E(A)
CA1.V-. CTAPLPA UID(authorized users/*) R(A) E(A)

SET RULE
COMPILE 'ACF2.MVA.DSNRULES(SYS3A0C)' STORE