IBM z/OS TSS Security Technical Implementation Guide
- Version/Release: V8R12
- Published: 2023-12-18
-
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
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000185
- Version
- TSS0-CE-000010
- Vuln IDs
-
- V-223871
- V-98449
- Rule IDs
-
- SV-223871r877712_rule
- SV-107553
Checks: C-25544r868923_chk
Execute the CA-TSS SAFCRRPT using the following as SYSIN input: RECORDID(-) DETAIL TRUST FIELDS(ISSUER SUBJECT ACTIVE EXPIRE TRUST) If no certificate information is found, this is not a finding. NOTE: Certificates are only valid when their Status is TRUST. Therefore, you may ignore certificates with the NOTRUST status during the following check. If the digital certificate information indicates that the issuer's distinguished name leads to one of the following this is not a finding: a) A DoD PKI Root Certification Authority b) An External Root Certification Authority (ECA) c) An approved External Partner PKI's Root Certification Authority The DoD Cyber Exchange website contains information as to which certificates may be acceptable (https://public.cyber.mil/pki-pke/interoperability/ or https://cyber.mil/pki-pke/interoperability/). Examples of an acceptable DoD CA are: DoD PKI Class 3 Root CA DoD PKI Med Root CA
Fix: F-25532r868924_fix
Remove or replace certificates where the issuer's distinguished name does not lead to a DoD PKI Root Certification Authority; External Root Certification Authority (ECA); or an approved External Partner PKI's Root Certification Authority. The DoD Cyber Exchange website contains information as to which certificates may be acceptable (https://public.cyber.mil/pki-pke/interoperability/ or https://cyber.mil/pki-pke/interoperability/).
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000185
- Version
- TSS0-CE-000020
- Vuln IDs
-
- V-223872
- V-98451
- Rule IDs
-
- SV-223872r877713_rule
- SV-107555
Checks: C-25545r516015_chk
Execute the CA-TSS SAFCRRPT using the following as SYSIN input: RECORDID(-) DETAIL FIELDS(ISSUER SUBJECT ACTIVE EXPIRE TRUST) If no certificate information is found, this is not a finding. NOTE: Certificates are only valid when their Status is TRUST. Therefore, you may ignore certificates with the NOTRUST status during the following checks. Check the expiration for each certificate with a status of TRUST. If the expiration date has passed, this is a finding.
Fix: F-25533r516016_fix
If the certificate is a user or device certificate with a status of TRUST, follow procedures to obtain a new certificate or re-key certificate. If it is an expired CA certificate remove it.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-CE-000030
- Vuln IDs
-
- V-223873
- V-98453
- Rule IDs
-
- SV-223873r877714_rule
- SV-107557
Checks: C-25546r516018_chk
If certificate name filtering is in use, the ISSM should document each active filter rule and have written approval to use the rule. Issue the following TSS command to list any certificate name filters defined to TSS: TSS LIST(SDT) CERTMAP(ALL) If there is nothing to list, this is not a finding. NOTE: Certificate name filters are only valid when their Status is TRUST. Therefore, you may ignore filters with the NOTRUST status. If certificate name filters are defined and they have a Status of TRUST, certificate name filtering is in use. If certificate name filtering is in use and filtering rules have been documented and approved by the ISSM, this is not a finding. If certificate name filtering is in use and filtering rules have not been documented and approved by the ISSM, this is a finding.
Fix: F-25534r516019_fix
Ensure any certificate name filtering rules in use are documented and approved by the ISSM.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000010
- Vuln IDs
-
- V-223874
- V-98455
- Rule IDs
-
- SV-223874r877715_rule
- SV-107559
Checks: C-25547r516021_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(ADMIN, BASIC) If any ACIDs other than TYPE=CENTRAL (SCA/MSCA) has the following administrative authority, this is a finding. FACILITIES(ALL) PROGRAM(ALL) PROGRAM(OWN) RESOURCE(ALL) ROSRES(ALL) VOLUME(ALL) VOLUME(OWN) MISC1(ALL) MISC1(LCF) MISC1(LTIME) MISC1(RDT) MISC1(USER) MISC2(ALL) MISC2(DLF) MISC2(NDT) MISC2(SMS) MISC4(ALL) MISC8(ALL) MISC8(LISTAPLU) MISC8(LISTRDT) MISC8(LISTSDT) MISC8(LISTSTC) MISC8(MCS) MISC9(ALL) MISC9(BYPASS) MISC9(CONSOLE) MISC9(GLOBAL) MISC9(MASTFAC) MISC9(MODE) MISC9(STC) MISC9(TRACE)
Fix: F-25535r868926_fix
Review all security administrator ACIDs. Evaluate the impact of limiting the amount of excessive administrative authorities. Develop a plan of action and implement the changes. The following are examples for other types (DCA, VCA, ZCA, LSCA) that require administrative authorities: (note: these are examples and does not mean everyone should have all of these levels). data set(ALL)ACC(ALL) data set(XAUTH,OWN,REPORT,AUDIT,INFO)ACC(ALL) OTRAN(ALL)ACC(ALL) ACID(ALL) ACID(INFO,MAINTAIN) MISC1(INSTDATA,SUSPEND,TSSSIM,NOATS) MISC2(TSO,TARGET) MISC8(PWMAINT,REMASUSP) MISC9(GENERIC) FACILITY(BATCH, TSO, ROSCOE, CICS, xxxx) Where "xxxx" is a facility the application security team grants access into for their application users. This must not be STC, CA1, DFHSM, or other domain level mastfac/facility. This is only for those "onlines" that users truly log in to for access to their applications/data such as TSO, CICS regions, IDMS, ROSCOE, FTP, etc. TSS ADMIN(acid)RESOURCE(REPORT,INFO,AUDIT) can be allowed and is required to run TSSUTIL reports. Note: "RESOURCE" can specify a more specific Resource Class, such as "OTRAN", "data set", "IDMSGON", "PROGRAM" for non SCA/MSCA type of accounts. These administrators will not have "RESOURCE" specified in administrative authority. Note: "ALL" will display as "*ALL*" but also means approved for any single administrative authority under that specific item.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000020
- Vuln IDs
-
- V-223875
- V-98457
- Rule IDs
-
- SV-223875r877716_rule
- SV-107561
Checks: C-25548r516024_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(BASIC) If only authorized personnel have BLP access and documentation for access is on file with the ISSO, this is not a finding.
Fix: F-25536r516025_fix
Review all ACIDs with the BLP attribute. Evaluate the impact of removing BLP access from unauthorized personnel. Develop a plan of action and remove BLP access from unauthorized ACIDs.
- RMF Control
- AC-2
- Severity
- High
- CCI
- CCI-000015
- Version
- TSS0-ES-000030
- Vuln IDs
-
- V-223876
- V-98459
- Rule IDs
-
- SV-223876r877717_rule
- SV-107563
Checks: C-25549r516027_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the global MODE Control Option value is set to "FAIL", this is not a finding. If the global MODE Control Option value is not set to "FAIL", this is a finding. Additional analysis may be required under the following conditions: Mode(IMPL) is allowed while a system is in implementation with a documented process that includes an implementation completion date.
Fix: F-25537r516028_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the MODE control option to (FAIL) and proceed with the change.
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- TSS0-ES-000040
- Vuln IDs
-
- V-223877
- V-98461
- Rule IDs
-
- SV-223877r877718_rule
- SV-107565
Checks: C-25550r516030_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the NPWRTHRESH Control Option value is not set to NPWRTHRESH(02), this is a finding.
Fix: F-25538r516031_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. NPWRTHRESH(02)
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- TSS0-ES-000050
- Vuln IDs
-
- V-223878
- V-98463
- Rule IDs
-
- SV-223878r877719_rule
- SV-107567
Checks: C-25551r516033_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the NPPTHRESH Control Option value is not set to NPWRTHRESH(02), this is a finding.
Fix: F-25539r516034_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. NPPTHRESH(02)
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- TSS0-ES-000060
- Vuln IDs
-
- V-223879
- V-98465
- Rule IDs
-
- SV-223879r877720_rule
- SV-107569
Checks: C-25552r516036_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PTHRESH Control Option value is not set to PTHRESH(02), this is a finding.
Fix: F-25540r516037_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. PTHRESH(02)
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- TSS0-ES-000070
- Vuln IDs
-
- V-223880
- V-98467
- Rule IDs
-
- SV-223880r877721_rule
- SV-107571
Checks: C-25553r516039_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PTHRESH Control Option value is not set to NPPTHRESH(02), this is a finding.
Fix: F-25541r516040_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. NPPTHRESH(02)
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- TSS0-ES-000080
- Vuln IDs
-
- V-223881
- V-98469
- Rule IDs
-
- SV-223881r877722_rule
- SV-107573
Checks: C-25554r516755_chk
Refer to the SMFPRMxx member in SYS1.PARMLIB. Determine the SMF and/or Logstream data set name. If the following statements are true, this is not a finding. -The ESM data set rules for the SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) restrict ALTER access to only z/OS systems programming personnel. -The ESM data set rules for the SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) restrict UPDATE access to z/OS systems programming personnel, and/or batch jobs that perform SMF dump processing and others as approved by ISSM. -The ESM data set rules for the SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) restrict READ access to auditors and others approved by the ISSM. -The ESM data set rules for SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.
Fix: F-25542r516756_fix
Ensure that allocate/alter authority to SMF collection files is limited to only systems programming staff and and/or batch jobs that perform SMF dump processing; access can be granted to others as determined by ISSM. Ensure that read access is limited to auditors. Access may be granted to others as determined by the ISSM. Ensure the accesses are being logged. Ensure that all (i.e., failures and successes) WRITE or greater access are logged. Ensure read access failures are logged.
- RMF Control
- AU-12
- Severity
- High
- CCI
- CCI-000171
- Version
- TSS0-ES-000090
- Vuln IDs
-
- V-223882
- V-98471
- Rule IDs
-
- SV-223882r877723_rule
- SV-107575
Checks: C-25555r516045_chk
Execute a data set list of access to SYS1.PARMLIB. If the ESM data set rules for SYS1.PARMLIB allow inappropriate (e.g., global READ) access, this is a finding. If data set rules for SYS1.PARMLIB do not restrict READ, WRITE or greater access to only systems programming personnel, this is a finding. If data set rules for SYS1.PARMLIB do not restrict READ and UPDATE access to only domain level security administrators, this is a finding. If data set rules for SYS1.PARMLIB do not restrict READ access to only system Level Started Tasks, authorized Data Center personnel, and auditors, this is a finding. If data set rules for SYS1.PARMLIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged, this is a finding.
Fix: F-25543r516046_fix
Ensure the accesses are being logged.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000186
- Version
- TSS0-ES-000100
- Vuln IDs
-
- V-223883
- V-98473
- Rule IDs
-
- SV-223883r877725_rule
- SV-107577
Checks: C-25556r877724_chk
Any keys or Certificates must be managed in ICSF or the external security manager and not in UNIX files. From the ISPF Command Shell enter: OMVS enter find / -name *.kdb and Find / -name *.jks If any files are present, this is a finding. OMVS enter find / -name *.kdb and Find / -name *.jks If any files are present, this is a finding.
Fix: F-25544r811041_fix
Define all Keys/Certificates to ICSF or the security database. Remove all .kdb and .jks key files.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000192
- Version
- TSS0-ES-000120
- Vuln IDs
-
- V-223885
- V-98477
- Rule IDs
-
- SV-223885r877726_rule
- SV-107581
Checks: C-25558r516054_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the NEWPHRASE Control Option conforms to the following requirements, this is not a finding. MA=1-32 MN=1-32 ID MAX=100 MIN=15-100 MINDAYS=1 NR=0-1 SC=1-32 WARN=1-10 If the PPSCHAR Control Option conform to the allowable list defined in CA Top Secret for z/OS Control Options Guide, this is not a finding. Note: These characters will be specified at a minimum. "40" represents the blank character. Characters can be identified by their character or hex equivalent.
Fix: F-25546r868928_fix
Note: Support of mixed case passwords can only be set when the security file has been copied by TSSXTEND with the option NEWPWBLOCK. Configure the NEWPHRASE Control Option values to the following requirements: MA=1-32 MN=1-32 ID MAX=100 MIN=15-100 MINDAYS=1 NR=0-1 SC=1-32 WARN=1-10 Configure the PPSCHAR Control Option to the allowable list defined in CA Top Secret for z/OS User Guide. Note: These characters will be specified at a minimum. "40" represents the blank character. Characters can be identified by their character or hex equivalent. Example: TSS MODIFY NEWPHRASE(MA=1,MN=1,ID,MAX=100,MIN=15,MINDAYS=1,NR=1,SC=1,WARN=10) TSS MODIFY PPSCHAR(c,c,c,c,...) (Use the allowable list defined in CA Top Secret for z/OS Control Options Guide.)
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000194
- Version
- TSS0-ES-000130
- Vuln IDs
-
- V-223886
- V-98479
- Rule IDs
-
- SV-223886r877727_rule
- SV-107583
Checks: C-25559r516057_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the NEWPW Control Option values conform to the following requirements, this is not a finding. NEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC) NOTE: For the Option SC, the PASSCHAR control option should be set to the allowable list defined in CA Top Secret for z/OS Control Options Guide. NOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.
Fix: F-25547r516058_fix
Note: Support of mixed case passwords can only be set when the security file has been copied by TSSXTEND with the option NEWPWBLOCK. Configure the NEWPW Control Option values conform to the following requirements: NEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC) NOTE: For the Option SC, the PASSCHAR control option should be set to the allowable list defined in CA Top Secret for z/OS Control Options Guide. NOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.
- RMF Control
- IA-5
- Severity
- High
- CCI
- CCI-000196
- Version
- TSS0-ES-000140
- Vuln IDs
-
- V-223887
- V-98481
- Rule IDs
-
- SV-223887r877728_rule
- SV-107585
Checks: C-25560r516060_chk
From the ISPF command shell line enter: TSS MODIFY(STATUS) If either of the following is included, this is not a finding. AES_ENCRYPTION(Active,128) AES_ENCRYPTION(Active,256)
Fix: F-25548r516061_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option as specified below: Convert passwords/password phrases from Triple-DES encryption to 128-bit AES or 256-bit encryption by running TSSMAINT (with the AESENCRYPT option specified) and then running TSSXTEND to copy the old security file to the new security file. Please consult CA-TSS Installation guide for more information.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000199
- Version
- TSS0-ES-000150
- Vuln IDs
-
- V-223888
- V-98483
- Rule IDs
-
- SV-223888r877729_rule
- SV-107587
Checks: C-25561r516063_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PWEXP Control Option value is not set to PWEXP(60), this is a finding.
Fix: F-25549r516064_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the following control option setting as specified and proceed with the change. PWEXP(60)
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000199
- Version
- TSS0-ES-000160
- Vuln IDs
-
- V-223889
- V-98485
- Rule IDs
-
- SV-223889r877730_rule
- SV-107589
Checks: C-25562r516066_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PPEXP Control Option will conform to the following requirements, this is not a finding. PPEXP(60)
Fix: F-25550r516067_fix
Configure the PPEXP Control Option value to conform to the following requirements. PPEXP(60) Example: TSS MODIFY PPEXP(60)
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000200
- Version
- TSS0-ES-000170
- Vuln IDs
-
- V-223890
- V-98487
- Rule IDs
-
- SV-223890r877731_rule
- SV-107591
Checks: C-25563r516069_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PWHIST Control Option value is not set to PWHIST(10) or greater, this is a finding.
Fix: F-25551r516070_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the following control option setting as specified and proceed with the change. PWHIST(10) or greater
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000200
- Version
- TSS0-ES-000180
- Vuln IDs
-
- V-223891
- V-98489
- Rule IDs
-
- SV-223891r877732_rule
- SV-107593
Checks: C-25564r516072_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PPHIST Control Option conforms to the following requirements, this is not a finding. PPHIST(10-64)
Fix: F-25552r516073_fix
Configure the PPHIST Control Option value to conforms to the following requirements: PPHIST(10-64) Example: TSS MODIFY PPHIST(10)
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000205
- Version
- TSS0-ES-000190
- Vuln IDs
-
- V-223892
- V-98491
- Rule IDs
-
- SV-223892r877733_rule
- SV-107595
Checks: C-25565r516075_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the NEWPW Control Option values conform to the following requirements, this is not a finding. NEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC) NOTE: For the Option SC, the PASSCHAR control option should be set to the allowable list defined in CA Top Secret for z/OS Control Options Guide. NOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.
Fix: F-25553r516076_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified and proceed with the change. (Support of mixed case passwords can only be set when the security file has been copied by TSSXTEND with the option NEWPWBLOCK.) Configure the NEWPW Control Option values to conform to the following requirements: NEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC) NOTE: For the Option SC, the PASSCHAR control option should be set to the allowable list defined in CA Top Secret for z/OS Control Options Guide. NOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000200
- Vuln IDs
-
- V-223893
- V-98493
- Rule IDs
-
- SV-223893r877734_rule
- SV-107597
Checks: C-25566r516078_chk
Execute a data set list of access to SYS1.LINKLIB. If the ESM data set rules for SYS1.LINKLIB allow inappropriate (e.g., global READ) access, this is a finding. If data set rules for SYS1.LINKLIB do not restrict READ, WRITE or greater access to only systems programming personnel, this is a finding. If data set rules for SYS1.LINKLIB do not restrict READ and UPDATE access to only domain level security administrators, this is a finding. If data set rules for SYS1.LINKLIB do not restrict READ access to only system Level Started Tasks, authorized Data Center personnel, and auditors, this is a finding. If data set rules for SYS1.LINKLIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged, this is a finding.
Fix: F-25554r516079_fix
Configure the ESM rules for SYS1.LINKLIB limit access to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000210
- Vuln IDs
-
- V-223894
- V-98495
- Rule IDs
-
- SV-223894r877735_rule
- SV-107599
Checks: C-25567r516081_chk
Execute a data set list of access for SYS1.SVCLIB. If all of the following are true, this is not a finding. If any of the following are untrue, this is a finding. ESM data set rules for SYS1.SVCLIB restrict WRITE or greater access to only z/OS systems programming personnel. ESM data set rules for SYS1.SVCLIB specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25555r516082_fix
Configure WRITE or greater access to SYS1.SVCLIB to be limited to system programmers only and all WRITE or greater access is logged and reviewed. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes for SYS1.SVCLIB. SYS1.SVCLIB contains SVCs and I/O appendages as such: they are very powerful and will be strictly controlled to avoid compromising system integrity.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000220
- Vuln IDs
-
- V-223895
- V-98497
- Rule IDs
-
- SV-223895r877736_rule
- SV-107601
Checks: C-25568r516084_chk
Execute a data set list of access for SYS1.IMAGELIB. If the following guidance is true, this is not a finding. The ACP data set rules for SYS1.IMAGELIB do not restrict WRITE or greater access to only systems programming personnel. The ACP data set rules for SYS1.IMAGELIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25556r516085_fix
Configure WRITE or greater access to SYS1.IMAGELIB to be limited to system programmers only and all WRITE or greater access is logged. Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect SYS1.IMAGELIB. SYS1.IMAGELIB is automatically APF-authorized. This data set contains modules, images, tables, and character sets which are essential to system print services.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000230
- Vuln IDs
-
- V-223896
- V-98499
- Rule IDs
-
- SV-223896r877737_rule
- SV-107603
Checks: C-25569r516087_chk
Execute a data set list of access for SYS1.LPALIB. If all of the following are untrue, this is a finding. If any of the following is true, this is a finding. The ESM data set rules for SYS1.LPALIB do not restrict WRITE or greater access to only z/OS systems programming personnel. The ESM data set rules for SYS1.LPALIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25557r516088_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect SYS1.LPALIB. Configure WRITE or greater access to SYS1.LPALIB to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000240
- Vuln IDs
-
- V-223897
- V-98501
- Rule IDs
-
- SV-223897r877738_rule
- SV-107605
Checks: C-25570r516090_chk
From Any ISPF input line, enter TSO ISRDDN APF. If all of the following are untrue, this is not a finding. If any of the following are true, this is a finding. The ACP data set rules for APF libraries do not restrict WRITE or greater access to only z/OS systems programming personnel. The ACP data set rules for APF libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25558r516091_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect APF Authorized Libraries. Configure WRITE or greater access to all APF-authorized libraries to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000250
- Vuln IDs
-
- V-223898
- V-98503
- Rule IDs
-
- SV-223898r877739_rule
- SV-107607
Checks: C-25571r516093_chk
Refer to AXRxx member of PARMLIB for each REXXLIB ADD statement. If the ESM data set rules for libraries in the REXXLIB concatenation restrict WRITE or greater access to only z/OS systems programming personnel, this is not a finding. If the ESM data set rules for libraries in the REXXLIB concatenation restrict READ access to the following, this is not a finding. Appropriate Started Tasks Auditors The user-id defined in PARMLIB member AXR00 AXRUSER(user-id) If the ESM data set rules for libraries in the REXXLIB concatenation specify that all (i.e., failures and successes) WRITE or greater access will be logged, this is not a finding.
Fix: F-25559r516094_fix
Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect APF Authorized Libraries. Configure ESM data set rules to limit WRITE or greater access to libraries included in the system REXXLIB concatenation to system programmers only. Configure ESM data set rules allow READ access to only appropriate Started Tasks and Auditors. Configure ESM data set rules to log WRITE or greater access (i.e., successes and failures).
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000260
- Vuln IDs
-
- V-223899
- V-98505
- Rule IDs
-
- SV-223899r877740_rule
- SV-107609
Checks: C-25572r516096_chk
From any ISPF input line, enter TSO ISRDDN LPA. If all of the following are untrue, this is not a finding. If any of the following is true, this is a finding. The ACP data set rules for LPA libraries do not restrict WRITE or greater access to only z/OS systems programming personnel. The ACP data set rules for LPA libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25560r516097_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect LPA Libraries. Configure the WRITE or greater access to all LPA libraries to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000270
- Vuln IDs
-
- V-223900
- V-98507
- Rule IDs
-
- SV-223900r877741_rule
- SV-107611
Checks: C-25573r516099_chk
Execute a dataset list of access for SYS1.NUCLEUS. If all of the following are untrue, there is not a finding. If any of the following is true, this is a finding. The ACP data set rules for SYS1.NUCLEUS do not restrict WRITE or greater access to only z/OS systems programming personnel. The ACP data set rules for SYS1.NUCLEUS do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25561r516100_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect SYS1.NUCLEUS. Configure the WRITE or greater access to SYS1.NUCLEUS to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- Low
- CCI
- CCI-000213
- Version
- TSS0-ES-000280
- Vuln IDs
-
- V-223901
- V-98509
- Rule IDs
-
- SV-223901r877742_rule
- SV-107613
Checks: C-25574r516102_chk
Review program entries in the IBM Program Properties Table (PPT). You may use a third-party product to examine these entries however, to determine program entries issue the following command from an ISPF command line: TSO ISRDDN LOAD IEFSDPPT Press Enter. For each module identified in the "eyecatcher" if all of the following are untrue, this is not a finding. If any of the following is true, this is a finding. The ACP data set rules for libraries that contain PPT modules do not restrict WRITE or greater access to only z/OS systems programming personnel. The ACP data set rules for libraries that contain PPT modules do not specify that all WRITE or greater access will be logged.
Fix: F-25562r516103_fix
Configure the WRITE or greater access to libraries containing PPT modules to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000290
- Vuln IDs
-
- V-223902
- V-98511
- Rule IDs
-
- SV-223902r877743_rule
- SV-107615
Checks: C-25575r516105_chk
From any ISPF input line, enter TSO ISRDDN LINKLIST. If all of the following are untrue, this is not a finding. If any of the following is true, this is a finding. The ACP data set rules for LINKLIST libraries do not restrict WRITE or greater access to only z/OS systems programming personnel. The ACP data set rules for LINKLIST libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.
Fix: F-25563r516106_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect the LINKLIST libraries. Configure the WRITE or greater access to LINKLIST libraries to be limited to system programmers only and all WRITE or greater access is logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000300
- Vuln IDs
-
- V-223903
- V-98513
- Rule IDs
-
- SV-223903r877744_rule
- SV-107617
Checks: C-25576r516108_chk
Determine all associated ESM security data sets and/or databases. If the following accesses to the ESM security data sets and/or databases are properly restricted as detailed below, this is not a finding. The ESM data set rules for ESM security data sets and/or databases restrict READ access to auditors and DASD batch. The ESM data set rules for ESM security data sets and/or databases restrict READ and/or greater access to z/OS systems programming personnel, security personnel, and/or batch jobs that perform ESM maintenance. All (i.e., failures and successes) data set access authorities (i.e., READ, UPDATE, ALTER, and CONTROL) for ESM security data sets and/or databases are logged.
Fix: F-25564r516109_fix
Review access authorization to critical security database files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect the ESM files. Configure READ and/or greater access to all ESM files and/or databases are limited to system programmers and/or security personnel, and/or batch jobs that perform ESM maintenance. READ access can be given to auditors and DASD batch. All accesses to ESM files and/or databases are logged.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000310
- Vuln IDs
-
- V-223904
- V-98515
- Rule IDs
-
- SV-223904r877745_rule
- SV-107619
Checks: C-25577r868930_chk
Refer to SYSCATxx member of SYS1.NUCLEUS. Multiple SYSCATxx members may be defined; if so, refer to Master Catalog message for IPL. If the member is not found, refer to the appropriate LOADxx member of SYS1.PARMLIB. If data set rules for the Master Catalog do not restrict greater than "READ" access to only z/OS systems programming personnel, this is a finding. If products or procedures requiring system programmer access for system-level maintenance meet the following specific case, this is not a finding: - The batch job or procedure must be documented in the SITE Security Plan. - Reside in a data set that is restricted to systems programmers' access only. If data set rules for the Master Catalog do not specify that all (i.e., failures and successes) greater than "READ" access will be logged, this is a finding.
Fix: F-25565r868931_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect the MASTER CATALOG. Configure the ESM rules for system catalog to only allow access above "READ" to systems programmers and those authorized by the ISSM/ISSO. Configure ESM rules for the master catalog to allow access above "READ" to systems programmers ONLY. Configure ESM rules for the master catalog to allow any products or procedures system programmer access for system-level maintenance that meet the following specific case: - The batch job or procedure must be documented in the SITE Security Plan. - Reside in a data set that is restricted to systems programmers' access only. All greater than read access must be logged.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000320
- Vuln IDs
-
- V-223905
- V-98517
- Rule IDs
-
- SV-223905r877746_rule
- SV-107621
Checks: C-25578r868933_chk
From the ISPF Command Shell enter: LISTCat USERCATALOG ALL NOPREFIX Review the ESM data set rules for each usercatalog defined. If the data set rules for User Catalogs do not restrict ALTER access to only z/OS systems programming personnel, this is a finding. If products or procedures requiring system programmer access for system-level maintenance meet the following specific case, this is not a finding: - The batch job or procedure must be documented in the SITE Security Plan. - Reside in a data set that is restricted to systems programmers' access only. If the data set rules for User Catalogs do not specify that all (i.e., failures and successes) ALTER access will be logged, this a finding. Note: If the USER CATALOGS contain SMS managed data sets, READ access is sufficient to allow user operations. If the USER CATALOGS do not contain SMS managed data sets, UPDATE access is required for user operation.
Fix: F-25566r868934_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect USER CATALOGS. Configure ESM rules for allocate access to USER CATALOGS, limited to system programmers only, and all allocate access is logged. Configure ESM rules for the USER CATALOGS to allow any products or procedures system programmer access for system-level maintenance that meet the following specific case: - The batch job or procedure must be documented in the SITE Security Plan. - Reside in a data set that is restricted to systems programmers' access only. Note: If the USER CATALOGS contain SMS managed data sets, READ access is sufficient to allow user operations. If the USER CATALOGS do not contain SMS managed data sets, UPDATE access is required for user operation.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000330
- Vuln IDs
-
- V-223906
- V-98519
- Rule IDs
-
- SV-223906r877747_rule
- SV-107623
Checks: C-25579r516117_chk
Have the systems programmer for z/OS supply the following information: The data set name and associated SREL for each SMP/E CSI utilized to maintain this system. The data set name of all SMP/E TLIBs and DLIBs used for installation and production support. A comprehensive list of the SMP/E DDDEFs for all CSIs may be used if valid. The ACP data set rules for system-level product installation libraries (e.g., SMP/E CSIs) allow inappropriate access. The ACP data set rules for system-level product installation libraries (e.g., SMP/E CSIs) do not restrict WRITE or greater access to only z/OS systems programming personnel. If all of the above are untrue, this is not a finding. If any of the above is true, or if these data sets cannot be identified due to a lack of requested information, this is a finding.
Fix: F-25567r516118_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect System-level product installation libraries. Configure allocate access to all system-level product execution libraries to be limited to system programmers only.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000340
- Vuln IDs
-
- V-223907
- V-98521
- Rule IDs
-
- SV-223907r877748_rule
- SV-107625
Checks: C-25580r516120_chk
The ESM data set rules for the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) do not restrict WRITE or greater access to only z/OS systems programming personnel. The ESM data set rules for the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) allow inappropriate access not documented and approved by ISSO. If both of the above are untrue, this is not a finding. If either of the above is true, this is a finding.
Fix: F-25568r516121_fix
Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect JES2 System data sets (spool, checkpoint, and parmlib data sets). Configure WRITE or greater access to JES2 System data sets (spool, checkpoint, and parmlib data sets) to be limited to system programmers only. Access other than this should be documented and approved by the ISSO. (Example: All SYS1.HASP* data sets.)
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000350
- Vuln IDs
-
- V-223908
- V-98523
- Rule IDs
-
- SV-223908r877749_rule
- SV-107627
Checks: C-25581r516123_chk
The ESM data set rules for SYS1.UADS restricts WRITE or Greater access to only z/OS systems programming personnel. The ESM data set rules for SYS1.UADS restricts READ and/or UPDATE access to z/OS systems programming personnel and/or security personnel. The ESM data set rules for SYS1.UADS specifies that all (i.e., failures and successes) data set access authorities (i.e., READ, UPDATE, ALTER, and CONTROL) will be logged. The ESM data set rules for SYS1.UADS restricts READ access to auditors as documented in Security Plan. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.
Fix: F-25569r516124_fix
Evaluate the impact of correcting any deficiency. Develop a plan of action and implement the changes as required to protect SYS1.UADS. SYS1.UADS WRITE or Greater authority is limited to the systems programming staff. Read and update access should be limited to the security staff. READ access is limited to Auditors when included in the site security plan Configure allocate access to SYS1.UADS to be limited to system programmers only, read and update access to SYS1.UADS to be limited to system programmer personnel and/or security personnel and all data set access is logged.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000360
- Vuln IDs
-
- V-223909
- V-98525
- Rule IDs
-
- SV-223909r877750_rule
- SV-107629
Checks: C-25582r868936_chk
Obtain the procedures and collection specifics for SMF data sets and backup. If the ESM data set rules for the SMF dump/backup files do not restrict WRITE or greater access to authorized DISA and site personnel (e.g., systems programmers and batch jobs that perform SMF processing), this is a finding. If the ESM data set rules for the SMF dump/backup files do restrict update access as documented in the site security plan, this is a finding. If the ESM data set rules for the SMF dump/backup files do not restrict READ access to auditors and others approved by the ISSM, this is a finding. If the ESM data set rules for SMF dump/backup files do not specify that all (i.e., failures and successes) WRITE or greater access will be logged, this is a finding.
Fix: F-25570r868937_fix
Review access authorization to critical system files. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required to protect data sets used to backup and/or dump SMF Collection Files. Configure data set rules for the SMF dump/backup files to restrict WRITE or greater access to authorized DISA and site personnel (e.g., systems programmers and batch jobs that perform SMF processing). Configure data set rules for the SMF dump/backup files to restrict UPDATE access to others approved the ISSM. Configure data set rules for the SMF dump/backup files to restrict READ access to authorized auditors and others approved by the ISSM. Ensure that all update and alter access authority to SMF history files will be logged using the ESM's facilities.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000370
- Vuln IDs
-
- V-223910
- V-98527
- Rule IDs
-
- SV-223910r877751_rule
- SV-107631
Checks: C-25583r516129_chk
Refer to data sets SYS1.DUMPxx, additionally, Dump data sets can be identified by reviewing the logical parmlib concatenation data sets for the current COMMNDxx member. Find the COM= which specifies the DUMPDS NAME (DD NAME=name-pattern) entry. The name-pattern is used to identify additional Dump data sets. If the ESM data set rules for System Dump data sets do not restrict READ, UPDATE, and/or ALTER access to only systems programming personnel, this is a finding. If the ESM data set rules for all System Dump data sets do not restrict READ access to personnel having justification to review these dump data sets, this is a finding.
Fix: F-25571r516130_fix
Configure data set rules for access to SYSTEM DUMP data set(s) to be limited to system programmers only, unless a letter justifying access is filed with the ISSO in the site security plan. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to restrict access to these data sets.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000380
- Vuln IDs
-
- V-223911
- V-98529
- Rule IDs
-
- SV-223911r877752_rule
- SV-107633
Checks: C-25584r516132_chk
Collect from the storage management group the identification of the DASD backup files and all associated storage management ACIDs. If ESM data set rules for system DASD backup files do not restrict WRITE or greater access to z/OS systems programming and/or batch jobs that perform DASD backups this is a finding. If READ Access to system backup data sets is not limited to auditors and others approved by the ISSM this is a finding.
Fix: F-25572r516133_fix
Obtain the high level indexes to backup data sets names define their access to be restricted by the System's ESM to System Programmers and batch jobs that perform the backups. Define READ Access to system backup data sets to be limited to auditors and others approved by the ISSM.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000390
- Vuln IDs
-
- V-223912
- V-98531
- Rule IDs
-
- SV-223912r877753_rule
- SV-107635
Checks: C-25585r516135_chk
Execute a dataset list of access for SYS(x).TRACE files. If the ESM data set rule for SYS1.TRACE restricts access to systems programming personnel and started tasks that perform GTF processing, this is not a finding. If the ESM data set rule for SYS1.TRACE restricts access to others as documented and approved by ISSM, this is not a finding.
Fix: F-25573r516136_fix
Configure the ESM access to SYS1.TRACE to be limited to system programmers or started tasks that perform GTF processing. Other user access can be granted as documented and approved by the ISSM.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000400
- Vuln IDs
-
- V-223913
- V-98533
- Rule IDs
-
- SV-223913r877754_rule
- SV-107637
Checks: C-25586r516138_chk
Execute a dataset list of access for System page data sets (i.e., PLPA, COMMON, and LOCALx). If ESM data set rules for system page data sets (PLPA, COMMON, and LOCAL) restrict access to only systems programming personnel, this is not a finding. If ESM data set rules for system page data sets (PLPA, COMMON, and LOCAL) restrict auditors to READ only, this is not a finding.
Fix: F-25574r516139_fix
Configure the ESM data set rules for system page data sets (PLPA, COMMON, and LOCAL) to restrict access to only systems programming personnel. Auditors may be allowed READ Access as approved by the ISSM.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000410
- Vuln IDs
-
- V-223914
- V-98535
- Rule IDs
-
- SV-223914r877755_rule
- SV-107639
Checks: C-25587r868939_chk
Examine the system for active exit modules. You may need the system administrator's help for this. There are third-party software products that can determine standard and dynamic exits loaded in the system. If all the exits are found within APF, LPA, and LINKLIST, this is not applicable. If ESM data set rules for libraries that contain system exit modules restrict WRITE or greater access to only z/OS systems programming personnel, this is not a finding. If the ESM data set rules for libraries that contain exit modules specify that all WRITE or greater access will be logged, this is not a finding.
Fix: F-25575r868940_fix
Using the ESM, protect the data sets associated with all product exits installed in the z/OS environment. This reduces the potential of a hacker adding a routine to a library and possibly creating an exposure. Confirm that all exits are tracked using a CMP. Develop usermods to include the source/object code used to support the exits. Have systems programming personnel review all z/OS and other product exits to confirm that the exits are required and are correctly installed. Configure ESM data set rules for all WRITE or greater access to libraries containing z/OS and other system-level exits will be logged using the ACP's facilities. Only systems programming personnel will be authorized to update the libraries containing z/OS and other system level exits.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000420
- Vuln IDs
-
- V-223915
- V-98537
- Rule IDs
-
- SV-223915r877756_rule
- SV-107641
Checks: C-25588r868942_chk
Refer to the following for the PROCLIB data sets that contain the STCs and TSO logons from the following sources: -MSTJCLxx member used during an IPL. The PROCLIB data sets are obtained from the IEFPDSI and IEFJOBS DD statements. -PROCxx DD statements and JES2 Dynamic PROCLIBs. Where 'xx' is the PROCLIB entries for the STC and TSU JOBCLASS configuration definitions. Verify that the accesses to the above PROCLIB data sets are properly restricted. If the following guidance is true, this is not a finding. If the ESM data set access authorizations restrict READ access to all authorized users, this is not a finding. If the ESM data set access authorizations restrict WRITE and/or greater access to systems programming personnel, this is not a finding.
Fix: F-25576r868943_fix
Configure ESM data set rules to restrict all WRITE and/or greater access to all PROCLIBs referenced in the Master JCL and JES2 or JES3 procedure for started tasks (STCs) and TSO logons to systems programming personnel only. Suggestion on how to update system to be compliant with this vulnerability: NOTE: All examples are only examples and may not reflect your operating environment. Obtain only the PROCLIB data sets that contain STC and TSO procedures. The data sets to be reviewed are obtained using the following steps: -All data sets contained in the MSTJCLxx member in the DD statement concatenation for IEFPDSI and IEFJOBS. -The data set in the PROCxx DD statement concatenation that are within the JES2 procedure or identified in the JES2 dynamic PROCLIB definitions. The specific PROCxx DD statement that is used is obtained from the PROCLIB entry for the JOBCLASSes of STC and TSU. The following are the data sets the process will obtain for analysis: MSTJCL00 //MSTJCL00 JOB MSGLEVEL=(1,1),TIME=1440 //EXEC PGM=IEEMB860,DPRTY=(15,15) //STCINRDR DD SYSOUT=(A,INTRDR) //TSOINRDR DD SYSOUT=(A,INTRDR) //IEFPDSI DD DSN=SYS3.PROCLIB,DISP=SHR <<=== //DD DSN=SYS2.PROCLIB,DISP=SHR <<=== //DD DSN=SYS1.PROCLIB,DISP=SHR <<=== //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR JES2 //JES2 PROC //IEFPROC EXEC PGM=HASJES20,PARM=NOREQ, //DPRTY=(15,15),TIME=1440,PERFORM=9 //ALTPARM DD DISP=SHR, //DSN=SYS1.PARMLIB(JES2BKUP) //HASPPARM DD DISP=SHR, //DSN=SYS1.PARMLIB(JES2PARM) //PROC00 DD DSN=SYS3.PROCLIB,DISP=SHR <<=== //DD DSN=SYS2.PROCLIB,DISP=SHR <<=== //DD DSN=SYS1.PROCLIB,DISP=SHR <<=== //PROC01 DD DSN=SYS4.USERPROC,DISP=SHR //DD DSN=SYS3.PROCLIB,DISP=SHR //DD DSN=SYS2.PROCLIB,DISP=SHR //DD DSN=SYS1.PROCLIB,DISP=SHR //IEFRDER DD SYSOUT=* //HASPLIST DD DDNAME=IEFRDER JES2 initialization parameter JOBCLASS PROCLIB entries JOBCLASS(*) ACCT=NO, /* ACCT # NOT REQUIRED (DEF.)*/ ... PROCLIB=01, /* DEFAULT TO //PROC01 DD (DEF.)*/ ... JOBCLASS(STC) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ ... PROCLIB=00, /* USE //PROC00 DD (DEF.)*/ ... JOBCLASS(TSU) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ ... PROCLIB=00, /* USE //PROC00 DD (DEF.)*/ ... PROCLIB data set that will be used in the access authorization process: SYS3.PROCLIB SYS2.PROCLIB SYS1.PROCLIB The following PROCLIB data set will NOT be used or evaluated: SYS4.USERPROC Recommendation for sites: The following are recommendations for the sites to ensure only PROCLIB data sets that contain the STC and TSO procedures are protected. -Remove all application PROCLIB data sets from MSTJCLxx and JES2 procedures. The customer will have all JCL changed to use the JCLLIB JCL statement to refer to the application PROCLIB data sets. Example: //USERPROC JCLLIB ORDER=(SYS4.USERPROC) -Remove all access to the application PROCLIB data sets and only authorize system programming personnel WRITE and/or greater access to these data sets. -Document the application PROCLIB data set access for the customers that require WRITE and/or greater access. Use this documentation as justification for the inappropriate access created by the scripts. -Change MSTJCLxx and JES2 procedure to identify STC and TSO PROCLIB data sets separate from application PROCLIB data sets. The following is a list of actions that can be performed to accomplish this recommendation: a. Ensure that MSTJCLxx contains only PROCLIB data sets that contain STC and TSO procedures. b. If an application PROCLIB data set is required for JES2, ensure that the JES2 procedure specifies more than one PROCxx DD statement concatenation or identified in the JES2 dynamic PROCLIB definitions. Identify one PROCxx DD statement data set concatenation that contains the STC and TSO PROCLIB data sets. Identify one or more additional PROCxx DD statements that can contain any other PROCLIB data sets. The concatenation of the additional PROCxx DD statements can contain the same data sets that are identified in the PROCxx DD statement for STC and TSO. The following is an example of the JES2 procedure: //JES2 PROC //IEFPROC EXEC PGM=HASJES20,PARM=NOREQ, //DPRTY=(15,15),TIME=1440,PERFORM=9 //ALTPARM DD DISP=SHR, //DSN=SYS1.PARMLIB(JES2BKUP) //HASPPARM DD DISP=SHR, //DSN=SYS1.PARMLIB(JES2PARM) //PROC00 DD DSN=SYS3.PROCLIB,DISP=SHR //DD DSN=SYS2.PROCLIB,DISP=SHR //DD DSN=SYS1.PROCLIB,DISP=SHR //PROC01 DD DSN=SYS4.USERPROC,DISP=SHR //DD DSN=SYS3.PROCLIB,DISP=SHR //DD DSN=SYS2.PROCLIB,DISP=SHR //DD DSN=SYS1.PROCLIB,DISP=SHR //IEFRDER DD SYSOUT=* //HASPLIST DD DDNAME=IEFRDER c. Ensure that the JES2 configuration file is changed to specify that the PROCLIB entry for the STC and TSU JOBCLASSes point to the proper PROCxx entry within the JES2 procedure or JES2 dynamic PROCLIB definitions that contain the STC and/or TSO procedures. All other JOBCLASSes can specify a PROCLIB entry that uses the same PROCxx or any other PROCxx DD statement identified in the JES2 procedure or identified in the JES2 dynamic PROCLIB definitions. The following is an example of the JES2 initialization parameters: JOBCLASS(*) ACCT=NO, /* ACCT # NOT REQUIRED (DEF.)*/ ... PROCLIB=01, /* DEFAULT TO //PROC01 DD (DEF.)*/ ... JOBCLASS(STC) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ ... PROCLIB=00, /* USE //PROC00 DD (DEF.)*/ ... JOBCLASS(TSU) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ ... PROCLIB=00, /* USE //PROC00 DD (DEF.)*/ ... d. Ensure that only system programming personnel are authorized WRITE and/or greater access to PROCLIB data sets that contain STC and TSO procedures.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000430
- Vuln IDs
-
- V-223916
- V-98539
- Rule IDs
-
- SV-223916r877757_rule
- SV-107643
Checks: C-25589r516147_chk
If the IEAABD. resource and/or generic equivalent is defined with no access and all access logged, this is not a finding. If the IEAABD.DMPAUTH. resource and/or generic equivalent is defined with READ access limited to authorized users, this is not a finding. If the IEAABD.DMPAUTH. resource and/or generic equivalent UPDATE or greater access is restricted to only systems personnel and all access is logged, this is not a finding. If the IEAABD.DMPAKEY resource and/or generic equivalent is defined and all access is restricted to systems personnel and that all access is logged, this is not a finding.
Fix: F-25577r868945_fix
Memory and privileged program dump resources are provided via resources in the FACILITY resource class. Ensure that the following are properly specified in the ESM. (Note: The resources and/or resource prefixes identified below are examples of a possible installation. The actual 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.) Below is listed the access requirements for memory and privileged program dump resources. Ensure the guidelines for the resource type, resources, and/or generic equivalent are followed. When protecting the facilities for dumps lists via the FACILITY resource class, ensure that the following items are in effect: IEAABD. IEAABD.DMPAUTH. IEAABD.DMPAKEY. The RACF resource rules for the resources specify UACC(NONE) and NOWARNING. Ensure that no access is given to IEAABD. resource. Example RDEF FACILITY IEAABD.** UACC(NONE) OWNER(owner group) AUDIT(ALL(READ)) IEAABD.DMPAUTH. READ access is limited to authorized users that have a valid job duties requirement for access. UPDATE access will be restricted to system programming personnel and access will be logged. Example: RDEF FACILITY IEAABD.DMPAUTH.** UACC(NONE) OWNER(owner group) AUDIT(ALL(UPDATE)) PERMIT IEAABD.DMPAUTH.** CLASS(FACILITY) ID(authusers) ACCESS(READ) PERMIT IEAABD.DMPAUTH.** CLASS(FACILITY) ID(syspsmpl) ACCESS(UPDATE) IEAABD.DMPAKEY. access will be restricted to system programming personnel and access will be logged. Example: RDEF FACILITY IEAABD.DMPAKEY.** UACC(NONE) OWNER(owner group) AUDIT(ALL(READ)) PERMIT IEAABD.DMPAKEY.** CLASS(FACILITY) ID(syspsmpl) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000440
- Vuln IDs
-
- V-223917
- V-98541
- Rule IDs
-
- SV-223917r877758_rule
- SV-107645
Checks: C-25590r516150_chk
Refer to the CSV-prefixed resources defined below: CSVAPF. CSVAPF.MVS.SETPROG.FORMAT.DYNAMIC CSVAPF.MVS.SETPROG.FORMAT.STATIC CSVDYLPA. CSVDYNEX. CSVDYNEX.LIST CSVDYNL. CSVDYNL.UPDATE.LNKLST CSVLLA. If the TSS IBMFAC resource class in the RDT has the DEFPROT attribute specified and/or the CSV resources and/or generic equivalent are owned this is not a finding. If the TSS resources and/or generic equivalent identified above are defined with ACTION(AUDIT) and UPDATE access restricted to system programming personnel this is not a finding. If the TSS CSVDYNEX.LIST resource and/or generic equivalent is defined with ACTION(AUDIT) and UPDATE access restricted to system programming personnel this is a finding. If the TSS CSVDYNEX.LIST resource and/or generic equivalent are defined with READ access restricted to auditors this is not a finding. If the products CICS and/or CONTROL-O are on the system, and the TSS access to the CSVLLA resource access to the CSVLLA resource and/or generic equivalent are defined with ACTION(AUDIT) and UPDATE access restricted to the CICS and CONTROL-O STC ACIDs this is not a finding. If any software product requires access to dynamic LPA updates on the system, the TSS access to the CSVDYLPA resource and/or generic equivalent will be defined with ACTION(AUDIT) and UPDATE only after the product has been validated with the appropriate STIG or SRG for compliance AND receives documented and filed authorization that details the need and any accepted risks from the site ISSM or equivalent security authority. Note: In the above, UPDATE access can be substituted with ALL or CONTROL. Review the permissions in the TSS documentation when specifying UPDATE.
Fix: F-25578r516151_fix
Configure TSS to ensure that the Dynamic List resources are defined to the IBMFAC resource class and protected. Only system programmers and a limited number of authorized users and Approved authorized Started Tasks are able to issue these commands. All access is logged. The required CSV-prefixed Facility Class resources are listed below. These resources or generic equivalents should be defined and permitted as required with only z/OS systems programmers and logging enabled. Minimum required list of CSV-prefixed resources: CSVAPF. CSVAPF.MVS.SETPROG.FORMAT.DYNAMIC CSVAPF.MVS.SETPROG.FORMAT.STATIC CSVDYLPA. CSVDYLPA.ADD. CSVDYLPA.ADD. CSVDYNEX. CSVDYNEX.LIST CSVDYNL. CSVDYNL.UPDATE.LNKLST CSVLLA. If DEFPROT is specified in the IBMFAC RDT the following command examples are not required. To prevent access to these resources, the CSV resources are protected using the following commands. The following commands are provided for example only: TSS ADDTO(deptacid) IBMFAC(CSV) or TSS ADDTO(deptacid) IBMFAC(CSVAPF) TSS ADDTO(deptacid) IBMFAC(CSVDYLPA) TSS ADDTO(deptacid) IBMFAC(CSVDYNEX) TSS ADDTO(deptacid) IBMFAC(CSVDYNL) TSS ADDTO(deptacid) IBMFAC(CSVDYLPA) TSS ADDTO(deptacid) IBMFAC(CSVLLA) Limit authority to those resources to z/OS systems programmers. Restrict to the absolute minimum number of personnel with ACTION(AUDIT) and UPDATE access. Sample commands are shown here to accomplish this: TSS PERMIT(syspsmpl) IBMFAC(CSVAPF.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.FORMAT) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.SETPROG.FORMAT.DYNAMIC) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.SETPROG.FORMAT.STATIC) ACCESS(UPDATE) ACTION(AUDIT) The CSVDYLPA.ADD resource will be permitted to BMC Mainview, CA 1, and CA Common Services STC ACIDs with ACTION(AUDIT) and UPDATE access. The CSVDYLPA resource will be permitted to BMC Mainview, CA 1, and CA Common Services STC ACIDs with ACTION(AUDIT) and UPDATE access. Sample commands are shown here to accomplish one set of resources: TSS PERMIT(syspsmpl) IBMFAC(CSVDYLPA.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(BMC Mainview STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CA 1 STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CCS STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CA 1 STC ACID) IBMFAC(CSVDYLPA.DELETE.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CCS STC ACID) IBMFAC(CSVDYLPA.DELETE.) ACCESS(UPDATE) ACTION(AUDIT) The CSVDYNEX.LIST resource and/or generic equivalent will be defined with ACTION(AUDIT) and UPDATE access restricted to system programming personnel. The CSVDYNEX.LIST resource and/or generic equivalent will be defined with READ access restricted to auditors. Sample commands are shown here to accomplish this: TSS PERMIT(syspsmpl) IBMFAC(CSVDYNEX.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(CSVDYNEX.LIST) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(smplsmpl) IBMFAC(CSVDYNEX.LIST) ACCESS(READ) The CSVLLA resource will be permitted to CICS and CONTROL-O STC ACIDs with ACTION(AUDIT) and UPDATE access. Sample commands are shown here to accomplish one set of resources: TSS PERMIT(syspsmpl) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CICS STC ACIDs) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(CONTROL-O STC ACID) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000450
- Vuln IDs
-
- V-223918
- V-98543
- Rule IDs
-
- SV-223918r877759_rule
- SV-107647
Checks: C-25591r516153_chk
From a command screen enter: TSS WHOHAS OPERCMDS(MVS) If any of below is untrue for any z/OS system command resource, this is a finding. Access to MVS resource of the OPERCMDS class is restricted to a limited number of authorized users, and all access logged. Access to "MVS.**" is not allowed. Access to z/OS system commands as defined in the table entitled MVS commands, RACF access authorities, and resource names, in the IBM z/OS MVS System Commands manual, is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users). NOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands. NOTE: The (MVS.SEND) Command will not be a finding if used by all. Access to specific z/OS system commands is logged as indicated in the table entitled MVS commands, RACF access authorities, and resource names, in the IBM z/OS MVS System Commands manual.
Fix: F-25579r516154_fix
Ensure access to the MVS resource of the OPERCMDS class is restricted to a limited number of authorized users, and all access is logged. Ensure access to z/OS system commands as defined in the table entitled MVS commands, RACF access authorities, and resource names, in the IBM z/OS MVS System Commands manual is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users). Ensure no access is granted at level MVS.**. NOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands. NOTE: The (MVS.SEND) Command will not be a finding if used by all. Example: TSS ADDTO(deptacid) OPERCMDS(MVS.) TSS PERMIT(usracid) OPERCMDS(MVS.ACTIVATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CANCEL.JOB.) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CONTROL.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.DISPLAY.) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.MONITOR) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.STOPMN) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000460
- Vuln IDs
-
- V-223919
- V-98545
- Rule IDs
-
- SV-223919r877760_rule
- SV-107649
Checks: C-25592r811046_chk
From the ISPF Command Shell enter: TSS WHOOWNS SYSCONS(*) For each Console defined enter: TSS WHOHAS SYSCONS(<console>) If the ACID associated with each console has READ access to the corresponding resource defined in the SYSCONS resource class, this is not a finding. If access authorization for SYSCONS resources restricts access to operations, the Master SCA, system programming personnel, or authorized personnel, this is not a finding. If the console defined is not defined to the TSS SYSCONS resource class enter: TSS LIST (RDT) RESCLASS(SYSCONS) If the SYSCONS resource class does not have the DEPROT attribute, this is a finding. For each Console defined enter: TSS WHOHAS(<CONSOLE>) If the console defined is not defined to the TSS SYSCONS resource class enter: TSS LIST (RDT) RESCLASS(SYSCONS) If the SYSCONS resource class does not have the DEPROT attribute, this is a finding.
Fix: F-25580r811047_fix
Ensure that all MCS consoles are defined to the SYSCONS resource class and READ access is limited to operators, and system programmers, or authorized personnel. Review the MCS console resources defined to z/OS and the ACP and ensure they conform to those outlined below. Each console defined in the CONSOLxx parmlib members is defined to TSS SYSCONS resource class and/or the SYSCONS resource class has the DEFPROT attribute. Example: TSS REPLACE(RDT) RESCLASS(SYSCONS) ATTR(DEFPROT) The ACID associated with each console has access to the corresponding resource defined in the SYSCONS resource class. Example: TSS PERMIT(MMGMST) SYSCONS(MMGMST) ACCESS(READ) Access authorization for SYSCONS resources restricts access to operations, the Master SCA, and system programming personnel. TSS PERMIT(opersmpl) SYSCONS(MMGMST) ACCESS(READ) TSS PERMIT(Master SCA) SYSCONS(MMGMST) ACCESS(READ) TSS PERMIT(syspsmpl) SYSCONS(MMGMST) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000470
- Vuln IDs
-
- V-223920
- V-98547
- Rule IDs
-
- SV-223920r877761_rule
- SV-107651
Checks: C-25593r516159_chk
TSS WHOOWNS TSOAUTH(*) If the Console is not defined to TSOAuth RESOURCE CLASS this is Not Applicable. Refer to the CONSOLxx member of SYS1.PARMLIB. For each Console defined if the following is true, this is not a finding. -User ACIDs are restricted to the INFO level in the MCSAUTH attribute. -User ACIDs are restricted to READ access to the MVS.MCSOPER.acid resource defined in the OPERCMDS resource class. -User ACIDs and/or profile ACIDs are restricted to the CONSOLE resource defined in the TSOAUTH resource class. If any of the above are untrue, this is a finding.
Fix: F-25581r516160_fix
Evaluate the impact of correcting any deficiencies. Develop a plan of action and implement the required changes. At the discretion of the ISSO, users may be allowed to issue z/OS system commands from a TSO session. With this in mind, ensure the following items are in effect for users granted the TSO CONSOLE privilege: -User ACIDs are restricted to the INFO level in the MCSAUTH attribute. -User ACIDs are restricted to READ access to the MVS.MCSOPER.acid resource defined in the OPERCMDS resource class. -User ACIDs and/or profile ACIDs are restricted to the CONSOLE resource defined in the TSOAUTH resource class. For Example: TSS ADDTO (userid) MCSAUTH(INFO) TSS PERMIT(userid) OPERCMDS(MVS.MCSOPER.userid) ACCESS(READ) ACTION(AUDIT) TSS PERMIT(oprprofileacid) TSOAUTH(CONSOLE) ACCESS(READ) ACTION(AUDIT)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000480
- Vuln IDs
-
- V-223921
- V-98549
- Rule IDs
-
- SV-223921r877762_rule
- SV-107653
Checks: C-25594r516162_chk
From the ISPF Command Shell enter: TSS WHOOWNS OPERCMDS(MVS) If the (MVS) resource is owned, this is not a finding. If the (MVS) resource is not owned, this is a finding. TSS LIST RDT RESCLASS(OPERCMDS) If the (MVS) resource is not OWNED and the OPERCMDS class does not have DEFPROT as an attribute, this is a finding.
Fix: F-25582r516163_fix
z/OS system command controls are provided via resources in the OPERCMDS resource class. Configure (MVS) of the OPERCMDS resource class to be properly owned or at a minimum the OPERCMDS resource in the RDT specifies the DEFPROT attribute. Name the actual owning ACID specified for deptacid in accordance with installation recommendations. When protecting the facilities for z/OS system commands via the OPERCMDS class, use the following controls: (1) Prevent access to the z/OS resources by default, and log all access. Create generic and specific permissions with logging as required using the required controls for z/OS System Commands listed in ACP00282. For example: TSS ADDTO(deptacid) OPERCMDS(MVS.) TSS PERMIT(usracid) OPERCMDS(MVS.ACTIVATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CANCEL.JOB.) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.CONTROL.) ACCESS(UPDATE) ACTION(AUDIT) TSS PERMIT(usracid) OPERCMDS(MVS.DISPLAY.) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.MONITOR) ACCESS(READ) TSS PERMIT(usracid) OPERCMDS(MVS.STOPMN) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000490
- Vuln IDs
-
- V-223922
- V-98551
- Rule IDs
-
- SV-223922r877763_rule
- SV-107655
Checks: C-25595r516165_chk
TSS MODIFY STATUS If the AUTH Control Option values are not set to AUTH(OVERRIDE, ALLOVER) or AUTH(MERGE, ALLOVER), this is a finding.
Fix: F-25583r516166_fix
Configure the AUTH control option is set to (OVERRIDE, ALLOVER) or (MERGE, ALLOVER). With (OVERRIDE, ALLOVER), TSS separately searches first the user, then profiles, and then the ALL record for its access authorization. With (MERGE, ALLOVER), TSS merges and searches the user and all profiles, and then the ALL record for its access authorization. Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting to AUTH(OVERRIDE, ALLOVER) or AUTH(MERGE, ALLOVER) and proceed with the change.
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000500
- Vuln IDs
-
- V-223923
- V-98553
- Rule IDs
-
- SV-223923r877764_rule
- SV-107657
Checks: C-25596r516168_chk
From the ISPF Command Shell enter: TSS WHOHAS MODE(*) If any ACIDs is permitted a mode of "DORM", "WARN", or "IMPL", this is a finding.
Fix: F-25584r516169_fix
Evaluate the impact associated with implementation of the removal of this access. Develop a plan of action to ensure that the ACIDs use the default MODE settings and proceed with the change.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000505
- Vuln IDs
-
- V-223924
- V-98555
- Rule IDs
-
- SV-223924r877765_rule
- SV-107659
Checks: C-25597r516171_chk
From the ISPF Command Shell enter: TSS WHOOWNS data set(*) If data set masking characters. (*, %, and +, **) are owned by the MSCA, this is not a finding.
Fix: F-25585r516172_fix
Configure all data set masking characters to be owned the MSCA. Example TSS commands to protect masking characters: TSS ADD(msca) DSN(*) TSS ADD(msca) DSN(%) TSS ADD(msca) DSN(+)
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000510
- Vuln IDs
-
- V-223925
- V-98557
- Rule IDs
-
- SV-223925r877766_rule
- SV-107661
Checks: C-25598r868947_chk
Refer to the SYS1.UADS. Ask the System Administrator for list of all emergency ACIDs available to the site along with the associated function of each. If there are no emergency ACIDs defined ask the system administrator for an alternate documented procedure to handle emergencies. If there are no emergency ACIDs and no documented emergency procedure, this is a finding. If at a minimum, an emergency ACID exists with the security administration attributes specified in accordance with the following requirements, this is not a finding. For emergency IDs with security administration privileges, but which cannot access and update system data sets: ADMIN Authority: ACID(ALL) DATA(ALL) OTRAN(ALL) MISC1(INSTDATA,SUSPEND,TSSSIM,NOATS) MISC2(TSO,TARGET) MISC8(PWMAINT,REMASUSP) MISC9(GENERIC) FACILITY(BATCH, TSO, ROSCOE, CICS, xxxx) Where 'xxxx' is a facility the application security team grants access into for their application users. An additional class of userids can exist to perform all operating system functions except ESM administration. These emergency ACID(s) will have ability to access and update all system data sets but will not have security administration privileges. See the following requirements: Data set permissions for the emergency ACIDs will be permitted as follows: TSS PER(acid) DSN(*****) ACCESS(ALL) ACTION(AUDIT) Security Bypass Attributes NODSNCHK, NOVOLCHK, and NORESCHK will not be given to the Emergency ACIDs. All emergency ACID(s) are to be implemented with logging to provide an audit trail of their activities. All emergency ACID(s) are to be maintained in both the ESM and SYS1.UADS to ensure they are available in the event that the ESM is not functional. All emergency ACID(s) will have distinct, different passwords in SYS1.UADS and in the ACP, and the site is to establish procedures to ensure that the passwords differ. The password for any ID in SYS1.UADS is never to match the password for the same ID in the ACP. All emergency ACID(s) will have documented procedures to provide a mechanism for the use of the IDs. Their release for use is to be logged, and the log is to be maintained by the ISSO. When an emergency ACID is released for use, its password is to be reset by the ISSO within 12 hours. 1) Review the access authorizations for all emergency ACIDs to ensure that all access permitted to these ACIDs is reviewed and approved by the ISSO. 2) If emergency ACIDs are utilized, ensure they are restricted to performing only the operating system recovery functions or the ESM administration functions. If these emergency ACID(s) have ability to ACCESS and UPDATE all system data sets, but do not have security administration privileges, this is not a finding. Note: If running Quest NC-Pass, validate that the Emergency ACIDS are identified to have the FACILITY of NCPASS and SECURID resource in the ABSTRACT resource class.
Fix: F-25586r868948_fix
Configure any emergency ACID to have only access to resources required to support the specific functions of the owning department and that access to these resources is audited. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes. TSS PER(acid) DSN(*****) ACCESS(ALL) ACTION(AUDIT) Security Bypass Attributes NODSNCHK, NOVOLCHK, and NORESCHK will not be given to the Emergency ACIDs. All emergency ACID(s) are to be implemented with logging to provide an audit trail of their activities. All emergency ACID(s) are to be maintained in both the ACP and SYS1.UADS to ensure they are available in the event that the ACP is not functional. All emergency ACID(s) will have distinct, different passwords in SYS1.UADS and in the ACP, and the site is to establish procedures to ensure that the passwords differ. The password for any ID in SYS1.UADS is never to match the password for the same ID in the ACP. All emergency ACID(s) will have documented procedures to provide a mechanism for the use of the IDs. Their release for use is to be logged, and the log is to be maintained by the ISSO. When an emergency ACID is released for use, its password is to be reset by the ISSO within 12 hours. If no emergency userids are in use on the system, develop and document a procedure to manage emergency access to the system.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000520
- Vuln IDs
-
- V-223926
- V-98559
- Rule IDs
-
- SV-223926r877767_rule
- SV-107663
Checks: C-25599r516177_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(BASIC) If any ACID(s) is (are) assigned FACILITY(*ALL*), this is a finding.
Fix: F-25587r516178_fix
The ISSO will ensure that blanket access to all facilities; FACILITY(ALL), is never granted. Review all access to FACILITY(*ALL*). Evaluate the impact of correcting the deficiency. Develop a plan of action and remove access to FAC(*ALL*). Example: TSS REM(acid) FAC(ALL)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000530
- Vuln IDs
-
- V-223927
- V-98561
- Rule IDs
-
- SV-223927r877768_rule
- SV-107665
Checks: C-25600r516180_chk
Review the ALL record for the assignment of FACILITY. If CA-Top Secret facilities are granted via the ALL record, with the exception of DFHSM/HSM, this is a finding. The DFHSM/HSM FACILITY can be determined by reviewing FACLIST for the FACILITY that contains INITPGM=ARC.
Fix: F-25588r516181_fix
Review ALL record for FACILITY access. Evaluate the impact of correcting the deficiency. Develop a plan of action and remove access.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000550
- Vuln IDs
-
- V-223928
- V-98563
- Rule IDs
-
- SV-223928r877769_rule
- SV-107667
Checks: C-25601r868950_chk
Refer the accesses to the TSS masking character (*, *., and/or **) for data sets. If the following guidance is true, this is not a finding. If the TSS data set access authorizations restrict READ access to auditors, this is not a finding. If the TSS data set access authorizations restrict READ and/or greater access to DASD administrators, Trusted Started Tasks, emergency users, and DASD batch users, this is not a finding. If CA VTAPE is installed on the systems and the TSS data set access authorizations restrict READ access to CA VTAPE STCs and/or batch users, this is not a finding. If the TSS data set access authorizations specify that all (i.e., failures and successes) EXECUTE and/or greater accesses are logged, this is not a finding.
Fix: F-25589r868951_fix
Review access authorization to the TSS mask character (*, *., and/or **) for data sets. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to restrict access to the data set mask permissions. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and, if required, that all WRITE and/or greater accesses are logged. The programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented, will work with the ISSO to confirm 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.) Auditors may require READ access to all data sets. DASD administrators, Trusted Started Tasks, emergency users, and DASD batch users that require READ and/or greater access to perform maintenance to all data sets. If CA VTAPE is installed on the system, READ access can be given to the CA VTAPE STCs and/or batch users. All accesses authorizations will be logged. The exception is the logging requirement is not required for Trusted Started Tasks. The following commands are provided as a sample for implementing data set controls: TSS ADDTO(msca) DATASET(*.) TSS PERMIT(smplsmpl) DATASET(*.) ACCESS(READ) ACTION(AUDIT) TSS PERMIT(CA VTape STC) DATASET(*.) ACCESS(READ) ACTION(AUDIT) TSS PERMIT(dasbsmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(dasdsmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(emersmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(tstcsmpl) DATASET(*.) ACCESS(ALL)
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-ES-000560
- Vuln IDs
-
- V-223929
- V-98565
- Rule IDs
-
- SV-223929r877770_rule
- SV-107669
Checks: C-25602r516186_chk
From the ISPF Command Shell enter: TSS WHOOWNS VOLUME(*) For each volume identified issue WHOHAS (<volume id>) If access authorizations greater than CREATE (e.g., CONTROL or ALL) granted for DASD volumes are within the requirements in the site security plan, this is not a finding. If access authorization for volumes exceeds the requirements without justification, this is a finding. NOTE: Domain-level DASD Administrators who are responsible for the Domain level DASD/storage administration. Volume level access to those team members who are directly responsible and perform Domain level DASD/Storage administration may be granted access to all volumes via PRIVPGM controls.
Fix: F-25590r516187_fix
Ensure that DASD VOLUME access authorization greater than CREATE is not permitted unless authorized by the ISSO. Review all access to DASD VOLUMEs. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the required changes. *Noted Exception: Domain level DASD Administrators who are responsible for the Domain level DASD/storage administration. Volume level access to those team members who are directly responsible and perform Domain level DASD/Storage administration may be granted access to all volumes via PRIVPGM controls. Domain Level DASD/Storage administrators access should be granted VOL(*ALL*)ACC(ALL)ACTION(AUDIT)PRIVPGM(list of privileged programs)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-ES-000570
- Vuln IDs
-
- V-223930
- V-98567
- Rule IDs
-
- SV-223930r877771_rule
- SV-107671
Checks: C-25603r868953_chk
Refer to the table of Sensitive Utilities resources and/or generic equivalent as detail in the table below. If the TSS resource access authorizations for the following sensitive utilities restrict access to the appropriate personnel, this is not a finding. Sensitive Utility Controls Program Product Function AHLGTF z/OS System Activity Tracing HHLGTF IHLGTF ICPIOCP z/OS System Configuration IOPIOCP IXPIOCP IYPIOCP IZPIOCP BLSROPTR z/OS Data Management DEBE OS/DEBE Data Management DITTO OS/DITTO Data Management FDRZAPOP FDR Product Internal Modification GIMSMP SMP/E Change Management Product ICKDSF z/OS DASD Management IDCSC01 z/OS IDCAMS Set Cache Module IEHINITT z/OS Tape Management IFASMFDP z/OS SMF Data Dump Utility IND$FILE z/OS PC to Mainframe File Transfer (Applicable only for classified systems) CSQJU003 IBM WebSphereMQ CSQJU004 CSQUCVX CSQ1LOGP CSQUTIL WHOIS z/OS Share MOD to identify user name from USERID. Restricted to data center personnel only. If the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding. If the TSS resource logging is correctly specified, this is not a finding.
Fix: F-25591r868954_fix
Ensure that the following are properly specified in the ACP. Note: The resources and/or resource prefixes identified below are examples of a possible installation. The actual resource type, 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. Ensure that all Sensitive Utility Controls resources and/or generic equivalent are properly protected according to the requirements specified in Sensitive Utility Controls table below. This table lists the resources, access requirements, and logging requirements for Sensitive Utilities, ensures the following guidelines are followed: Sensitive Utility Controls Program Product Function AHLGTF z/OS System Activity Tracing HHLGTF IHLGTF ICPIOCP z/OS System Configuration IOPIOCP IXPIOCP IYPIOCP IZPIOCP BLSROPTR z/OS Data Management DEBE OS/DEBE Data Management DITTO OS/DITTO Data Management FDRZAPOP FDR Product Internal Modification GIMSMP SMP/E Change Management Product ICKDSF z/OS DASD Management IDCSC01 z/OS IDCAMS Set Cache Module IEHINITT z/OS Tape Management IFASMFDP z/OS SMF Data Dump Utility IND$FILE z/OS PC to Mainframe File Transfer (Applicable only for classified systems) CSQJU003 IBM WebSphereMQ CSQJU004 CSQUCVX CSQ1LOGP CSQUTIL WHOIS z/OS Share MOD to identify user name from USERID. Restricted to data center personnel only. The TSS resources as designated in the above table are owned and/or DEFPROT is specified for the resource class. The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table. The following commands are provided as a sample for implementing resource controls: TSS ADD(dept-acid) PROGRAM(AHLGTF) TSS PERMIT(stcgsmpl) PROGRAM(AHLGTF) ACTION(AUDIT)
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000580
- Vuln IDs
-
- V-223931
- V-98569
- Rule IDs
-
- SV-223931r881331_rule
- SV-107673
Checks: C-25604r881330_chk
Refer to the site security plan, the system administrator, and system libraries to determine list of stated tasks available on the system. If the following guidance is true, this is not a finding. -All started tasks are assigned a unique user ACID or STC ACIDs that will be unique per product and function if supported by vendor documentation. -Every ACID with the STC Facility has a corresponding entry defined in the STC record. -Every ACID defined in the STC record has a corresponding user ACID defined to TSS with the STC Facility. -All STC ACIDs will have a password generated in accordance with STIG requirements. -All STC ACIDs will be sourced to the internal reader (e.g., ADD(stc-acid) SOURCE(INTRDR). -The STC ACIDs may have the NOSUSPEND attribute.
Fix: F-25592r516193_fix
Review the STC record and all associated ACIDs. Ensure STCs and associated ACIDs are defined to the STC record. Restrict access to required resources only. Evaluate the impact of correcting the deficiency. Ensure TSS started task table record contains an entry for each Started Proc that maps the proc to a unique userid, or STC ACIDs will be unique per product and function if supported by vendor documentation. Develop a plan of action and implement the changes as specified: All STC ACIDs will have the STC facility. An STC also may be granted the FAC(BATCH) if it requires the capability to submit batch jobs to the internal reader. It should be noted, however, that this also will allow the STC itself to be executed as a batch job. TSS ADD(stc-acid) FACILITY(STC BATCH) Each STC ACID will be defined with a password following the password requirement guidelines. The only exception is that these passwords will be defined as non-expiring. In addition, each STC will have its own unique password. Defining a password for started tasks prevents a user from logging onto a system with the STC ACID. TSS REP(stc-acid) PASSWORD(xxxxxxxx,0) Ensure the OPTIONS control option specifies a value of 4 to disable password checking for STCs. Otherwise operators will be forced to supply a password when STCs are started. All STC ACIDs will be sourced to the internal reader. This control will further protect the unauthorized use of STC ACIDs. TSS ADD(stc-acid) SOURCE(INTRDR) Every STC will be defined to the STC table, associated with a specific procedure, and granted minimum access. TSS ADD(STC) PROCNAME(stc-proc) ACID(stc-acid) Note: The STC ACIDs may have the NOSUSPEND attribute to exempt an STC ACID from suspension for excessive violations. Review the STC record and all associated ACIDs. Ensure STCs and associated ACIDs are defined to the STC record. Restrict access to required resources only. Evaluate the impact of correcting the deficiency. Ensure TSS started task table record contains an entry for each Started Proc that maps the proc to a unique userid, or STC ACIDs will be unique per product and function if supported by vendor documentation. Develop a plan of action and implement the changes as specified: All STC ACIDs will have the STC facility. An STC also may be granted the FAC(BATCH) if it requires the capability to submit batch jobs to the internal reader. It should be noted, however, that this also will allow the STC itself to be executed as a batch job. TSS ADD(stc-acid) FACILITY(STC BATCH) Each STC ACID will be defined with a password following the password requirement guidelines. The only exception is that these passwords will be defined as non-expiring. In addition, each STC will have its own unique password. Defining a password for started tasks prevents a user from logging onto a system with the STC ACID. TSS REP(stc-acid) PASSWORD(xxxxxxxx,0) Ensure the OPTIONS control option specifies a value of 4 to disable password checking for STCs. Otherwise operators will be forced to supply a password when STCs are started. All STC ACIDs will be sourced to the internal reader. This control will further protect the unauthorized use of STC ACIDs. TSS ADD(stc-acid) SOURCE(INTRDR) Every STC will be defined to the STC table, associated with a specific procedure, and granted minimum access. TSS ADD(STC) PROCNAME(stc-proc) ACID(stc-acid) Note: The STC ACIDs may have the NOSUSPEND attribute to exempt an STC ACID from suspension for excessive violations.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000590
- Vuln IDs
-
- V-223932
- V-98571
- Rule IDs
-
- SV-223932r877773_rule
- SV-107675
Checks: C-25605r516195_chk
From the ISPF Command enter: TSS MODIFY STATUS If the CANCEL Control Option is not specified, this is not a finding.
Fix: F-25593r516196_fix
Remove the CANCEL sub-option from the Control Options list. TSS MODIFY(control_option [(suboption_list)])
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000600
- Vuln IDs
-
- V-223933
- V-98573
- Rule IDs
-
- SV-223933r877774_rule
- SV-107677
Checks: C-25606r516198_chk
From the ISPF Command enter: TSS MODIFY STATUS If the HPBPW Control Option value is set to (3) days maximum, this is not a finding. If the HPBPW Control Option value is set to greater than (3) days, this is a finding.
Fix: F-25594r516199_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the HPBPW control option setting to a maximum of 3 days.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000610
- Vuln IDs
-
- V-223934
- V-98575
- Rule IDs
-
- SV-223934r877775_rule
- SV-107679
Checks: C-25607r516201_chk
From the ISPF Command enter: TSS MODIFY STATUS If the INSTDATA Control Option is set to NONE this is not a finding.
Fix: F-25595r516202_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the INSTDATA control option value to (0) and proceed with the change.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000620
- Vuln IDs
-
- V-223935
- V-98577
- Rule IDs
-
- SV-223935r877776_rule
- SV-107681
Checks: C-25608r516204_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the OPTIONS Control Option contains at a minimum option number (4), this is not a finding.
Fix: F-25596r516205_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. The OPTIONS Control Option must contain at a minimum option number (4). Example TSS PARMFILE Control Option entry: OPTIONS(4,5,6,12,14)
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000630
- Vuln IDs
-
- V-223936
- V-98579
- Rule IDs
-
- SV-223936r877777_rule
- SV-107683
Checks: C-25609r516207_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the TEMPDS Control Option value is set to TEMPDS(YES), this not a finding.
Fix: F-25597r516208_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting to TEMPDS(YES), and proceed with the change.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000640
- Vuln IDs
-
- V-223937
- V-98581
- Rule IDs
-
- SV-223937r877778_rule
- SV-107685
Checks: C-25610r868956_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) TYPE(SCA) DATA(BASIC) If the persons listed agree with the site security plan, this is not a finding.
Fix: F-25598r868957_fix
Review all security administrator ACIDs. Evaluate the impact of correcting the deficiency. Develop a plan of action and reduce the number of control ACIDs if not justified. Use information below as guidance. TYPE=CENTRAL, TYPE=MASTER or also known as "SCA" and "MSCA" level of ACIDS will adhere to the following restrictions based upon documented role/function an individual performs: -Domain level Information System Security Officer (ISSO) - full administrative authorities and access rights needed to perform required and documented role/responsibilities/function. -Assistance Domain Level Information System Security Officer or "backup" or ISSO (up to same access as 1). -DISA SRR Auditor, DoD IG Auditor, SAS70 Auditor - only "view" administrative authorities must be granted and only for those roles/functions that have been formally documented as DISA, DoD IG or SAS70 Auditors and approved by the DISA AO for those position/functions/roles. Exception: Until scoping is worked out and resolved, DISA OST team members may be defined as TYPE=CENTRAL with limited authority such as ACID(INFO,MAINTAIN). All OST Team member ACIDs will be changed to TYPE=LIMITED and scoped accordingly to allow password resets upon verification of users, yet to limit and eliminate any potential risk associated with resetting of MSCA or other SCA level accounts. NO other exceptions will exist.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000650
- Vuln IDs
-
- V-223938
- V-98583
- Rule IDs
-
- SV-223938r877779_rule
- SV-107687
Checks: C-25611r516213_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(ADMIN) If the ACIDs having MISC9(ALL) or MISC9(CONSOLE) authority are designated SCAs who are responsible for the security for the domain this is not a finding.
Fix: F-25599r516214_fix
Review all ACIDs with the MISC9 attribute. Evaluate the impact of removing MISC9(ALL) or MISC9(CONSOLE) access from ACIDs not required to assign the CONSOLE attribute. It is suggested that MISC9(CONSOLE) assignment privileges be limited to the MSCA. Develop a plan of action and implement the changes.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000660
- Vuln IDs
-
- V-223939
- V-98585
- Rule IDs
-
- SV-223939r877780_rule
- SV-107689
Checks: C-25612r516216_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the LUUPDONCE Control Option value is set to "YES", this is a finding.
Fix: F-25600r516217_fix
Configure LUUPDONCE control option is set to (NO). Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the control option setting to NO and proceed with the change.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000670
- Vuln IDs
-
- V-223940
- V-98587
- Rule IDs
-
- SV-223940r877781_rule
- SV-107691
Checks: C-25613r516219_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the ADSP Control Option value is not set to "ADSP(NO)", this is a finding.
Fix: F-25601r516220_fix
Configure the ADSP control option is set to (NO) indicating that the RACF bit in the DSCB will not be set. Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting to ADSP(NO) and proceed with the change.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-ES-000680
- Vuln IDs
-
- V-223941
- V-98589
- Rule IDs
-
- SV-223941r877782_rule
- SV-107693
Checks: C-25614r516222_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the RECOVER Control Option value is not set to "RECOVER(ON)", this is a finding.
Fix: F-25602r516223_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the following control option setting as specified and proceed with the change. RECOVER(ON)
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000382
- Version
- TSS0-ES-000690
- Vuln IDs
-
- V-223942
- V-98591
- Rule IDs
-
- SV-223942r877783_rule
- SV-107695
Checks: C-25615r516225_chk
Review each CONSOLxx parmlib member. If the following guidance is true, this is not a finding. The "DEFAULT" statement for each CONSOLxx member specifies "LOGON(REQUIRED)" or "LOGON(AUTO)". The "CONSOLE" statement for each console assigns a unique name using the "NAME" parameter. The "CONSOLE" statement for each console specifies "AUTH(INFO)". Exceptions are the "AUTH" parameter is not valid for consoles defined with "UNIT(PRT)" and specifying "AUTH(MASTER)" is permissible for the system console. Note: The site should be able to determine the system consoles. However, it is imperative that the site adhere to the "DEFAULT" statement requirement.
Fix: F-25603r516226_fix
Configure the "DEFAULT" statement to specify "LOGON(REQUIRED)" so that all operators are required to log on prior to entering z/OS system commands. At the discretion of the ISSO, "LOGON(AUTO)" may be used. If "LOGON(AUTO)" is used assure that the console userids are defined with minimal access. See ACP00292. Configure each "CONSOLE" statement to specify an explicit console NAME. And that "AUTH(INFO)" is specified, this also including extended MCS consoles. "AUTH(MASTER)" may be specified for systems console. Note: The site should be able to determine the system consoles. However, it is imperative that the site adhere to the "DEFAULT" statement requirement.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000382
- Version
- TSS0-ES-000700
- Vuln IDs
-
- V-223943
- V-98593
- Rule IDs
-
- SV-223943r877784_rule
- SV-107697
Checks: C-25616r516228_chk
Refer to IEASYS00 to determine correct CONSOLxx member. Examine the CONSOLxx member. If the following guidance is true, this is not a finding. Each console defined in the currently active CONSOLxx parmlib member in EXAM.RPT(PARMLIB) is associated with a valid TSS ACID. Each console ACID has no special privileges and/or attributes (e.g., BYPASSING, CONSOLE, etc.; excluding VTAM SMCS consoles). Each console ACID has no accesses to interactive on-line facilities (e.g., TSO, CICS, etc.; excluding VTAM SMCS consoles). Each console can have the Facility of CONSOLE. Each console ACID will be restricted from accessing all data sets and resources except MVS.MCSOPER.consolename in the OPERCMDS resource class and consolename in the CONSOLE resource class. NOTE: If LOGON(AUTO) is specified in the currently active CONSOLxx parmlib member, additional access may be required. Permissions for the console ACIDs and/or console profile may be given with access READ to MVS.CONTROL, MVS.DISPLAY, MVS.MONITOR, and MVS.STOPMN OPERCMDS resource.
Fix: F-25604r516229_fix
Review the MCS console resources defined to z/OS and the ACP, and ensure they conform to those outlined below. Each console defined in the currently active CONSOLxx parmlib member in EXAM.RPT(PARMLIB) is associated with a valid TSS ACID. Each console ACID has no special privileges and/or attributes (e.g., BYPASSING, CONSOLE, etc.). Each console ACID has no accesses to interactive on-line facilities (e.g., TSO, CICS, etc.; excluding VTAM SMCS consoles). Each console can have the Facility of CONSOLE. Each console ACID will be restricted from accessing all data sets and resources except MVS.MCSOPER.consolename in the OPERCMDS resource class and consolename in the CONSOLE resource class. NOTE: If LOGON(AUTO) is specified in the currently active CONSOLxx parmlib member, additional access may be required. Permissions for the console ACIDs and/or console profile may be given with access READ to MVS.CONTROL, MVS.DISPLAY, MVS.MONITOR, and MVS.STOPMN OPERCMDS resource. Example: (These are only examples, not requirements.) TSS CREATE(consnoautolog) TYPE(PROFILE) NAME('MCS consoles with no autolog') DEPT('SYS1') TSS CREATE(consautolog) TYPE(PROFILE) - NAME('MCS consoles with autolog') - DEPT('SYS1') TSS CREATE(consname) NAME('MCS console name') - FACILITY(CONSOLE) PASSWORD(password,0) - PROFILE(consgroup) TSS PER(consautolog) OPERCMDS(MVS.CONTROL) ACCESS(READ) TSS PER(consautolog) OPERCMDS(MVS.DISPLAY) ACCESS(READ) TSS PER(consautolog) OPERCMDS(MVS.MONITOR) ACCESS(READ) TSS PER(consautolog) OPERCMDS(MVS.STOPMN) ACCESS(READ) TSS PER(consname) SYSCONS(consname) ACCESS(READ)
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-ES-000710
- Vuln IDs
-
- V-223944
- V-98595
- Rule IDs
-
- SV-223944r877785_rule
- SV-107699
Checks: C-25617r516231_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the "CPFRCVUND" Control Option value is set to "YES", this is a finding.
Fix: F-25605r516232_fix
Configure the CPFRCVUND control option value to (NO). Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the control option setting to "NO" and proceed with the change.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-ES-000720
- Vuln IDs
-
- V-223945
- V-98597
- Rule IDs
-
- SV-223945r877786_rule
- SV-107701
Checks: C-25618r516234_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the CPFTARGET Control Option value specified is not set to "LOCAL", this is a finding.
Fix: F-25606r516235_fix
Configure the CPFTARGET Control Option value specified set to LOCAL.
- RMF Control
- IA-2
- Severity
- Low
- CCI
- CCI-000764
- Version
- TSS0-ES-000730
- Vuln IDs
-
- V-223946
- V-98599
- Rule IDs
-
- SV-223946r877787_rule
- SV-107703
Checks: C-25619r516237_chk
From the ISPF Command Shell enter: TSS LIST (ACIDs) DATA (BASIC) If any ACID does not have the "NAME" field completed, this is a finding.
Fix: F-25607r516238_fix
Review all ACID definitions and ensure the NAME field is completed. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement.
- RMF Control
- IA-2
- Severity
- High
- CCI
- CCI-000764
- Version
- TSS0-ES-000740
- Vuln IDs
-
- V-223947
- V-98601
- Rule IDs
-
- SV-223947r877788_rule
- SV-107705
Checks: C-25620r516240_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(PASSWORD) - NOTE: To evaluate the PASSWORD option NOPW, it must be run under the MSCA's authority, if not the information will not be generated. If PASSWORD(NOPW) is specified for any ACID types (USER, DCA, VCA, ZCA, LSCA, SCA, and MSCA), this is a finding.
Fix: F-25608r516241_fix
Review definition of all ACID types (including USER, DCA, VCA, ZCA, LSCA, SCA, and MSCA) except for structure ACIDS such as: DEPARTMENT, DIVISION, ZONE, GROUP, and PROFILE to ensure that all ACIDs specify a password. The following command is an example of how this can be corrected. TSS REPLACE(user_ACID) PASSWORD(Text4Pwd,60
- RMF Control
- IA-2
- Severity
- Low
- CCI
- CCI-000764
- Version
- TSS0-ES-000750
- Vuln IDs
-
- V-223948
- V-98603
- Rule IDs
-
- SV-223948r877789_rule
- SV-107707
Checks: C-25621r516243_chk
From the ISPF Command Shell enter: TSS LIST (ACIDs) DATA (BASIC,TSO,CICS) If all the fields and information listed below, are not present for all interactive users this is a finding. FIELD DESCRIPTION VALUE FACILITY Validated facilities to use BATCH, TSO, NCPASS, or other interactive Facility PASSWORD logon password must have a value INSTDATA Installation data optional PROFILE Profile(s) optional TSOLPROC Default TSO logon PROC optional for TSO users TSOLACCT Default TSO logon account may be required for a fee for service.
Fix: F-25609r516244_fix
Review all interactive ACID definitions to ensure required information is provided. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required according to the following: FIELD DESCRIPTION VALUE FACILITY Validated facilities to use BATCH, TSO, NCPASS, or other interactive Facility PASSWORD logon password must have a value INSTDATA Installation data optional PROFILE Profile(s) optional TSOLPROC Default TSO logon PROC optional for TSO users TSOLACCT Default TSO logon account may be required for a fee for service.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-ES-000770
- Vuln IDs
-
- V-223950
- V-98607
- Rule IDs
-
- SV-223950r877791_rule
- SV-107711
Checks: C-25623r516249_chk
Refer to data obtained from the site installation identifying batch type ACIDs. If all static batch ACIDs (ACIDs whose passwords never change) originating from a physical reader, RJE, or NJE are sourced to those readers such as (INTRDR, N12.IR, etc.) with the appropriate source Syntax, this is not a finding.
Fix: F-25611r516250_fix
Ensure that all static batch ACIDs (ACIDs whose passwords never change) originating from a physical reader, RJE, or NJE are sourced to those readers such as (INTRDR, N12.IR, etc.) with the appropriate source Syntax. Example: TSS ADD(batch-acid) SOURCE(device) Develop a plan of action and implement the changes as specified.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-ES-000780
- Vuln IDs
-
- V-223951
- V-98609
- Rule IDs
-
- SV-223951r877792_rule
- SV-107713
Checks: C-25624r516252_chk
Refer to data obtained from the site installation identifying DASD maintenance ACIDs. If each DASD Maintenance ACID has batch Facility, this is not a finding.
Fix: F-25612r516253_fix
Define all batch ACIDs to the BATCH facility.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000770
- Version
- TSS0-ES-000790
- Vuln IDs
-
- V-223952
- V-98611
- Rule IDs
-
- SV-223952r877793_rule
- SV-107715
Checks: C-25625r516255_chk
Obtain a list of all userids that are shared among multiple users (i.e., not uniquely identified system users). If there are no shared userids on this domain, this is not a finding. If there are shared userids on this domain, this is a finding. NOTE: Userid
Fix: F-25613r516256_fix
Identify user accounts defined to the ESM that are being shared among multiple users. This may require interviews with appropriate system-level support personnel. Remove the shared user accounts from the ESM.
- RMF Control
- IA-4
- Severity
- Medium
- CCI
- CCI-000795
- Version
- TSS0-ES-000800
- Vuln IDs
-
- V-223953
- V-98613
- Rule IDs
-
- SV-223953r877794_rule
- SV-107717
Checks: C-25626r516258_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) If every user shows a LAST-USED=yy.ddd within the past "35" days, this is not a finding. NOTE: VALID FOR INTERACTIVE USERIDS, NOT VALID FOR STARTED TASK USERIDS AND BATCH USERIDS.
Fix: F-25614r516259_fix
Develop a procedure to check all userids for inactivity of more than "35" days. If found, the ISSO must suspend an account, but not delete it until it is verified by the local ISSO that the user no longer requires access. If verification is not received within "60" days, the account may be deleted.
- RMF Control
- IA-4
- Severity
- Medium
- CCI
- CCI-000795
- Version
- TSS0-ES-000810
- Vuln IDs
-
- V-223954
- V-98615
- Rule IDs
-
- SV-223954r877795_rule
- SV-107719
Checks: C-25627r516261_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the INACTIVE Control Option is set to a value of "0", this is not a finding.
Fix: F-25615r516262_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the INACTIVE Control Option to a value of "0" days and proceed with the change. The INACTIVE Control Option value is set properly with the command: TSS MODIFY INACTIVE(0)
- RMF Control
- SC-4
- Severity
- Medium
- CCI
- CCI-001090
- Version
- TSS0-ES-000820
- Vuln IDs
-
- V-223955
- V-98617
- Rule IDs
-
- SV-223955r877796_rule
- SV-107721
Checks: C-25628r516264_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the AUTOERASE Control Option value is set to (ALL), this is not a finding.
Fix: F-25616r516265_fix
Configure the AUTOERASE control option is set to (ALL) for all systems to erase all residual information on DASD. Evaluate the impact associated with implementation of the control option. Develop a plan of action to set the AUTOERASE control option to (ALL) for all systems and implement.
- RMF Control
- SC-24
- Severity
- Medium
- CCI
- CCI-001190
- Version
- TSS0-ES-000830
- Vuln IDs
-
- V-223956
- V-98619
- Rule IDs
-
- SV-223956r877797_rule
- SV-107723
Checks: C-25629r516267_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If only systems personnel are defined in SYS1.UADS and the DOWN Control Option values are set to DOWN(BW,SB,TN,OW), this is not a finding. If non-systems personnel are defined in SYS1.UADS and the DOWN Control Option values are set to DOWN(BW,SB,TW,OW), this is not a finding.
Fix: F-25617r516268_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified below and proceed with the change. Setting if ONLY systems personnel are defined in SYS1.UADS: DOWN(BW,SB,TN,OW) Setting if any non-systems personnel are defined in SYS1.UADS: DOWN(BW,SB,TW,OW)
- RMF Control
- CM-7
- Severity
- High
- CCI
- CCI-001774
- Version
- TSS0-ES-000840
- Vuln IDs
-
- V-223957
- V-98621
- Rule IDs
-
- SV-223957r877798_rule
- SV-107725
Checks: C-25630r516270_chk
From the ISPF Command Shell enter: TSS MODIFY(FACILITY(ALL)) If the Facility Control Option does not specifies the sub option of "MODE=FAIL" for all facilities, this is a finding.
Fix: F-25618r516271_fix
Evaluate the impact associated with implementation of the Facility Control Option MODE sub-option. Develop a plan of action to implement the Facility Control Option MODE sub-option setting to "MODE=FAIL" and proceed with the change.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-002041
- Version
- TSS0-ES-000850
- Vuln IDs
-
- V-223958
- V-98623
- Rule IDs
-
- SV-223958r877799_rule
- SV-107727
Checks: C-25631r516273_chk
Ask the system administrator for the procedures for creating new ACIDs. If the procedure contains the "EXP" option, this is not a finding.
Fix: F-25619r516274_fix
Assure procedures to create New Acids include the "EXP" option. Example: TSS CREATE(USER02) NAME('ANDY POE') TYPE(USER) DEPARTMENT(PAYDEPT) PASSWORD(INITIAL,60,EXP) FACILITY(TSO)
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002233
- Version
- TSS0-ES-000860
- Vuln IDs
-
- V-223959
- V-98625
- Rule IDs
-
- SV-223959r877800_rule
- SV-107729
Checks: C-25632r516276_chk
From this ISPF Command Shell enter: TSS MODIFY STATUS If the SUBACID Control Option values are NOT set to "SUBACID(U,8)", this is a finding.
Fix: F-25620r516277_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting to "SUBACID(U,8)", and proceed with the change.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002233
- Version
- TSS0-ES-000870
- Vuln IDs
-
- V-223960
- V-98627
- Rule IDs
-
- SV-223960r877801_rule
- SV-107731
Checks: C-25633r516279_chk
From the ISPF Command Shell enter: TSS MODIFY FACILITY(ALL) enter TSS MODIFY FACILITY(<FACILITY>) If no Facility is defined with both the "MULTIUSER" and "ASUBM" attributes further analysis is not needed. For each Facility with "MULTIUSER" and "ASUBM" attribute, review the @ACIDS report to determine which ACID(s) has (have) the following: -A Master Facility of the Facility with "MULTIUSER" and "ASUBM" attribute, and, -The Facility of "BATCH" If each ACID that has the Master Facility of the Facility with "MULTIUSER" and "ASUBM" attribute and the Facility of "BATCH" is defined to the "PROPCNTL" resource class, this is not a finding.
Fix: F-25621r516280_fix
Ensure an associated ACID exists for all batch jobs and propagation control is being used. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as required. The following Example shows the CONTROL-M STC ACID being owned to the PROPCNTL resource class: TSS ADD(deptacid) PROPCNTL(control-m-acid)
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002233
- Version
- TSS0-ES-000880
- Vuln IDs
-
- V-223961
- V-98629
- Rule IDs
-
- SV-223961r877802_rule
- SV-107733
Checks: C-25634r516282_chk
Refer to the documentation of the processes used for submission of batch jobs via an automated process (i.e., scheduler or other sources) and each of the associated userids. Ensure that each identified batch ACID is sourced to a specific submission process used only for batch processing. If the following guidance is true, this is not a finding. -The job scheduler is cross-authorized to the batch ACIDs. -The Facility of BATCH is specified for each batch ACID. -Batch ACIDs with facilities other than BATCH should be questioned to ensure they are truly used for batch processing only, especially if a non-expiring password is used. -The batch ACIDS may have the NOSUSPEND attribute.
Fix: F-25622r516283_fix
Ensure associated ACIDs exist for all batch jobs and documentation justifying access to system resources is maintained and filed with the ISSO. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the required changes.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002234
- Version
- TSS0-ES-000890
- Vuln IDs
-
- V-223962
- V-98631
- Rule IDs
-
- SV-223962r877803_rule
- SV-107735
Checks: C-25635r516285_chk
From ISPF Command Shell enter: TSS MODIFY STATUS If the ADMINBY Control Option value is not set or set to "NOADMBY", this is a finding.
Fix: F-25623r516286_fix
Ensure ADMINBY control option is set to "ADMINBY" to record who when and where information in the ACID security record for administrative changes. Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting "ADMINBY" and proceed with the change.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002234
- Version
- TSS0-ES-000900
- Vuln IDs
-
- V-223963
- V-98633
- Rule IDs
-
- SV-223963r877804_rule
- SV-107737
Checks: C-25636r516288_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the LOG Control Option is NOT set to (SMF,INIT, SEC9, MSG), this is a finding.
Fix: F-25624r516289_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified below and proceed with the change. LOG(SMF,INIT, SEC9, MSG)
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002234
- Version
- TSS0-ES-000910
- Vuln IDs
-
- V-223964
- V-98635
- Rule IDs
-
- SV-223964r877805_rule
- SV-107739
Checks: C-25637r516291_chk
From ISPF Command Shell enter: Exec the CA-TSS TSSAUDIT Utility using CHANGES Control Statement. Note: If running Quest NC-Pass, validate that the MSCA ACID has the FACILITY of NCPASS and SECURID resource in the ABSTRACT resource class. If the MSCA password changes are documented in the change log, this is not a finding.
Fix: F-25625r516292_fix
Ensure that the MSCA password changes are documented with comments in the TSS Recovery file. The TSS Recovery file will be of sufficient size to ensure that the change is documented.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002235
- Version
- TSS0-ES-000920
- Vuln IDs
-
- V-223965
- V-98637
- Rule IDs
-
- SV-223965r877806_rule
- SV-107741
Checks: C-25638r516294_chk
From the ISPF Command Shell enter: TSS WHOOWNS IBMFAC(IEASYMUP) If the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding. Enter TSS WHOHAS IBMFAC(IEASYMUP) If TSS resource access authorizations restrict UPDATE and/or greater access to DASD administrators, Tape Library personnel, and system programming personnel, this is not a finding.
Fix: F-25626r516295_fix
Ensure that the System level symbolic resources are defined to the FACILITY resource class and protected. UPDATE access to the System level symbolic resources are limited to System Programmers, DASD Administrators, and/or Tape Library personnel. All access is logged. Ensure the guidelines for the resources and/or generic equivalent are followed. Limit access to the IEASYMUP resources to above personnel with UPDATE and/or greater access. The following commands are provided as a sample for implementing resource controls: TSS ADD(ADMIN) IBMFAC(IEASYMUP) TSS PERMIT(<dasdsmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT) TSS PERMIT(<syspsmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT) TSS PERMIT(<tapesmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT)
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002235
- Version
- TSS0-ES-000930
- Vuln IDs
-
- V-223966
- V-98639
- Rule IDs
-
- SV-223966r877807_rule
- SV-107743
Checks: C-25639r516297_chk
From the ISPF Command Shell enter: TSS LIST STC If *DEF* has action of *FAIL* this is not a finding. If the default ACID is defined enter: TSS List(<defined ACID>) If the ACID has no access to resources and no facility access and sourced to the internal reader, this is not a finding. If any of the above is untrue, this is a finding.
Fix: F-25627r516298_fix
Ensure the default STC ACID is defined in accordance with the following restrictions. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes as specified. All STCs not defined to TSS will fail upon initiation. The following command may be used to associate all undefined STCs with a default action of FAIL: TSS ADD(STC) PROCNAME(DEFAULT) ACID(FAIL) If a valid requirement exists to establish a default STC, the following restrictions also apply: a. The ISSO will maintain the written request, justification, and authorization. b. The STC's ACID will have no other facilities permitted to it. c. The STC's ACID will have a permission of DSN(*****) ACCESS(NONE). TSS PERMIT(stc-acid) DSN(*****) ACCESS(NONE) d. The STC's ACID will not have any permission to the resources available to TSS. e. The STC's ACID will be sourced to the internal reader: ADD(stc-acid) SOURCE(INTRDR) f. An entry will be made in the STC table identifying the default ACID name as follows ("stc-acid" site defined): TSS ADD(STC) PROCNAME(DEFAULT) ACID(stc-acid)
- RMF Control
- AC-6
- Severity
- High
- CCI
- CCI-002235
- Version
- TSS0-ES-000940
- Vuln IDs
-
- V-223967
- V-98641
- Rule IDs
-
- SV-223967r877808_rule
- SV-107745
Checks: C-25640r516300_chk
From the ISPF Command Shell enter: TSS LIST(STC) If only STCs listed as trusted in the IBM z/OS MVS Initialization and Tuning Reference are granted the BYPASS privilege, this is not a finding. Guidelines for reference: Assign the TRUSTED attribute when one of the following conditions applies: -The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation. -Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem. -Avoid assigning TRUSTED to a z/OS started procedure or address space unless it is listed here or you are instructed to do so by the product documentation. Additionally external security managers are candidates for trusted attribute. Any other started tasks not listed or not covered by the guidelines are a finding unless approval by the Authorizing Official AO.
Fix: F-25628r516301_fix
Review the STC record for ACIDs with the BYPASS attribute. Ensure only those trusted STCs that are listed in the IBM z/OS MVS Initialization and Tuning Reference, have been granted this authority. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes. Trusted STCs: While the actual list may vary based on local site requirements and software configuration, the started tasks listed in the IBM z/OS MVS Initialization and Tuning Reference is an approved list of started tasks that may be considered trusted started procedures. Guidelines for reference: Assign the TRUSTED attribute when one of the following conditions applies: -The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation. -Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem. -Avoid assigning TRUSTED to a z/OS started procedure or address space unless it is listed here or you are instructed to do so by the product documentation. Additionally external security managers are candidates for trusted attribute. Any other started tasks not; listed or not covered by the guidelines are a finding unless approval by the Authorizing Official AO.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002235
- Version
- TSS0-ES-000950
- Vuln IDs
-
- V-223968
- V-98643
- Rule IDs
-
- SV-223968r877809_rule
- SV-107747
Checks: C-25641r868959_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(ALL,PA) TYPE(SCA) If the MSCA ACID has access limited to performing security administration functions only, this is not a finding. Below is an example of allowed setup for MSCA account and authorities. "MSCA" as the Accessorid is merely an example here, which is site determined. List is not all inclusive. The primary SCA for the domain will be listed within the "NAME" field since they are responsible for the MSCA ACID. ACCESSORID = MSCA NAME = "primary SCA" TYPE = MASTER FACILITY = BATCH PROFILES = SECURID ATTRIBUTES = AUDIT,CONSOLE,NOATS data set = %. *. data set = ***** +. VOLUMES = *(G) XA data set = SYS3.TSS.BACKUP ACCESS = UPDATE ACTION = AUDIT ----------- ADMINISTRATION AUTHORITIES RESOURCE = *ALL* ACCESS = ALL ACID = *ALL* FACILITIES = *ALL* LIST DATA = *ALL*,PROFILES,PASSWORD,SESSKEY MISC1 = *ALL* MISC2 = *ALL* MISC4 = *ALL* MISC8 = *ALL* MISC9 = *ALL* NOTE 1: Update access to the backup security database is required by the MSCA account anytime the ISSO needs to run/submit the TSS Utility called TSSFAR. MSCA account may from time to time be required to have additional access for the period of project such as Extending the Security Database. NOTE 2: MSCA account must be used for such items as: TSSFAR, EXTENDING Security Database, creating SCA/LSCA accounts, working with LSCA accounts (scoping, admin rights, etc.). Most often the ISSO staff will utilize their normal SCA account. The MSCA account will not be anyone's primary security administrative account.
Fix: F-25629r868960_fix
The ISSO will review the MSCA and ensure access granted is limited to those resources necessary to support the security administration function. Evaluate the impact of correcting the deficiency and develop a plan of action to implement the changes. Below is an example of allowed setup for MSCA account and authorities. "MSCA" as the Accessorid is merely an example here, which is site determined. List is not all inclusive. The primary SCA for the domain will be listed within the "NAME" field since they are responsible for the MSCA ACID. ACCESSORID = MSCA NAME = "primary SCA" TYPE = MASTER FACILITY = BATCH PROFILES = SECURID ATTRIBUTES = AUDIT,CONSOLE,NOATS data set = %. *. data set = ***** +. VOLUMES = *(G) XA data set = SYS3.TSS.BACKUP ACCESS = UPDATE ACTION = AUDIT ----------- ADMINISTRATION AUTHORITIES RESOURCE = *ALL* ACCESS = ALL ACID = *ALL* FACILITIES = *ALL* LIST DATA = *ALL*,PROFILES,PASSWORD,SESSKEY MISC1 = *ALL* MISC2 = *ALL* MISC4 = *ALL* MISC8 = *ALL* MISC9 = *ALL* NOTE 1: Update access to the backup security database is required by the MSCA account anytime the ISSO needs to run/submit the TSS Utility called TSSFAR. MSCA account may from time to time be required to have additional access for the period of project such as Extending the Security Database. NOTE 2: MSCA account must be used for such items as: TSSFAR, EXTENDING Security Database, creating SCA/LSCA accounts, working with LSCA accounts (scoping, admin rights, etc). Most often the ISSO staff will utilize their normal SCA account. The MSCA account will not be anyone's primary security administrative account. NOTE 3: MSCA account must be limited in access, to least privileged access of resources required to function. NOTE 4: If running Quest NC-Pass, validate in ZNCP0020 that the MSCA ACID has the FACILITY of NCPASS and SECURID resource in the ABSTRACT resource class.
- RMF Control
- AC-6
- Severity
- High
- CCI
- CCI-002235
- Version
- TSS0-ES-000960
- Vuln IDs
-
- V-223969
- V-98645
- Rule IDs
-
- SV-223969r877810_rule
- SV-107749
Checks: C-25642r516306_chk
Execute TSS Report TSS AUDIT with PRIVILEGES control statement PRIVILEGES [SHORT]. For more information TSSAUDIT reports refer to the CA-TSS Report and Tracking Guide. Refer to the resulting report. If ACIDs with CONSOLE authority are limited to authorized SCA security administrators and the system programmers that maintain the CA-TSS software product only, this is not a finding.
Fix: F-25630r516307_fix
Review all ACIDs with the CONSOLE attribute. Ensure access is limited to authorized SCA security administrators only. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes. Ensure documentation providing justification for access is maintained and filed with the ISSO.
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002235
- Version
- TSS0-ES-000970
- Vuln IDs
-
- V-223970
- V-98647
- Rule IDs
-
- SV-223970r877811_rule
- SV-107751
Checks: C-25643r516309_chk
Execute TSS Report TSS AUDIT with PRIVILEGES control statement PRIVILEGES [SHORT]. For more information TSSAUDIT reports refer to the CA-TSS Report and Tracking Guide. Refer to the resulting report. If all security administrators have the "NOATS" attribute, this is not a finding.
Fix: F-25631r516310_fix
Review all security administrator ACIDs. Ensure the "NOATS" attribute has been assigned. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes. NOTE: The NOATS attribute may be added to an ACID or an ACID's PROFILE. The following command may be issued to determine if the NOATS attribute is defined to an ACID or an ACID's PROFILE: tss list(<acid>) data(basic,profile)
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-002238
- Version
- TSS0-ES-000980
- Vuln IDs
-
- V-223971
- V-98649
- Rule IDs
-
- SV-223971r877812_rule
- SV-107753
Checks: C-25644r516312_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the PTHRESH Control Option value is not set to "PTHRESH(2)", this is a finding.
Fix: F-25632r516313_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting as specified following and proceed with the change. PTHRESH(2)
- RMF Control
- AC-12
- Severity
- Medium
- CCI
- CCI-002361
- Version
- TSS0-ES-000990
- Vuln IDs
-
- V-223972
- V-98651
- Rule IDs
-
- SV-223972r877813_rule
- SV-107755
Checks: C-25645r516315_chk
From the ISPF Control Shell enter: TSS MODIFY STATUS If the VTHRESH Control Option values are not set to "VTHRRESH(10,NOT,CAN)", this is a finding.
Fix: F-25633r516316_fix
Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option setting to "VTHRESH(10,NOT,CAN)", and proceed with the change.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- TSS0-FT-000010
- Vuln IDs
-
- V-223973
- V-98653
- Rule IDs
-
- SV-223973r877814_rule
- SV-107757
Checks: C-25646r516318_chk
Refer to the FTP.DATA file specified on the SYSFTPD DD statement in the FTP started task JCL. The SYSFTPD DD statement is optional. The search order for FTP.DATA is: /etc/ftp.data SYSFTPD DD statement jobname.FTP.DATA SYS1.TCPPARMS(FTPDATA) tcpip.FTP.DATA Examine the BANNER statement. If the BANNER statement in the FTP Data configuration file specifies an HFS file or data set that contains a logon banner, this is not a finding. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
Fix: F-25634r516319_fix
Ensure the BANNER statement in the FTP Data configuration file specifies an HFS file or z/OS data set that contains a logon banner. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-FT-000020
- Vuln IDs
-
- V-223974
- V-98655
- Rule IDs
-
- SV-223974r877815_rule
- SV-107759
Checks: C-25647r516321_chk
If FTPDATA is configured with the following SMF statements, this is not a finding. FTP.DATA Configuration Statements SMF TYPE119 SMFJES TYPE119 SMFSQL TYPE119 SMFAPPE [Not coded or commented out] SMFDEL [Not coded or commented out] SMFEXIT [Not coded or commented out] SMFLOGN [Not coded or commented out] SMFREN [Not coded or commented out] SMFRETR [Not coded or commented out] SMFSTOR [Not coded or commented out]
Fix: F-25635r868962_fix
Configure SMF options to conform to the specifications in the FTPDATA Configuration Statements below or that they are commented out. SMF TYPE119 SMFJES TYPE119 SMFSQL TYPE119 SMFAPPE [Not coded or commented out] SMFDEL [Not coded or commented out] SMFEXIT [Not coded or commented out] SMFLOGN [Not coded or commented out] SMFREN [Not coded or commented out] SMFRETR [Not coded or commented out] SMFSTOR [Not coded or commented out] The FTP Server can provide audit data in the form of SMF records. SMF record type 119, the TCP/IP Statistics record, can be written with the following subtypes: 70 - Append 70 - Delete and Multiple Delete 72 - Invalid Logon Attempt 70 - Rename 70 - Get (Retrieve) and Multiple Get 70 - Put (Store and Store Unique) and Multiple Put SMF data produced by the FTP Server provides transaction information for both successful and unsuccessful FTP commands. This data may provide valuable information for security audit activities. Type 119 records use a more standard format and provide more information.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-FT-000030
- Vuln IDs
-
- V-223975
- V-98657
- Rule IDs
-
- SV-223975r877816_rule
- SV-107761
Checks: C-25648r516324_chk
From the ISPF Command Shell enter: omvs At the input line enter: cd /usr/sbin/ enter ls -alW If the following File permission and user Audit Bits are true, this is not a finding. /usr/sbin/ftpd 1740 fff /usr/sbin/ftpdns 1755 fff /usr/sbin/tftpd 0644 faf cd ls -alW If the following file permission and user Audit Bits are true, this is not a finding. /etc/ftp.data 0744 faf /etc/ftp.banner 0744 faf NOTES: Some of the files listed above are not used in every configuration. The absence of a file is not considered a finding. The /usr/sbin/ftpd and /usr/sbin/ftpdns objects are symbolic links to /usr/lpp/tcpip/sbin/ftpd and /usr/lpp/tcpip/sbin/ftpdns respectively. The permission and user audit bits on the targets of the symbolic links must have the required settings. The /etc/ftp.data file may not be the configuration file the server uses. It is necessary to check the SYSFTPD DD statement in the FTP started task JCL to determine the actual file. The TFTP Server does not perform any user identification or authentication, allowing any client to connect to the TFTP Server. Due to this lack of security, the TFTP Server will not be used. The TFTP Client is not secured from use. The permission bits for /usr/sbin/tftpd should be set to 644. The /etc/ftp.banner file may not be the banner file the server uses. It is necessary to check the BANNER statement in the FTP Data configuration file to determine the actual file. Also, the permission bit setting for this file must be set as indicated in the table above. A more restrictive set of permissions is not permitted. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25636r516325_fix
With the assistance of a systems programmer with UID(0) and/or SUPERUSER access, configure the UNIX permission bits and user audit bits on the HFS directories and files for the FTP Server to conform to the specifications in the table below: FTP Server HFS Object Security Settings File Permission Bits User Audit Bits /usr/sbin/ftpd 1740 fff /usr/sbin/ftpdns 1755 fff /usr/sbin/tftpd 0644 faf /etc/ftp.data 0744 faf /etc/ftp.banner 0744 faf The /usr/sbin/ftpd and /usr/sbin/ftpdns objects are symbolic links to /usr/lpp/tcpip/sbin/ftpd and /usr/lpp/tcpip/sbin/ftpdns respectively. The permission and user audit bits on the targets of the symbolic links must have the required settings. The TFTP Server does not perform any user identification or authentication, allowing any client to connect to the TFTP Server. Due to this lack of security, the TFTP Server will not be used. The TFTP Client is not secured from use. The /etc/ftp.data file may not be the configuration file the server uses. It is necessary to check the SYSFTPD DD statement in the FTP started task JCL to determine the actual file. The /etc/ftp.banner file may not be the banner file the server uses. It is necessary to check the BANNER statement in the FTP Data configuration file to determine the actual file. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing Some of the files listed above (e.g., /etc/ftp.data) are not used in every configuration. While the absence of a file is generally not a security issue, the existence of a file that has not been properly secured can often be an issue. Therefore, all files that do exist should have the specified permission and audit bit settings. The following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 1740 /usr/lpp/tcpip/sbin/ftpd chaudit rwx=f /usr/lpp/tcpip/sbin/ftpd chmod 1755 /usr/lpp/tcpip/sbin/ftpdns chaudit rwx=f /usr/lpp/tcpip/sbin/ftpdns chmod 0744 /etc/ftp.data chaudit w=sf,rx+f /etc/ftp.data chmod 0744 /etc/ftp.banner chaudit w=sf,rx+f /etc/ftp.banner
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-FT-000040
- Vuln IDs
-
- V-223976
- V-98659
- Rule IDs
-
- SV-223976r877817_rule
- SV-107763
Checks: C-25649r516327_chk
If WRITE and ALLOCATE access to the data set containing the FTP Data configuration file is restricted to systems programming personnel this is not a finding. Note: READ access to all authenticated users is permitted. If WRITE and ALLOCATE access to the data set containing the FTP Data configuration file is logged this is not a finding. If WRITE and ALLOCATE access to the data set containing the FTP banner file is restricted to systems programming personnel this is not a finding. Note: READ access to the data set containing the FTP banner file is permitted to all authenticated users. Notes: The MVS data sets mentioned above are not used in every configuration. Absence of a data set will not be considered a finding. The data set containing the FTP Data configuration file is determined by checking the SYSFTPD DD statement in the FTP started task JCL. The data set containing the FTP banner file is determined by checking the BANNER statement in the FTP Data configuration file.
Fix: F-25637r516328_fix
Review the data set access authorizations defined to the ACP for the FTP.DATA and FTP.BANNER files. Configure these data sets to be protected as follows:
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000202
- Version
- TSS0-FT-000050
- Vuln IDs
-
- V-223977
- V-98661
- Rule IDs
-
- SV-223977r877818_rule
- SV-107765
Checks: C-25650r516330_chk
Ask the System administrator fora list(s) of the locations for all FTP Control cards within a given application/AIS, ensuring no FTP control cards are within in-stream JCL, JCL libraries or any open access data sets. If access to PDS files where FTP Control cards are stored are not restricted to appropriate personnel this is a finding.
Fix: F-25638r516331_fix
Make sure that the FTP control Cards for each FTP are stored in a secure PDS and that they are not placed in the JCL libraries or in the in-stream JCL for each FTP.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000382
- Version
- TSS0-FT-000060
- Vuln IDs
-
- V-223978
- V-98663
- Rule IDs
-
- SV-223978r877819_rule
- SV-107767
Checks: C-25651r868964_chk
Refer to the Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL. Refer to the file(s) allocated by the STEPLIB DD statement in the FTP started task JCL. Refer to the libraries specified in the system Linklist and LPA. If any FTP Server exits are in use, identify them and validate that they were reviewed for integrity and approved by the site AO. Refer to the following items are in effect for FTP Server user exits: The FTCHKCMD, FTCHKIP, FTCHKJES, FTCHKPWD, FTPSMFEX and FTPOSTPR modules are not located in the FTP daemon's STEPLIB, Linklist, or LPA. NOTE: The ISPF ISRFIND utility can be used to search the system Linklist and LPA for specific modules. If both of the above are true, this is not a finding. If any FTP Server user exits are implemented and the site has not had the site systems programmer verify the exit was securely written and installed, this is a finding.
Fix: F-25639r516334_fix
Review the configuration statements in the FTP.DATA file. Review the FTP daemon STEPLIB, system Linklist, and Link Pack Area libraries. If FTP Server exits are enabled or present, and have not been approved by the site ISSM and not securely written and implemented by the site systems programmer, they should not be installed. Verify that none of the following exits are installed unless they have met the requirements listed above: FTCHKCMD FTCHKIP FTCHKJES FTCHKPWD FTPOSTPR FTPSMFEX
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-FT-000070
- Vuln IDs
-
- V-223979
- V-98665
- Rule IDs
-
- SV-223979r877820_rule
- SV-107769
Checks: C-25652r868966_chk
From the ISPD Command Shell enter: TSS LIST(FTPD) SEGMENT(OMVS) NOTE: The JCL member is typically named FTPD If the FTPD ACID has the STC facility, this is not a finding. If the FTPD ACID has the following z/OS UNIX attributes, this is not a finding. UID(0), HOME directory '/', shell program /bin/sh.
Fix: F-25640r868967_fix
Configure FTP daemon with the following items: -The FTP daemon is started from a JCL procedure library defined to JES2. NOTE: The JCL member is typically named FTPD. -The FTP daemon ACID is FTPD. -The FTPD ACID has the STC facility. -The FTPD ACID has the following z/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh. For example: TSS CREATE(FTPD) TYPE(USER) NAME(FTPD) DEPT(existing-dept) FACILITY(STC) PASSWORD(password,0) TSS ADD(FTPD) DFLTGRP(STCTCPX) GROUP(STCTCPX) TSS ADD(FTPD) SOURCE(INTRDR) TSS ADD(FTPD) UID(0) HOME(/) OMVSPGM(/bin/sh) TSS ADD(FTPD) MASTFAC(TCP) TSS ADD(STC) PROCNAME(FTPD) ACID(FTPD) TSS PERMIT(FTPD) IBMFAC(BPX.DAEMON) ACCESS(READ) TSS PERMIT(FTPD) IBMFAC(BPX.POE) ACCESS(READ) TSS PERMIT(FTPD) SERVAUTH(EZB.STACKACCESS.)ACCESS(READ)
- RMF Control
- SC-10
- Severity
- Medium
- CCI
- CCI-001133
- Version
- TSS0-FT-000080
- Vuln IDs
-
- V-223980
- V-98667
- Rule IDs
-
- SV-223980r877821_rule
- SV-107771
Checks: C-25653r516339_chk
Refer to the file specified on the SYSFTPD DD statement in the FTP started task JCL. If the INACTIVE statement is coded with a value greater than "600", this is a finding. If the INACTIVE statement is coded with a value of "0", this is a finding. If there is no INACTIVE statement coded or the INACTIVE statement is commented out, this is a finding.
Fix: F-25641r516340_fix
Code the FTPD configuration file to include the INACTIVE statement with a value between "1" and "600".
- RMF Control
- SC-10
- Severity
- Medium
- CCI
- CCI-001133
- Version
- TSS0-FT-000090
- Vuln IDs
-
- V-223981
- V-98669
- Rule IDs
-
- SV-223981r877822_rule
- SV-107773
Checks: C-25654r868969_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. If all the items below are true, this is not a finding. If any of the items below are untrue, this is a finding. The following items are in effect for the FTP daemon's started task JCL: -The SYSTCPD and SYSFTPD DD statements specify the TCP/IP Data and FTP Data configuration files respectively. -The ANONYMOUS keyword is not coded on the PARM parameter on the EXEC statement. -The ANONYMOUS=logonid combination is not coded on the PARM parameter on the EXEC statement. -The INACTIVE keyword is not coded on the PARM parameter on the EXEC statement. The AUTOLOG statement block can be configured to have TCP/IP start the FTP Server. The FTP entry (e.g., FTPD) can include the PARMSTRING parameter to pass parameters to the FTP procedure when started. NOTE: Parameters passed on the PARMSTRING parameter override parameters specified in the FTP procedure. If an FTP entry is configured in the AUTOLOG statement block in the TCP/IP Profile configuration file, ensure the following items are in effect: -The ANONYMOUS keyword is not coded on the PARMSTRING parameter. -The ANONYMOUS=logonid combination is not coded on the PARMSTRING parameter. -The INACTIVE keyword is not coded on PARMSTRING parameter.
Fix: F-25642r868970_fix
Review the FTP daemon's started task JCL. Ensure that the ANONYMOUS and INACTIVE startup parameters are not specified and configuration file names are specified on the appropriate DD statements. The FTP daemon program can accept parameters in the JCL procedure that is used to start the daemon. The ANONYMOUS and ANONYMOUS= keywords are designed to allow anonymous FTP connections. The INACTIVE keyword is designed to set the timeout value for inactive connections. Control of these options is recommended through the configuration file statements rather than the startup parameters. The systems programmer responsible for supporting ICS will ensure that the startup parameters for the FTP daemon does not include the ANONYMOUS, ANONYMOUS=, or INACTIVE keywords. During initialization the FTP daemon searches multiple locations for the TCPIP.DATA and FTP.DATA files according to fixed sequences. In the daemon's started task JCL, Data Definition (DD) statements will be used to specify the locations of the files. The SYSTCPD DD statement identifies the TCPIP.DATA file and the SYSFTPD DD statement identifies the FTP.DATA file. The systems programmer responsible for supporting ICS will ensure that the FTP daemon's started task JCL specifies the SYSTCPD and SYSFTPD DD statements for configuration files.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-001384
- Version
- TSS0-FT-000100
- Vuln IDs
-
- V-223982
- V-98671
- Rule IDs
-
- SV-223982r877823_rule
- SV-107775
Checks: C-25655r516345_chk
Refer to the file specified on the SYSFTPD DD statement in the FTP started task JCL. If the BANNER statement is not coded or is commented out, this is a finding.
Fix: F-25643r516346_fix
Code the FTPD configuration file to include the BANNER statement that points to the Standard Mandatory DoD Notice and Consent Banner statement.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-001384
- Version
- TSS0-FT-000110
- Vuln IDs
-
- V-223983
- V-98673
- Rule IDs
-
- SV-223983r877824_rule
- SV-107777
Checks: C-25656r516348_chk
Refer to the FTP.DATA file specified on the SYSFTPD DD statement in the FTP started task JCL. The SYSFTPD DD statement is optional. The search order for FTP.DATA is: /etc/ftp.data SYSFTPD DD statement jobname.FTP.DATA SYS1.TCPPARMS(FTPDATA) tcpip.FTP.DATA Examine the BANNER statement. If the BANNER statement in the FTP Data configuration file specifies an HFS file or data set that contains a logon banner, this is not a finding. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
Fix: F-25644r516349_fix
Ensure the BANNER statement in the FTP Data configuration file specifies an HFS file or z/OS data set that contains a logon banner. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- TSS0-FT-000120
- Vuln IDs
-
- V-223984
- V-98675
- Rule IDs
-
- SV-223984r877825_rule
- SV-107779
Checks: C-25657r516351_chk
From the ISPF Command Shell enter: TSS WHOOWNS PROGRAM(*) If the Program resources TFTPD and EZATD are owned appropriately in the PROGRAM resource class, this is not a finding. Enter TSS WHOHAS(TFTPD) TSS WHOHAS(EZATD) If no access to the program resources TFTPD and EZATD is permitted, this is not a finding.
Fix: F-25645r516352_fix
Evaluate the impact of implementing the following change. Develop a plan of action and implement the change as required. Ensure that the EZATD program and its alias TFTPD are defined to CA-TSS and no access to the program resources TFTPD and EZATD is permitted. The following commands provide a sample of how to protect the TFTP server program by assigning ownership and no permissions: TSS ADD(ADMIN) PROGRAM(TFTPD,EZATD)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000010
- Vuln IDs
-
- V-223985
- V-98677
- Rule IDs
-
- SV-223985r877826_rule
- SV-107781
Checks: C-25658r516354_chk
From the ISPF Command Shell enter: WHOOWNS OPERCMDS(JES2) NOTE: JES2 is typically the name of the JES2 subsystem. Refer to the SUBSYS report and locate the entry with the description of PRIMARY JOB ENTRY SUBSYSTEM. The SUBSYSTEM NAME of this entry is the name of the JES2 subsystem. If the JES2. resource is not owned, or is owned inappropriately, in the OPERCMDS class, this is a finding.
Fix: F-25646r516355_fix
The JES2. resource must be owned in the OPERCMDS class. NOTE: JES2 is typically the name of the JES2 subsystem. Refer to the SUBSYS report and locate the entry with the description of PRIMARY JOB ENTRY SUBSYSTEM. The SUBSYSTEM NAME of this entry is the name of the JES2 subsystem. Extended MCS support allows the installation to control the use of JES2 system commands through the ACP. These commands are subject to various types of potential abuse. For this reason, it is necessary to place restrictions on the JES2 system commands that can be entered by particular operators. To control access to JES2 system commands, the following recommendations will be applied when implementing security: For Example: The following command may be used to establish default protection for JES2 system commands defined to the OPERCMDS resource class: TSS ADDTO(deptacid) OPERCMDS(JES2.)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000020
- Vuln IDs
-
- V-223986
- V-98679
- Rule IDs
-
- SV-223986r877827_rule
- SV-107783
Checks: C-25659r516357_chk
Refer to SYS1.PARMLIB (JES2PARM) For each node entry If all JES2 defined NJE nodes and RJE workstations have a profile defined in the IBMFAC resource class, this is not a finding. Notes: Nodename is the NAME parameter value specified on the NODE statement. Review the JES2 parameters for NJE node definitions by searching for "NODE(" in the report. Workstation is RMTnnnn, where nnnn is the number on the RMT statement. Review the JES2 parameters for RJE workstation definitions by searching for "RMT(" in the report. NJE. and RJE. definitions will force logonid and password protection of all NJE and RJE connections respectively. This method is acceptable in lieu of using discrete profiles. If any JES2 defined NJE node or RJE workstation is not owned in the IBMFAC class, this is a finding.
Fix: F-25647r516358_fix
Ensure associated USERIDs exist for all RJE/NJE sources and review the authorizations for these remote facilities. Develop a plan of action and implement the changes as required by the OS/390 STIG.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000030
- Vuln IDs
-
- V-223987
- V-98681
- Rule IDs
-
- SV-223987r877828_rule
- SV-107785
Checks: C-25660r516360_chk
Refer the JES2PARM member of SYS1.PARMLIB Review the following resources in the JESINPUT resource class: NOTE: If any of the following are not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be owned. INTRDR (internal reader for batch jobs) nodename (NJE node) OFFn.* (spool offload receiver) Rnnnn (RJE workstation) RDRnn (local card reader) STCINRDR (internal reader for started tasks) TSUINRDR (internal reader for TSO logons) Note 1: Nodename is the NAME parameter in the NODE statement. Review the NJE node definitions by searching for "NODE(" in the report. Note 2: OFFn, where n is the number of the offload receiver. Review the spool offload receiver definitions by searching for "OFF(" in the report. Note 3: Rnnnn, where nnnn is the number of the remote workstation. Review the RJE node definitions by searching for "RMT(" in the report. Note 4: RDRnn, where nn is the number of the reader. Review the reader definitions by searching for "RDR(" in the report. From the ISPF Command Shell enter: TSS WHOOWNS JESINPUT(*) If all of the resources above are owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding. If any of the above resources are not owned, or are owned inappropriately, in the JESINPUT resource class, this is a finding.
Fix: F-25648r516361_fix
Review the following resources in the JESINPUT resource class: INTRDR (internal reader for batch jobs) nodename (NJE node) OFFn.* (spool offload receiver) Rnnnn (RJE workstation) RDRnn (local card reader) STCINRDR (internal reader for started tasks) TSUINRDR (internal reader for TSO logons) Note: If any of the following are not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be defined. Note 1: Nodename is the NAME parameter in the NODE statement. Review the JES2 parameters for NJE node definitions by searching for "NODE(" in the report. Note 2: OFFn, where n is the number of the offload receiver. Review the JES2 parameters for spool offload receiver definitions by searching for "OFF(" in the report. Note 3: Rnnnn, where nnnn is the number of the remote workstation. Review the JES2 parameters for RJE node definitions by searching for "RMT(" in the report. Note 4: RDRnn, where nn is the number of the reader. Review the JES2 parameters for reader definitions by searching for "RDR(" in the report. Ensure all of the defined resources above are owned by generic and/or fully qualified entries in the JESINPUT resource class. For Example: The following commands may be used to establish default protection for resources defined to the JESINPUT resource class: TSS ADDTO(deptacid) JESINPUT(OFFn.) Grant read access to authorized users for each of the resources defined to the JESINPUT resource class. The following is an example of granting operators with a profile ACID of jesopracid permission to restore jobs into any SPOOL off load processor after obtaining permission from the ISSO: TSS PERMIT(jesopracid) JESINPUT(OFF*.) ACCESS(READ) ACTION(AUDIT) The resource definition should be generic if all of the resources of the same type have identical access controls (e.g., if all off load receivers are equivalent).
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000040
- Vuln IDs
-
- V-223988
- V-98683
- Rule IDs
-
- SV-223988r877829_rule
- SV-107787
Checks: C-25661r516363_chk
From the ISPF Command Shell enter: TSS WHOOWNS JESINPUT(*) For each resource owned If all of the TSS resources and/or generic equivalent identified above are defined with access restricted to the appropriate personnel, this is not a finding. If any of the TSS resources and/or generic equivalent identified above are not defined with access restricted to the appropriate personnel, this is a finding. From the ISPF Command Shell enter: TSS LIST RDT(*) If the JESINPT RESOURCE does not have DEFPROT as an attribute, this is a finding.
Fix: F-25649r516364_fix
Configure access authorization for resources defined to the JESINPUT resource class to be restricted to the appropriate personnel. Grant read access to authorized users for each of the following input sources: INTRDR nodename OFFn.* OFFn.JR OFFn.SR Rnnnn.RDm RDRnn STCINRDR TSUINRDR and/or TSOINRDR The resource definition will be generic if all of the resources of the same type have identical access controls (e.g., if all off load receivers are equivalent). The default access will be NONE except for sources that are permitted to submit jobs for all users. Those resources may be defined as either NONE or READ.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000050
- Vuln IDs
-
- V-223989
- V-98685
- Rule IDs
-
- SV-223989r877830_rule
- SV-107789
Checks: C-25662r516366_chk
Refer the JES2PARM member of SYS1.PARMLIB Review the WRITER resource in the JESINPUT resource class: NOTE: If the WRITER resource is not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be owned. From the ISPF Command Shell enter: TSS WHOOWNS JESINPUT(WRITER) If the WRITER resource is owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding.
Fix: F-25650r516367_fix
Ensure the following items are in effect: -The JES2. resource is owned in the WRITER resource class. For Example: The following command may be used to establish default protection for resources defined to the WRITER resource class: TSS ADDTO(deptacid) WRITER(JES2.) -The ownership of all WRITER resources is appropriate. Grant read access to authorized users for each of the following WRITER resource class output destinations: JES2.LOCAL.devicename JES2.LOCAL.OFF*.JT JES2.LOCAL.OFF*.ST JES2.LOCAL.PRT* JES2.LOCAL.PUN* JES2.NJE.nodename JES2.RJE.devicename The following is an example of granting operators with a profile ACID of jesopracid permission to off load SYSOUT data sets into any SPOOL off load processor after obtaining permission from the ISSO: TSS PERMIT(jesopracid) WRITER(JES2.LOCAL.OFF*.ST) - ACCESS(READ) ACTION(AUDIT) The resource definition should be generic if all of the resources of the same type have identical access controls (e.g., if all off load transmitters are equivalent).
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000060
- Vuln IDs
-
- V-223990
- V-98687
- Rule IDs
-
- SV-223990r877831_rule
- SV-107791
Checks: C-25663r516369_chk
If the Classification of the system is unclassified, this is not applicable. From the ISPF Command Shell enter: TSS WHOHAS WRITER(JES2.) If the TSS WRITER resource or generic equivalent identified above is defined with access restricted to the appropriate personnel, this is not a finding. If the TSS WRITER resource or generic equivalent identified above is not defined with access restricted to the appropriate personnel, this is a finding. From the ISPF Command Shell enter: TSS LIST RDT(*) If the JESINPUT RESOURCE does not have DEFPROT as an attribute, this is a finding.
Fix: F-25651r868975_fix
Configure access authorization for resources defined to the WRITER resource class to be restricted to the operators and system programmers on a classified system only. Define resources in the ACP's respective WRITER class for each of the following output destinations: JES2.LOCAL.devicename JES2.LOCAL.OFFn.* JES2.LOCAL.OFFn.JT JES2.LOCAL.OFFn.ST JES2.LOCAL.PRTn JES2.LOCAL.PUNn JES2.NJE.nodename JES2.RJE.devicename The resource definition will be generic if all of the resources of the same type have identical access controls (e.g., if all off load transmitters are equivalent). If all users are permitted to route output to a specific destination, the resource controlling it may be defined with a default access of either NONE or READ. Otherwise it will be defined with a default access of NONE.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000070
- Vuln IDs
-
- V-223991
- V-98689
- Rule IDs
-
- SV-223991r877832_rule
- SV-107793
Checks: C-25664r516372_chk
Refer the JES2PARM member of SYS1.PARMLIB. Review the JESSPOOL resource in the JESINPUT resource class: NOTE: If the JESSPOOL resource is not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be owned. From the ISPF Command Shell enter: TSS WHOOWNS JESINPUT(JESSPOOL) If the JESSPOOL resource is owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding.
Fix: F-25652r516373_fix
Review the JES2 parameters to determine the localnodeid by searching for OWNNODE in the NJEDEF statement, and then searching for NODE(nnnn) (where nnnn is the value specified by OWNNODE). The NAME parameter value specified on this NODE statement is the localnodeid. The following command may be used to establish default protection for resources defined to the JESSPOOL resource class: TSS ADDTO(deptacid) JESSPOOL(localnodeid.) Due to the protection established with the previous command, the following command should be issued to ensure users are able to access their own spool data: TSS PERMIT(ALL) JESSPOOL(localnodeid.%) ACCESS(ALL)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000080
- Vuln IDs
-
- V-223992
- V-98691
- Rule IDs
-
- SV-223992r877833_rule
- SV-107795
Checks: C-25665r516375_chk
From the ISPF Command Shell enter: TSS WHOHAS OPERCMDS(JES2.) NOTE: JES2 is typically the name of the JES2 subsystem. Refer to the SUBSYS report and locate the entry with the description of PRIMARY JOB ENTRY SUBSYSTEM. The SUBSYSTEM NAME of this entry is the name of the JES2 subsystem. If access authorization to the JES2.UPDATE.JESNEWS resource in the OPERCMDS class restricts CONTROL access to the appropriate personnel (i.e., users responsible for maintaining the JES News data set) and all access is logged, this is not a finding.
Fix: F-25653r868977_fix
Configure access authorization to the JES2.UPDATE.JESNEWS resource in the OPERCMDS class to restrict CONTROL access to the appropriate personnel (i.e., users responsible for maintaining the JES News data set) and ensure all access is logged. NOTE: JES2 is typically the name of the JES2 subsystem. Refer to the SUBSYS report and locate the entry with the description of PRIMARY JOB ENTRY SUBSYSTEM. The SUBSYSTEM NAME of this entry is the name of the JES2 subsystem. For example: The following command example may be used to allow all valid TOP SECRET users read access to the JES News data set: TSS PERMIT(ALL) JESSPOOL(localnodeid.jesid.$JESNEWS.*.*.JESNEWS) - ACCESS(READ) The following is a sample command to allow production control personnel with a profile ACID of prodacid to update the JES News data set: TSS PERMIT(prodacid) OPERCMDS(JES2.UPDATE.JESNEWS) - ACCESS(CONTROL) ACTION(AUDIT)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000090
- Vuln IDs
-
- V-223993
- V-98693
- Rule IDs
-
- SV-223993r877834_rule
- SV-107797
Checks: C-25666r516378_chk
From the ISPF Command Shell enter: TSS WHOOWNS JESSPOOL(*) If JESSPOOL localnodeid resource is not defined, this is a finding. Enter TSS WHOHAS JESSPOOL(localnodeid.) Review the following resources defined to the JESSPOOL resource class: localnodeid.JES2.$TRCLOG.taskid.*.JESTRACE localnodeid.+MASTER+.SYSLOG.jobid.*.SYSLOG or localnodeid.+BYPASS+.SYSLOG.jobid.-.SYSLOG NOTE: These resource profiles may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example: localnodeid.JES2.*.*.*.JESTRACE localnodeid.+MASTER+.*.*.*.SYSLOG or localnodeid.+BYPASS+.*.*.*.SYSLOG NOTE: Review the JES2 parameters to determine the localnodeid by searching for OWNNODE in the NJEDEF statement, and then searching for NODE(nnnn) (where nnnn is the value specified by OWNNODE). The NAME parameter value specified on this NODE statement is the localnodeid. Another method is to issue the JES2 command $D NODE,NAME,OWNNODE=YES to obtain the NAME of the OWNNODE. If the access authorization for the resources mentioned above is restricted to the following, this is not a finding. -ACID(s) associated with external writer(s) can have complete access. NOTE: An external writer is an STC that removes data sets from the JES spool. In this case, it is responsible for archiving the JESTRACE and SYSLOG data sets. The STC default name is XWTR and the external writer program is called IASXWR00. -Systems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access. -Application Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource.
Fix: F-25654r516379_fix
Configure the access authorization for resources defined to the JESTRACE and SYSLOG resources in the JESSPOOL resource class to be restricted to the appropriate personnel. Review the following resources defined to the JESSPOOL resource class: localnodeid.JES2.$TRCLOG.taskid.*.JESTRACE localnodeid.+MASTER+.SYSLOG.jobid.*.SYSLOG or localnodeid.+BYPASS+.SYSLOG.jobid.*.SYSLOG NOTE: These resource profiles may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example: localnodeid.JES2.$TRCLOG. localnodeid.+MASTER+.SYSLOG. or localnodeid.+BYPASS+.SYSLOG. NOTE: Review the JES2 parameters to determine the localnodeid by searching for OWNNODE in the NJEDEF statement, and then searching for NODE(nnnn) (where nnnn is the value specified by OWNNODE). The NAME parameter value specified on this NODE statement is the localnodeid. Another method is to issue the JES2 command $D NODE,NAME,OWNNODE=YES to obtain the NAME of the OWNNODE. Ensure that access authorization for the resources mentioned above is restricted to the following: -ACID(s) associated with external writer(s) can have complete access. NOTE: An external writer is a STC that removes data sets from the JES spool. In this case, it is responsible for archiving the JESTRACE and SYSLOG data sets. The STC default name is XWTR and the external writer program is called IASXWR00. -Systems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access. -Application Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource. For Example: TSS ADD(dept-acid) JESSPOOL(localnodeid) TSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.JES2.$TRCLOG.) ACCESS(ALL) TSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.JES2.$TRCLOG.) ACCESS(ALL) TSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(ALL) TSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(ALL) TSS PERMIT(<appdsmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(READ) TSS PERMIT(<appssmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(READ) or TSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(ALL) TSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(ALL) TSS PERMIT(<appdsmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(READ) TSS PERMIT(<appssmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000100
- Vuln IDs
-
- V-223994
- V-98695
- Rule IDs
-
- SV-223994r877835_rule
- SV-107799
Checks: C-25667r516381_chk
From the ISPF Command Shell enter: TSS WHOHAS JESSPOOL(localnodeid.) If the following guidance is true, this is not a finding. Review the JESSPOOL report for resource permissions with the following naming convention. These permissions may be fully qualified, be specified as generic, or be specified with masking as indicated below: localnodeid.useracid.jobname.jobid.dsnumber.name localnodeid - The name of the node on which the SYSIN or SYSOUT data set currently resides. useracid - The user ACID associated with the job. This is the user ACID TSS uses for validation purposes when the job runs. jobname - The name that appears in the name field of the JOB statement. jobid - The job number JES2 assigned to the job. dsnumber - The unique data set number JES2 assigned to the spool data set. A D is the first character of this qualifier. name - The name of the data set specified in the DSN= parameter of the DD statement. If the JCL did not specify DSN= on the DD statement that creates the spool data set, JES2 uses a question mark (?). All users must have access to their own JESSPOOL resources. Permission can be granted by resource permission JESSPOOL(localnodeid.%.) ACCESS(ALL). This permission can be given to profiles, individual user, and/or the ALL record. Access to this resource does not require logging. Ensure the following items are in effect: The localnodeid. resource will be restricted to only system programmers, operators, and automated operations personnel, with access of ALL. All access will be logged. (localnodeid. resource includes all generic and/or masked permissions, example: localnodeid.**, localnodeid.*, etc.) The JESSPOOL localnodeid.userid.jobname.jobid.dsnumber.name, whether generic and/or masked, can be made available to users, when approved by the ISSO. Access will be identified at the minimum access for the user to accomplish the users function. All access will be logged. An example is team members within a team, providing the capability to view, help, and/or debug other team member jobs/processes. CSSMTP will be restricted to localnodeid.userid.jobname.jobid.dsnumber.name, whether generic and/or masked when approved by the ISSO. All access will be logged. Spooling products users (CA-SPOOL, CA View, etc.) will be restricted to localnodeid.userid.jobname.jobid.dsnumber.name, whether generic and/or masked when approved by the ISSO. Logging of access is not required.
Fix: F-25655r868979_fix
Configure the following items to be in effect for JESSPOOL resources. The JESSPOOL may have more restrictive security at the direction of the ISSO. The JESSPOOL resources may be fully qualified, be specified as generic, or be specified with masking as indicated below: localnodeid.userid.jobname.jobid.dsnumber.name localnodeid - The name of the node on which the SYSIN or SYSOUT data set currently resides. userid - The userid associated with the job. This is the userid used for validation purposes when the job runs. jobname - The name that appears in the name field of the JOB statement. jobid - The job number JES2 assigned to the job. dsnumber - The unique data set number JES2 assigned to the spool data set. A D is the first character of this qualifier. name - The name of the data set specified in the DSN= parameter of the DD statement. If the JCL did not specify DSN= on the DD statement that creates the spool data set, JES2 uses a question mark (?). All users must have access to their own JESSPOOL resources. Permission can be granted by resource permission JESSPOOL(localnodeid.%.) ACCESS(ALL). This permission can be given to profiles, individual user, and/or the ALL record. Access to this resource does not require logging. Example: TSS ADDTO(deptacid) JESSPOOL(localnode.) TSS PERMIT(ALL) JESSPOOL(localnode.%.) ACCESS(ALL) The localnodeid. resource will be restricted to only system programmers, operators, and automated operations personnel, with access of ALL. All access will be logged. (localnodeid. resource includes all generic and/or masked permissions, example: localnodeid.**, localnodeid.*, etc.) Example: TSS PERMIT(syspsmpl) JESSPOOL(localnodeid.) ACCESS(ALL) ACTION(AUDIT) The JESSPOOL localnodeid.userid.jobname.jobid.dsnumber.name, whether generic and/or masked, can be made available to users, when approved by the ISSO. Access will be identified at the minimum access for the user to accomplish the users function. All access will be logged. An example is team members within a team, providing the capability to view, help, and/or debug other team member jobs/processes. If frequent situations occur where users working on a common project require selective access to each other's jobs, then the installation may delegate to the individual users the authority to grant access, but only with the approval of the ISSO. Example: TSS PERMIT(Project1-profile) JESSPOOL(localnodeid.UMO) ACCESS(ALL) If IBM's SDSF product is installed on the system, resources defined to the JESSPOOL resource class control functions related to jobs, output groups, and SYSIN/SYSOUT data sets on various SDSF panels. CSSMTP will not be granted to the JESSPOOL resource of the high level "node." or "localnodeid.". CSSMTP can have access to the specific approved JESSPOOL resources, minimally qualified to the "node.userid." and all access will be logged. This will ensure system records who (userid) sent traffic to CSSMTP, when and what job/process. Spooling products users (CA-SPOOL, CA View, etc.) will be restricted to localnodeid.userid.jobname.jobid.dsnumber.name, whether generic and/or masked when approved by the ISSO. Logging of access is not required. The ISSO will review JESSPOOL resource rules. If a rule has been determined not to have been used within the last two years, the rule will be removed.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000110
- Vuln IDs
-
- V-223995
- V-98697
- Rule IDs
-
- SV-223995r877836_rule
- SV-107801
Checks: C-25668r516384_chk
From the ISPF Command Shell enter: TSS WHOHAS OPERCMDS(JES2.) If the JES2.** resource is defined to the OPERCMDS class with an access of NONE and all access is logged, this is not a finding. If access to JES2 system commands defined in the IBM z/OS JES2 commands is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users), this is not a finding. NOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands.
Fix: F-25656r516385_fix
Extended MCS support allows the installation to control the use of JES2 system commands through the ESM. These commands are subject to various types of potential abuse. For this reason, it is necessary to place restrictions on the JES2 system commands that can be entered by particular operators. Some commands are particularly dangerous and should only be used when less drastic options have been exhausted. Misuse of these commands can create a situation in which the only recovery is an IPL. To control access to JES2 system commands, apply the following: implementing security: Define the JES2.** resource in the OPERCMDS class with an access of NONE and all access is logged. Define the JES2 system commands as specified in the IBM z/OS JES2 Commands to be restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users), as determined in the documented site Security Plan. Define the JES2 system commands with proper logging as determined in the documented site Security Plan. Note: Display commands and others as deemed by the site IAW site security plan may be allowed for all users with no logging. Build a command file based on the referenced JES2 Command Table. A sample of the commands in the command file is provided here: RDEF OPERCMDS JES2.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('REQUIRED BY SRR PDI ZJES0052') RDEF OPERCMDS JES2.<command>.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('REQUIRED BY SRR PDI ZJES0052') PE JES2.<command>.** CL(OPERCMDS) ID(<syspsmpl>) ACC(U) SETR RACL(OPERCMDS) REF
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-JS-000120
- Vuln IDs
-
- V-223996
- V-98699
- Rule IDs
-
- SV-223996r877837_rule
- SV-107803
Checks: C-25669r516387_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(XA) If no XA ACID entries exist in the above reports, this is not applicable. For each ACID identified in the XA ACID entries, if the following items are true regarding ACID permissions, this is not a finding. -ACID permission (XA ACID) is logged (ACTION = AUDIT), only for Privileged USERIDS (MASTER, SCA, DCA, VCA, ZCA) if they are XAUTH; at the discretion of the ISSM/ISSO scheduling tasks may be exempted from logging. -Access authorization is restricted to scheduling tools, started tasks or other system applications required for running production jobs. -Other users may have minimal access required for running production jobs with documentation properly approved and filed with the site security official (ISSM or equivalent).
Fix: F-25657r516388_fix
For each ACID identified in the XA ACID entries, ensure the following items are in effect regarding ACID permissions: -ACID permission (XA ACID) is logged (ACTION = AUDIT), at the discretion of the ISSM/ISSO scheduling tasks may be exempted from logging. -ACID permission (XA ACID) is logged (ACTION = AUDIT), for Privileged users (MSCA, SCA, DCA, VCA, ZCA). -Access authorization is restricted to scheduling tools, started tasks, or other system applications required for running production jobs. Other users may have minimal access required for running production jobs with documentation properly approved and filed with the site security official (ISSM or equivalent). Consider the following recommendations when implementing security for Cross-Authorized ACIDs: Keep ACID cross authorization of ACIDs outside of those granted to the scheduling software to a minimum number of individuals. The simplest configuration is to have no ACID Cross Authorization except for the appropriate Scheduling task/software for production scheduling purposes as documented. Temporary Cross Authorization of the production batch ACID to the scheduling tasks may be allowed for a period for testing by the appropriate specific production Support Team members. Authorization, eligibility, and test period is determined by site policy. Access authorization is restricted to the minimum number of personnel required for running production jobs. However, ACID Cross Authorization usage must not become the default for all jobs submitted by individual userids (i.e., system programmer will use their assigned individual userids for software installation, duties, whereas a Cross-Authorized ACID would normally be utilized for scheduled batch production only and as such must normally be limited to the scheduling task such as CONTROLM) and not granted as a normal daily basis to individual users. Grant access to the user ACID for each cross-authorized ACID required: For Example: TSS PERMIT(ACID) ACID(Cross-Authorized ACID) ACTION(AUDIT) For production ACIDs being used by CONTROLM: TSS PER(CONTROLM)ACID(production user ACID)
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- TSS0-OS-000010
- Vuln IDs
-
- V-223997
- V-98701
- Rule IDs
-
- SV-223997r877838_rule
- SV-107805
Checks: C-25670r516390_chk
From an ISPF Command line enter: TSO ISRDDN APF An APF List results. On the Command line enter: DUPlicates (Make sure there is appropriate access. If there is not, you may receive insufficient access errors.) If any of the list of Sensitive Utilities exist in the duplicate APF modules returned, this is a finding. The following list contains Sensitive Utilities that will be checked. AHLGTF AMASPZAP AMAZAP AMDIOCP AMZIOCP BLSROPTR CSQJU003 CSQJU004 CSQUCVX CSQUTIL CSQ1LOGP DEBE DITTO FDRZAPOP GIMSMP HHLGTF ICKDSF ICPIOCP IDCSC01 IEHINITT IFASMFDP IGWSPZAP IHLGTF IMASPZAP IND$FILE IOPIOCP IXPIOCP IYPIOCP IZPIOCP WHOIS L052INIT TMSCOPY TMSFORMT TMSLBLPR TMSMULV TMSREMOV TMSTPNIT TMSUDSNB
Fix: F-25658r516391_fix
Review and ensure that duplicate sensitive utility(ies) and/or program(s) do not exist in APF-authorized libraries. Identify all versions of the sensitive utilities contained in APF-authorized libraries listed in the above check. In cases where duplicates exist, ensure no exposure has been created and written justification has been filed with the ISSO. Comparisons among all the APF libraries will be done to ensure that an exposure is not created by the existence of identically named modules. Address any sensitive utility concerns so that the function can be restricted as required.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- TSS0-OS-000020
- Vuln IDs
-
- V-223998
- V-98703
- Rule IDs
-
- SV-223998r877839_rule
- SV-107807
Checks: C-25671r868981_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. If all of the required SMF record types identified below are collected, this is not a finding. IBM SMF Records to be collected at a minimum: 0 (00) - IPL 6 (06) - External Writer/ JES Output Writer/ Print Services Facility (PSF) 7 (07) - [SMF] Data Lost 14 (0E) - INPUT or RDBACK Data Set Activity 15 (0F) - OUTPUT, UPDAT, INOUT, or OUTIN Data Set Activity 17 (11) - Scratch Data Set Status 18 (12) - Rename Non-VSAM Data Set Status 24 (18) - JES2 Spool Offload 25 (19) - JES3 Device Allocation 26 (1A) - JES Job Purge 30 (1E) - Common Address Space Work 32 (20) - TSO/E User Work Accounting 41 (29) - DIV Objects and VLF Statistics 42 (2A) - DFSMS statistics and configuration 43 (2B) - JES Start 45 (2D) - JES Withdrawal/Stop 47 (2F) - JES SIGNON/Start Line (BSC)/LOGON 48 (30) - JES SIGNOFF/Stop Line (BSC)/LOGOFF 49 (31) - JES Integrity 52 (34) - JES2 LOGON/Start Line (SNA) 53 (35) - JES2 LOGOFF/Stop Line (SNA) 54 (36) - JES2 Integrity (SNA) 55 (37) - JES2 Network SIGNON 56 (38) - JES2 Network Integrity 57 (39) - JES2 Network SYSOUT Transmission 58 (3A) - JES2 Network SIGNOFF 60 (3C) - VSAM Volume Data Set Updated 61 (3D) - Integrated Catalog Facility Define Activity 62 (3E) - VSAM Component or Cluster Opened 64 (40) - VSAM Component or Cluster Status 65 (41) - Integrated Catalog Facility Delete Activity 66 (42) - Integrated Catalog Facility Alter Activity 80 (50) - RACF/TOP SECRET Processing 81 (51) - RACF Initialization 82 (52) - ICSF Statistics 83 (53) - RACF Audit Record For Data Sets 90 (5A) - System Status 92 (5C) except subtypes 10, 11 - OpenMVS File System Activity 102 (66) - DATABASE 2 Performance 103 (67) - IBM HTTP Server 110 (6E) - CICS/ESA Statistics 118 (76) - TCP/IP Statistics 119 (77) - TCP/IP Statistics 199 (C7) - TSOMON 230 (E6) - ACF2 or as specified in ACFFDR (vendor-supplied default is 230) 231 (E7) - TSS logs security events under this record type
Fix: F-25659r868982_fix
Ensure that SMF recording options are consistent with those outlined below. IBM SMF Records to be collected at a minimum: 0 (00) - IPL 6 (06) - External Writer/ JES Output Writer/ Print Services Facility (PSF) 7 (07) - [SMF] Data Lost 14 (0E) - INPUT or RDBACK Data Set Activity 15 (0F) - OUTPUT, UPDAT, INOUT, or OUTIN Data Set Activity 17 (11) - Scratch Data Set Status 18 (12) - Rename Non-VSAM Data Set Status 24 (18) - JES2 Spool Offload 25 (19) - JES3 Device Allocation 26 (1A) - JES Job Purge 30 (1E) - Common Address Space Work 32 (20) - TSO/E User Work Accounting 41 (29) - DIV Objects and VLF Statistics 42 (2A) - DFSMS statistics and configuration 43 (2B) - JES Start 45 (2D) - JES Withdrawal/Stop 47 (2F) - JES SIGNON/Start Line (BSC)/LOGON 48 (30) - JES SIGNOFF/Stop Line (BSC)/LOGOFF 49 (31) - JES Integrity 52 (34) - JES2 LOGON/Start Line (SNA) 53 (35) - JES2 LOGOFF/Stop Line (SNA) 54 (36) - JES2 Integrity (SNA) 55 (37) - JES2 Network SIGNON 56 (38) - JES2 Network Integrity 57 (39) - JES2 Network SYSOUT Transmission 58 (3A) - JES2 Network SIGNOFF 60 (3C) - VSAM Volume Data Set Updated 61 (3D) - Integrated Catalog Facility Define Activity 62 (3E) - VSAM Component or Cluster Opened 64 (40) - VSAM Component or Cluster Status 65 (41) - Integrated Catalog Facility Delete Activity 66 (42) - Integrated Catalog Facility Alter Activity 80 (50) - RACF/TOP SECRET Processing 81 (51) - RACF Initialization 82 (52) - ICSF Statistics 83 (53) - RACF Audit Record For Data Sets 90 (5A) - System Status 92 (5C) except subtypes 10, 11 - OpenMVS File System Activity 102 (66) - DATABASE 2 Performance 103 (67) - IBM HTTP Server 110 (6E) - CICS/ESA Statistics 118 (76) - TCP/IP Statistics 119 (77) - TCP/IP Statistics 199 (C7) - TSOMON 230 (E6) - ACF2 or as specified in ACFFDR (vendor-supplied default is 230) 231 (E7) - TSS logs security events under this record type
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- TSS0-OS-000030
- Vuln IDs
-
- V-223999
- V-98705
- Rule IDs
-
- SV-223999r877840_rule
- SV-107809
Checks: C-25672r516396_chk
If the session manager in use initiates a session lock after a 15-minute period of inactivity for all connection types, this is not a finding.
Fix: F-25660r516397_fix
Configure the session manager in use to initiate a session lock after a 15-minute period of inactivity for all connection types.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-OS-000040
- Vuln IDs
-
- V-224000
- V-98707
- Rule IDs
-
- SV-224000r877841_rule
- SV-107811
Checks: C-25673r868984_chk
Review the FACILITY resource class for BPX.SMF. If the RACF rules are as follows, this is not a finding. BPX.SMF.119.94 - READ allowed for users running the ssh, sftp, or scp client commands. BPX.SMF.119.96 - READ allowed for users running the scp or sftp-server server commands. BPX.SMF.119.97 - READ allowed for users running the scp or sftp client commands. The following profile grants the permitted users the authority to write or test for any SMF record being recorded. Access should be permitted as follows: BPX.SMF - READ access only when documented and justified in Site Security Plan. Documentation should include a reason why a more specific profile is not acceptable.
Fix: F-25661r868985_fix
Configure Facility resource class for BPX.SMF as follows: BPX.SMF.119.94 - READ allowed for users running the ssh, sftp, or scp client commands. BPX.SMF.119.96 - READ allowed for users running the scp or sftp-server server commands. BPX.SMF.119.97 - READ allowed for users running the scp or sftp client commands. The following profile grants the permitted users the authority to write or test for any SMF record being recorded. Access should be permitted as follows: BPX.SMF - READ access only when documented and justified in Site Security Plan. Documentation should include a reason why a more specific profile is not acceptable.
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000131
- Version
- TSS0-OS-000050
- Vuln IDs
-
- V-224001
- V-98709
- Rule IDs
-
- SV-224001r877842_rule
- SV-107813
Checks: C-25674r516402_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJP,IEFUSO), INTERVAL(SMF,SYNC),NODETAIL) If the SMF collection options are specified as stated below with exception of those specified in the above NOTEs, this is not a finding. The settings for several parameters are critical to the collection process: ACTIVE Activates the collection of SMF data. MAXDORM(0500) Specifies the amount of real time that SMF allows data to remain in an SMF buffer before it is written to a recording data set. Value is site defined. SID Specifies the system ID to be recorded in all SMF records. SYS(DETAIL) Controls the level of detail recorded. SYS(INTERVAL) Ensures the periodic recording of data for long running jobs. SYS Specifies the types and sub types of SMF records that are to be collected. SYS(TYPE) indicates that the supplied list is inclusive (i.e., specifies the record types to be collected). Record types not listed are not collected. SYS(NOTYPE) indicates that the supplied list is exclusive (i.e., specifies those record types not to be collected). Record types listed are not collected. The site may use either form of this parameter to specify SMF record type collection. However, at a minimum, all record types are listed.
Fix: F-25662r516403_fix
Ensure that collection options for SMF Data are consistent with options specified below. Review all SMF recording specifications found in SMFPRMxx members. Ensure that SMF recording options used are consistent with those outlined below. The settings for several parameters are critical to the collection process: ACTIVE Activates the collection of SMF data. MAXDORM(mmss) Specifies the amount of real time that SMF allows data to remain in an SMF buffer before it is written to a recording data set. Use the MAXDORM parameter to minimize the amount of data lost because of system failure. This value is site determined and should be carefully configured. SID Specifies the system ID to be recorded in all SMF records. SYS(DETAIL) Controls the level of detail recorded. SYS(INTERVAL) Ensures the periodic recording of data for long running jobs. SYS Specifies the types and sub types of SMF records that are to be collected. SYS(TYPE) indicates that the supplied list is inclusive (i.e., specifies the record types to be collected). Record types not listed are not collected. SYS(NOTYPE) indicates that the supplied list is exclusive (i.e., specifies those record types not to be collected). Record types not listed are not collected. The site may use either form of this parameter to specify SMF record type collection. However, at a minimum all record types are listed.
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000139
- Version
- TSS0-OS-000060
- Vuln IDs
-
- V-224002
- V-98711
- Rule IDs
-
- SV-224002r877843_rule
- SV-107815
Checks: C-25675r516405_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member in SYS1.PARMLIB. If BUFUSEWARN is set for "75" (75%) or less, this is not a finding.
Fix: F-25663r516406_fix
Configure the BUFUSEWARN statement in SMFPRMxx to "75" (75%) or less.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-OS-000070
- Vuln IDs
-
- V-224003
- V-98713
- Rule IDs
-
- SV-224003r877844_rule
- SV-107817
Checks: C-25676r516408_chk
Ask the system administrator to determine if the system PASSWORD data set and OS passwords are being used. If, based on the information provided, it can be determined that the system PASSWORD data set and OS passwords are not used, this is not a finding. If it is evident that OS passwords are utilized, this is a finding.
Fix: F-25664r516409_fix
System programmers will ensure that the old OS Password Protection is not used and any data protected by the old OS Password technology is removed and protection is replaced by the ACP. Review the contents of the PASSWORD data set. Ensure that any protections it provides are provided by the ACP and delete the PASSWORD data set. Access to data sets on z/OS systems can be protected using the OS password capability of MVS. This capability has been available in MVS for many years, and its use is commonly found in data centers. Since the advent of ACPs, the use of OS passwords for file protection has diminished, and is commonly considered archaic and of little use. The use of z/OS passwords is not supported by all the ACPs.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-OS-000080
- Vuln IDs
-
- V-224004
- V-98715
- Rule IDs
-
- SV-224004r877845_rule
- SV-107819
Checks: C-25677r516411_chk
Refer to the System proclibs for the TSS STC. If the Security database is located on the same volume as either the backup, Alternate or Recovery file, this is a finding.
Fix: F-25665r516412_fix
Configure the placement of ESM files are on a separate volume from its backup and recovery data sets to provide backup and recovery in the event of physical damage to a volume. Identify the ESM database(s), backup database(s), and recovery data set(s). Develop a plan to keep these data sets on different physical volumes. Implement the movement of these critical ESM files. File location is an often overlooked factor in system integrity. It is important to ensure that the effects of hardware failures on system integrity and availability are minimized. Avoid collocation of files such as primary and alternate databases. For example, the loss of the physical volume containing the ESM database should not also cause the loss of the ESM backup database as a result of their collocation. Files that will be segregated from each other on separate physical volumes include, but are not limited to, the ESM database and its alternate or backup file.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-OS-000090
- Vuln IDs
-
- V-224005
- V-98717
- Rule IDs
-
- SV-224005r877846_rule
- SV-107821
Checks: C-25678r516414_chk
Refer to the TSS Proclib PARMFILE DD to determine the PARM member. If the BACKUP is missing or coded with blank or OFF this is a finding. Note: If the security data base is shared only one of the systems is required to configure the BACKUP option in the PARMFILE. Determine that the option is properly coded on one of the systems that share the security database. From the ISPF Command Shell enter: TSS MODIFY(Status) If the backup parameter is active with a valid time this is not a finding.
Fix: F-25666r516415_fix
Configure the TSS PARMLIB BACKUP parameter to include BACKUP statement with a valid time. Additionally, configure the BACKUP parameter in the TSS Parmfile to include BACKUP statement with a valid time for nightly backups.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-OS-000100
- Vuln IDs
-
- V-224006
- V-98719
- Rule IDs
-
- SV-224006r877847_rule
- SV-107823
Checks: C-25679r516417_chk
Examine the policy agent policy statements. If it can be determined that the policy agent employs a deny-all, allow-by exception firewall policy for allowing connections to other systems this is not a finding.
Fix: F-25667r516418_fix
Develop a policy application and policy agent to employ a deny-all, allow-by-exception firewall policy for allowing connections to other systems.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- TSS0-OS-000110
- Vuln IDs
-
- V-224007
- V-98723
- Rule IDs
-
- SV-224007r877848_rule
- SV-107827
Checks: C-25680r516420_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper APF and/or PROG member. Examine each entry and verify that it exists on the specified volume. If inaccessible APF libraries exist, this is a finding. ISRDDN APF
Fix: F-25668r516421_fix
Review the entire list of APF authorized libraries and remove those that are no longer valid designations.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- TSS0-OS-000120
- Vuln IDs
-
- V-224008
- V-98725
- Rule IDs
-
- SV-224008r877849_rule
- SV-107829
Checks: C-25681r868987_chk
Review program entries in the IBM Program Properties Table (PPT). You may use a third-party product to examine these entries; however, to determine program entries, issue the following command from an ISPF command line: TSO ISRDDN LOAD IEFSDPPT Press Enter. Interpret the display as follows: Examine contents at offset 8 Hex 'x2' - Bypass Password Protection Hex 'x3' - Bypass Password Protection Hex 'x4' - No data set Integrity Hex 'x5' - No data set Integrity Hex 'x6' - Both Hex 'x7' - Both Determine Privilege Key at offset 9. A value of hex '70' or less indicates an elevated privilege. For each module identified in the "eyecatcher" that has BYPASS Password Protection, No data set Integrity, an elevated Privilege Key, or any combination thereof, determine if there is a valid loaded module. Again, you may use a third-party product; otherwise, execute the following steps: From an ISPF command line TSO ISRDDN LOAD <privileged module> Press Enter. If the return message is "Load Failed", make sure there is an entry in PARMLIB member SCHEDxx that revokes the excessive privilege. If this is not true, this is a finding.
Fix: F-25669r868988_fix
Review the PPT and define all entries associated with nonexistent or inapplicable modules as invalidated. Nullify the invalid IEFSDPPT entry by ensuring that there is a corresponding SCHED entry, which confers no special attributes. Use the following recommendations and techniques to provide protection for the PPT: Review the IEFSDPPT module and all programs that IBM has, by default, placed in the PPT to validate their applicability to the execution system. Refer to the IBM z/OS MVS Initialization and Tuning Reference documentation for the version and release of z/OS installed at the individual site for the actual contents of the default IEFSDPPT. Modules for products not in use on the system will have their special privileges explicitly revoked. Do this by placing a PPT entry for each module in the SYS1.PARMLIB(SCHEDxx) member, specifying no special privileges. The PPT entry for each overridden program will be in the following format, accepting the default (unprivileged) values for the sub parameters: PPT PGMNAME(<program name>) Assemble documentation regarding these PPT entries, and the ISSO will keep it on file. Include the following in the documentation: -The product and release for which the PPT entry was made -The last date this entry was reviewed to authenticate status -The reason the module's privileges are being revoked
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- TSS0-OS-000130
- Vuln IDs
-
- V-224009
- V-98727
- Rule IDs
-
- SV-224009r877850_rule
- SV-107831
Checks: C-25682r516426_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. If "LNKAUTH=APFTAB" is not specified, this is a finding.
Fix: F-25670r516427_fix
Configure LNKAUTH=APFTAB in the IEASYS00 member of PARMLIB.
- RMF Control
- SC-4
- Severity
- Medium
- CCI
- CCI-001090
- Version
- TSS0-OS-000140
- Vuln IDs
-
- V-224010
- V-98729
- Rule IDs
-
- SV-224010r877851_rule
- SV-107833
Checks: C-25683r516429_chk
Check HMC, VM, and z/OS on how to validate and determine a DASD volume(s) is shared. Note: In VM issue the command "QUEUE DASD SYSTEM" this display will show shared volume(s) and indicates the number of systems sharing the volume. Validate all machines that require access to these shared volume(s) have the volume(s) mounted. Obtain a map or list VTOC of the shared volume(s). Check if shared volume(s) contain any critical or sensitive data sets. Identify shared and critical or sensitive data sets on the system being audited. These data sets can be APF, LINKLIST, LPA, Catalogs, etc, as well as product data sets. If all of the critical or sensitive data sets identified on shared volume(s) are protected and justified to be on shared volume(s), this is not a finding. List critical or sensitive data sets are possible security breaches, if not justified and not protected on systems having access to the data set(s) and on shared volume(s).
Fix: F-25671r516430_fix
Configure all identified volumes of shared DASD to be valid within the following. HMC VM z/OS If the shared volume(s) are valid and systems having access to these shared volume(s) are valid, map disk/VTOC list to obtain data sets on the shared volume(s). From this list obtain a list of sensitive and critical system data sets that are found on the shared volume(s). Ensure that the data sets are justified to be shared on the system and to reside on the shared volume(s). The ISSO will review all access requirements to validate that sensitive and critical system data sets are protected from unauthorized access across all systems that have access to the shared volume(s). Protecting the data set(s) whether the data set(s) are used or not used on the systems that have the shared volume(s) available to them.
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-001095
- Version
- TSS0-OS-000150
- Vuln IDs
-
- V-224011
- V-98731
- Rule IDs
-
- SV-224011r877852_rule
- SV-107835
Checks: C-25684r516432_chk
Examine the Policy Agent policy statements. If it can be determined that there are policy statements that manages excess capacity, this is not a finding.
Fix: F-25672r516433_fix
Develop Policy application and Policy agent to manage excess capacity.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001683
- Version
- TSS0-OS-000170
- Vuln IDs
-
- V-224013
- V-98735
- Rule IDs
-
- SV-224013r877853_rule
- SV-107839
Checks: C-25686r516438_chk
Ask the system Administrator for the documented process to notify appropriate personnel when accounts are created. If there is no documented process, this is a finding.
Fix: F-25674r516439_fix
Develop a documented process to notify appropriate personnel when accounts are created.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001684
- Version
- TSS0-OS-000180
- Vuln IDs
-
- V-224014
- V-98737
- Rule IDs
-
- SV-224014r877854_rule
- SV-107841
Checks: C-25687r516441_chk
Ask the system Administrator for the documented process to notify appropriate personnel when accounts are modified. If there is no documented process, this is a finding.
Fix: F-25675r516442_fix
Develop a documented process to notify appropriate personnel when accounts are modified.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001685
- Version
- TSS0-OS-000190
- Vuln IDs
-
- V-224015
- V-98739
- Rule IDs
-
- SV-224015r877855_rule
- SV-107843
Checks: C-25688r516444_chk
Ask the system Administrator for the documented process to notify appropriate personnel when accounts are deleted. If there is no documented process, this is a finding.
Fix: F-25676r516445_fix
Develop a documented process to notify appropriate personnel when accounts are deleted.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001686
- Version
- TSS0-OS-000200
- Vuln IDs
-
- V-224016
- V-98741
- Rule IDs
-
- SV-224016r877856_rule
- SV-107845
Checks: C-25689r516447_chk
Ask the system Administrator for the documented process to notify appropriate personnel when accounts are removed. If there is no documented process, this is a finding.
Fix: F-25677r516448_fix
Develop a documented process to notify appropriate personnel when accounts are removed.
- RMF Control
- CM-7
- Severity
- High
- CCI
- CCI-001764
- Version
- TSS0-OS-000210
- Vuln IDs
-
- V-224017
- V-98743
- Rule IDs
-
- SV-224017r877857_rule
- SV-107847
Checks: C-25690r868990_chk
This check applies to all products that meet the following criteria: - Uses authorized and restricted z/OS interfaces by utilizing Authorized Program Facility (APF) authorized modules or libraries. - Requires access to system data sets or sensitive information or requires special or privileged authority to run. For the products in the above category, refer to the vendor's support lifecycle information for current versions and releases. If the software products currently running on the reviewed system are at a version greater than or equal to the products listed in the vendor's Support Lifecycle information, this is not a finding.
Fix: F-25678r868991_fix
For all products that meet the following criteria: - Uses authorized and restricted z/OS interfaces by utilizing Authorized Program Facility (APF) authorized modules or libraries. - Requires access to system data sets or sensitive information or requires special or privileged authority to run. The ISSO will ensure that unsupported system software for the products in the above category is removed or upgraded prior to a vendor dropping support. Authorized software that is NO longer supported is a CAT I vulnerability. The customer and site will be given six months to mitigate the risk, develop a supported solution, or obtain a formal letter approving such risk/software.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- TSS0-OS-000220
- Vuln IDs
-
- V-224018
- V-98745
- Rule IDs
-
- SV-224018r877858_rule
- SV-107849
Checks: C-25691r516453_chk
From an ISPF Command line enter: TSO ISRDDN LPA Review the list. If there are any DUMMY entries, i.e., inaccessible LPA libraries, this is a finding.
Fix: F-25679r516454_fix
Review all entries contained in the LPA members for the actual existence of each library. Develop a plan of action to correct deficiencies. The system Link Pack Area (LPA) is the component of MVS that maintains core operating system functions resident in main storage. A security concern exists when libraries from which LPA modules are obtained require APF authorization. Control over residence in the LPA is specified within the operating system in the following members of the data set SYS1.PARMLIB: - LPALSTxx specifies the names of libraries to be concatenated to SYS1.LPALIB when the LPA is generated at IPL in an MVS/XA or MVS/ESA system. (The xx is the suffix designated by the LPA parameter in the IEASYSxx member of SYS1.PARMLIB or overridden by the computer operator at system initial program load [IPL].) - IEAFIXxx specifies the names of modules from SYS1.SVCLIB, the LPALSTxx concatenation, and the LNKLSTxx concatenation that are to be temporarily fixed in central storage in the Fixed LPA (FLPA) for the duration of an IPL. (The xx is the suffix designated by the FIX parameter in the IEASYSxx member of SYS1.PARMLIB or overridden by the computer operator at IPL.) - IEALPAxx specifies the names of modules that will be loaded from the following: ? SYS1.SVCLIB ? The LPALSTxx concatenation ? The LNKLSTxx concatenation as a temporary extension to the existing Pageable LPA (PLPA) in the Modified LPA (MLPA) for the duration of an IPL. (The xx is the suffix designated by the MLPA parameter in the IEASYSxx member of SYS1.PARMLIB or overridden by the computer operator at IPL.) Use the following recommendations and techniques to control the exposures created by the LPA facility: -The LPALSTxx, IEAFIXxx, and IEALPAxx members will contain only required libraries. On a semiannual basis, Software Support should review the volume serial numbers and verify them in accordance with the system catalog. Software Support will remove all non-existent libraries. The ISSO should modify and/or delete the rules associated with these libraries.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- TSS0-OS-000225
- Vuln IDs
-
- V-224019
- V-100515
- Rule IDs
-
- SV-224019r877859_rule
- SV-109619
Checks: C-25692r516456_chk
From and ISPF Command line enter: TSO ISRDDN LINKLIST Review the list, if there are any DUMMY entries i.e., inaccessible LINKLIST libraries, this is a finding.
Fix: F-25680r516457_fix
Review all entries contained in the LINKLIST for the actual existence of each library. Develop a plan of action to correct deficiencies. The Linklist is a default set of libraries that MVS searches for a specified program. This facility is used so that a user does not have to know the library names in which utility types of programs are stored. Control over membership in the Linklist is specified within the operating system. The data set SYS1.PARMLIB(LNKLSTxx) is used to specify the library names. (The xx is the suffix designated by the LNK parameter in the IEASYSxx member of SYS1.PARMLIB, or overridden by the computer operator at IPL.) Use the following recommendations and techniques to control the exposures created by the LINKLIST facility: 441-1Avoid inclusion of sensitive libraries in the LNKLSTxx member unless absolutely required. -The LNKLSTxx and PROGxx (LNKLST entries) members will contain only required libraries. On a semiannual basis, Software Support should review the volume serial numbers, and should verify them in accordance with the system catalog. Software Support will remove all nonexistent libraries. The ISSO should modify and/or delete the rules associated with these libraries.
- RMF Control
- CM-5
- Severity
- High
- CCI
- CCI-001813
- Version
- TSS0-OS-000230
- Vuln IDs
-
- V-224020
- V-98747
- Rule IDs
-
- SV-224020r877860_rule
- SV-107851
Checks: C-25693r516459_chk
Refer to the active tasks on the system. Use IBM SDSF or the system Log. If CA-TSS is active this is not a finding.
Fix: F-25681r516460_fix
Ensure that CA-TSS is active on the system.
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001849
- Version
- TSS0-OS-000240
- Vuln IDs
-
- V-224021
- V-98749
- Rule IDs
-
- SV-224021r877861_rule
- SV-107853
Checks: C-25694r516462_chk
Review the SMF dump procedure in there system. If the output data sets in the procedure have storage capacity to store at least one weeks' worth of audit data, this is not a finding.
Fix: F-25682r516463_fix
The system Link Pack Area (LPA) is the component of MVS that maintains core operating system functions resident in main storage. A security concern exists when libraries from which LPA modules are obtained require APF authorization.
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- TSS0-OS-000250
- Vuln IDs
-
- V-224022
- V-98751
- Rule IDs
-
- SV-224022r877862_rule
- SV-107855
Checks: C-25695r516465_chk
Ask the system administrator if there is an automated process is in place to collect and retain all SMF data produced on the system. If, based on the information provided, it can be determined that an automated process is in place to collect and retain all SMF data produced on the system, this is not a finding. If it cannot be determined this process exists and is being adhered to, this is a finding.
Fix: F-25683r516466_fix
Ensure that an automated process is in place to collect SMF data. Review SMF data collection and retention processes. Develop processes that are automatically started to dump SMF collection files immediately upon their becoming full. To ensure that all SMF data is collected in a timely manner, and to reduce the risk of data loss, ensure that automated mechanisms are in place to collect and retain all SMF data produced on the system. Dump the SMF files (MANx) in systems based on the following guidelines: -Dump each SMF file as it fills up during the normal course of daily processing. -Dump all remaining SMF data at the end of each processing day. Establish a process using Audit logging.
- RMF Control
- AU-8
- Severity
- Medium
- CCI
- CCI-001891
- Version
- TSS0-OS-000270
- Vuln IDs
-
- V-224023
- V-98755
- Rule IDs
-
- SV-224023r877863_rule
- SV-107859
Checks: C-25696r868993_chk
From UNIX System Services ISPF Shell, navigate to ribbon select tools. Select option 1 - Work with Processes. If SNTP Daemon (SNTPD) is not active, this is a finding.
Fix: F-25684r868994_fix
Obtain a copy of this sample procedure from SEZAINST and store it in one of your PROCLIB concatenation data sets. Perform the following step to start SNTPD as a procedure: Invoke the procedure using the system operator start command. The following sample, SEZAINST(SNTPD), shows how to start SNTPD as a procedure: //* //* Sample procedure for the Simple Network Time Protocol (SNTP) //* //* z/OS Communications Server Version 1 Release 13 //* SMP/E Distribution Name: SEZAINST(EZASNPRO) //* //* Copyright: Licensed Materials - Property of IBM //* 5650-ZOS //* Copyright IBM Corp. 2002, 2015 //* //* Status: CSV2R2 //* //SNTPD EXEC PGM=SNTPD,REGION=4096K,TIME=NOLIMIT, // PARM='/ -d' //SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,LRECL=132,BLKSIZE=132) //SYSIN DD DUMMY //SYSERR DD SYSOUT=* //SYSOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=132,BLKSIZE=132) //CEEDUMP DD SYSOUT=* //SYSABEND DD SYSOUT=*
- RMF Control
- AU-8
- Severity
- Medium
- CCI
- CCI-001891
- Version
- TSS0-OS-000280
- Vuln IDs
-
- V-224024
- V-98757
- Rule IDs
-
- SV-224024r877864_rule
- SV-107861
Checks: C-25697r516471_chk
From the ISPF Command Shell enter: cd /usr/sbin ls -al If the following File permission and user Audit Bits are true, this is not a finding. /usr/sbin/sntpd 1740 faf The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25685r516472_fix
With the assistance of a systems programmer with UID(0) and/or SUPERUSER access, configure the UNIX permission bits and user audit bits on the SNTPD to conform to the specifications below: /usr/sbin/sntpd 1740 faf
- RMF Control
- AU-8
- Severity
- Medium
- CCI
- CCI-002046
- Version
- TSS0-OS-000290
- Vuln IDs
-
- V-224025
- V-98759
- Rule IDs
-
- SV-224025r877865_rule
- SV-107863
Checks: C-25698r516474_chk
Refer to the CLOCKxx member of PARMLIB. If the ACCURACY parm is not coded, this is a finding. If the ACCURACY parm is coded to "1000", this is not a finding.
Fix: F-25686r516475_fix
Define the CLOCKxx statement to include the ACCURACY parm set to "1000".
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- TSS0-OS-000300
- Vuln IDs
-
- V-224026
- V-98761
- Rule IDs
-
- SV-224026r877866_rule
- SV-107865
Checks: C-25699r516477_chk
Examine the "Policy Agent" policy statements. If it can be determined that the policy that protects against or limits the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces, this is not a finding.
Fix: F-25687r516478_fix
Develop "Policy Agent" statements to protect against or limit the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-OS-000350
- Vuln IDs
-
- V-224031
- V-98771
- Rule IDs
-
- SV-224031r877869_rule
- SV-107875
Checks: C-25704r868996_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. Examine the JWT, SWT, and TWT values. If the JWT parameter is greater than "15" minutes, and the system is processing unclassified information, review the following items. If any of these items is true, this is not a finding. -If a session is not terminated, but instead is locked out after 15 minutes of inactivity, a process must be in place that requires user identification and authentication before the session is unlocked. Session lock-out will be implemented through system controls or terminal screen protections. -A system's default time for terminal lock-out or session termination may be lengthened to 30 minutes at the discretion of the ISSM or ISSO. The ISSM and/or ISSO will maintain the documentation for each system with a time-out adjusted beyond the 15-minute recommendation to explain the basis for this decision. -The ISSM and/or ISSO may set selected userids to have a time-out of up to 60 minutes in order to complete critical reports or transactions without timing out. Each exception must meet the following criteria: -The time-out exception cannot exceed 60 minutes. -A letter of justification fully documenting the user requirement(s) must be submitted and approved by the site ISSM or ISSO. In addition, this letter must identify an alternate means of access control for the terminal(s) involved (e.g., a room that is locked at all times, a room with a cipher lock to limit access, a password protected screen saver set to 30 minutes or less, etc.). -The requirement must be revalidated on an annual basis. If the TWT and SWT values are equal or less than the JWT value, this is not a finding.
Fix: F-25692r868997_fix
Configure the SMFPRMxx JWT to "15" minutes for classified systems. The JWT parameter can be greater than "15" minutes if the system is processing unclassified information and the following items are reviewed. -If a session is not terminated, but instead is locked out after "15" minutes of inactivity, a process must be in place that requires user identification and authentication before the session is unlocked. Session lock-out will be implemented through system controls or terminal screen protections. -A system's default time for terminal lock-out or session termination may be lengthened to "30" minutes at the discretion of the ISSM or ISSO. The ISSM and/or ISSO will maintain the documentation for each system with a time-out adjusted beyond the 15-minute recommendation to explain the basis for this decision. -The ISSM and/or ISSO may set selected userids to have a time-out of up to "60" minutes in order to complete critical reports or transactions without timing out. Each exception must meet the following criteria: -The time-out exception cannot exceed "60" minutes. -A letter of justification fully documenting the user requirement(s) must be submitted and approved by the site ISSM or ISSO. In addition, this letter must identify an alternate means of access control for the terminal(s) involved (e.g., a room that is locked at all times, a room with a cipher lock to limit access, a password protected screen saver set to 30 minutes or less, etc.). -The requirement must be revalidated on an annual basis. Configure any TWT and or SWT to be equal or less than the JWT.
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000060
- Version
- TSS0-OS-000360
- Vuln IDs
-
- V-224032
- V-98773
- Rule IDs
-
- SV-224032r877870_rule
- SV-107877
Checks: C-25705r516495_chk
Ask the system administrator for the configuration parameters for the session manager in use. If there is no session manager in use, this is a finding. If the session manager is not configured to conceal, via the session lock, information previously visible on the display with a publicly viewable image, this is a finding.
Fix: F-25693r516496_fix
Configure the session manager to conceal, via the session lock, information previously visible on the display with a publicly viewable image.
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- TSS0-OS-000370
- Vuln IDs
-
- V-224033
- V-98775
- Rule IDs
-
- SV-224033r877871_rule
- SV-107879
Checks: C-25706r516498_chk
Ask the system administrator for the configuration parameters for the session manager in use. If there is no session manager in use, this is a finding. If the session manager is not configured to initiate a session lock after a 15-minute period of inactivity, this is a finding.
Fix: F-25694r516499_fix
Configure the session manager to initiate a session lock after a 15-minute period of inactivity.
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- TSS0-OS-000380
- Vuln IDs
-
- V-224034
- V-98777
- Rule IDs
-
- SV-224034r877872_rule
- SV-107881
Checks: C-25707r516501_chk
Ask the system administrator for the configuration parameters for the session manager in use. If there is no session manager in use, this is a finding. If the session manager is not configured to retain a user's session lock until that user reestablishes access using established identification and authentication procedures, this is a finding.
Fix: F-25695r516502_fix
LPA (PLPA) in the Modified LPA (MLPA) for the duration of an IPL. (The xx is the suffix designated by the MLPA parameter in the IEASYSxx member of SYS1.PARMLIB or overridden by the computer operator at IPL.)
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000016
- Version
- TSS0-OS-000390
- Vuln IDs
-
- V-224035
- V-98779
- Rule IDs
-
- SV-224035r877873_rule
- SV-107883
Checks: C-25708r516504_chk
Ask the system administrator for the procedure to automatically remove or disable temporary user accounts after 72 hours. If there is no procedure, this is a finding.
Fix: F-25696r516505_fix
Develop a procedure to remove or disable emergency user accounts after the crisis is resolved or 72 hours.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001682
- Version
- TSS0-OS-000400
- Vuln IDs
-
- V-224036
- V-102937
- Rule IDs
-
- SV-224036r877874_rule
- SV-111899
Checks: C-25709r516507_chk
Ask the system administrator for the procedure to automatically remove or disable emergency accounts after the crisis is resolved or 72 hours. If there is no procedure, this is a finding.
Fix: F-25697r516508_fix
Develop a procedure to remove or disable emergency user accounts after the crisis is resolved or 72 hours.
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-002132
- Version
- TSS0-OS-000410
- Vuln IDs
-
- V-224037
- V-98781
- Rule IDs
-
- SV-224037r877875_rule
- SV-107885
Checks: C-25710r516510_chk
Ask the system administrator for the procedure to notify system administrators and ISSOs of account enabling actions. If there is no procedure, this is a finding.
Fix: F-25698r516511_fix
Develop a documented procedure to notify system administrators and ISSOs of account enabling actions.
- RMF Control
- CM-3
- Severity
- Medium
- CCI
- CCI-001744
- Version
- TSS0-OS-000420
- Vuln IDs
-
- V-224038
- V-98783
- Rule IDs
-
- SV-224038r877876_rule
- SV-107887
Checks: C-25711r516513_chk
Ask the system administrator for the procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner. If there is no procedure, this is a finding.
Fix: F-25699r516514_fix
Develop a procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner.
- RMF Control
- MA-4
- Severity
- Medium
- CCI
- CCI-000879
- Version
- TSS0-OS-000440
- Vuln IDs
-
- V-224039
- V-98785
- Rule IDs
-
- SV-224039r877877_rule
- SV-107889
Checks: C-25712r516516_chk
Ask the system administrator for the procedure to terminate all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed. If there is no procedure, this is a finding.
Fix: F-25700r516517_fix
Develop a procedure to terminate all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed.
- RMF Control
- SI-2
- Severity
- Medium
- CCI
- CCI-002617
- Version
- TSS0-OS-000450
- Vuln IDs
-
- V-224040
- V-98787
- Rule IDs
-
- SV-224040r877878_rule
- SV-107891
Checks: C-25713r516519_chk
Ask the system administrator for the procedure to remove all software components after updated versions have been installed. If there is no procedure, this is a finding.
Fix: F-25701r516520_fix
Develop a procedure to remove all software components after updated versions have been installed.
- RMF Control
- SI-6
- Severity
- Medium
- CCI
- CCI-002702
- Version
- TSS0-OS-000460
- Vuln IDs
-
- V-224041
- V-98789
- Rule IDs
-
- SV-224041r877879_rule
- SV-107893
Checks: C-25714r516522_chk
Ask the system administrator for the procedure to shut down the information system, restart the information system, and/or notify the system administrator when anomalies occur. If a procedure does not exist, this is a finding. If the procedure does not properly shut down the information system, restart the information system, and/or notify the system administrator when anomalies occur, this is a finding.
Fix: F-25702r516523_fix
Develop a procedure to shut down the information system, restart the information system, and/or notify the system administrator when anomalies occur.
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- TSS0-OS-000470
- Vuln IDs
-
- V-224042
- V-98791
- Rule IDs
-
- SV-224042r877880_rule
- SV-107895
Checks: C-25715r516525_chk
Ask the system administrator for the procedure to offload SMF files to a different system or media than the system being audited. If the procedure does not exist, this is a finding.
Fix: F-25703r516526_fix
Develop a procedure to offload SMF files to a different system or media than the system being audited.
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000058
- Version
- TSS0-OS-000480
- Vuln IDs
-
- V-224043
- V-98793
- Rule IDs
-
- SV-224043r877881_rule
- SV-107897
Checks: C-25716r516528_chk
Ask the system administrator for the configuration parameters for the session manager in use. If there is no session manager in use this is a finding. If the session manager in use does not allow users to directly initiate a session lock for all connection types, this is a finding.
Fix: F-25704r516529_fix
Configure the session manager to allow users to directly initiate a session lock for all connection types.
- RMF Control
- AC-17
- Severity
- High
- CCI
- CCI-000068
- Version
- TSS0-SH-000020
- Vuln IDs
-
- V-224044
- V-98795
- Rule IDs
-
- SV-224044r877882_rule
- SV-107899
Checks: C-25717r516758_chk
Locate the SSH daemon configuration file which may be found in /etc/ssh/ directory. Alternately: From UNIX System Services ISPF Shell navigate to ribbon select tools. Select option 1 - Work with Processes. If SSH Daemon is not active, this is not a finding. Examine SSH daemon configuration file. sshd_config If there are no Ciphers lines or the ciphers list contains any cipher not starting with "3des" or "aes", this is a finding. If the MACs line is not configured to "hmac-sha1" or greater, this is a finding. Examine the z/OS-specific sshd server system-wide configuration: zos_sshd_config If any of the following is untrue, this is a finding. FIPSMODE=YES CiphersSource=ICSF MACsSource=ICSF
Fix: F-25705r516759_fix
Edit the SSH daemon configuration and remove any ciphers not starting with "3des" or "aes". If necessary, add a "Ciphers" line using FIPS 140-2 compliant algorithms.
- RMF Control
- CM-7
- Severity
- High
- CCI
- CCI-000382
- Version
- TSS0-SH-000030
- Vuln IDs
-
- V-224045
- V-98797
- Rule IDs
-
- SV-224045r877883_rule
- SV-107901
Checks: C-25718r516534_chk
Locate the SSH daemon configuration file. May be found in /etc/ssh/ directory. Alternately: From UNIX System Services ISPF Shell navigate to ribbon select tools. Select option 1 - Work with Processes. If SSH Daemon is not active, this is not a finding. Examine SSH daemon configuration file. If the variables "Protocol 2,1" or "Protocol 1" are defined on a line without a leading comment, this is a finding.
Fix: F-25706r516535_fix
Edit the sshd_config file and set the "Protocol" setting to "2".
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-SL-000010
- Vuln IDs
-
- V-224046
- V-98799
- Rule IDs
-
- SV-224046r877884_rule
- SV-107903
Checks: C-25719r516537_chk
From an ISPF Enter cd /usr/sbin Enter ls -alW If File Permission Bits and User Audit Bits for SYSLOG Daemon HFS directories and files are as below this is not a finding. /usr/sbin/syslogd 1740 fff Enter cd /etc/ Enter ls -alW If File Permission Bits and User Audit Bits for Output log file defined in the configuration file are as below this is not a finding. /etc/syslog.conf 0744 faf 0744 fff Notes: The /usr/sbin/syslogd object is a symbolic link to /usr/lpp/tcpip/sbin/syslogd. The permission and user audit bits on the target of the symbolic link must have the required settings. The /etc/syslog.conf file may not be the configuration file the daemon uses. It is necessary to check the script or JCL used to start the daemon to determine the actual configuration file. For example, in /etc/rc: _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf For example, in the SYSLOGD started task JCL: //SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT // PARM='POSIX(ON) ALL31(ON)/ -f /etc/syslogd.conf' //SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT // PARM='POSIX(ON) ALL31(ON) /-f //''SYS1.TCPPARMS(SYSLOG)''' The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25707r516538_fix
Configure the UNIX permission bits and user audit bits on the HFS directories and files for the Syslog daemon to conform to the specifications in the SYSLOG Daemon HFS Object Security Settings table below. Log files should have security that prevents anyone except the syslogd process and authorized maintenance jobs from writing to or deleting them. A maintenance process to periodically clear the log files is essential. Logging stops if the target file system becomes full. SYSLOG Daemon HFS Object Security Settings File Permission Bits User Audit Bits /usr/sbin/syslogd 1740 fff [Configuration File] /etc/syslog.conf 0744 faf [Output log file defined in the configuration file] 0744 fff The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing NOTES: The /usr/sbin/syslogd object is a symbolic link to /usr/lpp/tcpip/sbin/syslogd. The permission and user audit bits on the target of the symbolic link must have the required settings. The /etc/syslog.conf file may not be the configuration file the daemon uses. It is necessary to check the script or JCL used to start the daemon to determine the actual configuration file. For example, in /etc/rc: _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf For example, in the SYSLOGD started task JCL: //SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT // PARM='POSIX(ON) ALL31(ON)/ -f /etc/syslogd.conf' //SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT // PARM='POSIX(ON) ALL31(ON) /-f //''SYS1.TCPPARMS(SYSLOG)''' The following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 1740 /usr/lpp/tcpip/sbin/syslogd chaudit rwx=f /usr/lpp/tcpip/sbin/syslogd chmod 0744 /etc/syslog.conf chaudit w=sf,rx+f /etc/syslog.conf chmod 0744 /log_dir/log_file chaudit rwx=f /log_dir/log_file
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-SL-000020
- Vuln IDs
-
- V-224047
- V-98801
- Rule IDs
-
- SV-224047r877885_rule
- SV-107905
Checks: C-25720r516540_chk
SYSLOGD may be started from the shell, a cataloged procedure (STC), or the BPXBATCH program. Additionally, other mechanisms (e.g., a job scheduler) may be used to automatically start the Syslog daemon. To thoroughly analyze this requirement you may need to view the OS SYSLOG using SDSF, find the last IPL, and look for the initialization of SYSLOGD. If the Syslog daemon SYSLOGD is started automatically during the initialization of the z/S/ system, this is not a finding.
Fix: F-25708r516541_fix
Review the files used to initialize tasks during system IPL (e.g., /etc/rc, SYS1.PARMLIB, any job scheduler definitions) configure the Syslog daemon to start automatically during z/OS system initialization. It is important that syslogd be started during the initialization phase of the z/OS system to ensure that significant messages are not lost. As with other z/OS UNIX daemons, there is more than one way to start SYSLOGD. It can be started as a process in the /etc/rc file or as a z/OS started task.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-SL-000030
- Vuln IDs
-
- V-224048
- V-98803
- Rule IDs
-
- SV-224048r877886_rule
- SV-107907
Checks: C-25721r868999_chk
From the ISPF Command Shell enter: TSS LIST(SYSLOGD) SEGMENT(OMVS) If the following guidance is true, this is not a finding. -The Syslog daemon userid is SYSLOGD. -The SYSLOGD userid has the STC facility. -The SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment. -The SYSLOGD started proc is assigned the SYSLOGD userid is in the Started Task Table. If Syslog daemon is started from /etc/rc then from the ISPF Command Shell enter: OMVS cd /etc cat rc If Syslog daemon is started from /etc/rc then ensure that the "_BPX_JOBNAME" and "_BPX_USERID" environment variables are assigned a value of SYSLOGD. If the Syslog daemon is started from /etc/rc and the "_BPX_JOBNAME" and "_BPX_USERID" environment variables are not assigned a value of SYSLOGD, this is a finding.
Fix: F-25709r869000_fix
Configure so that the Syslog daemon runs under its own user account. Specifically, it does not share the account defined for the z/OS UNIX kernel. The Syslog daemon userid is SYSLOGD. The SYSLOGD userid has the STC facility. The SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment. To set up and use as an MVS Started Proc, the following sample commands are provided: TSS CREATE(SYSLOGD) TYPE(USER) NAME(SYSLOGD) - DEPT(existing-dept) FACILITY(STC) - PASSWORD(password,0) TSS ADD(SYSLOGD) DFLTGRP(stctcpx) GROUP(stctcpx) TSS ADD(SYSLOGD) SOURCE(INTRDR) TSS ADD(SYSLOGD) UID(0) HOME(/) OMVSPGM(/bin/sh) The SYSLOGD started proc is assigned the SYSLOGD userid is in the Started Task Table. TSS ADD(STC) PROCNAME(SYSLOGD) ACID(SYSLOGD) If /etc/rc is used to start the Syslog daemon, ensure that the _BPX_JOBNAME and _BPX_ USERID environment variables are assigned a value of SYSLOGD.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-SM-000010
- Vuln IDs
-
- V-224049
- V-98805
- Rule IDs
-
- SV-224049r877887_rule
- SV-107909
Checks: C-25722r869002_chk
If all SMS resources and/or generic equivalent are properly protected according to the requirements specified and the following guidance is true, this is not a finding. The TSS resources are owned or DEFPROT is specified for the resource class. To avoid authorization failures once a base cluster is accessed via a PATH or AIX by a user or application that has authority to the PATH and AIX, but not the base cluster, APAR OA50118 must be applied. The resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE is defined with access of NONE. The resource STGADMIN.IGG.CATALOG.SECURITY.BOTH is defined with access of READ. Note: The resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE can be defined with read access for migration purposes. If it is, a detailed migration plan must be documented and filed by the ISSM that determines a definite migration period. All access must be logged. At the completion of migration, this resource must be configured with access of NONE. If the resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE and STGADMIN.IGG.CATALOG.SECURITY.BOTH are both defined, ADMIN.IGG.CATALOG.SECURITY.BOTH takes precedence. STGADMIN.DPDSRN.olddsname is restricted to system programmers and all access is logged. The STGADMIN.IGD.ACTIVATE.CONFIGURATION is restricted to system programmers and all access is logged. The STGADMIN.IGG.DEFDEL.UALIAS is restricted to centralized and decentralized security personnel and system programmers and all access is logged. The following resources and prefixes may be available to the end user. STGADMIN.ADR.COPY.CNCURRNT STGADMIN.ADR.COPY.FLASHCPY STGADMIN.ADR.COPY.TOLERATE.ENQF STGADMIN.ADR.DUMP.CNCURRNT STGADMIN.ADR.DUMP.TOLERATE.ENQF STGADMIN.ADR.RESTORE.TOLERATE.ENQF STGADMIN.ARC.ENDUSER. STGADMIN.IGG.ALTER.SMS The following resource is restricted to Application Production Support Team members, Automated Operations, DASD managers, and system programmers. STGADMIN.IDC.DCOLLECT The following resources are restricted to Application Production Support Team members, DASD managers, and system programmers. STGADMIN.ARC.CANCEL STGADMIN.ARC.LIST STGADMIN.ARC.QUERY STGADMIN.ARC.REPORT STGADMIN.DMO.CONFIG STGADMIN.IFG.READVTOC STGADMIN.IGG.DELGDG.FORCE The following resource prefixes, at a minimum, are restricted to DASD managers and system programmers. STGADMIN.ADR STGADMIN.ANT STGADMIN.ARC STGADMIN.DMO STGADMIN.ICK STGADMIN.IDC STGADMIN.IFG STGADMIN.IGG STGADMIN.IGWSHCDS The following Storage Administrator functions prefix is restricted to DASD managers and system programmers and all access is logged. STGADMIN.ADR.STGADMIN.
Fix: F-25710r869003_fix
Ensure that the following are properly specified in the ESM. Note: The resources and/or resource prefixes identified below are examples of a possible installation. The actual resource type, 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. Below is listed the access requirements for SMS Resources. Ensure the guidelines for the resources and/or generic equivalent are followed. The TSS resources are owned and/or DEFPROT is specified for the resource class. Configure resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE with no access. Note: The resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE can be defined with read access for migration purposes. If it is, a detailed migration plan must be documented and filed with the ISSM that determines a definite migration period. All access must be logged. At the completion of migration this resource must be configured with access = NONE. Configure STGADMIN.IGG.CATALOG.SECURITY.BOTH to have READ access for all. TSS ADD(ADMIN) IBMFAC(STGADMIN) or TSS REPLACE(RDT) RESCLASS(IBMFAC) ATTR(DEFPROT) The STGADMIN.DPDSRN.olddsname is restricted to System Programmers and all access is logged. Example: TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.DPDSRN.olddsname) - ACCESS(READ) ACTION(AUDIT) The STGADMIN.IGD.ACTIVATE.CONFIGURATION is restricted to system programmers and all access is logged. Example: TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IGD.ACTIVATE.CONFIGURATION) - ACCESS(READ) ACTION(AUDIT) The STGADMIN.IGG.DEFDEL.UALIAS is restricted to system programmers and security personnel and all access is logged. Example: TSS PERMIT(secasmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) - ACCESS(READ) ACTION(AUDIT) TSS PERMIT(secdsmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) - ACCESS(READ) ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) - ACCESS(READ) ACTION(AUDIT) The following resources and prefixes may be available to the end user. Example: STGADMIN.ADR.COPY.CNCURRNT STGADMIN.ADR.COPY.FLASHCPY STGADMIN.ADR.COPY.TOLERATE.ENQF STGADMIN.ADR.DUMP.CNCURRNT STGADMIN.ADR.DUMP.TOLERATE.ENQF STGADMIN.ADR.RESTORE.TOLERATE.ENQF STGADMIN.ARC.ENDUSER. STGADMIN.IGG.ALTER.SMS Example: TSS PERMIT(endusers) IBMFAC(STGADMIN.ADR.COPY.CNCURRNT.) - ACCESS(READ) The following resource is restricted to Application Production Support Team members, Automated Operations, DASD managers, and system programmers. STGADMIN.IDC.DCOLLECT Example: TSS PERMIT(appssmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ) TSS PERMIT(autosmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ) TSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ) TSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ) TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ) The following resources are restricted to Application Production Support Team members, DASD managers, and system programmers. Example: STGADMIN.ARC.CANCEL STGADMIN.ARC.LIST STGADMIN.ARC.QUERY STGADMIN.ARC.REPORT STGADMIN.DMO.CONFIG STGADMIN.IFG.READVTOC STGADMIN.IGG.DELGDG.FORCE Example: TSS PERMIT(appssmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ) TSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ) TSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ) TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ) The following resource prefixes, at a minimum, are restricted to DASD managers and system programmers. STGADMIN.ADR STGADMIN.ANT STGADMIN.ARC STGADMIN.DMO STGADMIN.ICK STGADMIN.IDC STGADMIN.IFG STGADMIN.IGG STGADMIN.IGWSHCDS Example: TSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ) TSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ) TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ) The following Storage Administrator functions prefix is restricted to DASD managers and system programmers and all access is logged. STGADMIN.ADR.STGADMIN. Example: TSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) - ACTION(AUDIT) TSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) - ACTION(AUDIT) TSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) - ACTION(AUDIT)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-SM-000020
- Vuln IDs
-
- V-224050
- V-98807
- Rule IDs
-
- SV-224050r877888_rule
- SV-107911
Checks: C-25723r869005_chk
Refer to the load modules residing in the following Load libraries to determine program resource definitions: v SYS1.DGTLLIB for DFSMSdfp/ISMF v SYS1.DGTLLIB for DFSMSdss/ISMF v SYS1.DFQLLIB for DFSMShsm If the installation moves these modules to another load library the installation-defined load library must be used in the program protection. If the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding. If the TSS resource access authorizations restrict access to the appropriate personnel, this is not a finding.
Fix: F-25711r869006_fix
Configure the following to be properly specified in the ACP. Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, 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. Reference the SMS Program Resources as provided by the following libraries: v SYS1.DGTLLIB for DFSMSdfp/ISMF v SYS1.DGTLLIB for DFSMSdss/ISMF v SYS1.DFQLLIB for DFSMShsm If the installation moves these modules to another load library the installation-defined load library must be used in the program protection. The TSS resources as designated in the above are owned and/or DEFPROT is specified for the resource class. The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above. The following commands are provided as a sample for implementing resource controls: Example: TSS ADD(dept-acid) PROGRAM(ACBFUTO2) TSS PERMIT(smplsmpl) PROGRAM(ACBFUTO2) TSS PERMIT(dasdsmpl) PROGRAM(ACBFUTO2) TSS PERMIT(secasmpl) PROGRAM(ACBFUTO2) TSS PERMIT(syspsmpl) PROGRAM(ACBFUTO2) TSS PERMIT(tstcsmpl) PROGRAM(ACBFUTO2)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-SM-000030
- Vuln IDs
-
- V-224051
- V-98809
- Rule IDs
-
- SV-224051r877889_rule
- SV-107913
Checks: C-25724r516552_chk
Refer to the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets: Source Control Data Set (SCDS) Active Control Data Set (ACDS) Communications Data Set (COMMDS) Automatic Class Selection Routine Source Data Sets (ACS) ACDS Backup COMMDS Backup If the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets restrict UPDATE and ALL access to only systems programming personnel, this is not a finding. If the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets do not restrict UPDATE and ALL access to only systems programming personnel, this is a finding. Note: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets.
Fix: F-25712r516553_fix
Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets: Source Control Data Set (SCDS) Active Control Data Set (ACDS) Communications Data Set (COMMDS) Automatic Class Selection Routine Source Data Sets (ACS) ACDS Backup COMMDS Backup Assign ownership of the data sets, replacing user-id with a user, department, or division that administer access to the SMS control data sets, and data name with the prefix of the SMS control data sets: TSS ADD(user-id) DSN(data name) Ensure the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets restrict UPDATE and ALL access to only z/OS systems programming personnel. Note: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets. Permit access to those personnel who manage the SMS environment, replacing user-id with the userid of the user or a Group profile: TSS PERMIT(user-id) DSN(data name) ACC(UPDATE) ACTION(AUDIT) Permit access to those personnel that perform maintenance on these data sets: TSS PERMIT(user-id) DSN(data name) ACC(ALL) ACTION(AUDIT)
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-SM-000040
- Vuln IDs
-
- V-224052
- V-98811
- Rule IDs
-
- SV-224052r877890_rule
- SV-107915
Checks: C-25725r516555_chk
Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), for the following SMS parameter settings: Parameter Key SMS ACDS(ACDS data set name) COMMDS(COMMDS data set name) If the required parameters are defined, this is not a finding.
Fix: F-25713r516556_fix
Configure the DFSMS-related PDS members and statements specified in the system parmlib concatenation as outlined below: Parameter Key SMS ACDS(ACDS data set name) COMMDS(COMMDS data set name)
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-SM-000050
- Vuln IDs
-
- V-224053
- V-98813
- Rule IDs
-
- SV-224053r877891_rule
- SV-107917
Checks: C-25726r516558_chk
Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets: Source Control Data Set (SCDS) Active Control Data Set (ACDS) Communications Data Set (COMMDS) Automatic Class Selection Routine Source Data Sets (ACS) ACDS Backup COMMDS Backup If the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets restrict UPDATE and ALL access to only systems programming personnel, this is not a finding. If the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets do not restrict UPDATE and ALL access to only systems programming personnel, this is a finding. Note: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets.
Fix: F-25714r516559_fix
Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets: Source Control Data Set (SCDS) Active Control Data Set (ACDS) Communications Data Set (COMMDS) Automatic Class Selection Routine Source Data Sets (ACS) ACDS Backup COMMDS Backup Assign ownership of the data sets, replacing user-id with a user, department, or division that administer access to the SMS control data sets, and data name with the prefix of the SMS control data sets: TSS ADD(user-id) DSN(data name) Ensure the TSS data set rules for the SCDS, ACDS, COMMDS, and ACS data sets restrict UPDATE and ALL access to only z/OS systems programming personnel. Note: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets. Permit access to those personnel who manage the SMS environment, replacing user-id with the userid of the user or a Group profile: TSS PERMIT(user-id) DSN(data name) ACC(UPDATE) ACTION(AUDIT) Permit access to those personnel that perform maintenance on these data sets: TSS PERMIT(user-id) DSN(data name) ACC(ALL) ACTION(AUDIT)
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-SS-000010
- Vuln IDs
-
- V-224054
- V-98815
- Rule IDs
-
- SV-224054r904400_rule
- SV-107919
Checks: C-25727r904398_chk
Locate the SSH daemon configuration file, which may be found in /etc/ssh/ directory. Alternately: From UNIX System Services ISPF Shell, navigate to ribbon select tools. Select option 1 - Work with Processes. If SSH Daemon is not active, this is not a finding. Examine SSH daemon configuration file. If ServerSMF is not coded with ServerSMF TYPE119_U83 or is commented out, this is a finding.
Fix: F-25715r904399_fix
Configure the SERVERSMF statement in the SSH Daemon configuration file to TYPE119_U83.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-001384
- Version
- TSS0-SS-000040
- Vuln IDs
-
- V-224055
- V-98817
- Rule IDs
-
- SV-224055r877893_rule
- SV-107921
Checks: C-25728r516564_chk
Locate the SSH daemon configuration file. May be found in /etc/ssh/ directory. Alternately: From UNIX System Services ISPF Shell navigate to ribbon select tools. Select option 1 - Work with Processes. If SSH Daemon is not active, this is not a finding. Examine SSH daemon configuration file. If Banner statement is missing or configured to none, this is a finding. Ensure that the contents of the file specified on the banner statement contain a logon banner. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. If there is any deviation this is a finding. STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
Fix: F-25716r516565_fix
Configure the banner statement to a file that contains the Department of Defense (DoD) logon banner. Ensure that the contents of the file specified on the banner statement contain a logon banner. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-TC-000010
- Vuln IDs
-
- V-224056
- V-98819
- Rule IDs
-
- SV-224056r877896_rule
- SV-107923
Checks: C-25729r877894_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. If the following items are in effect for the configuration statements specified in the TCP/IP Profile configuration file, this is not a finding. NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. -The SMFPARMS statement is not coded or commented out. -The DELETE statement is not coded or commented out for production systems. -The SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands. -The TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand. If the TCPCONFIG does not have the TTLS statement coded, this is a finding. NOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance.
Fix: F-25717r877895_fix
Ensure the following items are in effect for the configuration statements specified in the TCP/IP Profile configuration file: NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. -The SMFPARMS statement is not coded or commented out. -The DELETE statement is not coded or commented out for production systems. -The SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands. -The TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand. NOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance in STIG ID ITCP0070. BASE TCP/IP PROFILE.TCPIP CONFIGURATION STATEMENTS FUNCTIONS INCLUDE- Specifies the name of an MVS data set that contains additional PROFILE.TCPIP statements to be used - Alters the configuration specified by previous statements SMFPARMS- Specifies SMF logging options for some TCP applications; replaced by SMFCONFIG - Controls collection of audit data DELETE- Specifies some previous statements, including PORT and PORTRANGE, that are to be deleted - Alters the configuration specified by previous statements SMFCONFIG- Specifies SMF logging options for Telnet, FTP, TCP, API, and stack activity - Controls collection of audit data TCPCONFIG- Specifies various settings for the TCP protocol layer of TCP/IP - Controls port access TCPCONFIG coded with TTLS - Specifies that the AT-TLS function is activated for the TCP/IP stack. The AT-TLS function provides invocation of System SSL in the TCP transport layer of the stack. Note: If AT-TLS is enabled, you must activate the SERVAUTH class, define the INITSTACK resource profile, and permit users to it. NOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-TC-000020
- Vuln IDs
-
- V-224057
- V-98821
- Rule IDs
-
- SV-224057r877897_rule
- SV-107925
Checks: C-25730r516570_chk
From the ISPF Command Shell enter: omvs At the input line enter: cd /etc enter ls -alW If the following File permission and user Audit Bits are true this is not a finding. /etc/hosts 0744 faf /etc/protocol 0744 faf /etc/resolv.conf 0744 faf /etc/services 0740 faf cd /usr ls -alW If the following file permission and user Audit Bits are true this is not a finding. /usr/lpp/tcpip/sbin 0755 faf /usr/lpp/tcpip/bin 0755 faf Notes: Some of the files listed above are not used in every configuration. The absence of a file is not considered a finding. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25718r516571_fix
With the assistance of a systems programmer with UID(0) and/or SUPERUSER access, configure the UNIX permission bits and user audit bits on the HFS directories and files for the FTP Server to conform to the specifications in the table below: BASE TCP/IP HFS Object Security Settings File Permission Bits User Audit Bits /etc/hosts 0744 faf /etc/protocol 0744 faf /etc/resolv.conf 0744 faf /etc/services 0740 faf /usr/lpp/tcpip/sbin 0755 faf /usr/lpp/tcpip/bin 0755 faf Some of the files listed above (e.g., /etc/resolv.conf) are not used in every configuration. While the absence of a file is generally not a security issue, the existence of a file that has not been properly secured can often be an issue. Therefore, all directories and files that do exist will have the specified permission and audit bit settings. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing The following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 0744 /etc/hosts chaudit w=sf,rx+f /etc/hosts chmod 0744 /etc/protocol chaudit w=sf,rx+f /etc/protocol chmod 0744 /etc/resolv.conf chaudit w=sf,rx+f /etc/resolv.conf chmod 0740 /etc/services chaudit w=sf,rx+f /etc/services chmod 0755 /usr/lpp/tcpip/bin chaudit w=sf,rx+f /usr/lpp/tcpip/bin chmod 0755 /usr/lpp/tcpip/sbin chaudit w=sf,rx+f /usr/lpp/tcpip/sbin
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-TC-000030
- Vuln IDs
-
- V-224058
- V-98823
- Rule IDs
-
- SV-224058r877898_rule
- SV-107927
Checks: C-25731r869008_chk
If the following guidance is true, this is not a finding. -The EZA, EZB, and IST resources of the SERVAUTH resource class are properly owned and/or DEFPROT is specified in the SERVAUTH resource class. -No access is given to the EZA, EZB, and IST high level resources of the SERVAUTH resource class. -If the product CSSMTP is on the system, no access is given to EZB.CSSMTP of the SERVAUTH resource class. -If the product CSSMTP is on the system, EZB.CSSMTP.sysname.writername.JESnode will be specified and made available to the CSSMTP started task and authenticated users that require access to use CSSMTP for e-mail services. -Authenticated users that require access will be permitted access to the second level of the resources in the SERVAUTH resource class. Examples are the network (NETACCESS), port (PORTACCESS), stack (STACKACCESS), and FTP resources in the SERVAUTH resource class. -The EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements. -The EZB.FTP.*.*.ACCESS.HFS) resource access authorizations restrict access to FTP users with specific written documentation showing a valid requirement exists to access OMVS files and directories. -The EZB.INITSTACK.sysname.tcpname resource access authorizations restrict access before policies have been installed, to users authorized by the system security plan requiring access to the TCP/IP stack.
Fix: F-25719r869009_fix
Develop a plan of action to implement the required changes. Ensure the following items are in effect for TCP/IP resources. 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. -Ensure that the EZA, EZB, and IST resources of the SERVAUTH resource class are properly owned and/or DEFPROT is specified in the SERVAUTH resource class. -No access is given to the EZA, EZB, and IST resources of the SERVAUTH resource class. -If the product CSSMTP is on the system, no access is given to EZB.CSSMTP of the SERVAUTH resource class. EZB.CSSMTP.sysname.writername.JESnode will be specified and made available to the CSSMTP started task and authenticated users that require access to use CSSMTP for e-mail services. -Only authenticated users that require access are permitted access to the second level of the resources in the SERVAUTH resource class. Examples are the network (NETACCESS), port (PORTACCESS), stack (STACKACCESS), and FTP resources in the SERVAUTH resource class. -The EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements. -The EZB.FTP.*.*.ACCESS.HFS) resource access authorizations restrict access to FTP users with specific written documentation showing a valid requirement exists to access OMVS files and Directories. The EZB.INITSTACK.sysname.tcpname resource access authorizations restrict access to TCP/IP stack before policies have been installed to users authorized by the system security plan. The following commands are provided as a sample for implementing resource controls: TSS ADD(ADMIN) SERVAUTH(EZB) or TSS REPLACE(RDT) RESCLASS(SERVAUTH) ATTR(DEFPROT) TSS PER(authusers) SERVAUTH(EZB.CSSMTP.sysname.writername.JESnode) ACCESS(READ) TSS PER(authusers) SERVAUTH(EZB.FTP.) ACCESS(READ) TSS PER(ftpprofile)SERVAUTH(EZB.FTP.sysname.ftpstc.ACCESS.HFS)ACC(READ) TSS PER(authusers) SERVAUTH(EZB.NETACCESS.) ACCESS(READ) TSS PER(authusers) SERVAUTH(EZB.PORTACCESS.) ACCESS(READ) TSS PER(authusers) SERVAUTH(EZB.STACKACCESS.) ACCESS(READ) TSS PER(authusers) SERVAUTH(EZB.INITSTACK.) ACCESS(READ) TSS PER(ftpprofile)SERVAUTH(EZB.STACKACCESS.sysname.TCPIP)ACC(READ)
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-TC-000040
- Vuln IDs
-
- V-224059
- V-98825
- Rule IDs
-
- SV-224059r877899_rule
- SV-107929
Checks: C-25732r516576_chk
Execute a data set access list for all TCP/IP base components. If all of the following items are true, this is not a finding. WRITE and ALLOCATE access to product data sets is restricted to systems programming personnel (i.e., SMP/E distribution data sets with the prefix SYS1.TCPIP.AEZA and target data sets with the prefix SYS1.TCPIP.SEZA). WRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is restricted to systems programming personnel. Note: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same access authorization requirements. WRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is logged. Note: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same logging requirements. WRITE and ALLOCATE access to the data set(s) containing the configuration files shared by TCP/IP applications is restricted to systems programming personnel. Note: For systems running the TSS ACP replace the WRITE and ALLOCATE with WRITE, UPDATE, CREATE, CONTROL, SCRATCH, and ALL.
Fix: F-25720r516577_fix
Review the data set access authorizations defined to the ACP for the Base TCP/IP component. Configure these data sets to be protected in accordance with the following rules: WRITE and ALLOCATE access to product data sets is restricted to systems programming personnel (i.e., SMP/E distribution data sets with the prefix SYS1.TCPIP.AEZA and target data sets with the prefix SYS1.TCPIP. SEZA). WRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is restricted to systems programming personnel. Note: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same access authorization requirements. WRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is logged. Note: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same logging requirements. WRITE and ALLOCATE access to the data set(s) containing the configuration files shared by TCP/IP applications is restricted to systems programming personnel. Note: For systems running the TSS ACP replace the WRITE and ALLOCATE with WRITE, UPDATE, CREATE, CONTROL, SCRATCH, and ALL.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-TC-000050
- Vuln IDs
-
- V-224060
- V-98827
- Rule IDs
-
- SV-224060r877900_rule
- SV-107931
Checks: C-25733r869011_chk
Refer to the procedure libraries defined to JES2 and locate the TCPIP JCL member. Note: If GLOBALTCPIPDATA is specified, any TCPIP.DATA statements contained in the specified file or data set take precedence over any TCPIP.DATA statements found using the appropriate environment's (native MVS or z/OS UNIX) search order. If GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA. If the PROFILE and SYSTCPD DD statements specify the TCP/IP Profile and Data configuration files respectively, this not a finding. If the RESOLVER_CONFIG variable on the EXEC statement is set to the same file name specified on the SYSTCPD DD statement, this is not a finding.
Fix: F-25721r869012_fix
Review the TCP/IP started task JCL to ensure the configuration file names are specified on the appropriate DD statements and parameter option. During initialization, the TCP/IP stack uses fixed search sequences to locate the PROFILE.TCPIP and TCPIP.DATA files. However, uncertainty is reduced and security auditing is enhanced by explicitly specifying the locations of the files. In the TCP/IP started task's JCL, Data Definition (DD) statements can be used to specify the locations of the files. The PROFILE DD statement identifies the PROFILE.TCPIP file and the SYSTCPD DD statement identifies the TCPIP.DATA file. The location of the TCPIP.DATA file can also be specified by coding the RESOLVER_CONFIG environment variable as a parameter of the ENVAR option in the TCP/IP started task's JCL. In fact, the value of this variable is checked before the SYSTCPD DD statement by some processes. However, not all processes (e.g., TN3270 Telnet Server) will access the variable to get the file location. Therefore, specifying the file location explicitly, both on a DD statement and through the RESOLVER_CONFIG environment variable, reduces ambiguity. Note: If GLOBALTCPIPDATA is specified, any TCPIP.DATA statements contained in the specified file or data set take precedence over any TCPIP.DATA statements found using the appropriate environment's (native MVS or z/OS UNIX) search order. If GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA. The systems programmer responsible for supporting ICS will ensure that the TCP/IP started task's JCL specifies the PROFILE and SYSTCPD DD statements for the PROFILE.TCPIP and TCPIP.DATA configuration files and TCP/IP started task's JCL includes the RESOLVER_CONFIG variable, set to the name of the file specified on the SYSTCPD DD statement.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-TC-000060
- Vuln IDs
-
- V-224061
- V-98829
- Rule IDs
-
- SV-224061r877901_rule
- SV-107933
Checks: C-25734r869014_chk
Refer to system Proclibs to determine the TCPIP address space(s). From the ISPF Command Shell enter: TSS list(<TCPIP STCs>) SEGMENT(OMVS) For each TCPIP: If all of the following items are true, this is not a finding. If any item is untrue, this is a finding. From the ISPF Command Shell enter TSS LIST(EZAZSSI) SEGMENT(OMVS) If EZAZSSI STC has the STC facility, this is not finding. -Named TCPIP or, in the case of multiple instances, prefixed with TCPIP. -Has the STC facility. -z/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh Ensure the following items are in effect for the ACID assigned to the EZAZSSI started task: -Named EZAZSSI -Has the STC facility.
Fix: F-25722r869015_fix
Develop a plan of action to implement the required changes. Ensure the following items are in effect for the ACID(s) assigned to the TCP/IP address space(s): 1) Named TCPIP or, in the case of multiple instances, prefixed with TCPIP 2) Has the STC facility 3) z/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh Ensure the following items are in effect for the ACID assigned to the EZAZSSI started task: 1) Named EZAZSSI 2) Has the STC facility For example: The following commands can be used to create the user accounts and assign the privileges that are required for the TCP/IP address space and the EZAZSSI started task: TSS CREATE(TCPIP) TYPE(USER) NAME(TCPIP) DEPT(existing-dept) FACILITY(STC) PASSWORD(password,0) TSS ADD(TCPIP) DFLTGRP(STCTCPX) GROUP(STCTCPX) TSS ADD(TCPIP) SOURCE(INTRDR) TSS ADD(TCPIP) UID(0) HOME(/) OMVSPGM(/bin/sh) TSS ADD(TCPIP) MASTFAC(TCP) TSS ADD(STC) PROCNAME(TCPIP) ACID(TCPIP) TSS PERMIT(TCPIP) IBMFAC(BPX.DAEMON) ACCESS(READ) TSS CREATE(EZAZSSI) TYPE(USER) NAME(EZAZSSI) DEPT(existing-dept) FACILITY(STC) PASSWORD(password,0) TSS ADD(EZAZSSI) DFLTGRP(STCTCPX) GROUP(STCTCPX) TSS ADD(EZAZSSI) SOURCE(INTRDR) TSS ADD(EZAZSSI) UID(non-zero) HOME(/) OMVSPGM(/bin/sh) TSS ADD(EZAZSSI) MASTFAC(TCP) TSS ADD(STC) PROCNAME(EZAZSSI) ACID(EZAZSSI)
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-002314
- Version
- TSS0-TC-000070
- Vuln IDs
-
- V-224062
- V-98831
- Rule IDs
-
- SV-224062r877902_rule
- SV-107935
Checks: C-25735r516585_chk
Refer the TCPIP PROFILE DD statement to determine the TCP/IP Ports. If the PROFILE DD statement is not supplied use the default search order to find thee PROFILE data set. See the IP Configuration Guide for a description of the search order for PROFILE.TCPIP. If the all the Ports included into the configuration are restricted to the ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments, this is not a finding.
Fix: F-25723r516586_fix
Configure TCP/IP PROFILE port definitions to adhere to ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- TSS0-TN-000010
- Vuln IDs
-
- V-224065
- V-98837
- Rule IDs
-
- SV-224065r877903_rule
- SV-107941
Checks: C-25738r516594_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TN3270 started task JCL. If all USS tables referenced in BEGINVTAM USSTCP statements include MSG10 text that specifies the Standard logon banner this is not a finding. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. DOD requires that a logon warning banner be displayed. Within the TN3270 Telnet Server, the banner can be implemented through the USS table that is specified on a BEGINVTAM USSTCP statement. The text associated with message ID 10 (i.e., MSG10) in the USS table is sent to clients that are subject to USSTCP processing.
Fix: F-25726r516595_fix
Review all USS tables referenced in BEGINVTAM USSTCP statements in the PROFILE.TCPIP file. Ensure the MSG10 text specifies a logon banner in accordance with DISA requirements. See MGG10 below: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. DOD requires that a logon warning banner be displayed. Within the TN3270 Telnet Server, the banner can be implemented through the USS table that is specified on a BEGINVTAM USSTCP statement. The text associated with message ID 10 (i.e., MSG10) in the USS table is sent to clients that are subject to USSTCP processing.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-TN-000020
- Vuln IDs
-
- V-224066
- V-98839
- Rule IDs
-
- SV-224066r877904_rule
- SV-107943
Checks: C-25739r516597_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. If the following configuration statement settings are in effect in the TCP/IP Profile configuration data set, this is not a finding. NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration data set, the data set specified on this statement must be checked for the following items as well. -The TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block. -The TELNETPARMS SMFTERM statement is coded with the TYPE119 operand within each TELNETPARMS statement block. Note: The SMFINIT and SMFTERM statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks. If duplicate statements appear in the TELNETGLOBALS, TELNETPARMS, Telnet uses the last valid statement that was specified.
Fix: F-25727r516598_fix
Code TN3270 configuration file to the requirements specified below. NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. -The TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block. -The TELNETPARMS SMFTERM statement is coded with the TYPE119 operand within each TELNETPARMS statement block. NOTE: Effective in z/OS release 1.2, the SMFINIT and SMFTERM statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000068
- Version
- TSS0-TN-000030
- Vuln IDs
-
- V-224067
- V-98841
- Rule IDs
-
- SV-224067r877905_rule
- SV-107945
Checks: C-25740r516600_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. If the following items are in effect for the configuration specified in the TCP/IP Profile configuration file, this is not a finding. NOTE: If an INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. NOTE: FIPS 140-2 minimum encryption is the accepted level of encryption and will override this requirement if greater. -The TELNETGLOBALS block that specifies an ENCRYPTION statement states one or more of the below cipher specifications. -Each TELNETPARMS block that specifies the SECUREPORT statement, specifies an ENCRYPTION statement states one or more of the below cipher specifications. And the TELNETGLOBALS block does or does not specify an ENCRYPTION statement. Cipher Specifications SSL_3DES_SHA SSL_AES_256_SHA SSL_AES_128_SHA
Fix: F-25728r516601_fix
Configure the SECUREPORT and TELNETPARMS ENCRYPTION statements and/or the TELNETGLOBALS statement in the PROFILE.TCPIP file to conform to the requirements specified below. The TELNETGLOBALS block may specify an ENCRYPTION statement that specifies one or more of the below cipher specifications. Each TELNETPARMS block that specifies the SECUREPORT statement, an ENCRYPTION statement is coded with one or more of the below cipher specifications. And the TELNETGLOBALS block does or does not specify an ENCRYPTION statement. To prevent the use of non FIPS 140-2 encryption, the TELNETGLOBALS block and/or each TELNETPARMS block that specifies an ENCRYPTION statement will specify one or more of the following cipher specifications: Cipher Specifications SSL_3DES_SHA SSL_AES_256_SHA SSL_AES_128_SHA Note: Always check for the minimum allowed in FIPS 140-2.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-TN-000040
- Vuln IDs
-
- V-224068
- V-98843
- Rule IDs
-
- SV-224068r877906_rule
- SV-107947
Checks: C-25741r516603_chk
Refer to the TN3270 Profile configuration file identified by the PROFILE DD in the TN3270 procedure. NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. If all of the following are true, this is not a finding. If any of the above is untrue, this is a finding. -Within each BEGINVTAM statement block, one BEGINVTAM USSTCP statement is coded that specifies only the table name operand. No client identifier, such as host name or IP address, is specified so the statement applies to all connections not otherwise controlled. -The USS table specified on each "back stop" USSTCP statement mentioned in Item (1) above is coded to allow access only to session manager applications and NC PASS applications. -Within each BEGINVTAM statement block, additional BEGINVTAM USSTCP statements that specify a USS table that allows access to other applications may be coded only if the statements include a client identifier operand that references only secure terminals. -Any BEGINVTAM DEFAULTAPPL statement that does not specify a client identifier, or specifies any type of client identifier that would apply to unsecured terminals, specifies a session manager application or an NC PASS application as the application name. -Any BEGINVTAM LUMAP statement, if used with the DEFAPPL operand and applied to unsecured terminals, specifies only a session manager application or an NC PASS application. NOTE: The BEGINVTAM LINEMODEAPPL requirements will not be reviewed at this time. Further testing must be performed to determine how the CL/Supersession and NC-PASS applications work with line mode.
Fix: F-25729r516604_fix
Review the BEGINVTAM configuration statements in the PROFILE.TCPIP file. Ensure they conform to the specifications below. NOTE: If the INCLUDE statement is coded in the TN3270 Profile configuration file, the data set specified on this statement must be checked for the following items as well. Within each BEGINVTAM statement block, one BEGINVTAM USSTCP statement is coded that specifies only the table name operand. No client identifier, such as host name or IP address, is specified so the statement applies to all connections not otherwise controlled. The USS table specified on each "back stop" USSTCP statement mentioned above is coded to allow access only to session manager applications and NC PASS applications. Within each BEGINVTAM statement block, additional BEGINVTAM USSTCP statements that specify a USS table that allows access to other applications may be coded only if the statements include a client identifier operand that references only secure terminals. Any BEGINVTAM DEFAULTAPPL statement that does not specify a client identifier, or specifies any type of client identifier that would apply to unsecured terminals, specifies a session manager application or an NC PASS application as the application name.
- RMF Control
- SC-10
- Severity
- Medium
- CCI
- CCI-001133
- Version
- TSS0-TN-000050
- Vuln IDs
-
- V-224069
- V-98845
- Rule IDs
-
- SV-224069r877907_rule
- SV-107949
Checks: C-25742r516606_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. TELNETPARMS Block (one defined for each port the server is listening to, typically ports 23 and 992) If the TELNETPARMS INACTIVE statement is coded within each TELNETPARMS statement block and specifies a value between "1" and "900", this is not a finding. NOTE: Effective in z/OS release 1.2, the INACTIVE statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks.
Fix: F-25730r516607_fix
Configure the configuration statements in the PROFILE.Tn3270 to conform to the specifications below: NOTE: If the INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. The TELNETPARMS INACTIVE statement is coded either within the TELNETGLOBALS or within each TELNETPARMS statement block and specifies a value between "1" and "900".
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-001384
- Version
- TSS0-TN-000060
- Vuln IDs
-
- V-224070
- V-98847
- Rule IDs
-
- SV-224070r877908_rule
- SV-107951
Checks: C-25743r516609_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TN3270 started task JCL. If all USS tables referenced in BEGINVTAM USSTCP statements include MSG10 text that specifies the Standard logon banner, this is not a finding. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. DOD requires that a logon warning banner be displayed. Within the TN3270 Telnet Server, the banner can be implemented through the USS table that is specified on a BEGINVTAM USSTCP statement. The text associated with message ID 10 (i.e., MSG10) in the USS table is sent to clients that are subject to USSTCP processing.
Fix: F-25731r516610_fix
Review all USS tables referenced in BEGINVTAM USSTCP statements in the PROFILE.TCPIP file. Ensure the MSG10 text specifies a logon banner in accordance with DISA requirements. See MGG10 below: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. DOD requires that a logon warning banner be displayed. Within the TN3270 Telnet Server, the banner can be implemented through the USS table that is specified on a BEGINVTAM USSTCP statement. The text associated with message ID 10 (i.e., MSG10) in the USS table is sent to clients that are subject to USSTCP processing.
- RMF Control
- SC-8
- Severity
- Medium
- CCI
- CCI-002420
- Version
- TSS0-TN-000070
- Vuln IDs
-
- V-224071
- V-98849
- Rule IDs
-
- SV-224071r877909_rule
- SV-107953
Checks: C-25744r516612_chk
Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL. If the following items are in effect for the configuration specified in the TCP/IP Profile configuration file, this is not a finding. NOTE: If an INCLUDE statement is coded in the TCP/IP Profile configuration file, the data set specified on this statement must be checked for the following items as well. NOTE: FIPS 140-2 minimum encryption is the accepted level of encryption and will override this requirement if greater. -The TELNETGLOBALS block that specifies an ENCRYPTION statement states one or more of the below cipher specifications. -Each TELNETPARMS block that specifies the SECUREPORT statement, specifies an ENCRYPTION statement states one or more of the below cipher specifications. And the TELNETGLOBALS block does or does not specify an ENCRYPTION statement. Cipher Specifications SSL_3DES_SHA SSL_AES_256_SHA SSL_AES_128_SHA
Fix: F-25732r516613_fix
Configure the SECUREPORT and TELNETPARMS ENCRYPTION statements and/or the TELNETGLOBALS statement in the PROFILE.TCPIP file to conform to the requirements specified below. The TELNETGLOBALS block may specify an ENCRYPTION statement that specifies one or more of the below cipher specifications. Each TELNETPARMS block that specifies the SECUREPORT statement, an ENCRYPTION statement is coded with one or more of the below cipher specifications. And the TELNETGLOBALS block does or does not specify an ENCRYPTION statement. To prevent the use of non FIPS 140-2 encryption, the TELNETGLOBALS block and/or each TELNETPARMS block that specifies an ENCRYPTION statement will specify one or more of the following cipher specifications: Cipher Specifications SSL_3DES_SHA SSL_AES_256_SHA SSL_AES_128_SHA Note: Always check for the minimum allowed in FIPS 140-2.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-TS-000010
- Vuln IDs
-
- V-224072
- V-98851
- Rule IDs
-
- SV-224072r877910_rule
- SV-107955
Checks: C-25745r516615_chk
From the ISPF Command Shell enter: TSS WHOOWNS TSOAUTH(*) For each resource defined enter: TSS WHOHAS(<tsoauth resource>) If the following guidance is true, this is not a finding. -The ACCT authorization is restricted to security personnel. -The CONSOLE authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.) and READ access may be given to all user when SDSF in install at the ISSOs discretion. -The MOUNT authorization is restricted to DASD batch users only. -The OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.). -The PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to auditors. -The TESTAUTH authorization is restricted to only z/OS systems programming personnel.
Fix: F-25733r869017_fix
Configure the TSOAUTH resource class to control sensitive TSO/E commands. Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, 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. Below is listed the access requirements for TSOAUTH resources. Ensure the guidelines for the resources and/or generic equivalent are followed. -The ACCT authorization is restricted to security personnel. -The CONSOLE authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.) and READ access may be given to all user when SDSF in install at the ISSOs discretion. -The MOUNT authorization is restricted to DASD batch users only. -The OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.). -The PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to audit users. -The TESTAUTH authorization is restricted to only z/OS systems programming personnel.
- RMF Control
- AC-6
- Severity
- High
- CCI
- CCI-002235
- Version
- TSS0-TS-000020
- Vuln IDs
-
- V-224073
- V-98853
- Rule IDs
-
- SV-224073r877911_rule
- SV-107957
Checks: C-25746r516618_chk
Ask the system administrator to provide a list of all emergency userids available to the site along with the associated function of each. If any SYS1.UADS userids are assigned for other than emergency purposes, this is a finding.
Fix: F-25734r516619_fix
Configure the SYS1.UADS entries to ensure LOGONIDs defined include only those users required to support specific functions related to system recovery. Evaluate the impact of accomplishing the change.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-US-000010
- Vuln IDs
-
- V-224074
- V-98855
- Rule IDs
-
- SV-224074r877912_rule
- SV-107959
Checks: C-25747r516621_chk
Refer to the logical parmlib data sets, example: SYS1.PARMLIB(BPXPRMxx), for the following FILESYSTYPE entry: FILESYSTYPE TYPE(AUTOMNT) ENTRYPOINT(BPXTAMD) If the above entry is not found or is commented out in the BPXPRMxx member(s), this is not applicable. From the ISPF Command Shell enter: OMVS cd /etc cat auto.master perform a contents list for the file identified Example: cat u.map Note: The /etc/auto.master HFS file (and the use of Automount) is optional. If the file does not exist, this is not applicable. Note: The setuid parameter and the security parameter have a significant security impact. For this reason these parameters must be explicitly specified and not allowed to default. If each MapName file specifies the "setuid No" and "security Yes" statements for each automounted directory, this is not a finding. If there is any deviation from the required values, this is a finding.
Fix: F-25735r516622_fix
Review the settings in /etc/auto.master and /etc/mapname for z/OS UNIX security parameters and configure the values to conform to the specifications below. The /etc/auto.master HFS file (and the use of Automount) is optional. The setuid parameter and the security parameter have a significant security impact. For this reason these parameters must be explicitly specified and not be allowed to default. Each MapName file will specify the "setuid NO" and "security YES" statements for each automounted directory. If there is a deviation from the required values, documentation must exist for the deviation. "Security NO" disables security checking for file access. "Security NO" is only allowed on test and development domains. "Setuid YES" allows a user to run under a different UID/GID identity. Justification documentation is required to validate the use of "setuid YES".
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000140
- Version
- TSS0-US-000020
- Vuln IDs
-
- V-224075
- V-98857
- Rule IDs
-
- SV-224075r877913_rule
- SV-107961
Checks: C-25748r516624_chk
Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member in SYS1.PARMLIB. If NOBUFFS is set to "HALT", this is not a finding. Note: If availability is an overriding concern NOBUFFS can be set to MSG.
Fix: F-25736r516625_fix
Configure NOBUFFS to "HALT" unless availability is an overriding concern then NOBUFFS can be set to MSG.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000030
- Vuln IDs
-
- V-224076
- V-98859
- Rule IDs
-
- SV-224076r877914_rule
- SV-107963
Checks: C-25749r516627_chk
From the ISPF Command Shell enter: TSS WHOOWNS IBMFAC(BPX.) If the BPX. resource is properly owned, this is not a finding. From the ISPF Command Shell enter: TSS WHOHAS (<each BPX resource>) If any item below are untrue, this is a finding. -There are no TSS rules that allow access to the BPX resource. -There are no TSS rules for BPX.SAFFASTPATH defined. -The TSS rules for each of the BPX resources listed in the z/OS UNIX System Services Planning, Establishing UNIX security, restrict access to appropriate system tasks or systems programming personnel.
Fix: F-25737r516628_fix
Because they convey especially powerful privileges, the settings for BPX.DAEMON, BPX.SAFFASTPATH, BPX.SERVER, and BPX.SUPERUSER require special attention. Review the following items for the IBMFAC resource class: -The TSS owner defined for the BPX resource. -There are no TSS rules that allow access to the BPX resource. -There are no TSS rules for BPX.SAFFASTPATH defined. The TSS rules for each of the BPX resources listed in General Facility Class BPX Resources Table, in the z/OS UNIX System Services Planning, Establishing UNIX security restrict access to appropriate system tasks or systems programming personnel. Access can be permitted only to users with a requirement for the resource that is documented to the ISSO. Access to BPX.DAEMON must be restricted to the z/OS UNIX kernel userid, z/OS UNIX daemons (e.g., inetd, syslogd, ftpd), and other system software daemons (e.g., web servers). When BPX.SAFFASTPATH is defined, calls to the ACP are not performed for file accesses and there is no audit trail of access failures. This configuration is unacceptable. Therefore BPX.SAFFASTPATH must not be used on any system. For Example: The following commands can be used to provide the required protection: TSS ADD(ADMIN) IBMFAC(BPX.) TSS PERMIT(ALL) IBMFAC(BPX.SAFFASTPATH) ACCESS(NONE) NOTE: The PERMIT command for BPX.SAFFASTPATH must be executed on TOP SECRET systems. If access to BPX.SAFFSTPATH were allowed, z/OS UNIX would perform permission bit checking internally instead of calling the ACP. On TOP SECRET systems this would bypass any audit trail of violations. In addition, the z/OS UNIX kernel userid (OMVS is the example in this section) must not have the TOP SECRET NORESCHK privilege. Having that privilege would allow access to BPX.SAFFASTPATH even though the access restriction was in place.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000040
- Vuln IDs
-
- V-224077
- V-98861
- Rule IDs
-
- SV-224077r877915_rule
- SV-107965
Checks: C-25750r856139_chk
From the ISPF Command Shell enter: TSS WHOOWNS SURROGAT(*) If the TSS resources and/or generic equivalent for BPX. is not owned enter: TSS LIST RDT If the TSS resources and/or generic equivalent for BPX. is not owned or DEFPROT is specified for the resource class, this is a finding. From the ISPF Command Shell enter: TSS WHOHAS SURROGAT(BPX.) If the TSS resource access authorizations restrict BPX.SRV.user to system software processes (e.g., web servers) that act as servers under z/OS UNIX, this is not a finding. If the RACF rules for all BPX.SRV.user SURROGAT resources restrict access to authorized users identified in the Site Security Plan, this is not a finding.
Fix: F-25738r856140_fix
Ensure that BPX. SRV.userid resources are properly protected and access is restricted to appropriate system tasks or systems programming personnel. SURROGAT class BPX resources are used in conjunction with server applications that are performing tasks on behalf of client users that may not supply an authenticator to the server. This can be the case when clients are otherwise validated or when the requested service is performed from userids representing groups. Ensure there is a TSS owner defined for the (BPX.) SURROGAT class resource. For Example: TSS ADD(dept) SURROGAT(BPX.) Ensure the TSS rules for all BPX.SRV.user SURROGAT resources restrict access to system software processes (e.g., web servers) that act as servers under z/OS UNIX and to users whose access and approval are identified in the Site Security Plan. For Example: TSS PERMIT(<websrv>) SURROGAT(BPX.SRV.<webadm>) ACCESS(READ)
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-US-000050
- Vuln IDs
-
- V-224078
- V-98863
- Rule IDs
-
- SV-224078r877916_rule
- SV-107967
Checks: C-25751r516633_chk
From the ISPF Command Shell enter: TSS WHOOWNS UNIXPRIV(*) If the TSS resources and/or generic equivalent for SUPERUSER. is not owned enter: TSS LIST RDT If the TSS resources and/or generic equivalent for SUPERUSER. is not owned or DEFPROT is specified for the resource class, this is a finding. From the ISPF Command Shell enter: TSS WHOHAS SURROGAT(SUPERUSER.) If the TSS resource access authorizations restrict BPX.SRV.user to system software processes (e.g., web servers) that act as servers under z/OS UNIX, this is not a finding.
Fix: F-25739r516634_fix
Ensure that all SUPERUSER resources for the UNIXPRIV resource class are restricted to appropriate system tasks and/or system programming personnel. Review the following items for the UNIXPRIV resource class: -The TSS owner defined for the SUPERUSER resource. -There are no TSS rules that allow access to the SUPERUSER resource. -There is no TSS rule for CHOWN.UNRESTRICTED defined. -The TSS rules for each of the SUPERUSER resources listed in the z/OS UNIX System Services Planning, Establishing UNIX security, restrict access to appropriate system tasks or systems programming personnel.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000060
- Vuln IDs
-
- V-224079
- V-98865
- Rule IDs
-
- SV-224079r877917_rule
- SV-107969
Checks: C-25752r516636_chk
Refer to the proper BPXPRMxx member in SYS1.PARMLIB If the ESM data set rules for the data sets referenced in the ROOT and the MOUNT statements in BPXPRMxx restrict update access to the z/OS UNIX kernel (i.e., OMVS or OMVSKERN), this is not a finding. If the ESM data set rules for the data set referenced in the ROOT and the MOUNT statements in BPXPRMxx restrict WRITE or greater access to systems programming personnel, this is not a finding.
Fix: F-25740r516637_fix
Review the access authorizations defined in the ACP for the MVS data sets that contain operating system components and for the MVS data sets that contain HFS file systems and ensure that they conform to the specifications below. Review the UNIX permission bits on the HFS directories and files and ensure that they conform to the specifications below: Define ESM data set rules for the data sets referenced in the ROOT and the MOUNT statements in BPXPRMxx to restrict update access to the z/OS UNIX kernel (i.e., OMVS or OMVSKERN). Define ESM data set rules for the data sets referenced in the ROOT and the MOUNT statements in BPXPRMxx to restrict WRITE or greater access to systems programming personnel.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000070
- Vuln IDs
-
- V-224080
- V-98867
- Rule IDs
-
- SV-224080r877918_rule
- SV-107971
Checks: C-25753r516639_chk
If the ESM data set rules for each of the data sets listed in the table below restrict WRITE or greater access to systems programming personnel, this is not a finding. MVS DATA SETS WITH z/OS UNIX COMPONENTS DATA SET NAME/MASK MAINTENANCE TYPE FUNCTION SYS1.ABPX* Distribution IBM z/OS UNIX ISPF panels, messages, tables, clists SYS1.AFOM* Distribution IBM z/OS UNIX Application Services SYS1.BPA.ABPA* Distribution IBM z/OS UNIX Connection Scaling Process Mgr. SYS1.CMX.ACMX* Distribution IBM z/OS UNIX Connection Scaling Connection Mgr. SYS1.SBPX* Target IBM z/OS UNIX ISPF panels, messages, tables, clists SYS1.SFOM* Target IBM z/OS UNIX Application Services SYS1.CMX.SCMX* Target IBM z/OS UNIX Connection Scaling Connection Mgr.
Fix: F-25741r869019_fix
Define ESM data set rules for each of the data sets listed in the table below; restrict WRITE or greater access to systems programming personnel. MVS DATA SETS WITH z/OS UNIX COMPONENTS DATA SET NAME/MASK MAINTENANCE TYPE FUNCTION SYS1.ABPX* Distribution IBM z/OS UNIX ISPF panels, messages, tables, clists SYS1.AFOM* Distribution IBM z/OS UNIX Application Services SYS1.BPA.ABPA* Distribution IBM z/OS UNIX Connection Scaling Process Mgr. SYS1.CMX.ACMX* Distribution IBM z/OS UNIX Connection Scaling Connection Mgr. SYS1.SBPX* Target IBM z/OS UNIX ISPF panels, messages, tables, clists SYS1.SFOM* Target IBM z/OS UNIX Application Services SYS1.CMX.SCMX* Target IBM z/OS UNIX Connection Scaling Connection Mgr. The data sets designated as distribution data sets should have all access restricted to systems programming personnel. TSO/E users who also use z/OS UNIX should have read access to the SYS1.SBPX* data sets. Read access for all users to the remaining target data sets is at the site's discretion. All other access must be restricted to systems programming personnel.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000080
- Vuln IDs
-
- V-224081
- V-98869
- Rule IDs
-
- SV-224081r877919_rule
- SV-107973
Checks: C-25754r516642_chk
Refer to the pathname from the STEPLIBLIST line in BPXPRMxx member of PARMLIB. From the ISPF Command shell enter: ISHELL on the command line: on the path name line enter: /etc/ From the resulting display scroll down to the <stepliblist name> from BPXPRMxx parm. Enter B for browse on that line. If ESM data set rules for libraries specified restrict WRITE or greater access to only systems programming personnel, this is not a finding. If the ESM data set rules for libraries specify that all (i.e., failures and successes) WRITE or greater access will be logged, this is not a finding.
Fix: F-25742r516643_fix
Configure the WRITE or greater access to libraries residing in the /etc/steplib to be limited to system programmers only.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000090
- Vuln IDs
-
- V-224082
- V-98871
- Rule IDs
-
- SV-224082r877920_rule
- SV-107975
Checks: C-25755r516645_chk
From the ISPF Command Shell enter: omvs enter CD / enter ls -alW If the HFS permission bits and user audit bits for each directory and file match or are more restrictive than the specified settings listed in the SYSTEM DIRECTORY SECURITY SETTINGS table below, this is not a finding. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing SYSTEM DIRECTORY SECURITY SETTINGS DIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION / [root] 755 faf Root level of all file systems. Holds critical mount points. /bin 1755 fff Shell scripts and executables for basic functions /dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation. Files are created during system IPL and on a per-demand basis. /etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes /lib 1755 fff System libraries including dynamic link libraries and files for static linking /samples 1755 fff Sample configuration and other files /tmp 1777 fff Temporary data used by daemons, servers, and users. Note: /tmp must have the sticky bit on to restrict file renames and deletions. /u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files /usr 1755 fff Shell scripts, executables, help (man) files and other data. Contains sub-directories (e.g., lpp) and mount points used by program products that may be in separate file systems. /var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX.
Fix: F-25743r516646_fix
Configure the UNIX permission bits and user audit bits on each of the HFS directories in the table SYSTEM DIRECTORY SECURITY SETTINGS below to be equal or more restrictive. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing SYSTEM DIRECTORY SECURITY SETTINGS DIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION / [root] 755 faf Root level of all file systems. Holds critical mount points. /bin 1755 fff Shell scripts and executables for basic functions /dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation. Files are created during system IPL and on a per-demand basis. /etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes /lib 1755 fff System libraries including dynamic link libraries and files for static linking /samples 1755 fff Sample configuration and other files /tmp 1777 fff Temporary data used by daemons, servers, and users. Note: /tmp must have the sticky bit on to restrict file renames and deletions. /u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files /usr 1755 fff Shell scripts, executables, help (man) files and other data. Contains sub-directories (e.g., lpp) and mount points used by program products that may be in separate file systems. /var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX. The following commands are a sample of the commands to be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 0755 / chaudit w=sf,rx+f / chmod 0755 /bin chaudit rwx=f /bin
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000100
- Vuln IDs
-
- V-224083
- V-98873
- Rule IDs
-
- SV-224083r877921_rule
- SV-107977
Checks: C-25756r869021_chk
From the ISPF Command Shell enter: OMVS For each file listed in the table below enter: ls -alW /<directory name>/<file name> If the HFS permission bits and user audit bits for each directory and file match or are more restrictive than the specified settings listed in the table, this is not a finding. NOTE: Some of the files listed are not used in every configuration. Absence of any of the files is not considered a finding. SYSTEM FILE SECURITY SETTINGS FILE PERMISSION BITS USER AUDIT BITS FUNCTION /bin/sh 1755 faf z/OS UNIX shell Note: /bin/sh has the sticky bit on to improve performance. /dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention. /dev/null 666 fff A null file; data written to it is discarded. /etc/auto.master any mapname files 740 faf Configuration files for automount facility /etc/inetd.conf 740 faf Configuration file for network services /etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment /etc/log 744 fff Kernel initialization output file /etc/profile 755 faf Environment setup script executed for each user /etc/rc 744 faf Kernel initialization script for z/OS UNIX environment /etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables /etc/table name 740 faf List of z/OS userids and group names with corresponding alias names /usr/lib/cron/at.allow /usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands /usr/lib/cron/cron.allow /usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command NOTE: Some of the files listed are not used in every configuration. Absence of any of the files is not considered a finding. NOTE: The names of the MapName files are site-defined. Refer to the listing in the EAUTOM report. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25744r869022_fix
Define the UNIX permission bits and user audit bits on the HFS files as listed in the table below. SYSTEM FILE SECURITY SETTINGS FILE PERMISSION BITS USER AUDIT BITS FUNCTION /bin/sh 1755 faf z/OS UNIX shell Note: /bin/sh has the sticky bit on to improve performance. /dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention. /dev/null 666 fff A null file; data written to it is discarded. /etc/auto.master any mapname files 740 faf Configuration files for automount facility /etc/inetd.conf 740 faf Configuration file for network services /etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment /etc/log 744 fff Kernel initialization output file /etc/profile 755 faf Environment setup script executed for each user /etc/rc 744 faf Kernel initialization script for z/OS UNIX environment /etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables /etc/table name 740 faf List of z/OS userids and group names with corresponding alias names /usr/lib/cron/at.allow /usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands /usr/lib/cron/cron.allow /usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command There are a number of files that must be secured to protect system functions in z/OS UNIX. Where not otherwise specified, these files must receive a permission setting of 744 or 774. The 774 setting may be used at the site's discretion to help to reduce the need for assignment of superuser privileges. The table identifies permission bit and audit bit settings that are required for these specific files. More restrictive permission settings may be used at the site's discretion or as specific environments dictate. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing The following commands are a sample of the commands to be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 1755 /bin/sh chaudit w=sf,rx+f /bin/sh chmod 0740 /dev/console chaudit rwx=f /dev/console
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000110
- Vuln IDs
-
- V-224084
- V-98875
- Rule IDs
-
- SV-224084r877922_rule
- SV-107979
Checks: C-25757r516651_chk
On the OMVS Command line enter the following command string: find / -type d -perm -0002 ! -perm -1000 -exec ls -aldWE {} \; If there are no directories that have the other write permission bit set on without the sticky bit set on, there is no finding. NOTE: In the symbolic permission bit display, the sticky bit is indicated as a "t" or "T" in the execute portion of the other permissions. For example, a display of the permissions of a directory with the sticky bit on could be "drwxrwxrwt". If all directories that have the other write permission bit set on do not contain any files with the setuid bit set on, this is not a finding. NOTE: In the symbolic permission bit display, the setuid bit is indicated as an "s" or "S" in the execute portion of the owner permissions. For example, a display of the permissions of a file with the setuid bit on could be "-rwsrwxrwx". If all directories that have the other write permission bit set on do not contain any files with the setgid bit set on, this is not a finding. NOTE: In the symbolic permission bit display, the setgid bit is indicated as an "s" or "S" in the execute portion of the group permissions. For example, a display of the permissions of a file with the setgid bit on could be "-rwxrwsrwx".
Fix: F-25745r516652_fix
Configure directory permissions as follows There are no directories that have the other write permission bit set on without the sticky bit set on. NOTE: In the symbolic permission bit display, the sticky bit is indicated as a "t" or "T" in the execute portion of the other permissions. For example, a display of the permissions of a directory with the sticky bit on could be "drwxrwxrwt". All directories that have the other write permission bit set on do not contain any files with the setuid bit set on. NOTE: In the symbolic permission bit display, the setuid bit is indicated as an "s" or "S" in the execute portion of the owner permissions. For example, a display of the permissions of a file with the setuid bit on could be "-rwsrwxrwx". All directories that have the other write permission bit set on do not contain any files with the setgid bit set on. NOTE: In the symbolic permission bit display, the setgid bit is indicated as an "s" or "S" in the execute portion of the group permissions. For example, a display of the permissions of a file with the setgid bit on could be "-rwxrwsrwx".
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- TSS0-US-000120
- Vuln IDs
-
- V-224085
- V-98877
- Rule IDs
-
- SV-224085r877923_rule
- SV-107981
Checks: C-25758r516654_chk
From the ISPF Command Shell enter: TSS MODIFY STATUS If the Control Option is HFSSEC(OFF), this is Not Applicable. Enter: TSS LIST RDT If the DEFPROT attribute is specified for the HFSSEC resource class in the RDT, this is not a finding.
Fix: F-25746r516655_fix
Ensure that the HFSSEC resource class has the attribute DEFPROT. For Example: TSS REPLACE(RDT) RESCLASS(HFSSEC) ATTR(DEFPROT)
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-US-000130
- Vuln IDs
-
- V-224086
- V-98879
- Rule IDs
-
- SV-224086r877924_rule
- SV-107983
Checks: C-25759r869024_chk
Refer to the IEASYS00 member of SYS1.PARMLIB. If the parameter is specified as OMVS=xx or OMVS=(xx,xx,...) in the IEASYSxx member, this is not a finding. If the OMVS statement is not specified, OMVS=DEFAULT is used. In minimum mode there is no access to permanent file systems or to the shell, and IBM's Communication Server TCP/IP will not run.
Fix: F-25747r869025_fix
Configure the settings in PARMLIB and /etc for z/OS UNIX security parameters with values that conform to the specifications below: The parameter is specified as OMVS=xx or OMVS=(xx,xx,...) in the IEASYSxx member. Note: If the OMVS statement is not specified, OMVS=DEFAULT is used. In minimum mode there is no access to permanent file systems or to the shell, and IBM's Communication Server TCP/IP will not run.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-US-000140
- Vuln IDs
-
- V-224087
- V-98881
- Rule IDs
-
- SV-224087r877925_rule
- SV-107985
Checks: C-25760r516660_chk
Refer to the BPXPRM00 member of SYS1.PARMLIB. If the required parameter keywords and values are defined as detailed below, this is not a finding. Parameter Keyword Value SUPERUSER BPXROOT TTYGROUP TTY STEPLIBLIST /etc/steplib USERIDALIASTABLE Will not be specified. ROOT SETUID will be specified MOUNT NOSETUID SETUID (for Vendor-provided files)SECURITY STARTUP_PROC OMVS
Fix: F-25748r516661_fix
Define the settings in PARMLIB member BPXPRMxx for z/OS UNIX security parameters values to conform to the specifications below: Parameter Keyword Value SUPERUSER BPXROOT TTYGROUP TTY STEPLIBLIST /etc/steplib USERIDALIASTABLE Will not be specified. ROOT SETUID will be specified MOUNT NOSETUIDSETUID (for Vendor-provided files)SECURITY STARTUP_PROC OMVS
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000150
- Vuln IDs
-
- V-224088
- V-98883
- Rule IDs
-
- SV-224088r877926_rule
- SV-107987
Checks: C-25761r516663_chk
From the ISPF Command Shell enter: ISHELL /etc/profile If the final or only instance of the UMASK command in /etc/profile is specified as "umask 077", this is not a finding. If the LOGNAME variable is marked read-only (i.e., "readonly LOGNAME") in /etc/profile, this is not a finding.
Fix: F-25749r516664_fix
Configure the etc/profile to specify the UMASK command is executed with a value of 077 and the LOGNAME variable is marked read-only for the /etc/profile file, exceptions are documented with the ISSO.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-US-000160
- Vuln IDs
-
- V-224089
- V-98885
- Rule IDs
-
- SV-224089r877927_rule
- SV-107989
Checks: C-25762r869027_chk
From the ISPF Command Shell enter: ISHELL /etc/rc If all of the CHMOD commands in /etc/rc do not result in less restrictive access than what is specified in the tables below, this is not a finding. NOTE: The use of CHMOD commands in /etc/rc is required in most environments to comply with the required settings, especially for dynamic objects such as the /dev directory. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) If all of the CHAUDIT commands in /etc/rc do not result in less auditing than what is specified in the tables below, this is not a finding. NOTE: The use of CHAUDIT commands in /etc/rc may not be necessary. If none are found, there is not a finding. The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing If the _BPX_JOBNAME variable is appropriately set (i.e., to match daemon name) as each daemon (e.g., syslogd, inetd) is started in /etc/rc, this is not a finding. NOTE: If _BPX_JOBNAME is not specified, the started address space will be named using an inherited value. This could result in reduced security in terms of operator command access. SYSTEM DIRECTORY SECURITY SETTINGS DIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION / [root] 755 faf Root level of all file systems. Holds critical mount points. /bin 1755 fff Shell scripts and executables for basic functions /dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation. Files are created during system IPL and on a per-demand basis. /etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes /lib 1755 fff System libraries including dynamic link libraries and files for static linking /samples 1755 fff Sample configuration and other files /tmp 1777 fff Temporary data used by daemons, servers, and users. Note: /tmp must have the sticky bit on to restrict file renames and deletions. /u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files /usr 1755 fff Shell scripts, executables, help (man) files and other data. Contains sub-directories (e.g., lpp) and mount points used by program products that may be in separate file systems. /var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX. SYSTEM FILE SECURITY SETTINGS FILE PERMISSION BITS USER AUDIT BITS FUNCTION /bin/sh 1755 faf z/OS UNIX shell Note: /bin/sh has the sticky bit on to improve performance. /dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention. /dev/null 666 fff A null file; data written to it is discarded. /etc/auto.master and any mapname files 740 faf Configuration files for automount facility /etc/inetd.conf 740 faf Configuration file for network services /etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment /etc/log 744 fff Kernel initialization output file /etc/profile 755 faf Environment setup script executed for each user /etc/rc 744 faf Kernel initialization script for z/OS UNIX environment /etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables /etc/table name 740 faf List of z/OS userids and group names with corresponding alias names /usr/lib/cron/at.allow /usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands /usr/lib/cron/cron.allow /usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command
Fix: F-25750r869028_fix
Review the settings in the /etc/rc. The /etc/rcfile is the system initialization shell script. When z/OS UNIX kernel services start, /etc/rc is executed to set file permissions and ownership for dynamic system files and to perform other system startup functions such as starting daemons. There can be many commands in /etc/rc. There are two specific guidelines that must be followed: Verify that The CHMOD or CHAUDIT command does not result in less restrictive security than what is specified in the table in the z/OS UNIX System Services Planning, Establishing UNIX security under the SYSTEM DIRECTORY SECURITY SETTINGS. Immediately prior to each command that starts a daemon, the _BPX_JOBNAME variable must be set to match the daemon's name (e.g., inetd, syslogd). The use of _BPX_USERID is at the site's discretion, but is recommended.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-US-000170
- Vuln IDs
-
- V-224090
- V-98887
- Rule IDs
-
- SV-224090r877928_rule
- SV-107991
Checks: C-25763r516669_chk
If the system in not classified this is not applicable. From a command line issue the following command: TSS MODIFY STATUS Note: One must have appropriate access to perform this command (have the site security officer to issue command). If system is classified and UNIQUSER is off i.e., (UNIQUSER(OFF) this is not a finding.
Fix: F-25751r516670_fix
Ensure that Use of the OMVS default UIDs will not be allowed on any classified system. Set Control Option UNIQUSER off.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000382
- Version
- TSS0-US-000180
- Vuln IDs
-
- V-224091
- V-98889
- Rule IDs
-
- SV-224091r877929_rule
- SV-107993
Checks: C-25764r516672_chk
From the UNIX System Services ISPF Shell enter /etc/inetd.conf If any Restricted Network Services that are listed below are specified or not commented out this is a finding. RESTRICTED NETWORK SERVICES/PORTS Service Port Chargen 19 Daytime 13 Discard 9 Echo 7 Exec 512 finger 79 shell 514 time 37 login 513 smtp 25 timed 525 nameserver 42 systat 11 uucp 540 netstat 15 talk 517 qotd 17 tftp 69
Fix: F-25752r516673_fix
Review the settings in The /etc/inetd.conf file determine if every entry in the file represents a service that is actually in use. Services that are not in use must be disabled to reduce potential security exposures. The following services must be disabled in /etc/inetd.conf unless justified and documented with the ISSO: RESTRICTED NETWORK SERVICES Service Port Chargen 19 Daytime 13 Discard 9 Echo 7 Exec 512 finger 79 shell 514 time 37 login 513 smtp 25 timed 525 nameserver 42 systat 11 uucp 540 netstat 15 talk 517 qotd 17 tftp 69 /etc/inetd.conf The /etc/inetd.conf file is used by the INETD daemon. It specifies how INETD is to handle service requests on network sockets. Specifically, there is one entry in inetd.conf for each service. Each service entry specifies several parameters. The login_name parameter is of special interest. It specifies the userid under which the forked daemon is to execute. This userid is defined to the ACP and it may require a UID(0) (i.e., superuser authority) value.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000190
- Vuln IDs
-
- V-224092
- V-98891
- Rule IDs
-
- SV-224092r877930_rule
- SV-107995
Checks: C-25765r869030_chk
A site can choose to have both an OMVSGRP group and an STCOMVS group or combine the groups under one of these names. If OMVSGRP and/or STCOMVS groups are defined and have a unique GID in the range of 1-99, this is not a finding.
Fix: F-25753r869031_fix
Define the OMVSGRP group and/or the STCOMVS group to the security database with a unique GID in the range of 1-99. OMVSGRP is the name suggested by IBM for all the required userids. STCOMVS is the standard name used at some sites for the userids that are associated with z/OS UNIX started tasks and daemons. These groups can be combined at the site's discretion.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000200
- Vuln IDs
-
- V-224093
- V-98893
- Rule IDs
-
- SV-224093r877931_rule
- SV-107997
Checks: C-25766r516678_chk
If OMVS userid is defined to the ESM as follows, this is not a finding. -No access to interactive on-line facilities (e.g., TSO, CICS, etc.) -Default group specified as OMVSGRP or STCOMVS -UID(0) -HOME directory specified as "/" -Shell program specified as "/bin/sh"
Fix: F-25754r516679_fix
Define OMVS userid to the ESM as specified below: -No access to interactive on-line facilities (e.g., TSO, CICS, etc.) -Default group specified as OMVSGRP or STCOMVS -UID(0) -HOME directory specified as "/" -Shell program specified as "/bin/sh"
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000210
- Vuln IDs
-
- V-224094
- V-98895
- Rule IDs
-
- SV-224094r877932_rule
- SV-107999
Checks: C-25767r516681_chk
Refer to system PARMLIB member BPXPRMxx (xx is determined by OMVS entry in IEASYS00.) Determine the user ID identified by the SUPERUSER parameter. (BPXROOT is the default). From a command input screen enter: LISTUSER (superuser userid) TSO CICS OMVS If the SUPERUSER userid is defined as follows, this is not a finding: - No access to interactive on-line facilities (e.g., TSO, CICS, etc.) - Default group specified as OMVSGRP or STCOMVS - UID(0) - HOME directory specified as "/" - Shell program specified as "/bin/sh"
Fix: F-25755r516682_fix
Define the user ID identified in the BPXPRM00 SUPERUSER parameter as specified below: - No access to interactive on-line facilities (e.g., TSO, CICS, etc.) - Default group specified as OMVSGRP or STCOMVS - UID(0) - HOME directory specified as "/" - Shell program specified as "/bin/sh"
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000220
- Vuln IDs
-
- V-224095
- V-98897
- Rule IDs
-
- SV-224095r877933_rule
- SV-108001
Checks: C-25768r516684_chk
RMFGAT is the userid for the Resource Measurement Facility (RMF) Monitor III Gatherer. If RMFGAT is not define this is not applicable. From a command input screen enter: TSS LIST (RMFGAT) DATA ALL If RMFGAT is defined as follows, this is not a finding: -Default group specified as OMVSGRP or STCOMVS -A unique, non-zero UID -HOME directory specified as "/" -Shell program specified as "/bin/sh"
Fix: F-25756r516685_fix
Define RMFGAT user account is defined as specified below: -Default group specified as OMVSGRP or STCOMVS -A unique, non-zero UID -HOME directory specified as "/" -Shell program specified as "/bin/sh"
- RMF Control
- IA-2
- Severity
- High
- CCI
- CCI-000764
- Version
- TSS0-US-000230
- Vuln IDs
-
- V-224096
- V-98899
- Rule IDs
-
- SV-224096r877934_rule
- SV-108003
Checks: C-25769r516687_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) SEGMENT(OMVS) If UID(0) is assigned only to system tasks such as the z/OS/ UNIX kernel (i.e., OMVS), z/OS UNIX daemons (e.g., inetd, syslogd, ftpd), and other system software daemons, this is not a finding. If UID(0) is assigned to security administrators who create or maintain user account definitions; and to systems programming accounts dedicated to maintenance (e.g., SMP/E) of HFS-based components, this is not a finding. NOTE: The assignment of UID(0) confers full time superuser privileges. This is not appropriate for personal user accounts. Access to the BPX.SUPERUSER resource is used to allow personal user accounts to gain short-term access to superuser privileges. If UID(0) is assigned to non-systems or non-maintenance accounts, this is a finding.
Fix: F-25757r516688_fix
Ensure that UID(0) is defined/assigned as specified below: UID(0) is assigned only to system tasks such as the z/OS UNIX kernel (i.e., OMVS), z/OS UNIX daemons (e.g., inetd, syslogd, ftpd), and other system software daemons. UID(0) is assigned to security administrators who create or maintain user account definitions; and to systems programming accounts dedicated to maintenance (e.g., SMP/E) of HFS-based components. NOTE: The assignment of UID(0) confers full time superuser privileges, this is not appropriate for personal user accounts. Access to the BPX.SUPERUSER resource is used to allow personal user accounts to gain short-term access to superuser privileges.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000240
- Vuln IDs
-
- V-224097
- V-98901
- Rule IDs
-
- SV-224097r877935_rule
- SV-108005
Checks: C-25770r516690_chk
NOTE: This only applies to users of z/OS UNIX (i.e., users with an OMVS profile defined). From the ISPF Command Shell enter: TSS LIST(ACIDS) SEGMENT(OMVS) If any user account is not defined as follows, this is a finding. -A unique UID number (except for UID(0) users) -A unique HOME directory (except for UID(0) and other system task accounts) -Shell program specified as "/bin/sh", "/bin/tcsh", "/bin/echo", or "/bin/false" NOTE: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default).
Fix: F-25758r516691_fix
Configure each user account to be defined as specified below: NOTE: This only applies to users of z/OS UNIX (i.e., users with an OMVS profile defined). -A unique UID number (except for UID(0) users) -A unique HOME directory (except for UID(0) and other system task accounts) -Shell program specified as "/bin/sh", "/bin/tcsh", "/bin/echo", or "/bin/false" NOTE: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default).
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-US-000250
- Vuln IDs
-
- V-224098
- V-98903
- Rule IDs
-
- SV-224098r877936_rule
- SV-108007
Checks: C-25771r516693_chk
From the ISPF Command Shell enter: TSS LIST(ACIDS) DATA(NAME) SEGMENT(OMVS) This check applies to any user identifier (ACID) used to model OMVS access on the mainframe. This includes OMVSUSR; MODLUSER, and BPX.UNIQUE.USER. ENTER TSS MODIFY STATUS If ANY MODLUSER is specified then UNIQUSER must be specified as "ON" in the STATUS. If user identifier (ACID) used to model OMVS user account is defined as follows, this is not finding. A non-writable HOME directory Shell program specified as "/bin/echo", or "/bin/false" Note: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default).
Fix: F-25759r516694_fix
Use of the OMVS default UID will not be allowed on any classified system. Define the user identifier (ACID) used to model OMVS user account with a non-writable home directory, such as "\" root, and a non-executable, but existing, binary file, "/bin/false" or "/bin/echo."
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- TSS0-UT-000010
- Vuln IDs
-
- V-224099
- V-98905
- Rule IDs
-
- SV-224099r877939_rule
- SV-108009
Checks: C-25772r877937_chk
From UNIX System Services ISPF Shell, enter path "/etc/otelnet/banner/". If this file does not contain the banner below, check the UNIX System Services ISPF Shell path /etc/banner. If neither file contains the banner below, this is a finding. If the banner below is contained in either, this is not a finding. This banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
Fix: F-25760r877938_fix
Configure the /etc/otelnet/banner file and ensure the text specifies a logon banner in accordance with DISA requirements. Alternately, the /etc/banner file may be used in accordance with DISA requirements.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-UT-000020
- Vuln IDs
-
- V-224100
- V-98907
- Rule IDs
-
- SV-224100r877940_rule
- SV-108011
Checks: C-25773r516699_chk
From the ISPF Command Shell enter: omvs cd /etc cat inetd.conf If the "otelnetd" command specifies any user other than "OMVS" or "OMVSKERN", this is a finding.
Fix: F-25761r516700_fix
The user account used at the startup of "otelnetd" is specified in the "inetd" configuration file. This account is used to perform the identification and authentication of the user requesting the session. Because the account is only used until user authentication is completed, there is no need for a unique account for this function. The z/OS UNIX kernel account can be used.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-UT-000030
- Vuln IDs
-
- V-224101
- V-98909
- Rule IDs
-
- SV-224101r877941_rule
- SV-108013
Checks: C-25774r516702_chk
From the ISPF Command Shell enter: omvs At the input line enter: cd /usr enter ls -alW If the following File permission and user Audit Bits are true, this is not a finding. /usr/sbin/otelnetd 1740 fff cd /etc ls -alW If the following file permission and user Audit Bits are true this is not a finding. /etc/banner 0744 faf The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing
Fix: F-25762r516703_fix
With the assistance of a systems programmer with UID(0) and/or SUPERUSER access, will review the UNIX permission bits and user audit bits on the HFS directories and files for the z/OS UNIX Telnet Server. Ensure they conform to the specifications below: z/OS UNIX TELNET Server HFS Object Security Settings File Permission Bits User Audit Bits /usr/sbin/otelnetd 1740 fff /etc/banner 0744 faf NOTE: The /usr/sbin/otelnetd object is a symbolic link to /usr/lpp/tcpip/sbin/otelnetd. The permission and user audit bits on the target of the symbolic link must have the required settings. The following represents a hierarchy for permission bits from least restrictive to most restrictive: 7 rwx (least restrictive) 6 rw- 3 -wx 2 -w- 5 r-x 4 r-- 1 --x 0 --- (most restrictive) The possible audit bits settings are as follows: f log for failed access attempts a log for failed and successful access - no auditing The following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits: chmod 1740 /usr/lpp/tcpip/sbin/otelnetd chaudit rwx=f /usr/lpp/tcpip/sbin/otelnetd chmod 0744 /etc/banner chaudit w=sf,rx+f /etc/banner
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-UT-000040
- Vuln IDs
-
- V-224102
- V-98911
- Rule IDs
-
- SV-224102r877942_rule
- SV-108015
Checks: C-25775r516705_chk
From the ISPF Command Shell enter: ISHELL Enter /etc/ for a pathname - you may need to issue a CD /etc/ select FILE NAME inetd.conf If Option -D login is included on the otelnetd command, this is not a finding. If Option -c 900 is included on the otelnetd command, this is not a finding. NOTE: "900" indicates a session timeout value of "15" minutes and is currently the maximum value allowed.
Fix: F-25763r516706_fix
Configure the startup parameters in the inetd.conf file for otelnetd to conform to the specifications below. The otelnetd startup command includes the options -D login and -c 900, where: -D login indicates that messages should be written to the syslogd facility for login and logout activity. -c 900 indicates that the Telnet session should be terminated after "15" minutes of inactivity. NOTE: "900" is the maximum value; any value between "1" and "900" is acceptable.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-001384
- Version
- TSS0-UT-000050
- Vuln IDs
-
- V-224103
- V-98913
- Rule IDs
-
- SV-224103r877943_rule
- SV-108017
Checks: C-25776r516708_chk
From the ISPF Command Shell enter: OMVS cat inetd.conf If the otelnet startup command includes option "-h" this is a finding.
Fix: F-25764r516709_fix
The otelnetd startup command should not include the option "-h", where: -h indicates that the logon banner should not be displayed.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-VT-000010
- Vuln IDs
-
- V-224104
- V-98915
- Rule IDs
-
- SV-224104r877944_rule
- SV-108019
Checks: C-25777r516711_chk
Create a list of data set names containing all VTAM start options, configuration lists, network resource definitions, commands, procedures, exit routines, all SMP/E TLIBs, and all SMP/E DLIBs used for installation and in development/production VTAM environments. If the ESM data set rules for all VTAM system data sets restrict access to only network systems programming staff, this is not a finding. If RACF data set rules for all VTAM system data sets all READ access to auditors only, this is not a finding. These data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements.
Fix: F-25765r516712_fix
Configure TSS data set rules for all VTAM system data sets restrict access to only network systems programming staff. Auditors may have READ access as documented by and approved by the ISSM. These data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements. The following sample TSS commands show proper permissions for VTAM data sets (replace "profile" with the profile name of the network systems programming staff authorities): TSS PERMIT(profile) DSN(SYS1.VTAM.) ACC(ALL) TSS PERMIT(profile) DSN('SYS1.VTAMLIB.) ACC(ALL) TSS PERMIT(profile) DSN(SYS1.VTAM.SISTCLIB.) ACC(ALL) TSS PERMIT(profile) DSN(SYS3.VTAM.) ACC(ALL) TSS PERMIT(profile) DSN(SYS3.VTAMLIB.) ACC(ALL)
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- TSS0-VT-000020
- Vuln IDs
-
- V-224105
- V-98917
- Rule IDs
-
- SV-224105r877945_rule
- SV-108021
Checks: C-25778r516714_chk
Ask the system administrator to supply the following information: - Documentation regarding terminal naming standards. - Documentation of all procedures controlling terminal logons to the system. - A complete list of all USS commands used by terminal users to log on to the system. - Members and data set names containing USSTAB and LOGAPPL definitions of all terminals that can log on to the system (e.g., SYS1.VTAMLST). - Members and data set names containing logon mode parameters. If USSTAB definitions are only used for secure terminals (e.g., terminals that are locally attached to the host or connected to the host via secure leased lines), this is not a finding. If USSTAB definitions are used for any unsecured terminals (e.g., dial up terminals or terminals attached to the Internet such as TN3270 or KNET 3270 emulation), this is a finding.
Fix: F-25766r516715_fix
Configure USSTAB definitions to be only used for secure terminals. Only terminals that are locally attached to the host or connected to the host via secure leased lines located in a secured area. Only authorized personnel may enter the area where secure terminals are located. USSTAB or LOGAPPL definitions are used to control logon from secure terminals. These terminals can log on directly to any VTAM application (e.g., TSO, CICS, etc.) of their choice and bypass Session Manager services. Secure terminals are usually locally attached to the host or connected to the host via a private LAN without access to an external network. Only authorized personnel may enter the area where secure terminals are located.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-TC-000080
- Vuln IDs
-
- V-245537
- V-98833
- Rule IDs
-
- SV-245537r877948_rule
- SV-107937
Checks: C-48812r877946_chk
Refer to the Data configuration file specified on the SYSTCPD DD statement in the TCPIP started task JCL. Note: If GLOBALTCPIPDATA is specified, any TCPIP.DATA statements contained in the specified file or data set take precedence over any TCPIP.DATA statements found using the appropriate environment's (native MVS or z/OS UNIX) search order. If GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA. If the DOMAINORIGIN/DOMAIN (The DOMAIN statement is functionally equivalent to the DOMAINORIGIN Statement) is specified in the TCP/IP Data configuration file, this is not a finding.
Fix: F-48768r877947_fix
Configure the TCPIP.DATA file to include the DOMAINORIGIN/DOMAIN (The DOMAIN statement is functionally equivalent to the DOMAINORIGIN Statement). Note: If GLOBALTCPIPDATA is specified, any TCPIP.DATA statements contained in the specified file or data set take precedence over any TCPIP.DATA statements found using the appropriate environment's (native MVS or z/OS UNIX) search order. If GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA.
- RMF Control
- SC-28
- Severity
- Medium
- CCI
- CCI-002476
- Version
- TSS0-OS-000320
- Vuln IDs
-
- V-251108
- V-98765
- Rule IDs
-
- SV-251108r877949_rule
- SV-107869
Checks: C-54543r804053_chk
Determine if IBM's DS880 Disks or equivalent hardware solutions are in use. If IBMs DS880 Disks or equivalent hardware solutions are not in use for systems that require "data at rest", this is a finding.
Fix: F-54497r804054_fix
Employ IBM's DS8880 hardware or equivalent hardware solutions to ensure full disk encryption.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- TSS0-TC-000100
- Vuln IDs
-
- V-252554
- Rule IDs
-
- SV-252554r816962_rule
Checks: C-56010r816960_chk
Use the z/OS UNIX pasearch -t command to query information from the z/OS UNIX Policy Agent. The command is issued from the UNIX System Services shell. Examine the results for AT-TLS initiation and control statements. If there are no AT-TLS initiation and controls statements, this is a finding. Verify the statements specify a FIPS 140-2 compliant value. If none of the following values are present, this is a finding ECDHE_ECDSA_AES_128_CBC_SHA256 ECDHE_ECDSA_AES_256_CBC_SHA384 ECDHE_RSA_AES_128_CBC_SHA256 ECDHE_RSA_AES_256_CBC_SHA384 TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256
Fix: F-55960r816961_fix
Develop a plan of action to implement the required changes. Ensure the following items are in effect for TCP/IP resources. Develop AT-TLS policy. Install in the policy agent. Ensure the statements specify a FIPS 140-2 compliant value of the following values. ECDHE_ECDSA_AES_128_CBC_SHA256 ECDHE_ECDSA_AES_256_CBC_SHA384 ECDHE_RSA_AES_128_CBC_SHA256 ECDHE_RSA_AES_256_CBC_SHA384 TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-FT-000130
- Vuln IDs
-
- V-255896
- V-98185
- Rule IDs
-
- SV-255896r877951_rule
- SV-107289
Checks: C-59573r877347_chk
Refer to the Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL. If the UMASK statement is coded with a value of "077", this is not a finding.
Fix: F-59516r877348_fix
Configure the FTP configuration to include the UMASK statement with a value of "077". If the FTP Server requires a UMASK value less restrictive than "077", requirements should be justified and documented with the ISSO.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- TSS0-IC-000010
- Vuln IDs
-
- V-255940
- V-18014
- Rule IDs
-
- SV-255940r881312_rule
- SV-95665
Checks: C-59617r881310_chk
Refer to the CSFPRMxx member in the logical PARMLIB concatenation. If the configuration parameters are specified as follows this is not a finding. REASONCODES(ICSF) COMPAT(NO) SSM(NO) SSM can be dynamically set by defining the CSF.SSM.ENABLE SAF profile within the XFACILIT resource Class. If this profile is not limited to authorized personnel this is a finding. CHECKAUTH(YES) FIPSMODE(YES,FAIL(YES)) AUDITKEYLIFECKDS (TOKEN(YES),LABEL(YES)). AUDITKEYLIFEPKDS (TOKEN(YES),LABEL(YES)). AUDITKEYLIFETKDS (TOKENOBJ(YES),SESSIONOBJ(YES)). AUDITKEYUSGCKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)). AUDITKEYUSGPKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)). AUDITPKCS11USG (TOKENOBJ(YES),SESSIONOBJ(YES),NOKEY(YES),INTERVAL(n)). DEFAULTWRAP -This parameter can be determined by the site. ENHANCED wrapping specifies the new X9.24 compliant CBC wrapping is used. If DEFAULTWRAP is not specified, the default wrapping method will be ORIGINAL for both internal and external tokens. Starting with ICSF FMID HCR77C0, the value for this option can be updated without restarting ICSF by using either the SETICSF command or the ICSF Multi-Purpose service. If this access is not restricted to appropriate personnel, this is a finding. (Note: Other options may be site defined.
Fix: F-59560r881311_fix
Evaluate the impact associated with implementation of the control options. Develop a plan of action to implement the control options for CSFPRMxx as specified below: REASONCODES(ICSF) COMPAT(NO) SSM(NO) SSM can be dynamically set by defining the CSF.SSM.ENABLE SAF profile within the XFACILIT resource Class. This profile must limited to authorized personnel. CHECKAUTH(YES) FIPSMODE(YES,FAIL(YES)) AUDITKEYLIFECKDS (TOKEN(YES),LABEL(YES)). AUDITKEYLIFEPKDS (TOKEN(YES),LABEL(YES)). AUDITKEYLIFETKDS (TOKENOBJ(YES),SESSIONOBJ(YES)). AUDITKEYUSGCKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)). AUDITKEYUSGPKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)). AUDITPKCS11USG (TOKENOBJ(YES),SESSIONOBJ(YES),NOKEY(YES),INTERVAL(n)). DEFAULTWRAP -This parameter can be determined by the site. ENHANCED wrapping specifies the new X9.24 compliant CBC wrapping is used. If DEFAULTWRAP is not specified, the default wrapping method will be ORIGINAL for both internal and external tokens. Starting with ICSF FMID HCR77C0, the value for this option can be updated without restarting ICSF by using either the SETICSF command or the ICSF Multi-Purpose service. This access must be restricted to appropriate personnel. Note: Other options may be site defined.
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- TSS0-IC-000020
- Vuln IDs
-
- V-255941
- V-16932
- Rule IDs
-
- SV-255941r881315_rule
- SV-30550
Checks: C-59618r881313_chk
Verify that access to the IBM IntegrTated Crypto Service Facility (ICSF) install data sets are properly restricted. Execute a data set list of access to the IBM Integrated Crypto Service Facility (ICSF) install data sets If the TSS data set rules for the data sets does not restrict UPDATE and/or ALL access to systems programming personnel this is a finding. If the TSS data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATE and/or ALL access will be logged this is a finding.
Fix: F-59561r881314_fix
Ensure that update and allocate access to IBM Integrated Crypto Service Facility (ICSF) install data sets is limited to System Programmers only, and all update and allocate access is logged. Read access can be given to Auditors and any other users that have a valid requirement to utilize these data sets. 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 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. Data sets to be protected will be: SYS1.CSF The following commands are provided as a sample for implementing data set controls: TSS PERMIT(syspaudt) DSN(SYS1.CSF.) ACCESS(R) TSS PERMIT(tstcaudt) DSN(SYS1.CSF.) ACCESS(R) TSS PERMIT(icsfusrs) DSN(SYS1.CSF.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS1.CSF.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(tstcaudt) DSN(SYS1.CSF.) ACCESS(ALL) ACTION(AUDIT)
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-IC-000040
- Vuln IDs
-
- V-255942
- V-17452
- Rule IDs
-
- SV-255942r881318_rule
- SV-30591
Checks: C-59619r881316_chk
Review the IBM Integrated Crypto Service Facility (ICSF) STC/Batch ACID(s) for the following: ___ Is defined with Facility of STC and/or BATCH. ___ Is sourced to the INTRDR. c) If all of the above are true this is not a finding d) If any of the above is untrue this is a finding.
Fix: F-59562r881317_fix
The Systems Programmer and IAO will ensure that the started task for IBM Integrated Crypto Service Facility (ICSF) Started Task(s) is properly Identified / 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. Define the started task userid CSFSTART for IBM Integrated Crypto Service Facility (ICSF). Example: TSS CRE(CSFSTART) DEPT(Dept) NAME('ICSF STC') - FAC(STC) PASSWORD(password,0) - SOURCE(INTRDR)
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000764
- Version
- TSS0-IC-000050
- Vuln IDs
-
- V-255943
- V-17454
- Rule IDs
-
- SV-255943r881321_rule
- SV-30580
Checks: C-59620r881319_chk
from the ISPF Command Shell enter TSS LIST(STC) If the IBM Integrated Crypto Service Facility (ICSF) started task(s) is (are) not defined in the TSS STC record this is a finding.
Fix: F-59563r881320_fix
The IBM Integrated Crypto Service Facility (ICSF) 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 ACID must be assigned for the IBM Integrated Crypto Service Facility (ICSF) started task(s) thru a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(CSFSTART) ACID(CSFSTART)
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- TSS0-IC-000030
- Vuln IDs
-
- V-255944
- V-17067
- Rule IDs
-
- SV-255944r881324_rule
- SV-30565
Checks: C-59621r881322_chk
Verify that access to the IBM Integrated Crypto Service Facility (ICSF) STC data sets are properly restricted. The data sets to be protected are identified in the data set referenced in the CSFPARM DD statement of the ICSF started task(s) and/or batch job(s); the entries for CKDSN and PKDSN specify the data sets. If the following guidance is true, this is not a finding. If the TSS data set access authorizations do not restrict READ access to auditors, this is a finding. If the TSS data set access authorizations do not restrict WRITE and/or greater access to systems programming personnel, this is a finding. If the TSS data set access authorizations do not restrict WRITE and/or greater access to the product STC(s) and/or batch job(s), this is a finding.
Fix: F-59564r881323_fix
The ISSO will ensure that WRITE and/or greater access to IBM Integrated Crypto Service Facility (ICSF) STC and/or batch data sets are limited to system programmers and ICSF STC and/or batch jobs only. READ access can be given to auditors at the ISSO's discretion. The installing systems programmer will identify and document the product data sets and categorize them according to who will have what type of access and if required which type of access is logged. The installing systems programmer will identify any additional groups requiring access to specific data sets, and once documented the installing systems programmer 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.) The data sets to be protected are identified in the data set referenced in the CSFPARM DD statement of the ICSF started task(s) and/or batch job(s); the entries for CKDSN and PKDSN specify the data sets. Note: Currently on most CSD systems, the CKDSN specifies SYS3.CSF.CKDS and PKDSN specifies SYS3.CSF.PKDS. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(audtaudt) DSN(SYS3.CDS.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.CDS.) ACCESS(R) TSS PERMIT(tstcaudt) DSN(SYS3.CDS.) ACCESS(R) TSS PERMIT(icsfstc) DSN(SYS3.CDS.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.CDS.) ACCESS(ALL) TSS PERMIT(tstcaudt) DSN(SYS3.CDS.) ACCESS(ALL) TSS PERMIT(icsfstc) DSN(SYS3.CDS.) ACCESS(ALL)