What changed in z/OS CA 1 Tape Management for RACF STIG V7R2V7R2 changes

z/OS CA 1 Tape Management for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 11 checks updated. It has 11 checks, against 11 in V7R1.

  • 0 added
  • 0 removed
  • 11 updated

Updated fields: Check text 11Fix text 3Discussion 2

Updated in V7R2 (11)

V-224448CAT IICA 1 Tape Management system password will be changed from the default.Check text

Check text

Refer to the following report produced by the z/OS Data Collection: - CA1RPT(TMSTMVT) - for r11.5 and below. - CA1RPT(TMOOPTxx) - for r12.0 and above. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCA10041). For r11.5 and below refer to offset x'18' from the beginning of module TMSTMVT. For r12.0 and above refer to the SHUTDWN option specified in the TMOOPTxx. The TMOOPTxx member is specified in the TMOSYSxx member in the data set allocated by the TMSPARM DD statement in the TMSINIT STC. If the default CA 1 system password is not being utilized, this is not a finding. NOTE: The default system password for CA 1 provided by CA is CA1(TMS). The default system passwords provided by SSO are SSOCA1DF and SSOC@1DF.

V-224449CAT IICA 1 Tape Management user exits, when in use, must be reviewed and/or approved.Check text

Check text

Refer to the following report produced by the z/OS Data Collection: - CA1RPT(TMSCKLVL). Determine if CA 1 user exits, TMSUXnA and TMSUXnS (for r11.5 and below) or TMSXITA and TMSXITS (for r12.0 and above) are active. If both CA 1 user exits are not found, this is not a finding. If one or both user exits are installed and the following requirements are true, this is not a finding: ___ The usage and function of the user exit(s) is fully documented. ___ The use of the user exit(s) is approved. ___ All associated documentation is on file with the ISSO.

V-224450CAT IICA 1 Tape Management installation data sets must be properly protected.Check text

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CA1PROD). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10000). Verify that the accesses to the CA 1 Tape Management installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set rules for the data sets restricts READ access to all authorized users. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged. ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

V-224451CAT IICA-1 Tape Management STC data sets must be properly protected.Check text, Fix text

Check text

Refer to the following report produced by the RACF Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(CA1STC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10001). Verify that the accesses to CA1 Tape Management Started Tasks (STCs) 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. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations restrict WRITE and/or greater access to CA1 Tape Management STCs and/or batch users. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

