STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS BMC CONTROL-O for TSS Security Technical Implementation Guide

V-224597

CAT II (Medium)

BMC CONTROL-O is not properly defined to the Facility Matrix Table for Top Secret.

Rule ID

SV-224597r1145966_rule

STIG

z/OS BMC CONTROL-O for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Improperly defined security controls for the BMC CONTROL-O could result in the compromise of the network, operating system, and customer data.

Check Content

Refer to the following reports produced by the TSS Data Collection:

- TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values.
- TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup.

If the BMC CONTROL-O Facility Matrix table is defined as follows, this is a finding.

FAC(USERxx=NAME=CONTROLO,PGM=CTO,ID=nn,ACTIVE,SHRPRF)
FAC(CONTROLO=ASUBM,NOABEND,MULTIUSER,NOXDEF,SIGN(S))
FAC(CONTROLO=RES,LUMSG,STMSG,WARNPW,NORNDPW)
FAC(CONTROLO=NOAUDIT,NOTSOC,MODE=FAIL)
FAC(CONTROLO=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

Fix Text

The BMC CONTROL-O systems programmer and the ISSO will ensure that the TOP SECRET Facility Matrix Table is proper defined using the following example:

CONTROLO:
FAC(USERxx=NAME=CONTROLO,PGM=CTO,ID=nn,ACTIVE,SHRPRF)
FAC(CONTROLO=ASUBM,NOABEND,MULTIUSER,NOXDEF)
FAC(CONTROLO=LUMSG,STMSG,SIGN(S),WARNPW,NORNDPW)
FAC(CONTROLO=NOAUDIT,RES,NOTSOC,MODE=FAIL)
FAC(CONTROLO=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)