IBM z/OS MCS consoles access authorization(s) for CONSOLE resource(s) must be properly protected.

An XCCDF Rule

Description

<VulnDiscussion>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. Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID: SV-223689r853595_rule
Severity: Medium
References: CCI-000213 CCI-002235
Updated: 9 months ago

Define all MCS consoles to the CONSOLE resource class and configure READ access to be limited to operators and system programmers.

Configure the MCS console resources defined to z/OS and the ESM to conform to those outlined below.

Each console defined in the CONSOLxx parmlib member is defined to RACF with a corresponding profile in the CONSOLE resource class. See the IBM zOS OPERATIONS AND PLANNING guide for further information.
Each CONSOLE profile is defined with UACC(NONE). 

Example:
RDEF CONSOLE MMDMST UACC(NONE) OWNER(syspsmpl) 
RDEF CONSOLE MMD041 UACC(NONE) OWNER(syspsmpl) 
RDEF CONSOLE MMDSCN UACC(NONE) OWNER(syspsmpl)
RDEF CONSOLE ** UACC(NONE) OWNER(syspsmpl) DATA(** represents all consoles not specifically defined)

Do not permit any user or group access to the ** profile. If a new console is added to the CONSOLxx member it will be covered by this profile and a subsequent error will display in the log, which will allow identification of the undefined console.

The userid associated with each console will have READ access to the corresponding resource defined in the CONSOLE resource class. A sample command file to accomplish this is shown here:

PE MMDMST CL(CONSOLE) ID(mmdmst)
PE MMDSCN CL(CONSOLE) ID(mmdscn)
PE MMD041 CL(CONSOLE) ID(mmd041)

Access authorization for CONSOLE resources restricts READ access to operations and system programming personnel or authorized personnel. A sample command file showing a permission of READ access for sysprogs and operators is shown here:

PE MMDMST CL(CONSOLE) ID(syspsmpl opersmpl)
PE MMDSCN CL(CONSOLE) ID(syspsmpl opersmpl)
PE MMD041 CL(CONSOLE) ID(syspsmpl opersmpl)

IBM z/OS MCS consoles access authorization(s) for CONSOLE resource(s) must be properly protected.

Description

Remediation - Manual Procedure