From z/OS TSS STIG
Part of ACP00291
Associated with IA controls: DCCS-1, DCCS-2
MCS consoles can be used to issue operator commands. Failure to properly control access to MCS consoles could result in unauthorized personnel issuing sensitive operator commands. This exposure may threaten the integrity and availability of the operating system environment, and compromise the confidentiality of customer data.
Refer to the following report produced by the z/OS Data Collection: - EXAM.RPT(PARMLIB) Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ACP00291) Review each CONSOLxx parmlib member, ensure the following items are in effect. ____ The DEFAULT statement for each CONSOLxx member specifies LOGON(REQUIRED) or LOGON(AUTO). ____ The CONSOLE statement for each console assigns a unique name using the NAME parameter. ____ The CONSOLE statement for each console specifies AUTH(INFO). Exceptions are the AUTH parameter is not valid for consoles defined with UNIT(PRT) and specifying AUTH(MASTER) is permissible for the system console.
The Systems programmer should use the following recommendations and techniques to provide protection for MCS consoles: Ensure that the DEFAULT statement specifies LOGON(REQUIRED) so that all operators are required to log on prior to entering z/OS system commands. At the discretion of the IAO, LOGON(AUTO) may be used. Ensure that each CONSOLE statement specifies an explicit console NAME. And that AUTH(INFO) is specified, this also including extended MCS consoles. AUTH(MASTER) may be specified for systems console.
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer