STIGQter: STIG Summary: IBM z/OS ACF2 Security Technical Implementation Guide Version: 8 Release: 2 Benchmark Date: 23 Apr 2021: STIGQter: STIG Summary: IBM z/OS ACF2 Security Technical Implementation Guide Version: 8 Release: 2 Benchmark Date: 23 Apr 2021:SV-223478r533198_rule
V-223478
SRG-OS-000480-GPOS-00227
ACF2-ES-000600
CAT II
10
Configure the placement of ESM 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 ESM 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 ESM 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 ESM database should not also cause the loss of the ESM 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 ESM database and its alternate or backup file.
From the ACF Command screen enter:
SET CONTROL(GSO)
SHOW SYSTEMS
If the ESM database is not located on the same volume as either its alternate or backup file, this is not a finding.
If the ESM database is collocated with either its alternate or backup, this is a finding.
V-223478
False
ACF2-ES-000600
From the ACF Command screen enter:
SET CONTROL(GSO)
SHOW SYSTEMS
If the ESM database is not located on the same volume as either its alternate or backup file, this is not a finding.
If the ESM database is collocated with either its alternate or backup, this is a finding.
M
4100