acceptedz/OS BMC IOA for ACF2 STIGDISASTIG.DOD.MILRelease: 7 Benchmark Date: 26 Oct 20186I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>ZB000000<GroupDescription></GroupDescription>ZIOAA000BMC IOA installation data sets will be properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000213CCI-002234The 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:
$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)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 ACF2 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 ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel.
___ The ACF2 data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged.ZB000001<GroupDescription></GroupDescription>ZIOAA001BMC IOA STC data sets must be properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-001499Ensure 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 System 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:
$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
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 ACF2 data set access authorizations restrict READ access to auditors and BMC users
___ The ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel.
___ The ACF2 data set access authorizations restrict UPDATE access to the BMC STCs, batch users and BMC administrators.ZB000030<GroupDescription></GroupDescription>ZIOAA030BMC IOA Started Task name must be properly identified and defined to the system ACP.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000764The 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):
SET LID
CHANGE IOAGATE STC MUSASS NO-SMCRefer 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-SMCRefer 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-SMCZB000020<GroupDescription></GroupDescription>ZIOAA020BMC IOA resources will be properly defined and protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000035CCI-002234The 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:
$key($$addcnd) type(ioa)
- uid(<autoaudt>) allow
- uid(<operaudt>) allow
- uid(<pcspaudt>) allow
- uid(<prodaudt>) allow
- uid(<syspaudt>) allow
- uid(*) prevent
Refer to the following report produced by the ACF2 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 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 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.
ZB000060<GroupDescription></GroupDescription>ZIOA0060BMC IOA security exits are not installed or configured properly.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000035The 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.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.ZB000040<GroupDescription></GroupDescription>ZIOAA040BMC IOA configuration/parameter values are not specified properly.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000035The 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 IOAFAC
SAFSCLAS SURROGAT
IOATCBS YESRefer 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 IOAFAC
SAFSCLAS SURROGAT
IOATCBS YESZB000002<GroupDescription></GroupDescription>ZIOAA002BMC IOA User data sets will be properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Systems Programmer</Responsibility><IAControls></IAControls>DPMS Target BMC IOADISADPMS TargetBMC IOA2002CCI-000213The 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:
$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)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 ACF2 data set access authorizations restricts READ access to auditors.
___ The ACF2 data set access authorizations restricts WRITE and/or greater access to systems programming personnel.
___ The ACF2 data set access authorizations restricts WRITE and/or greater access to the BMC STCs and/or batch users.
___ The ACF2 data set access authorizations restricts UPDATE access to production control and scheduling personnel and the BMC users.