BMC Mainview for z/OS Started task(s) must be properly defined to the STARTED resource class for RACF.

From z/OS BMC MAINVIEW for z/OS for RACF STIG

Associated with IA controls: ECCD-2, ECCD-1

Associated with: CCI-000764

SV-33841r1_rule BMC Mainview for z/OS Started task(s) must be properly defined to the STARTED resource class for RACF.

Vulnerability discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

Check content

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(ZMVZ0032) Verify that the BMC Mainview for z/OS started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry.

Fix text

The BMC Mainview system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the BMC Mainview started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started MV$CAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$CAS) group(stc)) rdef started MV$MVS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$MVS) group(stc)) setr racl(started) ref

Pro Tips

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.