What changed in z/OS BMC CONTROL-O for TSS STIG V7R2V7R2 changes

Check text

Refer to the following applicable reportsreport 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(ZCTO0040). TheIf the following keywords willspecify have the specified values in the BMC CONTROL-O security parameter member:, this is not a finding. Keyword Value DEFMCHKO $$CTOEDM SECTOLO NO DFMO01 EXTEND DFMO02 EXTEND DFMO03 EXTEND DFMO04 EXTEND DFMO08 EXTEND DFMO10 PROD (new for 6.3.xx) DFMO15 EXTEND

Fix text

The BMC CONTROL-O 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-O security parameters for the specific Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. Keyword Value DEFMCHKO $$CTOEDM SECTOLO NO DFMO01 EXTEND DFMO02 EXTEND DFMO03 EXTEND DFMO04 EXTEND DFMO08 EXTEND DFMO10 PROD (new for 6.3.xx) DFMO15 EXTEND

V-224589 in V7R2

Check text

Refer to the following applicable reportsreport produced by the z/OS Data Collection: - IOA.RPT(CTOPARM). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCTO0041). TheIf the following keywords willspecify have the specified values in the BMC CONTROL-O security parameter member:, this is not a finding. Keyword Value RUNTDFT OWNER RUNTCACH 100 AUTOMLOG V

Fix text

The BMC CONTROL-O 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-O security parameters for the specific Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. Keyword Value RUNTDFT OWNER RUNTCACH 100 AUTOMLOG V

V-224590 in V7R2

Fix text

The systemsystems programmer responsible for the BMC CONTROL-O will review the BMC CONTROL-O operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s): CTOSE01 CTOSE02 CTOSE03 CTOSE04 CTOSE08 CTOSE10 CTOSE15 Ensure that the security exit(s) has (have) not been modified. If 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.

V-224591 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTORPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTO0000). Verify that the accesses to the BMC CONTROL-O installation data sets are properly restricted. If the following guidance is true, this is not a finding. The TSS data set rules for the data sets restrictsrestrict READ access to auditors, BMC users, and BMC STCs and/or batch users. The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to systems programming personnel. The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-O 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, 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.*.CTOI. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.CTOI.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.CTOI.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS2.IOA.*.CTOI.) ACCESS(R) TSS PERMIT(&ltbmcuser>) DSN(SYS2.IOA.*.CTOI.) ACCESS(R) TSS PERMIT(CONTROLO) DSN(SYS2.IOA.*.CTOI.) ACCESS(R)

V-224592 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTOSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTO0001). Verify that the accesses to the BMC CONTROL-O STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrict READ access to auditors, operators, and domain level production control and scheduling personnel. ___ The TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set access authorizations restrict UPDATE access to the BMC users and BMC STCs and/or batch users.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-O STC data sets are limited to systems programmers only. UPDATE access can be given to BMC users and the BMC STCs and/or batch users. READ access can be given to auditors, operators, and domain level production control and scheduling personnel. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have what type of access and if required which type of access is logged. The installing systems programmer will identify any additional groups requiring access to specific data sets, and once documented, the installing systems programmer will work with the ISSO to see that they are properly restricted to the ACP (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.*.CTOO. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.IOA.*.CTOO.) ACCESS(ALL) TSS PERMIT(CONTROLO) DSN(SYS3.IOA.*.CTOO.) ACCESS(UPDATE) TSS PERMIT(&ltbmcuser>) DSN(SYS3.IOA.*.CTOO.) ACCESS(UPDATE) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.IOA.*.CTOO.) ACCESS(READ) TSS PERMIT(&ltoperaudt>) DSN(SYS3.IOA.*.CTOO.) ACCESS(READ) TSS PERMIT(&ltpcspaudt>) DSN(SYS3.IOA.*.CTOO.) ACCESS(READ)

V-224593 in V7R2

Check text

Refer to the following reportsreport produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCTO0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTO0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC CONTROL-O 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 TSS resources are owned or DEFPROT is specified for the resource class. The TSS resource access authorizations restrict access to the appropriate personnel. The TSS resource logging requirements are specified.

V-224594 in V7R2

Title

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

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review each BMC CONTROL-O STC/Batch ACID(s). forIf the following: ___ Defined withattributes Facilityare ofdefined, STCthis and/oris BATCH. ___ Definednot witha Master Facility of CONTROLOfinding. ___ IsFACILITY(STC, sourced to the BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR.) NOSUSPEND MASTFAC(CONTROLO)

Fix text

The BMC CONTROL-O systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly Identified identified/ defined to the Systemsystem ACP. If the product requires a Started Task, verify that it is properly defined to the Systemsystem 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: TSS CREATE(CONTROLO) TYPE(USER) - NAME('*STC* for IOA') DEPT(xxxx) - FAC(STC) - MASTFAC(CONTROLO) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

Discussion

BMC CONTROL-O 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-224595 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZCTO0032). VerifyIf that the BMC CONTROL-O started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The BMC CONTROL-O systemsystems programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the Systemsystem ACP. A unique ACID must be assigned for the BMC CONTROL-O started task(s) thruthrough a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(CONTOLO) ACID(CONTROLO)

Discussion

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.

V-224596 in V7R2

Check text

Refer to the following reportreports produced by the TSS Data Collection: - TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values. - TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup. EnsureIf the BMC CONTROL-O Facility Matrix table is defined as follows:, this is a finding. FAC(USERxx=NAME=CONTROLO,PGM=CTO,ID=nn,ACTIVE,SHRPRF) FAC(CONTROLO=ASUBM,NOABEND,MULTIUSER,NOXDEF,SIGN(S)) FAC(CONTROLO=RES,LUMSG,STMSG,WARNPW,NORNDPW) FAC(CONTROLO=NOAUDIT,NOTSOC,MODE=FAIL) FAC(CONTROLO=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

Fix text

The BMC CONTROL-O systemsystems programmer and the IAOISSO will ensure that the TOP SECRET Facility Matrix Table is proper defined using the following example: CONTROLO: FAC(USERxx=NAME=CONTROLO,PGM=CTO,ID=nn,ACTIVE,SHRPRF) FAC(CONTROLO=ASUBM,NOABEND,MULTIUSER,NOXDEF) FAC(CONTROLO=LUMSG,STMSG,SIGN(S),WARNPW,NORNDPW) FAC(CONTROLO=NOAUDIT,RES,NOTSOC,MODE=FAIL) FAC(CONTROLO=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

V-224597 in V7R2