DoD Compliance · STIG

z/OS CA Common Services for ACF2 Security Technical Implementation Guide

V7R2 · · 8 months ago · Released 01 Oct 2025 · 2 rules

Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.

Digest of Updates vs. V7R1 · 30 Jan 2025 ✎ 2

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 2

V-224268 Medium descriptioncheckfix CA Common Services installation datasets will be properly protected.
V-224269 Medium descriptioncheckfix CA Common Services Started Task name will be properly identified and/or defined to the system ACP.

Sort by

Expand all

CA Common Services installation datasets will be properly protected.

CM-5 - Medium - CCI-001499 - V-224268 - SV-224268r1141369_rule

RMF Control

CM-5

Severity

CCI

CCI-001499

Version

ZCCSA000

Vuln IDs

V-224268
V-16932

Rule IDs

SV-224268r1141369_rule
SV-40833

CA Common Services 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.

Checks: C-25941r1141367_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CCSRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCCS0000). Verify that the accesses to the CA Common Services 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: F-25929r1141368_fix

The ISSO will ensure that WRITE and/or greater access to CA Common Services 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. Datasets to be protected may begin with: SYS2.CCS SYS2A.CCS SYS3.CCS The following commands are provided as a sample for implementing dataset controls: $KEY(S2C) $PREFIX(SYS2) CCS.- UID(syspaudt) R(A) W(L) A(L) E(A) CCS.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) CCS.- UID(authorized users/*) R(A) E(A) SET RULE COMPILE 'ACF2.MVA.DSNRULES(S2C)' STORE

CA Common Services Started Task name will be properly identified and/or defined to the system ACP.

IA-2 - Medium - CCI-000764 - V-224269 - SV-224269r1144186_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

ZCCSA030

Vuln IDs

V-224269
V-17452

Rule IDs

SV-224269r1144186_rule
SV-40856

CA Common Services requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Checks: C-25942r1141370_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Verify that the logonid(s) for the CA Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC

Fix: F-25930r1141371_fix

The ISSO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how a Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): SET LID insert CAS9 stc name('STC, CAS9')