Ensure that WRITE and/or greater access to CA1 Tape management STC data sets is limited to systems programmers and/or CA1 Tape management STC(s) and/or batch user(s) only. READ access can be given to auditors. (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: CA1.TMS* (Data sets that are altered by the product's STCs, this can be more specific.) The following commands are provided as a sample for implementing data set controls: Ad 'SYS3.CA1.TMS*.**' UACC(NONW) OWNER(SYS3) - AUDIT(FAILURES(READ)) - DATA('CA1 STC DS') PE 'CA1.TMS*.**' ID(&ltsyspaudt> ACC(A) PE 'CA1.TMS*.**' ID (&ltTape Management STCs and/or batch users >) ACC(A) PE 'CA1.TMS*.**' ID (&ltaudtaudt>) ACC(R)

V-224452CAT IICA 1 Tape Management TMC, AUDIT and optional RDS and VPD data sets will be properly protected.Check text, Fix text

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CA1RPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10003). EnsureVerify that all CA 1 Tape Management TMC, AUDIT and optional RDS and VPD data sets are properly protected. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restricts READ access to application support personnel, production control and scheduling personnel, operations personnel, and auditors. ___ The RACF data set access authorizations restricts WRITE and/or greater access to only systems programming personnel and tape management personnel. ___ The RACF data set access authorizations restricts UPDATE access is limited to CA 1 batch production jobs, and CA 1 started tasks. ___ The RACF data set access authorizations specify that all (i.e., failures and successes) ALTER access are logged. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

Fix text

The ISSO will ensure that WRITE and/or greater access to CA 1 TMC, AUDIT and optional RDS and VPD data sets are limited to only systems programming personnel and tape management personnel. UPDATE access can be given to CA 1 STCs and/or batch users. READ access can be given to application support personnel, production control and scheduling personnel, operations personnel, and auditors. ALTER access will be logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, 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 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.) Due to the unique file structure of the TMC and Audit data sets, CA 1 uses the YSVC programs to handle all direct I/O activity. Because standard OPEN/CLOSE macros are not used, typical data set security checks are not performed. Even if a user does not have readREAD authorityaccess to these data sets, the YSVC programs can enable that user to read and update records within these files. Therefore, control READ access to the TMC and Audit data sets by the YSVCUNCD and YSVCCOND resource names. Typical users should be restricted to conditional READ access. Restrict CA 1 batch production jobs, and CA 1 started tasks to the following access authority: Unconditional READ and UPDATE access to the TMC, Audit, Retention, and Vault Pattern Description data sets. NOTENote: READ and UPDATE access to the TMC and Audit data sets are controlled by the YSVCUNCD and YSVCCOND resource names, and by standard ACP data set controls, because some CA 1 utilities use conventional OPEN/CLOSE methods. The following commands are provided as a sample for implementing data set controls: ad 'SYS3.CA1.AUDIT.**' uaac(none) owner(SYS3) - audit(success(alter) failures(read)) ad 'SYS3.CA1.RDS.**' uaac(none) owner(SYS3) - audit(success(alter) failures(read)) ad 'SYS3.CA1.TMC.**' uaac(none) owner(SYS3) - audit(success(alter) failures(read)) ad 'SYS3.CA1.VPD.**' uaac(none) owner(SYS3) - audit(success(alter) failures(read)) pe 'SYS3.CA1.AUDIT.**' id(&ltaudtaudt>) acc(r) pe 'SYS3.CA1.AUDIT.**' id(&ltoperaudt>) acc(r) pe 'SYS3.CA1.AUDIT.**' id(&ltpcspaudt>) acc(r) pe 'SYS3.CA1.AUDIT.**' id(CA1 STCs) acc(u) pe 'SYS3.CA1.AUDIT.**' id(&ltsyspaudt>) acc(a) pe 'SYS3.CA1.AUDIT.**' id(&lttapeaudt>) acc(a) pe 'SYS3.CA1.AUDIT.**' id(&lttstcaudt>) acc(a) pe 'SYS3.CA1.RDS.**' id(&ltsyspaudt>) acc(a) pe 'SYS3.CA1.RDS.**' id(&lttapeaudt>) acc(a) pe 'SYS3.CA1.RDS.**' id(&lttstcaudt>) acc(a) pe 'SYS3.CA1.TMC.**' id(&ltappsaudt>) acc(r) pe 'SYS3.CA1.TMC.**' id(&ltaudtaudt>) acc(r) pe 'SYS3.CA1.TMC.**' id(&ltoperaudt>) acc(r) pe 'SYS3.CA1.TMC.**' id(&ltpcspaudt>) acc(r) pe 'SYS3.CA1.TMC.**' id(CA1 STCs) acc(u) pe 'SYS3.CA1.TMC.**' id(&ltsyspaudt>) acc(a) pe 'SYS3.CA1.TMC.**' id(&lttapeaudt>) acc(a) pe 'SYS3.CA1.TMC.**' id(&lttstcaudt>) acc(a) pe 'SYS3.CA1.VPD.**' id(&ltsyspaudt>) acc(a) pe 'SYS3.CA1.VPD.**' id(&lttapeaudt>) acc(a) pe 'SYS3.CA1.VPD.**' id(&lttstcaudt>) acc(a)

V-224453CAT IICA 1 Tape Management command resources must be properly defined and protected.Check text

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CA@MD). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10020). EnsureVerify that all CA 1 command resources are properly protected according to the requirements specified in CA 1 Command Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. ___ The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The RACF resource logging is specified as designated in the above table. ___ The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. ___ A Deny-By-Default entry of "**" is defined with UACC(NONE) and no Access Granted.

V-224454CAT IICA 1 Tape Management function and password resources must be properly defined and protected.Check text

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CA@APE). Refer to the following report produced by the z/OS Data Collection: - CA1RPT(TMSSECAB). - CA1RPT(TMSTMVT) - for r11.5 and below. - CA1RPT(TMOOPTxx) - for r12.0 and above. - CA1RPT(TMOSECxx) - for r12.6 and above. Automated Analysis requiring additional analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCA10021). EnsureVerify that all CA 1 function and password resources are properly protected according to the requirements specified in the CA 1 Function and Password Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. ___ The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The RACF resource logging is specified as designated in the above table. ___ The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. ___ A Deny-By-Default entry of "**" is defined with UACC(NONE) and no Access Granted. Note: CA 1 password resources may require additional analysis to ensure access authorization is justified. CA 1 system password is obtained at offset x'18' from the beginning of module TMSTMVT for r11.5 and below and SHUTDWN option specified in the TMOOPTxx for r12.0 and above. CA 1 Online User Passwords can be obtained from TMSSECAB for all releases or TMOSECxx, if present, for r12.6 and above.

