What changed in z/OS BMC CONTROL-D for ACF2 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). The following keywords will 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-224106 in V7R2

Title

BMC CONTROL-D installation data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTDRPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTD0000). Verify that the accesses to the BMC CONTROL-D installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors, BMC users, security personnel (domain level and decentralized), and BMC STCs and/or batch users. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access areis logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D installation datadatasets setsis 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 datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure 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 setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS2.IOA.*.CTDI. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) IOA.-.CTDI.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTDI.- UID(&ltaudtaudt>) R(A) E(A) IOA.-.CTDI.- UID(&ltbmcuser>) R(A) E(A) IOA.-.CTDI.- UID(&ltsecaaudt>) R(A) E(A) IOA.-.CTDI.- UID(&ltsecdaudt>) R(A) E(A) IOA.-.CTDI.- UID(CONTROLD) R(A) E(A)

Discussion

BMC CONTROL-D installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

V-224108 in V7R2

Title

BMC CONTROL-D STC data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTDSTC). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTD0001). Verify that the accesses to the BMC CONTROL-D STC datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors and CONTROL-D end users. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to BMC STCs and/or batch users. ___ The ACF2 datadataset set access authorizations restrict UPDATE access to centralized and decentralized security personnel.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D STC datadatasets setsis 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 datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure 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 setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS3.IOA.*.CTDO. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) IOA.-.CTDO.- UID(syspaudt) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(tstcaudt) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTDO.- UID(secaaudt) R(A) W(A) E(A) IOA.-.CTDO.- UID(secdaudt) R(A) W(A) E(A) IOA.-.CTDO.- UID(audtaudt) R(A) E(A) IOA.-.CTDO.- UID(bmcuser) R(A) E(A)

Discussion

BMC CONTROL-D STC datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

V-224109 in V7R2

Title

BMC CONTROL-D user data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZCTD0002). Verify that the accesses to the BMC CONTROL-D User datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The ACF2 datadataset set access authorizations restrict UPDATE access to centralized and decentralized security personnel, and/or CONTROL-D end users.

Fix text

The ISSO must ensure that WRITE and/or greater access to BMC CONTROL-D User datadatasets setsis 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. The ISSO can approve ALLOC access in circumstances where it is determined to be necessary and appropriate for systems operations to execute in a normal secure manner. READ access can be given to auditors. The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer must identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS3.IOA.*.CTDR. CTRUSR. CTDSRV. CTDJB1. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) IOA.-.CTDR.- UID(syspaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(tstcaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(bmcuser) R(A) W(A) E(A) IOA.-.CTDR.- UID(secaaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(secdaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(audtaudt) R(A) E(A) $KEY(CTRUSR) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDSRV) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDJB1) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A)

Discussion

BMC CONTROL-D User data setsdatasets, CDAM and Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

V-224110 in V7R2

Check text

Refer to the following report produced by the ACF2dataset Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(ZCTD0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the Datadataset 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 ACF2 resources are defined with a default access of PREVENT. ___ The ACF2 resource access authorizations restrict access to the appropriate personnel. ___ The ACF2 resource logging requirements are specified.

Fix text

The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. 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 (Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Use BMC CONTROL-D Resources and BMC INCONTROL Resources Descriptions tables in the zOS STIG Addendum. These tables list the resources, descriptions, and access and logging requirements. Ensure the guidelines for the resources and/or generic equivalent specified in the z/OS STIG Addendum are followed. The following commands are provided as a sample for implementing resource controls: $key($$addnot) type(ioa) - uid(&ltappsaudt>) allow - uid(&ltoperaudt>) allow - uid(&ltpcspaudt>) allow - uid(&ltsyspaudt>) allow - uid(*) prevent

V-224111 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 ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). InsureVerify that the logonids(s) for the BMC CONTROL-D started task(s) includes the following:. If the following attributes are defined, this is not a finding. STC MUSASS NO-SMC

Fix text

The BMC CONTROL-D systemsystems programmer 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. Example: SET LID CHANGE CONTROLD STC MUSASS NO-SMC

Discussion

BMC CONTROL-D requires a started task that will be restricted to certain resources, datasets, 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-224112 in V7R2