Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS BMC IOA for RACF Security Technical Implementation Guide

V7R1 · · · Released 02 Apr 2025 · 8 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Digest of Updates vs. V6R8 · 23 Nov 2022 ✎ 5

Comparison against the immediately-prior release (V6R8). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 5

  • V-224415 Medium fix BMC IOA security exits are not installed or configured properly.
  • V-224416 Medium descriptioncheckfix BMC IOA installation data sets will be properly protected.
  • V-224418 Medium descriptioncheckfix BMC IOA user data sets will be properly protected.
  • V-224419 Medium descriptioncheckfix BMC IOA resources must be properly defined and protected.
  • V-224422 Medium fix BMC IOA configuration/parameter values are not specified properly.
Sort by
b
BMC IOA security exits are not installed or configured properly.
CM-3 - Medium - CCI-001744 - V-224415 - SV-224415r1070111_rule
RMF Control
CM-3
Severity
M
CCI
CCI-001744
Version
ZIOA0060
Vuln IDs
  • V-224415
  • V-17985
Rule IDs
  • SV-224415r1070111_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-26092r1070109_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-26080r1070110_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 data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224416 - SV-224416r1070143_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZIOAR000
Vuln IDs
  • V-224416
  • V-16932
Rule IDs
  • SV-224416r1070143_rule
  • SV-31825
BMC IOA installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-26093r1070141_chk

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 RACF 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 RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26081r1070142_fix

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 update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter 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: ad 'SYS2.IOA.*.IOAI.**' uacc(none) owner(SYS2) - audit(success(update) failures(read)) - data('BMC IOA Install DS') pe 'SYS2.IOA.*.IOAI.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.IOA.*.IOAI.**' id(<audtaudt> <bmcuser> <operaudt>) acc(r) pe 'SYS2.IOA.*.IOAI.**' id(<pcspaudt> BMC STCs) acc(r) setr generic(dataset) refresh

b
BMC IOA STC data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224417 - SV-224417r958616_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZIOAR001
Vuln IDs
  • V-224417
  • V-17067
Rule IDs
  • SV-224417r958616_rule
  • SV-31947
BMC IOA STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26094r868426_chk

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 RACF data set access authorizations restrict READ access to auditors and BMC users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict UPDATE access to the BMC STCs, batch users and BMC administrators. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26082r868427_fix

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 Systems Programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing Systems Programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) 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: ad 'SYS3.IOA.*.IOAO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC IOA STC DS') pe 'SYS3.IOA.*.IOAO.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.IOA.*.IOAO.**' id(BMC STCs <bmcadmin>) acc(u) pe 'SYS3.IOA.*.IOAO.**' id(<audtaudt> <bmcuser>) acc(r) setr generic(dataset) refresh

b
BMC IOA user data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224418 - SV-224418r1070146_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZIOAR002
Vuln IDs
  • V-224418
  • V-21592
Rule IDs
  • SV-224418r1070146_rule
  • SV-32153
BMC IOA user data sets, 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 data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-26095r1070144_chk

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 RACF data set access authorizations restricts READ access to auditors. The RACF data set access authorizations restricts WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations restricts WRITE and/or greater access to the BMC STCs and/or batch users. The RACF data set access authorizations restricts UPDATE access to production control and scheduling personnel and the BMC users. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix: F-26083r1070145_fix

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 update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter 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: ad 'SYS3.IOA.*.IOAC.**' uacc(none) owner(SYS3) - audit(failures(read)) - data('BMC IOA User DS') pe 'SYS3.IOA.*.IOAC.**' id(<syspaudt> <tstcaudt> BMC STCs) acc(a) pe 'SYS3.IOA.*.IOAC.**' id(<bmcuser> <pcspaudt>) acc(u) pe 'SYS3.IOA.*.IOAC.**' id(<audtaudt>) acc(r) setr generic(dataset) refresh

b
BMC IOA resources must be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224419 - SV-224419r1070164_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZIOAR020
Vuln IDs
  • V-224419
  • V-17947
Rule IDs
  • SV-224419r1070164_rule
  • SV-32065
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-26096r1070162_chk

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 RACF resources are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource logging requirements are specified. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.

Fix: F-26084r1070163_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 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: rdef $ioa $$addcnd.** uacc(none) owner(admin) - audit(failure(read)) - data('protected per zioar020') pe $$addcnd.** cl($ioa) id(<autoaudt>) acc(alter) pe $$addcnd.** cl($ioa) id(<operaudt>) acc(alter) pe $$addcnd.** cl($ioa) id(<pcspaudt>) acc(alter) pe $$addcnd.** cl($ioa) id(<prodaudt>) acc(alter) pe $$addcnd.** cl($ioa) id(<syspaudt>) acc(alter)

b
BMC IOA Started Task name must be properly identified and defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224420 - SV-224420r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZIOAR030
Vuln IDs
  • V-224420
  • V-17452
Rule IDs
  • SV-224420r958482_rule
  • SV-32077
BMC IOA requires a started task that will be restricted to certain resources, datasets and other system functions. By 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.
Checks: C-26097r518923_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) Verify that the userid(s) for the BMC IOA started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED

Fix: F-26085r518924_fix

The IAO 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): au IOAGATE name('stc, BMC IOA') owner(stc) dfltgrp(stc) nopass

b
BMC IOA Started task(s) must be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-224421 - SV-224421r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZIOAR032
Vuln IDs
  • V-224421
  • V-17454
Rule IDs
  • SV-224421r958482_rule
  • SV-32181
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.
Checks: C-26098r518926_chk

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZIOA0032) Verify that the BMC IOA started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry.

Fix: F-26086r518927_fix

The BMC IOA system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the BMC IOA started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started IOAGATE.** uacc(none) owner(admin) audit(all(read)) stdata(user(IOAGATE) group(stc)) setr racl(started) ref

b
BMC IOA configuration/parameter values are not specified properly.
CM-7 - Medium - CCI-000381 - V-224422 - SV-224422r1070122_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
ZIOAR040
Vuln IDs
  • V-224422
  • V-18014
Rule IDs
  • SV-224422r1070122_rule
  • SV-31959
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-26099r518929_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: Keyword Value DEFMCHKI $$IOAEDM SECTOLI NO DFMI06 EXTEND DFMI07 EXTEND DFMI09 EXTEND DFMI12 EXTEND DFMI16 EXTEND DFMI32 EXTEND DFMI40 EXTEND DFMI42 EXTEND IOACLASS $IOA RACSCLAS SURROGAT IOATCBS YES

Fix: F-26087r1070121_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 $IOA RACSCLAS SURROGAT IOATCBS YES