V-224455CAT IICA 1 Tape Management Started Task name will be properly identified and/or defined to the system ACP.Check text, Discussion

Check text

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

Discussion

CA 1 Tape Management requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining 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.

V-224456CAT IICA 1 Tape Management Started task will be properly defined to the STARTED resource class for RACF.Check text, Discussion

Check text

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(ZCA10032). If the CA 1 Tape Management started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Discussion

Access to product resources shouldmust 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.

V-224457CAT IICA 1 Tape Management Resource Class will be defined or active in the ACP.Check text

Check text

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(SETROPTS). - DSMON.RPT(RACCDT) - Alternate list of active resource classes. Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZCA10038). If the CA 1 Tape Management resource class(es) is (are) active, this is not a finding.

V-224458CAT IICA 1 Tape Management external security options must be specified properly.Check text, Fix text

Check text

Refer to the following report produced by the z/OS Data Collection: - CA1RPT(TMSSTATS). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCA10040). CA 1 external security utilizing RACF is accomplished in the manner described in this section. NOTENote: The TMOOPTxx member is specified in the TMOSYSxx member in the data set allocated by the TMSPARM DD statement in the TMSINIT STC. By default, the suffix 00 is used for these members. However, overrides can be specified by PARM value(s) on the EXEC statement in the TMSINIT STC and/or in the TMOSYSxx member. Review the options and values of the below CA 1 parameters. If the options are set to the specified value, this is not a finding. CA 1 SECURITY OPTIONS - RACF Option Standard Value BATCH YES obsolete as of r12.0 CATSEC NO obsolete as of r12.0 CMD YES CREATE see Note 1 DSNB YES FUNC YES see Note 2 OCEOV NO see Note 3 PMASK Do not specify or change PSWD YES SCRTCH NO SECWTO YES UNDEF FAIL UX0AUPD NO see Note 4 YSVC YES Note 1 : The CREATE parameter defines the level of access that is required to create a data set on tape. The default value is UPDATE. However, the vendor recommends the value be set to CREATE if you are running CA Top Secret or ACF2 and ALTER if you are running RACF. Note 2 : The FUNC option provides supplementary security for BLP access. The tape label bypass privilege must still be specified in the RACF userid record to allow access to BLP processing. Note 3 : The vendor recommends that OCEOV be set to NO and the RACF SETROPTS option TAPEDSN be active. Be advised that if OCEOV is disabled and RACF TAPEDSN is not active, tape data set protection will not be in effect. Note 4 : The UX0AUPD will specify YES only if you alter the fields in the TMC and the TMSUXxA (for r11.5 and below) or TMSXITA (for r12.0 and above) is changed.

Fix text

The systems programmer/ISSO will ensure that the CA 1 external security options are specified in accordance with the ACP being used. CA 1 Tape Management ACP security interfaces are controlled by options coded in the TMOOPTxx member identified in the TMOSYSxx member of the data set allocated by the TMSPARM DD statement in the TMSINIT STC. The specific required option settings are dependent on the ACP in use on the system. CA 1 SECURITY OPTIONS - RACF OPTION STANDARD VALUE BATCH YES obsolete as of r12.0 CATSEC NO obsolete as of r12.0 CMD YES CREATE see note 1 DSNB YES FUNC YES see note 2 OCEOV NO see note 3 PMASK Do not specify or change PSWD YES SCRTCH NO SECWTO YES UNDEF FAIL UX0AUPD NO see note 4 YSVC YES Note 1 The CREATE parameter defines the level of access that is required to create a data set on tape. The default value is UPDATE. However, the vendor recommends the value be set to CREATE if you are running CA Top Secret or ACF2 and ALTER if you are running RACF. Note 2 The FUNC option provides supplementary security for BLP access. The tape label bypass privilege must still be specified in the ACF2 user LID record to allow access to BLP processing. Note 3 The vendor recommends that OCEOV be set to NO and the RACF SETROPTS option TAPEDSN be active. Be advised that if OCEOV is disabled and RACF TAPEDSN is not active, tape data set protection will not be in effect. Note 4 The UX0AUPD will specify YES only if you alter the fields in the TMC and the TMSUXxA (for r11.5 and below) or TMSXITA (for r12.0 and above) is changed.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.