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

z/OS BMC IOA for RACF STIG

  • Version/Release: V6R7
  • Published: 2018-09-20
  • Released: 2018-10-26
  • 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

b
BMC IOA installation data sets will be properly protected.
AC-3 - Medium - CCI-000213 - V-16932 - SV-31825r2_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZIOAR000
Vuln IDs
  • V-16932
Rule IDs
  • SV-31825r2_rule
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.Information Assurance OfficerSystems Programmer
Checks: C-6193r4_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-3264r4_fix

The IAO will ensure that WRITE and/or greater access to BMC IOA installation data sets are limited to System 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. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO 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: 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-17067 - SV-31947r3_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZIOAR001
Vuln IDs
  • V-17067
Rule IDs
  • SV-31947r3_rule
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.Information Assurance OfficerSystems Programmer
Checks: C-5231r3_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-377r2_fix

Ensure that WRITE and/or greater access to BMC IOA STC data sets are limited to System 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 IAO 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 Started Task name must be properly identified and defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-17452 - SV-32077r2_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZIOAR030
Vuln IDs
  • V-17452
Rule IDs
  • SV-32077r2_rule
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.Information Assurance Officer
Checks: C-835r3_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-18155r5_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-17454 - SV-32181r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZIOAR032
Vuln IDs
  • V-17454
Rule IDs
  • SV-32181r1_rule
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.Information Assurance OfficerInformation Assurance Manager
Checks: C-20346r1_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-3829r1_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 resources must be properly defined and protected.
AC-4 - Medium - CCI-000035 - V-17947 - SV-32065r3_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZIOAR020
Vuln IDs
  • V-17947
Rule IDs
  • SV-32065r3_rule
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 system programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.Information Assurance OfficerSystems Programmer
Checks: C-319r2_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-342r2_fix

The IAO will work with the systems programmer to verify that the following are properly specified in the 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 zOS 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 security exits are not installed or configured properly.
AC-4 - Medium - CCI-000035 - V-17985 - SV-32018r1_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZIOA0060
Vuln IDs
  • V-17985
Rule IDs
  • SV-32018r1_rule
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.Information Assurance OfficerSystems Programmer
Checks: C-5253r1_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-423r1_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 configuration/parameter values are not specified properly.
AC-4 - Medium - CCI-000035 - V-18014 - SV-31959r1_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZIOAR040
Vuln IDs
  • V-18014
Rule IDs
  • SV-31959r1_rule
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.Systems Programmer
Checks: C-3615r1_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-6681r1_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 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

b
BMC IOA User data sets will be properly protected
AC-3 - Medium - CCI-000213 - V-21592 - SV-32153r2_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZIOAR002
Vuln IDs
  • V-21592
Rule IDs
  • SV-32153r2_rule
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.Information Assurance OfficerSystems Programmer
Checks: C-3250r3_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-18484r4_fix

The IAO will ensure that WRITE and/or greater access to BMC IOA User data sets are limited to System 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. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO 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.*.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