Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Refer to the JCL procedure libraries defined to JES2 for the SDSF started task member for SDSFPARM DD statement. Refer to the ISRPRMxx members in the logical PARMLIB concatenation. Refer to the results of the "F SDSF,D" command. Where SDSF should specify the SDSF started task name. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZISF0040) Ensure the following Group Parameters are specified or not specified in the GROUP statements defined in the ISFPARMS members. If the following guidance is true, this is not a finding. For each GROUP statement: AUPDT(0) AUTH will not be specified CMDAUTH will not be specified CMDLEV will not be specified DSPAUTH will not be specified NAME a value will be specified for the NAME
Ensure that the following Group function parameters appear and/or do not appear in ISFPARMS. For each GROUP statement: AUPDT(0) AUTH will not be specified CMDAUTH will not be specified CMDLEV will not be specified DSPAUTH will not be specified NAME a value will be specified for the NAME The ISFPARMS GROUP statement defines user groups and their characteristics. Some of these characteristics include access authorization to SDSF functions and commands. Access to these functions and commands will be controlled using SAF resources. The use of the SAF interface is consistent with the DOD requirement to control all products within the operating system using the ACP. To ensure SAF security is always in effect, authorizations to SDSF functions and commands should not be defined in ISFPARMS DD statement in the SDSF JCL member.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ISFRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZISF0000) Verify that the accesses to the IBM SDSF installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set rules for the data sets restricts READ access to all authorized users. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged. ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
The ISSO will ensure that WRITE and/or greater access to IBM SDSF installation data sets is limited to System 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 data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged and identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS1.ISF.AISF SYS1.ISF.SISF The following commands are provided as a sample for implementing data set controls: AD 'sys1.isf.aisf*.**' UACC(NONE) OWNER(SYS1) AUDIT(SUCCESS(UPDATE) FAILURES(READ)) AD 'sys1.isf.sisf*.**' UACC(NONE) OWNER(SYS1) AUDIT(SUCCESS(UPDATE) FAILURES(READ)) PE 'sys1.isf.aisf*.**' ID(syspaudt) ACC(A) PE 'sys1.isf.sisf*.**' ID(syspaudt) ACC(A) PE 'sys1.isf.sisf*.**' ID(authorized users/*) ACC(R)
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 System Display and Search Facility (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 RACF data set rules for the data sets restricts READ access to the auditors. ___ The RACF data set rules for the data sets restricts UPDATE access to SDSF Started Tasks. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING. 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 dataset 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.
Ensure that the HASPINDX dataset 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 dataset 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 will be: SYS1.ISF.AISF SYS1.ISF.SISF The following commands are provided as a sample for implementing data set controls: AD 'sys1.haspindx.**' UACC(NONE) OWNER(SYS1) AUDIT(FAILURES(READ)) PE ' sys1.haspindx.**' ID(syspaudt) ACC(A) PE ' sys1.haspindx.**' ID(sdsf stc) ACC(U) PE ' sys1.haspindx.**' ID(audtaudt) ACC(R)
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZISF0020) Automated Analysis requiring additional analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZISF0020) Ensure that all IBM System Display and Search Facility (SDSF) resources are properly protected according to the requirements specified in SDSF SAF Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. ___ The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. ___ The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The RACF resource logging is specified as designated in the above table. ___ The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING. ___ The RACF resource access authorizations for SDSF GROUP.group-name will require additional analysis to justify access.
The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. (Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, resources, and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Ensure that the IBM System Display and Search Facility (SDSF) command resource access is in accordance with those outlined in SDSF SAF Resources table in the zOS STIG Addendum. Use SDSF SAF Resources and SDSF SAF Resource Descriptions tables in the zOS STIG Addendum. These tables list the resources and access requirements for IBM System Display and Search Facility (SDSF); ensure the following guidelines are followed: The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. The RACF resource logging is specified as designated in the above table. The RACF resource access authorizations for the resources designated in the above table specify UACC(NONE) and NOWARNING. The RACF resource access authorizations for SDSF GROUP.group-name will require additional analysis to justify access. The following commands are provided as a sample for implementing resource controls: RDEFINE SDSF ISFATTR.JOBCL.** UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) PERMIT ISFATTR.JOBCL.** CLASS(SDSF) ACCESS(UPDATE) ID(operaudt) PERMIT ISFATTR.JOBCL.** CLASS(SDSF) ACCESS(UPDATE) ID(syspaudt)
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZISF0021) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZISF0021) Ensure that all SDSF resources are properly protected according to the requirements specified in the SDSF Server OPERCMDS Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. ___ The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. ___ The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The RACF resource logging is specified as designated in the above table. ___ The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING.
The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. Ensure that the IBM SDSF resource access is in accordance with those outlined in SDSF Server OPERCMDS Resources table in the zOS STIG Addendum. Use SDSF Server OPERCMDS Resources table in the zOS STIG Addendum. These tables list the resources and access requirements for IBM SDSF; ensure the following guidelines are followed: The RACF resources and/or generic equivalent as designated in the above table are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. The RACF resource logging is specified as designated in the above table. The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. The following commands are provided as a sample for implementing resource controls: RDEFINE OPERCMDS SDSF.MODIFY.** UACC(NONE) OWNER(ADMIN) - AUDIT(FAILURE(READ),SUCCESSFUL(UPDATE)) RDEFINE OPERCMDS SDSF.MODIFY.DISPLAY UACC(NONE) OWNER(ADMIN) - AUDIT(FAILURE(READ)) PERMIT SDSF.MODIFY.** CLASS(OPERCMDS) ACCESS(CONTROL) ID(syspaudt) PERMIT SDSF.MODIFY.DISPLAY CLASS(OPERCMDS) ACCESS(READ) ID(audtaudt) PERMIT SDSF.MODIFY.DISPLAY CLASS(OPERCMDS) ACCESS(READ) ID(operaudt) PERMIT SDSF.MODIFY.DISPLAY CLASS(OPERCMDS) ACCESS(READ) ID(syspaudt)
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) Verify that the userid(s) for the IBM SDSF started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED
The ISSO working with the systems programmer will ensure the IBM SDSF 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): au SDSF name('STC, SDSF') owner(stc) dfltgrp(stc) nopass - data('SDSF stc')
Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZISF0032) If the IBM SDSF started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.
The ISSO working with the systems programmer will ensure the IBM SDSF Started Task(s) is properly identified and/or defined to the System ACP. A unique userid must be assigned for the IBM SDSF started task(s) thru a corresponding STARTED class entry. The following commands are provided as a sample for defining Started Task(s): rdef started SDSF.** uacc(none) owner(admin) audit(all(read)) - stdata(user(SDSF) group(stc)) setr racl(started) ref
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(SETROPTS) - DSMON.RPT(RACCDT) - Alternate list of active resource classes Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZISF0038) If the IBM System Display and Search Facility (SDSF) resource class(es) is (are) active, this is not a finding.
The ISSO will ensure that the IBM SDSF Resource Class(es) is (are) active. Use the following commands as an example: SETROPTS CLASSACT(SDSF)