STIGQter STIGQter: STIG Summary: IBM z/OS ACF2 Security Technical Implementation Guide Version: 9 Release: 9 Benchmark Date: 01 Jul 2026:

CA-ACF2 database must be on a separate physical volume from its backup and recovery data sets.

DISA Rule

SV-223478r1225708_rule

Vulnerability Number

V-223478

Group Title

SRG-OS-000480-GPOS-00227

Rule Version

ACF2-ES-000600

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure the placement of ACF2 files are on a separate volume from its backup and recovery data sets to provide backup and recovery in the event of physical damage to a volume.

Identify the ACF2 database(s), backup database(s), and recovery data set(s). Develop a plan to keep these data sets on different physical volumes. Implement the movement of these critical ACF2 files.

File location is an often overlooked factor in system integrity. It is important to ensure that the effects of hardware failures on system integrity and availability are minimized. Avoid collocation of files such as primary and alternate databases. For example, the loss of the physical volume containing the ACF2 database should not also cause the loss of the ACF2 backup database as a result of their collocation. Files that will be segregated from each other on separate physical volumes include, but are not limited to, the ACF2 database and its alternate or backup file.

Check Contents

From the ACF Command screen, enter:
SET CONTROL(GSO)
SHOW DDSN

Exexute the ISPF Data Set List Utility for each dataset listed to determine the volume.

If the ACF2 database is not located on the same volume as either its alternate or backup file, this is not a finding.

If the ACF2 database is collocated with either its alternate or backup, this is a finding.

Vulnerability Number

V-223478

Documentable

False

Rule Version

ACF2-ES-000600

Severity Override Guidance

From the ACF Command screen, enter:
SET CONTROL(GSO)
SHOW DDSN

Exexute the ISPF Data Set List Utility for each dataset listed to determine the volume.

If the ACF2 database is not located on the same volume as either its alternate or backup file, this is not a finding.

If the ACF2 database is collocated with either its alternate or backup, this is a finding.

Check Content Reference

M

Target Key

4100