What changed in z/OS BMC CONTROL-D for RACF STIG V7R2V7R2 changes

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(ZCTD0040). TheIf the following keywords willspecify have the specified values in the BMC CONTROL-D security parameter member:, this is not a finding. Keyword Value DEFMCHKD $$CTDEDM SECTOLD NO DFMD01 EXTEND DFMD04 EXTEND DFMD08 EXTEND DFMD19 EXTEND DFMD23 EXTEND DFMD24 EXTEND DFMD26 EXTEND DFMD27 EXTEND

V-224388 in V7R2

Check text

Interview the systems programmer responsible for the BMC CONTROL-D. Determine if the site has modified the following security exit(s): CTDSE01 CTDSE04 CTDSE08 CTDSE19 CTDSE24 CTDSE28 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-224389 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTDRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0000). Verify that the accesses to the BMC CONTROL-D 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, security personnel (domain level and decentralized), 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 CONTROL-D installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, security personnel (domain level and decentralized), 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 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: SYS2.IOA.*.CTDI. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.IOA.*.CTDI.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('BMC CONTROL-D Install DS') pe 'SYS2.IOA.*.CTDI.**' id(&ltsyspaudt>) acc(a) pe 'SYS2.IOA.*.CTDI.**' id(&ltaudtaudt> &ltsecaaudt> &ltsecdaudt>) acc(r) pe 'SYS2.IOA.*.CTDI.**' id(&ltbmcuser> CONTROLD) acc(r) setr generic(dataset) refresh

V-224390 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTDSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0001). Verify that the accesses to the BMC CONTROL-D 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 CONTROL-D end users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict WRITE and/or greater access to BMC STCs and/or batch users. ___ The RACF data set access authorizations restrict UPDATE access to centralized and decentralized security personnel. ___ 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 CONTROL-D STC data sets are limited to systems programmers and BMC STCs and/or batch users. UPDATE access can be given to centralized and decentralized security personnel. 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 ensure 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.*.CTDO. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.CTDO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC CONTROL-D STC DS') pe 'SYS3.IOA.*.CTDO.**' id(syspaudt tstcaudt) acc(a) pe 'SYS3.IOA.*.CTDO.**' id(BMC STCs) acc(a) pe 'SYS3.IOA.*.CTDO.**' id(secaaudt secdaudt) acc(u) pe 'SYS3.IOA.*.CTDO.**' id(bmcuser audtaudt) acc(r) setr generic(dataset) refresh

V-224391 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0002). Verify that the accesses to the BMC CONTROL-D User 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. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The RACF data set access authorizations restrict UPDATE access to centralized and decentralized security personnel, and/or CONTROL-D end users. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

The ISSO must ensure that WRITE and/or greater access to BMC CONTROL-D User data sets are limited to systems programmers and BMC STCs and/or batch users. Additionally, UPDATE access can be given to centralized and decentralized security personnel, and 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 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.*.CTDR. CTRUSR. CTDSRV. CTDJB1. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.IOA.*.CTDR.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC CONTROL-D Repository DS') pe 'SYS3.IOA.*.CTDR.**' id(syspaudt tstcaudt BMC STCs) acc(a) pe 'SYS3.IOA.*.CTDR.**' id(bmcuser) acc(u) pe 'SYS3.IOA.*.CTDR.**' id(secaaudt secdaudt) acc(u) pe 'SYS3.IOA.*.CTDR.**' id(audtaudt) acc(r) ad 'CTRUSR.**' uacc(none) owner(CTRUSR) - audit(failures(read)) - data('BMC CONTROL-D CDAM DS') pe 'CTRUSR.**' id(syspaudt tstcaudt BMC STCs) acc(a) pe 'CTRUSR.**' id(bmcuser) acc(u) pe 'CTRUSR.**' id(secaaudt secdaudt) acc(u) pe 'CTRUSR.**' id(audtaudt) acc(r) ad 'CTDSRV.**' uacc(none) owner(CTDSRV) - audit(failures(read)) - data('BMC CONTROL-D CDAM DS') pe 'CTDSRV.**' id(syspaudt tstcaudt BMC STCs) acc(a) pe 'CTDSRV.**' id(bmcuser) acc(u) pe 'CTDSRV.**' id(secaaudt secdaudt) acc(u) pe 'CTDSRV.**' id(audtaudt) acc(r) ad 'CTDJB1.**' uacc(none) owner(CTDJB1) - audit(failures(read)) - data('BMC CONTROL-D CDAM DS') pe 'CTDJB1.**' id(syspaudt tstcaudt BMC STCs) acc(a) pe 'CTDJB1.**' id(bmcuser) acc(u) pe 'CTDJB1.**' id(secaaudt secdaudt) acc(u) pe 'CTDJB1.**' id(audtaudt) acc(r) setr generic(dataset) refresh

V-224392 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCTD0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC CONTROL-D 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-224393 in V7R2

Title

BMC CONTROL-D Started Task name is not properly identified / defined to the system ACP.

Check text

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). TheVerify that the userid(s) for the BMC CONTROL-D started task(s) and/oris batch job userid(sare) isproperly defined. andIf isthe assignedfollowing theattributes RACFare PROTECTEDdefined, attributethis is not a finding. PROTECTED

Fix text

The BMC systemsystems programerprogrammer and the IAOISSO will ensure that a product's Started Task(s) is properly Identified / 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. A sample is provided here: au CONTROLD name('stc, BMC Controld') owner(stc) dfltgrp(stc) nopass

Discussion

Products that require a started task will require that the started task 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-224394 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(ZCTD0032). Verify that the BMC CONTROL-D 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 CONTROL-D 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 CONTROL-D started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started CONTROLD.** uacc(none) owner(admin) audit(all(read)) stdata(user(CONTROLD) 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-224395 in V7R2