Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS BMC IOA for ACF2 Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-27
  • Released: 2025-10-01
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
BMC IOA security exits are not installed or configured properly.
CM-3 - Medium - CCI-001744 - V-224243 - SV-224243r1069967_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-001744
Version
ZIOA0060
Vuln IDs
  • V-224243
  • V-17985
Rule IDs
  • SV-224243r1069967_rule
  • SV-32018
The BMC IOA security exits enable access authorization checking to BMC IOA commands, features, and online functionality. If these exit(s) is (are) not in place, activities by unauthorized users may result. BMC IOA 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.
Checks: C-25916r1069965_chk

Interview the systems programmer responsible for the BMC IOA. Determine if the site has modified the following security exit(s): IOASE06 IOASE07 IOASE09 IOASE12 IOASE16 IOASE32 IOASE40 IOASE42 Ensure the above security exit(s) has (have) not been modified. If 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.

Fix: F-25904r1069966_fix

The system 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.

b
BMC IOA installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224244 - SV-224244r1141526_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZIOAA000
Vuln IDs
  • V-224244
  • V-16932
Rule IDs
  • SV-224244r1141526_rule
  • SV-31824
BMC IOA 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.
Checks: C-25917r1141524_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(IOARPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZIOA0000). Verify that the accesses to the BMC IOA installation datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors, BMC users, operations, production control and scheduling personnel, and BMC STCs and/or batch users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix: F-25905r1141525_fix

The ISSO will ensure that WRITE and/or greater access to BMC IOA installation datasets is 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 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 Access Control Program (ACP) active on the system. (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.) Datasets to be protected will be: SYS2.IOA.*.IOAI The following commands are provided as a sample for implementing dataset 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)

b
BMC IOA STC datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224245 - SV-224245r1141529_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZIOAA001
Vuln IDs
  • V-224245
  • V-17067
Rule IDs
  • SV-224245r1141529_rule
  • SV-31946
BMC IOA 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.
Checks: C-25918r1141527_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(IOASTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZIOA0001). Verify that the accesses to the BMC IOA STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors and BMC users The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset access authorizations restrict UPDATE access to the BMC STCs, batch users, and BMC administrators.

Fix: F-25906r1141528_fix

Ensure that WRITE and/or greater access to BMC IOA STC datasets is 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 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. (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.) Datasets to be protected will be: SYS3.IOA.*.IOAO The following commands are provided as a sample for implementing dataset 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)

b
BMC IOA User datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224246 - SV-224246r1141532_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZIOAA002
Vuln IDs
  • V-224246
  • V-21592
Rule IDs
  • SV-224246r1141532_rule
  • SV-32152
BMC IOA User datasets, 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 datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-25919r1141530_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(IOAUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZIOA0002). Verify that the accesses to the BMC IOA User datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. The ACF2 dataset access authorizations restrict UPDATE access to production control and scheduling personnel and the BMC users.

Fix: F-25907r1141531_fix

The ISSO will ensure that WRITE and/or greater access to BMC IOA User datasets is 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 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 Access Control Program (ACP) active on the system. (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.) Datasets to be protected will be: SYS3.IOA.*.IOAC The following commands are provided as a sample for implementing dataset 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)

b
BMC IOA resources will be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224247 - SV-224247r1141535_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZIOAA020
Vuln IDs
  • V-224247
  • V-17947
Rule IDs
  • SV-224247r1141535_rule
  • SV-32064
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 systems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.
Checks: C-25920r1141533_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(ZIOA0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset 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: F-25908r1141534_fix

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 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

b
BMC IOA Started Task name must be properly identified and defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224248 - SV-224248r1144183_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZIOAA030
Vuln IDs
  • V-224248
  • V-17452
Rule IDs
  • SV-224248r1144183_rule
  • SV-32076
BMC IOA 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.
Checks: C-25921r1141536_chk

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: F-25909r1141537_fix

The ISSO 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

b
BMC IOA configuration/parameter values are not specified properly.
CM-7 - Medium - CCI-000381 - V-224249 - SV-224249r1141540_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
ZIOAA040
Vuln IDs
  • V-224249
  • V-18014
Rule IDs
  • SV-224249r1141540_rule
  • SV-31958
BMC IOA 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.
Checks: C-25922r1141539_chk

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

Fix: F-25910r1069977_fix

The BMC IOA 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 IOA security parameters for the specific Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. 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