STIGQter: STIG Summary: z/OS IBM System Display and Search Facility (SDSF) for TSS Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025: STIGQter: STIG Summary: z/OS IBM System Display and Search Facility (SDSF) for TSS Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025:SV-225106r1146034_rule
V-225106
SRG-OS-000080
ZISFT002
CAT II
10
Ensure that the HASPINDX data set identified in the INDEX parameter value of ISFPARMS options statement is restricted as described below.
The HASPINDX data set is used by SDSF when building the SYSLOG panel. This data set contains information related to all SYSLOG jobs and data sets on the spool. Since SDSF dynamically allocates this data set, explicit user access authorization to this data set should not be required. Due to the potentially sensitive data in this data set, access authorization will be restricted.
READ access is restricted to the auditors.
UPDATE access is restricted to SDSF Started Tasks.
WRITE and/or greater access is restricted to systems programming personnel.
Note: If running z/OS V1R11 or above, with the use of a new JES logical log, the HASPINDX, may not exist and may make this vulnerability not applicable (N/A). However if used the HASPINDX data set must be restricted.
Note: If running z/OS V1R11 systems or above and NOT using JES logical log, the HASPINDX data set must be protected.
Data sets to be protected may be:
SYS1.HASPINDX
The following commands are provided as a sample for implementing data set controls:
TSS ADD(SYS1) DSN(SYS1)
TSS PERMIT(syspaudt) DSN(SYS1.HASPINDX) ACCESS(ALL)
TSS PERMIT(sdsf stc) DSN(SYS1.HASPINDX) ACCESS(UPDATE)
TSS PERMIT(audtaudt) DSN(SYS1.HASPINDX) ACCESS(READ)
If the z/OS operating system is Release 2.2 or higher this is not applicable.
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(SDSFRPT).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZISF0002)
Verify that the accesses to the IBM SDSF HASPINDX data set specified on the INDEX control statement in the ISFPARMS statements (identified in the SFSFPARM DD statement of the SDSF stc) are properly restricted.
If the following guidance is true, this is not a finding.
The TSS data set rules for the data sets restrict READ access to the auditors.
The TSS data set rules for the data sets restrict UPDATE access to SDSF Started Tasks.
The TSS data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel.
Note: If running z/OS V1R11 or above, with the use of a new JES logical log, the HASPINDX, may not exist and may make this vulnerability not applicable (NA). However if used the HASPINDX data set must be restricted.
Note: If running z/OS V1R11 systems or above and NOT using JES logical log, the HASPINDX data set must be protected.
V-225106
False
ZISFT002
If the z/OS operating system is Release 2.2 or higher this is not applicable.
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(SDSFRPT).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZISF0002)
Verify that the accesses to the IBM SDSF HASPINDX data set specified on the INDEX control statement in the ISFPARMS statements (identified in the SFSFPARM DD statement of the SDSF stc) are properly restricted.
If the following guidance is true, this is not a finding.
The TSS data set rules for the data sets restrict READ access to the auditors.
The TSS data set rules for the data sets restrict UPDATE access to SDSF Started Tasks.
The TSS data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel.
Note: If running z/OS V1R11 or above, with the use of a new JES logical log, the HASPINDX, may not exist and may make this vulnerability not applicable (NA). However if used the HASPINDX data set must be restricted.
Note: If running z/OS V1R11 systems or above and NOT using JES logical log, the HASPINDX data set must be protected.
M
4201