BMC IOA Started task(s) must be properly defined to the STARTED resource class for RACF.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224421 | ZIOAR032 | SV-224421r518928_rule | Medium |
| Description |
| 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. |
| STIG | Date |
| z/OS BMC IOA for RACF Security Technical Implementation Guide | 2022-10-07 |
Details
| Check Text (C-26098r518926_chk) |
| 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(ZIOA0032) Verify that the BMC IOA started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry. |
| Fix Text (F-26086r518927_fix) |
| The BMC IOA 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 IOA started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started IOAGATE.** uacc(none) owner(admin) audit(all(read)) stdata(user(IOAGATE) group(stc)) setr racl(started) ref |