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

z/OS BMC IOA for TSS STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 9 checks updated. It has 9 checks, against 9 in V7R1.

  • 0 added
  • 0 removed
  • 9 updated

Updated fields: Check text 8Fix text 7Discussion 2

Updated in V7R2 (9)

V-224598CAT IIBMC IOA security exits are not installed or configured properly.Fix text

Fix text

The systemsystems programmer responsible for the BMC IOA will review the BMC IOA operating environment. Ensure that the following security exit(s) is (are) installed properly. Determine if the site has modified the following security exit(s): IOASE06 IOASE07 IOASE09 IOASE12 IOASE16 IOASE32 IOASE40 IOASE42 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-224599CAT IIBMC IOA installation data sets will be properly protected.Check text, Fix text

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 TSS 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 TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel. The TSS data set access authorizations 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 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: TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.IOAI.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ) TSS PERMIT(&ltaudtaudt>) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ) TSS PERMIT(&ltbmcuser>) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ) TSS PERMIT(&ltoperaudt>) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ) TSS PERMIT(&ltpcspaudt>) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ) TSS PERMIT(BMC STCs) DSN(SYS2.IOA.*.IOAI.) ACCESS(READ)

V-224600CAT IIBMC IOA STC data sets must be properly protected.Check text, Fix text

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 TSS data set access authorizations restrict READ access to auditors and BMC users. ___ 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 STCs, batch users and BMC administrators.

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 Systemssystems Programmerprogrammer 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 Systemssystems Programmerprogrammer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented he will work with the ISSO to seeensure 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.*.IOAO. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.IOA.*.IOAO.) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(SYS3.IOA.*.IOAO.) ACCESS(ALL) TSS PERMIT(BMC STCs) DSN(SYS3.IOA.*.IOAO.) ACCESS(U) TSS PERMIT(&ltbmcadmin>) DSN(SYS3.IOA.*.IOAO.) ACCESS(U) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.IOA.*.IOAO.) ACCESS(R) TSS PERMIT(&ltbmcuser>) DSN(SYS3.IOA.*.IOAO.) ACCESS(R)

V-224601CAT IIBMC IOA User data sets will be properly protected.Check text, Fix text

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 TSS data set access authorizations restrictsrestrict READ access to auditors. The TSS data set access authorizations restrictsrestrict WRITE and/or greater access to systems programming personnel. The TSS data set access authorizations restrictsrestrict WRITE and/or greater access to the BMC STCs and/or batch users. The TSS data set access authorizations restrictsrestrict UPDATE access to production control and scheduling personnel and the BMC users.

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: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.IOA.*.IOAC.) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(SYS3.IOA.*.IOAC.) ACCESS(ALL) TSS PERMIT(BMC STCs) DSN(SYS3.IOA.*.IOAC.) ACCESS(ALL) TSS PERMIT(&ltbmcuser>) DSN(SYS3.IOA.*.IOAC.) ACCESS(U) TSS PERMIT(&ltpcspaudt>) DSN(SYS3.IOA.*.IOAC.) ACCESS(U) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.IOA.*.IOAC.) ACCESS(R)

V-224602CAT IIBMC IOA resources must be properly defined and protected.Check text

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 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-224603CAT IIBMC IOA Started Task name must be properly identified and defined to the system ACP.Check text, Fix text, Discussion

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). VerifyReview that the ACID(s) for the BMC IOA startedSTC/Batch taskACID(s) is (are) properly defined. If the following attributes are defined, this is not a finding. FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) MASTFAC(IOA) SOURCE(INTRDR) NOSUSPEND MASTFAC(IOA)

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 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. The following commands are provided as a sample for defining Started Task(s): TSS CREATE(IOAGATE) TYPE(USER) - NAME('*STC* for IOA') DEPT(xxxx) - FAC(STC,BATCH) - MASTFAC(IOA) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

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-224604CAT IIBMC IOA Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.Check text, Fix text, Discussion

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(ZIOA0032). VerifyIf that the BMC IOA started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The BMC IOA 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 IOA 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(IOAGATE) ACID(IOAGATE)

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-224605CAT IIBMC IOA is not properly defined to the Facility Matrix Table for Top Secret.Check text, Fix text

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 IOA Facility Matrix table is defined as follows:stated below, this is not a finding. FAC(USERxx=NAME=IOA,PGM=IOA,ID=nn,ACTIVE,SHRPRF,ASUBM) FAC(IOA=NOABEND,MULTIUSER,NOXDEF,SIGN(S),RES,LUMSG) FAC(IOA=STMSG,WARNPW,NORNDPW,NOAUDIT,NOTSOC,MODE=FAIL) FAC(IOA=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

Fix text

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

V-224606CAT IIBMC IOA configuration/parameter values are not specified properly.Check text

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(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 TSSCLAS ACIDCHK IOATCBS YES

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.