Title

z/OS system commands must be properly protected. (Cat II impact)

Discussion

z/OS system commands provide a method of controlling the operating environment. Failure to properly control access to z/OS system commands could result in unauthorized personnel issuing sensitive system commands. This exposure may threaten the integrity and availability of the operating system environment, and compromise the confidentiality of customer data.

Check Content

From a command screen enter: TSS WHOHAS OPERCMDS(MVS) Alternately: Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ACP00282) - SENSITVE.RPT(WHOHOPER) – Alternate report Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ACP00282) Access to MVS resource of the OPERCMDS class is restricted to a limited number of authorized users, and all access logged. Access to "MVS.**" is not allowed. Access to z/OS system commands as defined in the table entitled Required Controls on z/OS System Commands, in the z/OS STIG Addendum, is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users). NOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands. NOTE: The (MVS.SEND) Command will not be a finding if used by all. Access to specific z/OS system commands is logged as indicated in the table entitled Required Controls on z/OS System Commands, in the z/OS STIG Addendum. If any of the above is untrue for any z/OS system command resource, this is a FINDING. If all of the above is true, there is NO FINDING.

Fix Text

Ensure access to the MVS resource of the OPERCMDS class is restricted to a limited number of authorized users, and all access is logged. Ensure access to z/OS system commands as defined in the table entitled Required Controls on z/OS System Commands, in the z/OS STIG Addendum is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users). Ensure no access is granted at level MVS.**. NOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands. NOTE: The (MVS.SEND) Command will not be a finding if used by all. Example: TSS ADDTO(deptacid) OPERCMDS(MVS.) TSS PERMIT(usracid) OPERCMDS(MVS.ACTIVATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CANCEL.JOB.) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CONTROL.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.DISPLAY.) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.MONITOR) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.STOPMN) ACCESS(READ)

Additional Identifiers

Rule ID: SV-7920r4_rule

Vulnerability ID: V-7482

Group Title: ACP00282

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.