V7R2 changes
z/OS BMC IOA for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 6 checks updated. It has 7 checks, against 7 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 6 updated
Updated fields: Check text 6Fix text 5Discussion 5Title 3
Updated in V7R2 (6)
V-224244CAT IIBMC IOA installation datasets will be properly protected.Title, Check text, Fix text, Discussion
Title
BMC IOA 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(IOARPT).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZIOA0000).
Verify that the accesses to the BMC IOA 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, operations, production control and scheduling personnel, 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 IOA installation datadatasets setsis 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 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 Access Control Program (ACP) 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.*.IOAI.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS2)
IOA.-.IOAI.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
IOA.-.IOAI.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)
IOA.-.IOAI.- UID(<audtaudt>) R(A) E(A)
IOA.-.IOAI.- UID(<bmcuser>) R(A) E(A)
IOA.-.IOAI.- UID(<operaudt>) R(A) E(A)
IOA.-.IOAI.- UID(<pcspaudt>) R(A) E(A)
IOA.-.IOAI.- UID(BMC STCs) R(A) E(A)
Discussion
BMC IOA 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-224245CAT IIBMC IOA STC datasets must be properly protected.Title, Check text, Fix text, Discussion
Title
BMC IOA 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(IOASTC).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZIOA0001).
Verify that the accesses to the BMC IOA 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 BMC users
___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel.
___ The ACF2 datadataset 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 datadatasets setsis 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 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.*.IOAO.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS3)
IOA.-.IOAO.- UID(<syspaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAO.- UID(<tstcaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAO.- UID(BMC STCs) R(A) W(A) E(A)
IOA.-.IOAO.- UID(<bmcadmin>)R(A) W(A) E(A)
IOA.-.IOAO.- UID(<audtaudt>)R(A) E(A)
IOA.-.IOAO.- UID(<bmcuser>) R(A) E(A)
Discussion
BMC IOA 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-224246CAT IIBMC IOA User datasets will be properly protected.Title, Check text, Fix text, Discussion
Title
BMC IOA User data sets will be properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(IOAUSER).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZIOA0002).
Verify that the accesses to the BMC IOA User datadatasets sets are properly restricted. If the following guidance is true, this is not a finding.
The ACF2 datadataset set access authorizations restrictsrestrict READ access to auditors.
The ACF2 datadataset set access authorizations restrictsrestrict WRITE and/or greater access to systems programming personnel.
The ACF2 datadataset set access authorizations restrictsrestrict WRITE and/or greater access to the BMC STCs and/or batch users.
The ACF2 datadataset 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 datadatasets setsis 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 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 Access Control Program (ACP) 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.*.IOAC.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS3)
IOA.-.IOAC.- UID(<syspaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAC.- UID(<tstcaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAC.- UID(BMC STCs) R(A) W(A) A(A) E(A)
IOA.-.IOAC.- UID(<bmcuser>) R(A) W(A) E(A)
IOA.-.IOAC.- UID(<pcspaudt>) R(A) W(A) E(A)
IOA.-.IOAC.- UID(<audtaudt>) R(A) E(A)
Discussion
BMC IOA User data setsdatasets, IOA Core 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-224247CAT IIBMC IOA resources will be properly defined and protected.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the ACF2dataset Data Collection and Data Set and Resource Data Collection:
- SENSITVE.RPT(ZIOA0020).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.
Automated Analysis
Refer to the following report produced by the Datadataset 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 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 Access Control Program (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 IOA Resources and BMC INCONTROL Resources Descriptions tables in the z/OS 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($$addcnd) type(ioa)
- uid(<autoaudt>) allow
- uid(<operaudt>) allow
- uid(<pcspaudt>) allow
- uid(<prodaudt>) allow
- uid(<syspaudt>) allow
- uid(*) prevent
Discussion
BMC IOA 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 systemsystems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.
V-224248CAT 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 ACF2 Data Collection:
- ACF2CMDS.RPT(ATTSTC).
Verify that the logonid(s) for the BMC IOA started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.
STC
MUSASS
NO-SMC
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 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.
The following commands are provided as a sample for defining Started Task(s):
SET LID
CHANGE IOAGATE STC MUSASS NO-SMC
Discussion
BMC IOA 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-224249CAT IIBMC IOA configuration/parameter values are not specified properly.Check text
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(ZIOA0040).
The following keywords will 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 IOAFAC
SAFSCLAS SURROGAT
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.