What changed in z/OS BMC IOA for RACF STIG V7R2V7R2 changes

Check text

Interview the systems programmer responsible for the BMC IOA. Determine if the site has modified the following security exit(s): IOASE06 IOASE07 IOASE09 IOASE12 IOASE16 IOASE32 IOASE40 IOASE42 EnsureVerify the above security exit(s) has (have) not been modified. If the above security exit(s) has (have) been modified, ensureverify that the security exit(s) has (have) been approved by the site systems programmer and the approval is on file for examination.

V-224415 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(IOARPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZIOA0000). Verify that the accesses to the BMC IOA installation data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set access authorizations restrict READ access to auditors, BMC users, operations, production control and scheduling personnel, and BMC STCs and/or batch users. The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC IOA installation data sets are limited to systems programmers only. READ access can be given to auditors, BMC users, operations, production control and scheduling personnel, and BMC STCs and/or batch users. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Data sets to be protected will be: SYS2.IOA.*.IOAI. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.IOA.*.IOAI.**' uacc(none) owner(SYS2) - audit(success(update) failures(read)) - data('BMC IOA Install DS') pe 'SYS2.IOA.*.IOAI.**' id(&ltsyspaudt> &lttstcaudt>) acc(a) pe 'SYS2.IOA.*.IOAI.**' id(&ltaudtaudt> &ltbmcuser> &ltoperaudt>) acc(r) pe 'SYS2.IOA.*.IOAI.**' id(&ltpcspaudt> BMC STCs) acc(r) setr generic(dataset) refresh

V-224416 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(IOASTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZIOA0001). Verify that the accesses to the BMC IOA STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restrict READ access to auditors and BMC users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict UPDATE access to the BMC STCs, batch users and BMC administrators. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

Ensure that WRITE and/or greater access to BMC IOA STC data sets are limited to systems programmers only. UPDATE access can be given to BMC STCs, batch users and BMC administrators. READ access can be given to auditors and BMC users. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing Systems Programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Data sets to be protected will be: SYS3.IOA.*.IOAO. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.IOAO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC IOA STC DS') pe 'SYS3.IOA.*.IOAO.**' id(&ltsyspaudt> &lttstcaudt>) acc(a) pe 'SYS3.IOA.*.IOAO.**' id(BMC STCs &ltbmcadmin>) acc(u) pe 'SYS3.IOA.*.IOAO.**' id(&ltaudtaudt> &ltbmcuser>) acc(r) setr generic(dataset) refresh

V-224417 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(IOAUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZIOA0002). Verify that the accesses to the BMC IOA user data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set access authorizations restricts READ access to auditors. The RACF data set access authorizations restricts WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations restricts WRITE and/or greater access to the BMC STCs and/or batch users. The RACF data set access authorizations restricts UPDATE access to production control and scheduling personnel and the BMC users. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC IOA User data sets are limited to systems programmers and/or BMC STCs and/or batch users only. UPDATE access can be given to production control and scheduling personnel and the BMC users. READ access can be given to auditors. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Data sets to be protected will be: SYS3.IOA.*.IOAC. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.IOAC.**' uacc(none) owner(SYS3) - audit(failures(read)) - data('BMC IOA User DS') pe 'SYS3.IOA.*.IOAC.**' id(&ltsyspaudt> &lttstcaudt> BMC STCs) acc(a) pe 'SYS3.IOA.*.IOAC.**' id(&ltbmcuser> &ltpcspaudt>) acc(u) pe 'SYS3.IOA.*.IOAC.**' id(&ltaudtaudt>) acc(r) setr generic(dataset) refresh

V-224418 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZIOA0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZIOA0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC IOA Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. Note: To determine what resource class is used review the IOACLASS setting in SECPARM. The "Trigger" resources i.e., $$SECxxx (xxx is unique to the product) are defined in the FACILITY resource class. The RACF resources are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging requirements are specified. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.

V-224419 in V7R2

Check text

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the BMC IOA started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED

Fix text

The IAOISSO working with the systems programmer will ensure the BMC IOA Started Task(s) is (are) properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): au IOAGATE name('stc, BMC IOA') owner(stc) dfltgrp(stc) nopass

Discussion

BMC IOA requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.

V-224420 in V7R2

Check text

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, this is a finding.

Fix text

The BMC IOA system programmer and the IAOISSO 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

Discussion

Access to product resources shouldmust 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.

V-224421 in V7R2

Check text

Refer to the following applicable reports produced by the z/OS Data Collection: - IOA.RPT(SECPARM). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZIOA0040). TheIf the following keywords willspecify have the specified values in the BMC IOA security parameter member:, this is not a finding. Keyword Value DEFMCHKI $$IOAEDM SECTOLI NO DFMI06 EXTEND DFMI07 EXTEND DFMI09 EXTEND DFMI12 EXTEND DFMI16 EXTEND DFMI32 EXTEND DFMI40 EXTEND DFMI42 EXTEND IOACLASS $IOA RACSCLAS SURROGAT IOATCBS YES

V-224422 in V7R2