{"stig":{"title":"z/OS BMC CONTROL-D for ACF2 Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224106","ruleId":"SV-224106r1141432_rule","severity":"medium","ruleTitle":"BMC CONTROL-D configuration/parameter values are not specified properly.","description":"BMC CONTROL-D configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data.","checkContent":"Refer to the following applicable reports produced by the z/OS Data Collection:\n\n- IOA.RPT(SECPARM).\n\nAutomated Analysis\nRefer to the following report produced by the z/OS Data Collection:\n\n- PDI(ZCTD0040).\n\nThe following keywords will have the specified values in the BMC CONTROL-D security parameter member. This is not a finding.\n\nKeyword\tValue\nDEFMCHKD\t$$CTDEDM\nSECTOLD\tNO\nDFMD01\tEXTEND\nDFMD04\tEXTEND\nDFMD08\tEXTEND\nDFMD19\tEXTEND\nDFMD23\tEXTEND\nDFMD24\tEXTEND\nDFMD26\tEXTEND\nDFMD27\tEXTEND","fixText":"The BMC CONTROL-D Systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Set the standard values for the BMC CONTROL-D security parameters for the specific ACP environment along with additional IOA security parameters with standard values as documented below.\n\nKeyword\tValue\nDEFMCHKD\t$$CTDEDM\nSECTOLD\tNO\nDFMD01\tEXTEND\nDFMD04\tEXTEND\nDFMD08\tEXTEND\nDFMD19\tEXTEND\nDFMD23\tEXTEND\nDFMD24\tEXTEND\nDFMD26\tEXTEND\nDFMD27\tEXTEND","ccis":["CCI-000381"]},{"vulnId":"V-224107","ruleId":"SV-224107r1041234_rule","severity":"medium","ruleTitle":"BMC CONTROL-D security exits are not installed or configured properly.","description":"The BMC CONTROL-D security exits enable access authorization checking to BMC CONTROL-D commands, features, and online functionality. If these exit(s) is (are) not in place, activities by unauthorized users may result. BMC CONTROL-D security exit(s) interface with the ACP. If an unauthorized exit was introduced into the operating environment, system security could be weakened or bypassed. These exposures may result in the compromise of the operating system environment, ACP, and customer data.","checkContent":"Interview the systems programmer responsible for the BMC CONTROL-D. Determine if the site has modified the following security exit(s):\n\nCTDSE01\nCTDSE04\nCTDSE08\nCTDSE19\nCTDSE24\nCTDSE28\n\nEnsure the above security exit(s) has (have) not been modified.\n\nIf the above security exit(s) has (have) been modified, ensure that the security exit(s) has (have) been approved by the site systems programmer and the approval is on file for examination.","fixText":"The systems programmer responsible for the BMC CONTROL-D will review the BMC CONTROL-D operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s):\n\nCTDSE01\nCTDSE04\nCTDSE08\nCTDSE19\nCTDSE24\nCTDSE28\n\nEnsure that the security exit(s) has (have) not been modified.\n\nIf the security exit(s) has (have) been modified, ensure the security exit(s) has (have) been checked as to not violate any security integrity within the system and approval documentation is on file.","ccis":["CCI-001744"]},{"vulnId":"V-224108","ruleId":"SV-224108r1141435_rule","severity":"medium","ruleTitle":"BMC CONTROL-D installation datasets will be properly protected.","description":"BMC CONTROL-D installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(CTDRPT).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZCTD0000).\n\nVerify that the accesses to the BMC CONTROL-D installation datasets are properly restricted. If the following guidance is true, this is not a finding.\n\nThe ACF2 dataset access authorizations restrict READ access to auditors, BMC users, security personnel (domain level and decentralized), and BMC STCs and/or batch users.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access is logged.","fixText":"The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D installation datasets is 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.\n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.\n\n(Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be: \nSYS2.IOA.*.CTDI\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nIOA.-.CTDI.-  UID(<syspaudt>) R(A) W(L) A(L) E(A)\nIOA.-.CTDI.-  UID(<audtaudt>) R(A) E(A)\nIOA.-.CTDI.-  UID(<bmcuser>) R(A) E(A)\nIOA.-.CTDI.-  UID(<secaaudt>) R(A) E(A)\nIOA.-.CTDI.-  UID(<secdaudt>) R(A) E(A)\nIOA.-.CTDI.-  UID(CONTROLD) R(A) E(A)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224109","ruleId":"SV-224109r1141438_rule","severity":"medium","ruleTitle":"BMC CONTROL-D STC datasets must be properly protected.","description":"BMC CONTROL-D STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(CTDSTC).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZCTD0001).\n\nVerify that the accesses to the BMC CONTROL-D STC datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset access authorizations restrict READ access to auditors and CONTROL-D end users.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to BMC STCs and/or batch users.\n\nThe ACF2 dataset access authorizations restrict UPDATE access to centralized and decentralized security personnel.","fixText":"The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D STC datasets is 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.\n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.\n\n(Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be: \nSYS3.IOA.*.CTDO\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS3)\nIOA.-.CTDO.- UID(syspaudt) R(A) W(A) A(A) E(A)\nIOA.-.CTDO.- UID(tstcaudt) R(A) W(A) A(A) E(A)\nIOA.-.CTDO.- UID(BMC STCs) R(A) W(A) A(A) E(A)\nIOA.-.CTDO.- UID(secaaudt) R(A) W(A) E(A)\nIOA.-.CTDO.- UID(secdaudt) R(A) W(A) E(A)\nIOA.-.CTDO.- UID(audtaudt) R(A) E(A)\nIOA.-.CTDO.- UID(bmcuser) R(A) E(A)","ccis":["CCI-001499"]},{"vulnId":"V-224110","ruleId":"SV-224110r1141441_rule","severity":"medium","ruleTitle":"BMC CONTROL-D user datasets must be properly protected.","description":"BMC CONTROL-D User datasets, CDAM and Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(CTMUSER).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZCTD0002).\n\nVerify that the accesses to the BMC CONTROL-D User datasets are properly restricted. If the following guidance is true, this is not a finding.\n\nThe ACF2 dataset access authorizations restrict READ access to auditors.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users.\n\nThe ACF2 dataset access authorizations restrict UPDATE access to centralized and decentralized security personnel and/or CONTROL-D end users.","fixText":"The ISSO must ensure that WRITE and/or greater access to BMC CONTROL-D User datasets is 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.\n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer must identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.\n\n(Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be: \nSYS3.IOA.*.CTDR\nCTRUSR\nCTDSRV\nCTDJB1\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS3)\nIOA.-.CTDR.- UID(syspaudt) R(A) W(A) A(A) E(A)\nIOA.-.CTDR.- UID(tstcaudt) R(A) W(A) A(A) E(A)\nIOA.-.CTDR.- UID(BMC STCs) R(A) W(A) A(A) E(A)\nIOA.-.CTDR.- UID(bmcuser) R(A) W(A) E(A)\nIOA.-.CTDR.- UID(secaaudt) R(A) W(A) E(A)\nIOA.-.CTDR.- UID(secdaudt) R(A) W(A) E(A)\nIOA.-.CTDR.- UID(audtaudt) R(A) E(A)\n\n$KEY(CTRUSR)\n- UID(syspaudt) R(A) W(A) A(A) E(A)\n- UID(tstcaudt) R(A) W(A) A(A) E(A)\n- UID(BMC STCs) R(A) W(A) A(A) E(A)\n- UID(bmcuser) R(A) W(A) E(A)\n- UID(secaaudt) R(A) W(A) E(A)\n- UID(secdaudt) R(A) W(A) E(A)\n- UID(audtaudt) R(A) E(A)\n\n$KEY(CTDSRV)\n- UID(syspaudt) R(A) W(A) A(A) E(A)\n- UID(tstcaudt) R(A) W(A) A(A) E(A)\n- UID(BMC STCs) R(A) W(A) A(A) E(A)\n- UID(bmcuser) R(A) W(A) E(A)\n- UID(secaaudt) R(A) W(A) E(A)\n- UID(secdaudt) R(A) W(A) E(A)\n- UID(audtaudt) R(A) E(A)\n\n$KEY(CTDJB1)\n- UID(syspaudt) R(A) W(A) A(A) E(A)\n- UID(tstcaudt) R(A) W(A) A(A) E(A)\n- UID(BMC STCs) R(A) W(A) A(A) E(A)\n- UID(bmcuser) R(A) W(A) E(A)\n- UID(secaaudt) R(A) W(A) E(A)\n- UID(secdaudt) R(A) W(A) E(A)\n- UID(audtaudt) R(A) E(A)","ccis":["CCI-001499"]},{"vulnId":"V-224111","ruleId":"SV-224111r1141444_rule","severity":"medium","ruleTitle":"BMC CONTROL-D resources will be properly defined and protected.","description":"BMC CONTROL-D can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(ZCTD0020).\n- ACF2CMDS.RPT(RESOURCE) - Alternate report.\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZCTD0020).\n\nVerify 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.\n\nNote: 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\n\nThe ACF2 resources are defined with a default access of PREVENT.\n\nThe ACF2 resource access authorizations restrict access to the appropriate personnel.\n\nThe ACF2 resource logging requirements are specified.","fixText":"The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP.\n\nNote: 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\n\n(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 installed on a system through the product's installation guide and can be site specific.)\n\nUse 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.\n\nThe following commands are provided as a sample for implementing resource controls:\n\n$key($$addnot) type(ioa)\n- uid(<appsaudt>) allow\n- uid(<operaudt>) allow\n- uid(<pcspaudt>) allow\n- uid(<syspaudt>) allow\n- uid(*) prevent","ccis":["CCI-000213","CCI-002234"]},{"vulnId":"V-224112","ruleId":"SV-224112r1144176_rule","severity":"medium","ruleTitle":"BMC CONTROL-D Started Task name is not properly identified/defined to the system ACP.","description":"BMC CONTROL-D requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.","checkContent":"Refer to the following report produced by the ACF2 Data Collection:\n\n- ACF2CMDS.RPT(ATTSTC).\n\nVerify 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.\n\nSTC\nMUSASS\nNO-SMC","fixText":"The BMC CONTROL-D systems programmer and the ISSO will ensure that a product's Started Task(s) is properly Identified / defined to the System ACP. \n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.\n\nExample:\n\nSET LID\nCHANGE CONTROLD STC MUSASS NO-SMC","ccis":["CCI-000764"]}]}