STIGQter: STIG Summary: z/OS BMC MAINVIEW for z/OS for RACF STIG Version: 6 Release: 7 Benchmark Date: 20 Jan 2015:

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

DISA Rule

SV-33841r1_rule

Vulnerability Number

V-17454

Group Title

ZB000032

Rule Version

ZMVZR032

Severity

CAT II

CCI(s)

• CCI-000764 - The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users).

Weight

10

Fix Recommendation

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

Check Contents

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.

Vulnerability Number

V-17454

Documentable

False

Rule Version

ZMVZR032

Severity Override Guidance

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.

Check Content Reference

M

Responsibility

Information Assurance Manager

Target Key

2093

Comments