STIGQter STIGQter: STIG Summary: IBM z/OS TSS Security Technical Implementation Guide Version: 8 Release: 2 Benchmark Date: 23 Apr 2021:

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

DISA Rule

SV-224004r561402_rule

Vulnerability Number

V-224004

Group Title

SRG-OS-000480-GPOS-00227

Rule Version

TSS0-OS-000080

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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.

Check Contents

Refer to the System proclibs for the TSS STC.

If the Security database is located on the same volume as either the backup, Alternate or Recovery file, this is a finding.

Vulnerability Number

V-224004

Documentable

False

Rule Version

TSS0-OS-000080

Severity Override Guidance

Refer to the System proclibs for the TSS STC.

If the Security database is located on the same volume as either the backup, Alternate or Recovery file, this is a finding.

Check Content Reference

M

Target Key

4102

Comments