{"stig":{"title":"IBM z/OS TSS Security Technical Implementation Guide","version":"9","release":"8"},"checks":[{"vulnId":"V-223871","ruleId":"SV-223871r998483_rule","severity":"medium","ruleTitle":"All IBM z/OS digital certificates in use must have a valid path to a trusted Certification Authority (CA).","description":"Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted.\n\nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.\n\nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a CA. A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA.\n\nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182","checkContent":"Execute the CA-TSS SAFCRRPT using the following as SYSIN input:\nRECORDID(-) DETAIL TRUST FIELDS(ISSUER SUBJECT ACTIVE EXPIRE TRUST)\n\nIf no certificate information is found, this is not a finding.\n\nNOTE: Certificates are only valid when their Status is TRUST. Therefore, you may ignore certificates with the NOTRUST status during the following check.\n\nIf the digital certificate information indicates that the issuer's distinguished name leads to one of the following this is not a finding:\na) A DOD PKI Root Certification Authority\nb) An External Root Certification Authority (ECA)\nc) An approved External Partner PKI's Root Certification Authority\n\nThe 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/).\n\nExamples of an acceptable DOD CA are:\nDOD PKI Class 3 Root CA\nDOD PKI Med Root CA","fixText":"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.\n\nThe 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/).","ccis":["CCI-000185","CCI-002470","CCI-004909"]},{"vulnId":"V-223872","ruleId":"SV-223872r958448_rule","severity":"medium","ruleTitle":"Expired IBM z/OS digital certificates must not be used.","description":"Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted.\n\nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.\n\nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA.\n\nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.","checkContent":"Execute the CA-TSS SAFCRRPT using the following as SYSIN input:\nRECORDID(-) DETAIL FIELDS(ISSUER SUBJECT ACTIVE EXPIRE TRUST)\n\nIf no certificate information is found, this is not a finding.\n\nNOTE: Certificates are only valid when their Status is TRUST. Therefore, you may ignore certificates with the NOTRUST status during the following checks.\n\nCheck the expiration for each certificate with a status of TRUST.\n\nIf the expiration date has passed, this is a finding.","fixText":"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.","ccis":["CCI-000185"]},{"vulnId":"V-223873","ruleId":"SV-223873r958482_rule","severity":"medium","ruleTitle":"IBM z/OS must have Certificate Name Filtering implemented with appropriate authorization and documentation.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"If certificate name filtering is in use, the ISSM should document each active filter rule and have written approval to use the rule.\n\nIssue the following TSS command to list any certificate name filters defined to TSS:\n\nTSS LIST(SDT) CERTMAP(ALL)\n\nIf there is nothing to list, this is not a finding.\n\nNOTE: Certificate name filters are only valid when their Status is TRUST. Therefore, you may ignore filters with the NOTRUST status.\n\nIf certificate name filters are defined and they have a Status of TRUST, certificate name filtering is in use.\n\nIf certificate name filtering is in use and filtering rules have been documented and approved by the ISSM, this is not a finding.\n\nIf certificate name filtering is in use and filtering rules have not been documented and approved by the ISSM, this is a finding.","fixText":"Ensure any certificate name filtering rules in use are documented and approved by the ISSM.","ccis":["CCI-000764"]},{"vulnId":"V-223874","ruleId":"SV-223874r1137691_rule","severity":"high","ruleTitle":"CA-TSS Security control ACIDs must be limited to the administrative authorities authorized and that require these privileges to perform their job duties.","description":"The use of security policy filters provides protection for the confidentiality of data by restricting the flow of data. A crucial part of any flow control solution is the ability to configure policy filters. This allows the operating system to enforce multiple and different security policies. Policy filters serve to enact and enforce the organizational policy as it pertains to controlling data flow.","checkContent":"From the ISPF Command Shell enter:\n\nTSS LIST(ACIDS) DATA(ADMIN, BASIC)\n\nIf any ACIDs other than TYPE=CENTRAL (SCA/MSCA) has the following administrative authority, this is a finding.\n\nFACILITIES(ALL)\nPROGRAM(ALL)\nPROGRAM(OWN)\nRESOURCE(ALL)\nROSRES(ALL)\nVOLUME(ALL)\nVOLUME(OWN)\n\nMISC1(ALL)\nMISC1(LCF)\nMISC1(LTIME)\nMISC1(RDT)\nMISC1(USER)\n\nMISC2(ALL)\nMISC2(DLF)\nMISC2(NDT)\nMISC2(SMS)\n\nMISC4(ALL)\n\nMISC8(ALL)\nMISC8(LISTAPLU)\nMISC8(LISTRDT)\nMISC8(LISTSDT)\nMISC8(LISTSTC)\nMISC8(MCS)\n\nMISC9(ALL)\nMISC9(BYPASS)\nMISC9(CONSOLE)\nMISC9(GLOBAL)\nMISC9(MASTFAC)\nMISC9(MODE)\nMISC9(STC)\nMISC9(TRACE)","fixText":"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.\n\nThe 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).\n\ndata set(ALL)ACC(ALL)\ndata set(XAUTH,OWN,REPORT,AUDIT,INFO)ACC(ALL)\nOTRAN(ALL)ACC(ALL)\nACID(ALL)\nACID(INFO,MAINTAIN)\nMISC1(INSTDATA,SUSPEND,TSSSIM,NOATS)\nMISC2(TSO,TARGET)\nMISC8(PWMAINT,REMASUSP)\nMISC9(GENERIC)\nFACILITY(BATCH, TSO, ROSCOE, CICS, xxxx)\n\nWhere \"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.\n\nTSS ADMIN(acid)RESOURCE(REPORT,INFO,AUDIT) can be allowed and is required to run TSSUTIL reports.\n\nNote: \"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. \n\nNote: \"ALL\" will display as \"*ALL*\" but also means approved for any single administrative authority under that specific item.","ccis":["CCI-000213"]},{"vulnId":"V-223875","ruleId":"SV-223875r1137691_rule","severity":"medium","ruleTitle":"The number of CA-TSS ACIDs possessing the tape Bypass Label Processing (BLP) privilege must be limited.","description":"The use of security policy filters provides protection for the confidentiality of data by restricting the flow of data. A crucial part of any flow control solution is the ability to configure policy filters. This allows the operating system to enforce multiple and different security policies. Policy filters serve to enact and enforce the organizational policy as it pertains to controlling data flow.","checkContent":"From the ISPF Command Shell enter: \nTSS LIST(ACIDS) DATA(BASIC)\n\nIf only authorized personnel have BLP access and documentation for access is on file with the ISSO, this is not a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-223876","ruleId":"SV-223876r958362_rule","severity":"high","ruleTitle":"CA-TSS MODE Control Option must be set to FAIL.","description":"Enterprise environments make account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other errors.\n\nA comprehensive account management process that includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in non-centralized account stores such as multiple servers. This requirement applies to all account types, including individual/user, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service.\n\nThe automated mechanisms may reside within the operating system itself or may be offered by other infrastructure providing automated account management capabilities. Automated mechanisms may be composed of differing technologies that, when placed together, contain an overall automated mechanism supporting an organization's automated account management requirements.\n\nAccount management functions include: assigning group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephonic notification to report atypical system account usage.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the global MODE Control Option value is set to \"FAIL\", this is not a finding.\n\nIf the global MODE Control Option value is not set to \"FAIL\", this is a finding. \n\nAdditional analysis may be required under the following conditions:\nMode(IMPL) is allowed while a system is in implementation with a documented process that includes an implementation completion date.","fixText":"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.","ccis":["CCI-000015"]},{"vulnId":"V-223877","ruleId":"SV-223877r958388_rule","severity":"medium","ruleTitle":"The CA-TSS NPWRTHRESH Control Option must be properly set.","description":"By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the NPWRTHRESH Control Option value is not set to NPWRTHRESH(02), this is a finding.","fixText":"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.\n\nNPWRTHRESH(02)","ccis":["CCI-000044"]},{"vulnId":"V-223878","ruleId":"SV-223878r958388_rule","severity":"medium","ruleTitle":"The CA-TSS NPPTHRESH Control Option must be properly set.","description":"By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the NPPTHRESH Control Option value is not set to NPWRTHRESH(02), this is a finding.","fixText":"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.\n\nNPPTHRESH(02)","ccis":["CCI-000044"]},{"vulnId":"V-223879","ruleId":"SV-223879r1050764_rule","severity":"medium","ruleTitle":"The CA-TSS PTHRESH Control Option must be set to 2.","description":"By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the PTHRESH Control Option value is not set to PTHRESH(02), this is a finding.","fixText":"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.\n\nPTHRESH(02)","ccis":["CCI-000044","CCI-002238"]},{"vulnId":"V-223881","ruleId":"SV-223881r958434_rule","severity":"medium","ruleTitle":"IBM z/OS must limit access for SMF collection files (i.e., SYS1.MANx) to appropriate users and/or batch jobs that perform SMF dump processing.","description":"SMF data collection is the system activity journaling facility of the z/OS system. Unauthorized access could result in the compromise of logging and recording of the operating system environment, ESM, and customer data.\n\nUnauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000256-GPOS-00097, CCI-001494, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099, SRG-OS-000080-GPOS-00048, SRG-OS-000206-GPOS-00084, SRG-OS-000324-GPOS-00125","checkContent":"Refer to the SMFPRMxx member in SYS1.PARMLIB. Determine the SMF and/or Logstream data set name.\n\nIf the following statements are true, this is not a finding.\n\n-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.\n-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.\n-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.\n-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.","fixText":"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.\n\nEnsure that read access is limited to auditors. Access may be granted to others as determined by the ISSM.\n\nEnsure the accesses are being logged.\n\nEnsure that all (i.e., failures and successes) WRITE or greater access are logged.\n\nEnsure read access failures are logged.","ccis":["CCI-000162","CCI-000163","CCI-000164","CCI-000165","CCI-000213","CCI-001314","CCI-001493","CCI-001494","CCI-001495","CCI-002235"]},{"vulnId":"V-223882","ruleId":"SV-223882r998484_rule","severity":"high","ruleTitle":"IBM z/OS SYS1.PARMLIB must be properly protected.","description":"Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nSatisfies: SRG-OS-000063-GPOS-00032, SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000362-GPOS-00149, SRG-OS-000337-GPOS-00129, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set list of access to SYS1.PARMLIB.\n\nIf the ESM data set rules for SYS1.PARMLIB allow inappropriate (e.g., global READ) access, this is a finding.\n\nIf data set rules for SYS1.PARMLIB do not restrict READ, WRITE or greater access to only systems programming personnel, this is a finding.\n\nIf data set rules for SYS1.PARMLIB do not restrict READ and UPDATE access to only domain level security administrators, this is a finding.\n\nIf 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.\n\nIf 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.","fixText":"Ensure the accesses are being logged.","ccis":["CCI-000171","CCI-000213","CCI-001499","CCI-003980","CCI-001914","CCI-002235"]},{"vulnId":"V-223883","ruleId":"SV-223883r998485_rule","severity":"medium","ruleTitle":"IBM z/OS for PKI-based authentication must use ICSF or the ESM to store keys.","description":"If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure.\n\nThe cornerstone of the PKI is the private key used to encrypt or digitally sign information.\n\nIf the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user.\n\nBoth the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.","checkContent":"Any keys or Certificates must be managed in ICSF or the external security manager and not in UNIX files.\n\nFrom the ISPF Command Shell enter:\nOMVS\nenter\nfind / -name *.kdb\nand \nFind / -name *.jks\n\nIf any files are present, this is a finding.\n\nOMVS\nenter\nfind / -name *.kdb\nand \nFind / -name *.jks\n\nIf any files are present, this is a finding.","fixText":"Define all Keys/Certificates to ICSF or the security database.\n\nRemove all .kdb and .jks key files.","ccis":["CCI-000186","CCI-004910"]},{"vulnId":"V-223885","ruleId":"SV-223885r998486_rule","severity":"medium","ruleTitle":"The CA-TSS NEWPHRASE and PPSCHAR Control Options must be properly set.","description":"Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\nSatisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the NEWPHRASE Control Option conforms to the following requirements, this is not a finding. \n\nMA=1-32\nMN=1-32\nID\nMAX=100\nMIN=15-100\nMINDAYS=1\nNR=0-1\nSC=1-32\nWARN=1-10\n\nIf 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.\n\nNote: These characters will be specified at a minimum. \"40\" represents the blank character. Characters can be identified by their character or hex equivalent.","fixText":"Note: Support of mixed case passwords can only be set when the security file has been copied by TSSXTEND with the option NEWPWBLOCK.\n\nConfigure the NEWPHRASE Control Option values to the following requirements:\n\nMA=1-32\nMN=1-32\nID\nMAX=100\nMIN=15-100\nMINDAYS=1\nNR=0-1\nSC=1-32\nWARN=1-10\n\nConfigure the PPSCHAR Control Option to the allowable list defined in CA Top Secret for z/OS User Guide.\n\nNote: These characters will be specified at a minimum. \"40\" represents the blank character. Characters can be identified by their character or hex equivalent.\n\nExample:\n\nTSS MODIFY NEWPHRASE(MA=1,MN=1,ID,MAX=100,MIN=15,MINDAYS=1,NR=1,SC=1,WARN=10)\nTSS MODIFY PPSCHAR(c,c,c,c,...)\n\n(Use the allowable list defined in CA Top Secret for z/OS Control Options Guide.)","ccis":["CCI-004066","CCI-004065"]},{"vulnId":"V-223886","ruleId":"SV-223886r998487_rule","severity":"medium","ruleTitle":"The CA-TSS NEWPW control options must be properly set.","description":"If the private key is stolen, this will lead to the compromise of the authentication and nonrepudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user.\n\nSatisfies: SRG-OS-000071-GPOS-00039, SRG-OS-000072-GPOS-00040, SRG-OS-000075-GPOS-00043, SRG-OS-000480-GPOS-00225, SRG-OS-000266-GPOS-00101, SRG-OS-000279-GPOS-00109","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the NEWPW Control Option values conform to the following requirements, this is not a finding.\n\nNEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC)\n\nNOTE: 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.\n\nNOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.","fixText":"Note: Support of mixed case passwords can only be set when the security file has been copied by TSSXTEND with the option NEWPWBLOCK.\n\nConfigure the NEWPW Control Option values conform to the following requirements:\n\nNEWPW(MIN=8,WARN=10, MINDAYS=1, NR=0, ID, TS, SC, RS, FA, FN, MC, UC, LC)\n\nNOTE: 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.\n\nNOTE: For the Option RS, at a minimum use the reserved word prefix list found in the site security plan.","ccis":["CCI-004066","CCI-002361","CCI-004065","CCI-004061"]},{"vulnId":"V-223887","ruleId":"SV-223887r998488_rule","severity":"high","ruleTitle":"IBM z/OS must use NIST FIPS-validated cryptography to protect passwords in the security database.","description":"Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.\n\nSatisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000074-GPOS-00042","checkContent":"From the ISPF command shell line enter:\nTSS MODIFY(STATUS)\n\nIf either of the following is included, this is not a finding.\n\nAES_ENCRYPTION(Active,128)\nAES_ENCRYPTION(Active,256)","fixText":"Evaluate the impact associated with implementation of the control option.\n\nDevelop a plan of action to implement the control option as specified below:\n\nConvert 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.\n\nPlease consult CA-TSS Installation guide for more information.","ccis":["CCI-004062","CCI-000197"]},{"vulnId":"V-223888","ruleId":"SV-223888r1038967_rule","severity":"medium","ruleTitle":"The CA-TSS PWEXP Control Option must be set to 60.","description":"Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the PWEXP Control Option value is not set to PWEXP(60), this is a finding.","fixText":"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.\n\nPWEXP(60)","ccis":["CCI-004066"]},{"vulnId":"V-223889","ruleId":"SV-223889r1038967_rule","severity":"medium","ruleTitle":"The CA-TSS PPEXP Control Option must be properly set.","description":"Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the PPEXP Control Option will conform to the following requirements, this is not a finding.\n\nPPEXP(60)","fixText":"Configure the PPEXP Control Option value to conform to the following requirements.\n\nPPEXP(60)\n\nExample:\n\nTSS MODIFY PPEXP(60)","ccis":["CCI-004066"]},{"vulnId":"V-223890","ruleId":"SV-223890r998491_rule","severity":"medium","ruleTitle":"The CA-TSS PWHIST Control Option must be set to 10 or greater.","description":"Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the PWHIST Control Option value is not set to PWHIST(10) or greater, this is a finding.","fixText":"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.\n\nPWHIST(10) or greater","ccis":["CCI-004061"]},{"vulnId":"V-223891","ruleId":"SV-223891r998492_rule","severity":"medium","ruleTitle":"The CA-TSS PPHIST Control Option must be properly set.","description":"Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the PPHIST Control Option conforms to the following requirements, this is not a finding.\n\nPPHIST(10-64)","fixText":"Configure the PPHIST Control Option value to conforms to the following requirements:\n\nPPHIST(10-64)\n\nExample:\n\nTSS MODIFY PPHIST(10)","ccis":["CCI-004061"]},{"vulnId":"V-223893","ruleId":"SV-223893r1137691_rule","severity":"medium","ruleTitle":"CA-TSS access to SYS1.LINKLIB must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000362-GPOS-00149, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set list of access to SYS1.LINKLIB.\n\nIf the ESM data set rules for SYS1.LINKLIB allow inappropriate (e.g., global READ) access, this is a finding.\n\nIf data set rules for SYS1.LINKLIB do not restrict READ, WRITE or greater access to only systems programming personnel, this is a finding.\n\nIf data set rules for SYS1.LINKLIB do not restrict READ and UPDATE access to only domain level security administrators, this is a finding.\n\nIf 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.\n\nIf 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.","fixText":"Configure the ESM rules for SYS1.LINKLIB limit access to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-003980"]},{"vulnId":"V-223894","ruleId":"SV-223894r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to SYS1.SVCLIB to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set list of access for SYS1.SVCLIB.\n\nIf all of the following are true, this is not a finding.\n\nIf any of the following are untrue, this is a finding.\n\nESM data set rules for SYS1.SVCLIB restrict WRITE or greater access to only z/OS systems programming personnel.\nESM data set rules for SYS1.SVCLIB specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223895","ruleId":"SV-223895r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to SYS1.IMAGELIB to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set list of access for SYS1.IMAGELIB.\n\nIf the following guidance is true, this is not a finding.\n\nThe ACP data set rules for SYS1.IMAGELIB do not restrict WRITE or greater access to only systems programming personnel.\nThe ACP data set rules for SYS1.IMAGELIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"Configure WRITE or greater access to SYS1.IMAGELIB to be limited to system programmers only and all WRITE or greater access is logged.\n\nReview 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.\n\nSYS1.IMAGELIB is automatically APF-authorized. This data set contains modules, images, tables, and character sets which are essential to system print services.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223896","ruleId":"SV-223896r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to SYS1.LPALIB to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set list of access for SYS1.LPALIB.\n\nIf all of the following are untrue, this is a finding.\n\nIf any of the following is true, this is a finding.\n\nThe ESM data set rules for SYS1.LPALIB do not restrict WRITE or greater access to only z/OS systems programming personnel.\nThe ESM data set rules for SYS1.LPALIB do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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. \n\nConfigure WRITE or greater access to SYS1.LPALIB to be limited to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223897","ruleId":"SV-223897r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit WRITE or greater access to all APF-authorized libraries to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"From Any ISPF input line, enter TSO ISRDDN APF. \n\nIf all of the following are untrue, this is not a finding.\n\nIf any of the following are true, this is a finding.\n\nThe ACP data set rules for APF libraries do not restrict WRITE or greater access to only z/OS systems programming personnel.\nThe ACP data set rules for APF libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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. \n\nConfigure WRITE or greater access to all APF-authorized libraries to be limited to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223898","ruleId":"SV-223898r1137691_rule","severity":"high","ruleTitle":"IBM z/OS libraries included in the system REXXLIB concatenation must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Refer to AXRxx member of PARMLIB for each REXXLIB ADD statement.\n\nIf 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.\n\nIf the ESM data set rules for libraries in the REXXLIB concatenation restrict READ access to the following, this is not a finding.\n\nAppropriate Started Tasks\nAuditors\nThe user-id defined in PARMLIB member AXR00 AXRUSER(user-id)\n\nIf 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.","fixText":"Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to protect APF Authorized Libraries. \n\nConfigure ESM data set rules to limit WRITE or greater access to libraries included in the system REXXLIB concatenation to system programmers only.\nConfigure ESM data set rules allow READ access to only appropriate Started Tasks and Auditors.\nConfigure ESM data set rules to log WRITE or greater access (i.e., successes and failures).","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223899","ruleId":"SV-223899r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to all LPA libraries to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"From any ISPF input line, enter TSO ISRDDN LPA. \n\nIf all of the following are untrue, this is not a finding.\n\nIf any of the following is true, this is a finding.\n\nThe ACP data set rules for LPA libraries do not restrict WRITE or greater access to only z/OS systems programming personnel.\nThe ACP data set rules for LPA libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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.\n\nConfigure the WRITE or greater access to all LPA libraries to be limited to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223900","ruleId":"SV-223900r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to SYS1.NUCLEUS to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Execute a dataset list of access for SYS1.NUCLEUS.\n\nIf all of the following are untrue, there is not a finding.\n\nIf any of the following is true, this is a finding.\n\nThe ACP data set rules for SYS1.NUCLEUS do not restrict WRITE or greater access to only z/OS systems programming personnel.\nThe ACP data set rules for SYS1.NUCLEUS do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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.\n\nConfigure the WRITE or greater access to SYS1.NUCLEUS to be limited to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223901","ruleId":"SV-223901r1137691_rule","severity":"low","ruleTitle":"CA-TSS must limit Write or greater access to libraries that contain PPT modules to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"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:\nTSO ISRDDN LOAD IEFSDPPT\nPress Enter.\n\nFor each module identified in the \"eyecatcher\" if all of the following are untrue, this is not a finding.\n\nIf any of the following is true, this is a finding.\n\nThe ACP data set rules for libraries that contain PPT modules do not restrict WRITE or greater access to only z/OS systems programming personnel.\nThe ACP data set rules for libraries that contain PPT modules do not specify that all WRITE or greater access will be logged.","fixText":"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.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223902","ruleId":"SV-223902r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit WRITE or greater access to LINKLIST libraries to system programmers only.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"From any ISPF input line, enter TSO ISRDDN LINKLIST.\n\nIf all of the following are untrue, this is not a finding.\n\nIf any of the following is true, this is a finding.\n\nThe ACP data set rules for LINKLIST libraries do not restrict WRITE or greater access to only z/OS systems programming personnel.\n\nThe ACP data set rules for LINKLIST libraries do not specify that all (i.e., failures and successes) WRITE or greater access will be logged.","fixText":"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.\n\nConfigure the WRITE or greater access to LINKLIST libraries to be limited to system programmers only and all WRITE or greater access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223903","ruleId":"SV-223903r1137691_rule","severity":"high","ruleTitle":"CA-TSS security data sets and/or databases must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000134-GPOS-00068, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Determine all associated ESM security data sets and/or databases.\n\nIf the following accesses to the ESM security data sets and/or databases are properly restricted as detailed below, this is not a finding.\n\nThe ESM data set rules for ESM security data sets and/or databases restrict READ access to auditors and DASD batch.\n\nThe 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.\n\nAll (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.","fixText":"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.\n\nConfigure 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.","ccis":["CCI-000213","CCI-001084","CCI-001499","CCI-002235"]},{"vulnId":"V-223904","ruleId":"SV-223904r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit access to the System Master Catalog to appropriate authorized users.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Refer to SYSCATxx member of SYS1.NUCLEUS.\n\nMultiple SYSCATxx members may be defined; if so, refer to Master Catalog message for IPL.\n\nIf the member is not found, refer to the appropriate LOADxx member of SYS1.PARMLIB.\n\nIf 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.\n\nIf products or procedures requiring system programmer access for system-level maintenance meet the following specific case, this is not a finding:\n- The batch job or procedure must be documented in the SITE Security Plan. \n- Reside in a data set that is restricted to systems programmers' access only. \n\nIf 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.","fixText":"Review access authorization to critical system files.\n\nEvaluate the impact of correcting the deficiency.\n\nDevelop a plan of action and implement the changes as required to protect the MASTER CATALOG.\n\nConfigure the ESM rules for system catalog to only allow access above \"READ\" to systems programmers and those authorized by the ISSM/ISSO.\n\nConfigure ESM rules for the master catalog to allow access above \"READ\" to systems programmers ONLY.\n\nConfigure 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:\n- The batch job or procedure must be documented in the SITE Security Plan. \n- Reside in a data set that is restricted to systems programmers' access only.\n\nAll greater than read access must be logged.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223905","ruleId":"SV-223905r1137691_rule","severity":"medium","ruleTitle":"CA-TSS allocate access to system user catalogs must be limited to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"From the ISPF Command Shell enter:\nLISTCat USERCATALOG ALL NOPREFIX\n\nReview the ESM data set rules for each usercatalog defined.\n\nIf the data set rules for User Catalogs do not restrict ALTER access to only z/OS systems programming personnel, this is a finding.\n\nIf products or procedures requiring system programmer access for system-level maintenance meet the following specific case, this is not a finding:\n- The batch job or procedure must be documented in the SITE Security Plan. \n- Reside in a data set that is restricted to systems programmers' access only.\n\nIf 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.\n\nNote: 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.","fixText":"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.\n\nConfigure ESM rules for allocate access to USER CATALOGS, limited to system programmers only, and all allocate access is logged.\n\nConfigure 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:\n- The batch job or procedure must be documented in the SITE Security Plan. \n- Reside in a data set that is restricted to systems programmers' access only.\n\nNote: 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.","ccis":["CCI-000213"]},{"vulnId":"V-223906","ruleId":"SV-223906r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit WRITE or greater access to all system-level product installation libraries to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Have the systems programmer for z/OS supply the following information:\n\nThe data set name and associated SREL for each SMP/E CSI utilized to maintain this system.\n\nThe 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.\n\nThe ACP data set rules for system-level product installation libraries (e.g., SMP/E CSIs) allow inappropriate access.\n\nThe 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.\n\nIf all of the above are untrue, this is not a finding.\n\nIf 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.","fixText":"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.\n\nConfigure allocate access to all system-level product execution libraries to be limited to system programmers only.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223907","ruleId":"SV-223907r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit WRITE or greater access to the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"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.\n\nThe 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.\n\nIf both of the above are untrue, this is not a finding.\n\nIf either of the above is true, this is a finding.","fixText":"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).\n\nConfigure WRITE or greater access to JES2 System data sets (spool, checkpoint, and parmlib data sets) to be limited to system programmers only. \nAccess other than this should be documented and approved by the ISSO. (Example: All SYS1.HASP* data sets.)","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223908","ruleId":"SV-223908r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit Write or greater access to SYS1.UADS to system programmers only, and Read and Update access must be limited to system programmer personnel and/or security personnel.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"The ESM data set rules for SYS1.UADS restricts WRITE or Greater access to only z/OS systems programming personnel.\n\nThe ESM data set rules for SYS1.UADS restricts READ and/or UPDATE access to z/OS systems programming personnel and/or security personnel.\n\nThe 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.\n\nThe ESM data set rules for SYS1.UADS restricts READ access to auditors as documented in Security Plan.\n\nIf all of the above are untrue, this is not a finding.\n\nIf any of the above is true, this is a finding.","fixText":"Evaluate the impact of correcting any deficiency. Develop a plan of action and implement the changes as required to protect SYS1.UADS.\nSYS1.UADS WRITE or Greater authority is limited to the systems programming staff. \n\nRead and update access should be limited to the security staff. \n\nREAD access is limited to Auditors when included in the site security plan\n\nConfigure 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.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223909","ruleId":"SV-223909r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit access to data sets used to back up and/or dump SMF collection files to appropriate users and/or batch jobs that perform SMF dump processing.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000206-GPOS-00084, SRG-OS-000324-GPOS-00125","checkContent":"Obtain the procedures and collection specifics for SMF data sets and backup.\n\nIf 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.\n\nIf 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.\n\nIf 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.\n\nIf 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.","fixText":"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.\n\nConfigure 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). \n\nConfigure data set rules for the SMF dump/backup files to restrict UPDATE access to others approved the ISSM.\n\nConfigure data set rules for the SMF dump/backup files to restrict READ access to authorized auditors and others approved by the ISSM.\n\nEnsure that all update and alter access authority to SMF history files will be logged using the ESM's facilities.","ccis":["CCI-000213","CCI-001314","CCI-002235"]},{"vulnId":"V-223910","ruleId":"SV-223910r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit access to SYSTEM DUMP data sets to system programmers only.","description":"System DUMP data sets are used to record system data areas and virtual storage associated with system task failures. Unauthorized access could result in the compromise of the operating system environment, ACP, and customer data.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"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.\n\nIf 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.\n\nIf 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.","fixText":"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.\n\nEvaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to restrict access to these data sets.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223911","ruleId":"SV-223911r1137691_rule","severity":"medium","ruleTitle":"CA-TSS WRITE or Greater access to System backup files must be limited to system programmers and/or batch jobs that perform DASD backups.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Collect from the storage management group the identification of the DASD backup files and all associated storage management ACIDs.\n\nIf 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.\n\nIf  READ Access to system backup data sets is not limited to auditors and others approved by the ISSM this is a finding.","fixText":"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.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223912","ruleId":"SV-223912r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit access to SYS(x).TRACE to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Execute a dataset list of access for SYS(x).TRACE files.\n\nIf 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.\n\nIf the ESM data set rule for SYS1.TRACE restricts access to others as documented and approved by ISSM, this is not a finding.","fixText":"Configure the ESM access to SYS1.TRACE to be limited to system programmers or started tasks that perform GTF processing.\nOther user access can be granted as documented and approved by the ISSM.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223913","ruleId":"SV-223913r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must limit access to System page data sets (i.e., PLPA, COMMON, and LOCALx) to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Execute a dataset list of access for System page data sets (i.e., PLPA, COMMON, and LOCALx).\n\nIf 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.\n\nIf ESM data set rules for system page data sets (PLPA, COMMON, and LOCAL) restrict auditors to READ only, this is not a finding.","fixText":"Configure the ESM data set rules for system page data sets (PLPA, COMMON, and LOCAL) to restrict access to only systems programming personnel.\n\nAuditors may be allowed READ Access as approved by the ISSM.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223914","ruleId":"SV-223914r1137691_rule","severity":"high","ruleTitle":"CA-TSS must limit WRITE or greater access to libraries containing EXIT modules to system programmers only.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"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. \n\nIf all the exits are found within APF, LPA, and LINKLIST, this is not applicable.\n\nIf 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.\n\nIf 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.","fixText":"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. \n\nConfigure 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.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223915","ruleId":"SV-223915r958726_rule","severity":"high","ruleTitle":"CA-TSS must limit all system PROCLIB data sets to system programmers only and appropriate authorized users.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000080-GPOS-00048","checkContent":"Refer to the following for the PROCLIB data sets that contain the STCs and TSO logons from the following sources:\n\n-MSTJCLxx member used during an IPL. The PROCLIB data sets are obtained from the IEFPDSI and IEFJOBS DD statements.\n\n-PROCxx DD statements and JES2 Dynamic PROCLIBs. Where 'xx' is the PROCLIB entries for the STC and TSU JOBCLASS configuration definitions. \n\nVerify that the accesses to the above PROCLIB data sets are properly restricted. If the following guidance is true, this is not a finding.\n\nIf the ESM data set access authorizations restrict READ access to all authorized users, this is not a finding.\n\nIf the ESM data set access authorizations restrict WRITE and/or greater access to systems programming personnel, this is not a finding.","fixText":"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.\n\nSuggestion on how to update system to be compliant with this vulnerability:\n\nNOTE: All examples are only examples and may not reflect your operating environment.\n\nObtain only the PROCLIB data sets that contain STC and TSO procedures. The data sets to be reviewed are obtained using the following steps:\n\n-All data sets contained in the MSTJCLxx member in the DD statement concatenation for IEFPDSI and IEFJOBS.\n-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:\n\nMSTJCL00\n\n//MSTJCL00 JOB MSGLEVEL=(1,1),TIME=1440 \n//EXEC PGM=IEEMB860,DPRTY=(15,15) \n//STCINRDR DD SYSOUT=(A,INTRDR) \n//TSOINRDR DD SYSOUT=(A,INTRDR) \n//IEFPDSI DD DSN=SYS3.PROCLIB,DISP=SHR <<===\n//DD DSN=SYS2.PROCLIB,DISP=SHR <<===\n//DD DSN=SYS1.PROCLIB,DISP=SHR <<===\n//SYSUADS DD DSN=SYS1.UADS,DISP=SHR \n//SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR\n\nJES2\n\n//JES2 PROC \n//IEFPROC EXEC PGM=HASJES20,PARM=NOREQ, \n//DPRTY=(15,15),TIME=1440,PERFORM=9 \n//ALTPARM DD DISP=SHR, \n//DSN=SYS1.PARMLIB(JES2BKUP) \n//HASPPARM DD DISP=SHR, \n//DSN=SYS1.PARMLIB(JES2PARM) \n//PROC00 DD DSN=SYS3.PROCLIB,DISP=SHR <<===\n//DD DSN=SYS2.PROCLIB,DISP=SHR <<===\n//DD DSN=SYS1.PROCLIB,DISP=SHR <<===\n//PROC01 DD DSN=SYS4.USERPROC,DISP=SHR \n//DD DSN=SYS3.PROCLIB,DISP=SHR \n//DD DSN=SYS2.PROCLIB,DISP=SHR \n//DD DSN=SYS1.PROCLIB,DISP=SHR \n//IEFRDER DD SYSOUT=* \n//HASPLIST DD DDNAME=IEFRDER\n\nJES2 initialization parameter JOBCLASS PROCLIB entries\n\nJOBCLASS(*) ACCT=NO, /* ACCT # NOT REQUIRED (DEF.)*/ \n...\nPROCLIB=01, /* DEFAULT TO //PROC01 DD (DEF.)*/\n...\nJOBCLASS(STC) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ \n...\nPROCLIB=00, /* USE //PROC00 DD (DEF.)*/ \n...\nJOBCLASS(TSU) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/\n...\nPROCLIB=00, /* USE //PROC00 DD (DEF.)*/ \n...\nPROCLIB data set that will be used in the access authorization process:\n\nSYS3.PROCLIB\nSYS2.PROCLIB \nSYS1.PROCLIB \n\nThe following PROCLIB data set will NOT be used or evaluated:\n\nSYS4.USERPROC\n\nRecommendation for sites:\n\nThe following are recommendations for the sites to ensure only PROCLIB data sets that contain the STC and TSO procedures are protected.\n\n-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.\n\nExample:\n\n//USERPROC JCLLIB ORDER=(SYS4.USERPROC)\n\n-Remove all access to the application PROCLIB data sets and only authorize system programming personnel WRITE and/or greater access to these data sets.\n\n-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.\n\n-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:\n\na. Ensure that MSTJCLxx contains only PROCLIB data sets that contain STC and TSO procedures.\nb. 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:\n\n//JES2 PROC \n//IEFPROC EXEC PGM=HASJES20,PARM=NOREQ, \n//DPRTY=(15,15),TIME=1440,PERFORM=9 \n//ALTPARM DD DISP=SHR, \n//DSN=SYS1.PARMLIB(JES2BKUP) \n//HASPPARM DD DISP=SHR, \n//DSN=SYS1.PARMLIB(JES2PARM) \n//PROC00 DD DSN=SYS3.PROCLIB,DISP=SHR \n//DD DSN=SYS2.PROCLIB,DISP=SHR\n//DD DSN=SYS1.PROCLIB,DISP=SHR \n//PROC01 DD DSN=SYS4.USERPROC,DISP=SHR \n//DD DSN=SYS3.PROCLIB,DISP=SHR \n//DD DSN=SYS2.PROCLIB,DISP=SHR \n//DD DSN=SYS1.PROCLIB,DISP=SHR \n//IEFRDER DD SYSOUT=* \n//HASPLIST DD DDNAME=IEFRDER\n\nc. 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:\n\nJOBCLASS(*) ACCT=NO, /* ACCT # NOT REQUIRED (DEF.)*/ \n...\nPROCLIB=01, /* DEFAULT TO //PROC01 DD (DEF.)*/\n...\nJOBCLASS(STC) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/ \n...\nPROCLIB=00, /* USE //PROC00 DD (DEF.)*/ \n...\nJOBCLASS(TSU) AUTH=ALL, /* ALLOW ALL COMMANDS (DEF.)*/\n...\nPROCLIB=00, /* USE //PROC00 DD (DEF.)*/ \n...\n\nd. Ensure that only system programming personnel are authorized WRITE and/or greater access to PROCLIB data sets that contain STC and TSO procedures.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223916","ruleId":"SV-223916r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must protect memory and privileged program dumps in accordance with proper security requirements.","description":"Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Screen, enter:\nTSS WHOHAS IBMFAC(IEAABD)\n\nIf the IEAABD. resource and/or generic equivalent is defined with no access and all access logged, this is not a finding.\n\nIf the IEAABD.DMPAUTH. resource and/or generic equivalent is defined with READ access limited to authorized users, this is not a finding.\n\nIf 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.\n\nIf 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.","fixText":"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.\n\n(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.)\n\nThe access requirements for memory and privileged program dump resources are listed below. 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:\n\nIEAABD.\nIEAABD.DMPAUTH.\nIEAABD.DMPAKEY.\n\nIf DEFPROT is specified in the IBMFAC RDT the following command examples are not required. To prevent access to these resources, the program dump resources and/or generic equivalent are protected using the following command.\n\nExample:\n\nTSS ADDTO(deptacid) IBMFAC(IEAABD.)\n\nIEAABD.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.\n\nExample:\n\nTSS PERMIT(authusers) IBMFAC(IEAABD.DMPAUTH.) ACCESS(READ)\nTSS PERMIT(syspaudt) IBMFAC(IEAABD.DMPAUTH.) ACCESS(UPDATE) ACTION(AUDIT)\n\nIEAABD.DMPAKEY. access will be restricted to system programming personnel and access will be logged.\n\nExample:\n\nTSS PERMIT(syspaudt) IBMFAC(IEAABD.DMPAKEY.) ACCESS(READ) ACTION(AUDIT)","ccis":["CCI-000213"]},{"vulnId":"V-223917","ruleId":"SV-223917r1137691_rule","severity":"high","ruleTitle":"IBM z/OS must protect dynamic lists in accordance with proper security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Refer to the CSV-prefixed resources defined below:\n\nCSVAPF.\nCSVAPF.MVS.SETPROG.FORMAT.DYNAMIC\nCSVAPF.MVS.SETPROG.FORMAT.STATIC\nCSVDYLPA.\nCSVDYNEX.\nCSVDYNEX.LIST\nCSVDYNL.\nCSVDYNL.UPDATE.LNKLST\nCSVLLA.\n\nIf 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.\n\nIf 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.\n\nIf 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.\n\nIf the TSS CSVDYNEX.LIST resource and/or generic equivalent are defined with READ access restricted to auditors this is not a finding.\n\nIf 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.\n\nIf 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.\n\nNote: In the above, UPDATE access can be substituted with ALL or CONTROL. Review the permissions in the TSS documentation when specifying UPDATE.","fixText":"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.\n\nThe 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:\n\nCSVAPF.\nCSVAPF.MVS.SETPROG.FORMAT.DYNAMIC\nCSVAPF.MVS.SETPROG.FORMAT.STATIC\nCSVDYLPA.\nCSVDYLPA.ADD.\nCSVDYLPA.ADD.\nCSVDYNEX.\nCSVDYNEX.LIST\nCSVDYNL.\nCSVDYNL.UPDATE.LNKLST\nCSVLLA.\n\nIf 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.\n\nThe following commands are provided for example only:\n\nTSS ADDTO(deptacid) IBMFAC(CSV)\nor\nTSS ADDTO(deptacid) IBMFAC(CSVAPF)\nTSS ADDTO(deptacid) IBMFAC(CSVDYLPA)\nTSS ADDTO(deptacid) IBMFAC(CSVDYNEX)\nTSS ADDTO(deptacid) IBMFAC(CSVDYNL)\nTSS ADDTO(deptacid) IBMFAC(CSVDYLPA)\nTSS ADDTO(deptacid) IBMFAC(CSVLLA)\n\nLimit authority to those resources to z/OS systems programmers. Restrict to the absolute minimum number of personnel with ACTION(AUDIT) and UPDATE access.\n\nSample commands are shown here to accomplish this:\n\nTSS PERMIT(syspsmpl) IBMFAC(CSVAPF.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.FORMAT) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.SETPROG.FORMAT.DYNAMIC) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(CSVAPF.MVS.SETPROG.SETPROG.FORMAT.STATIC) ACCESS(UPDATE) ACTION(AUDIT)\n\nThe CSVDYLPA.ADD resource will be permitted to BMC Mainview, CA 1, and CA Common Services STC ACIDs with ACTION(AUDIT) and UPDATE access.\n\nThe CSVDYLPA resource will be permitted to BMC Mainview, CA 1, and CA Common Services STC ACIDs with ACTION(AUDIT) and UPDATE access.\n\nSample commands are shown here to accomplish one set of resources:\n\nTSS PERMIT(syspsmpl) IBMFAC(CSVDYLPA.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(BMC Mainview STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CA 1 STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CCS STC ACID) IBMFAC(CSVDYLPA.ADD.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CA 1 STC ACID) IBMFAC(CSVDYLPA.DELETE.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CCS STC ACID) IBMFAC(CSVDYLPA.DELETE.) ACCESS(UPDATE) ACTION(AUDIT)\n\nThe CSVDYNEX.LIST resource and/or generic equivalent will be defined with ACTION(AUDIT) and UPDATE access restricted to system programming personnel.\n\nThe CSVDYNEX.LIST resource and/or generic equivalent will be defined with READ access restricted to auditors.\n\nSample commands are shown here to accomplish this:\n\nTSS PERMIT(syspsmpl) IBMFAC(CSVDYNEX.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(CSVDYNEX.LIST) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(smplsmpl) IBMFAC(CSVDYNEX.LIST) ACCESS(READ) \n\nThe CSVLLA resource will be permitted to CICS and CONTROL-O STC ACIDs with ACTION(AUDIT) and UPDATE access.\n\nSample commands are shown here to accomplish one set of resources:\n\nTSS PERMIT(syspsmpl) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CICS STC ACIDs) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT)\nTSS PERMIT(CONTROL-O STC ACID) IBMFAC(CSVLLA.) ACCESS(UPDATE) ACTION(AUDIT)","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223918","ruleId":"SV-223918r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS system commands must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From a command screen enter:\nTSS WHOHAS OPERCMDS(MVS)\n\nIf any of below is untrue for any z/OS system command resource, this is a finding.\n\nAccess to MVS resource of the OPERCMDS class is restricted to a limited number of authorized users, and all access logged.\nAccess to \"MVS.**\" is not allowed.\n\nAccess 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).\n\nNOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands.\n\nNOTE: The (MVS.SEND) Command will not be a finding if used by all.\n\nAccess 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.","fixText":"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). \n\nEnsure no access is granted at level MVS.**.\nNOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands. \nNOTE: The (MVS.SEND) Command will not be a finding if used by all. \n\nExample:\nTSS ADDTO(deptacid) OPERCMDS(MVS.)\nTSS PERMIT(usracid) OPERCMDS(MVS.ACTIVATE) ACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.CANCEL.JOB.) ACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.CONTROL.) ACCESS(UPDATE)\nACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.DISPLAY.) ACCESS(READ)\nTSS PERMIT(usracid) OPERCMDS(MVS.MONITOR) ACCESS(READ)\nTSS PERMIT(usracid) OPERCMDS(MVS.STOPMN) ACCESS(READ)","ccis":["CCI-000213"]},{"vulnId":"V-223919","ruleId":"SV-223919r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS MCS consoles access authorization(s) for CONSOLE resource(s) must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS SYSCONS(*)\n\nFor each Console defined enter:\nTSS WHOHAS SYSCONS(<console>)\n\nIf the ACID associated with each console has READ access to the corresponding resource defined in the SYSCONS resource class, this is not a finding.\n\nIf access authorization for SYSCONS resources restricts access to operations, the Master SCA, system programming personnel, or authorized personnel, this is not a finding.\n\nIf the console defined is not defined to the TSS SYSCONS resource class enter: \nTSS LIST (RDT) RESCLASS(SYSCONS)\n\nIf the SYSCONS resource class does not have the DEPROT attribute, this is a finding.\n\nFor each Console defined enter:\nTSS WHOHAS(<CONSOLE>)\n\nIf the console defined is not defined to the TSS SYSCONS resource class enter: \nTSS LIST (RDT) RESCLASS(SYSCONS)\n\nIf the SYSCONS resource class does not have the DEPROT attribute, this is a finding.","fixText":"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.\n\nReview the MCS console resources defined to z/OS and the ACP and ensure they conform to those outlined below.\n\nEach console defined in the CONSOLxx parmlib members is defined to TSS SYSCONS resource class and/or the SYSCONS resource class has the DEFPROT attribute.\n\nExample:\n\nTSS REPLACE(RDT) RESCLASS(SYSCONS) ATTR(DEFPROT)\n\nThe ACID associated with each console has access to the corresponding resource defined in the SYSCONS resource class.\n\nExample:\n\nTSS PERMIT(MMGMST) SYSCONS(MMGMST) ACCESS(READ)\n\nAccess authorization for SYSCONS resources restricts access to operations, the Master SCA, and system programming personnel.\n\nTSS PERMIT(opersmpl) SYSCONS(MMGMST) ACCESS(READ)\nTSS PERMIT(Master SCA) SYSCONS(MMGMST) ACCESS(READ)\nTSS PERMIT(syspsmpl) SYSCONS(MMGMST) ACCESS(READ)","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223920","ruleId":"SV-223920r1137691_rule","severity":"medium","ruleTitle":"CA-TSS must properly define users that have access to the CONSOLE resource in the TSOAUTH resource class.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"TSS WHOOWNS TSOAUTH(*)\nIf the Console is not defined to TSOAuth RESOURCE CLASS this is Not Applicable.\n\nRefer to the CONSOLxx member of SYS1.PARMLIB. \n\nFor each Console defined if the following is true, this is not a finding.\n\n-User ACIDs are restricted to the INFO level in the MCSAUTH attribute.\n-User ACIDs are restricted to READ access to the MVS.MCSOPER.acid resource defined in the OPERCMDS resource class.\n-User ACIDs and/or profile ACIDs are restricted to the CONSOLE resource defined in the TSOAUTH resource class.\n\nIf any of the above are untrue, this is a finding.","fixText":"Evaluate the impact of correcting any deficiencies. Develop a plan of action and implement the required changes.\n\nAt 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: \n-User ACIDs are restricted to the INFO level in the MCSAUTH attribute. \n-User ACIDs are restricted to READ access to the MVS.MCSOPER.acid resource defined in the OPERCMDS resource class. \n-User ACIDs and/or profile ACIDs are restricted to the CONSOLE resource defined in the TSOAUTH resource class. \n\nFor Example:\nTSS ADDTO (userid) MCSAUTH(INFO)\nTSS PERMIT(userid) OPERCMDS(MVS.MCSOPER.userid) \nACCESS(READ) ACTION(AUDIT)\nTSS PERMIT(oprprofileacid) TSOAUTH(CONSOLE) \nACCESS(READ) ACTION(AUDIT)","ccis":["CCI-000213"]},{"vulnId":"V-223921","ruleId":"SV-223921r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS Operating system commands (MVS.) of the OPERCMDS resource class must be properly owned.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS OPERCMDS(MVS)\n\nIf the (MVS) resource is owned, this is not a finding.\n\nIf the (MVS) resource is not owned, this is a finding.\n\nTSS LIST RDT RESCLASS(OPERCMDS)\n\nIf the (MVS) resource is not OWNED and the OPERCMDS class does not have DEFPROT as an attribute, this is a finding.","fixText":"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. \n\nWhen protecting the facilities for z/OS system commands via the OPERCMDS class, use the following controls:\n\n(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. \n\nFor example:\n\nTSS ADDTO(deptacid) OPERCMDS(MVS.)\nTSS PERMIT(usracid) OPERCMDS(MVS.ACTIVATE) ACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.CANCEL.JOB.) ACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.CONTROL.) ACCESS(UPDATE)\nACTION(AUDIT)\nTSS PERMIT(usracid) OPERCMDS(MVS.DISPLAY.) ACCESS(READ)\nTSS PERMIT(usracid) OPERCMDS(MVS.MONITOR) ACCESS(READ)\nTSS PERMIT(usracid) OPERCMDS(MVS.STOPMN) ACCESS(READ)","ccis":["CCI-000213"]},{"vulnId":"V-223922","ruleId":"SV-223922r1137691_rule","severity":"medium","ruleTitle":"CA-TSS AUTH Control Option values specified must be set to (OVERRIDE,ALLOVER) or (MERGE,ALLOVER).","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"TSS MODIFY STATUS\n\nIf the AUTH Control Option values are not set to AUTH(OVERRIDE, ALLOVER) or AUTH(MERGE, ALLOVER), this is a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-223923","ruleId":"SV-223923r1137691_rule","severity":"high","ruleTitle":"Access to the CA-TSS MODE resource class must be appropriate.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOHAS MODE(*)\n\nIf any ACIDs is permitted a mode of \"DORM\", \"WARN\", or \"IMPL\", this is a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-223924","ruleId":"SV-223924r1137691_rule","severity":"medium","ruleTitle":"Data set masking characters must be properly defined to the CA-TSS security database.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS data set(*)\n\nIf data set masking characters. (*, %, and +, **) are owned by the MSCA, this is not a finding.","fixText":"Configure all data set masking characters to be owned the MSCA.\n\nExample TSS commands to protect masking characters:\n\nTSS ADD(msca) DSN(*)\nTSS ADD(msca) DSN(%)\nTSS ADD(msca) DSN(+)","ccis":["CCI-000213"]},{"vulnId":"V-223925","ruleId":"SV-223925r1137691_rule","severity":"high","ruleTitle":"CA-TSS Emergency ACIDs must be properly limited and must audit all resource access.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer to the SYS1.UADS.\n\nAsk the System Administrator for list of all emergency ACIDs available to the site along with the associated function of each.\n\nIf there are no emergency ACIDs defined ask the system administrator for an alternate documented procedure to handle emergencies. \n\nIf there are no emergency ACIDs and no documented emergency procedure, this is a finding.\n\nIf at a minimum, an emergency ACID exists with the security administration attributes specified in accordance with the following requirements, this is not a finding.\n\nFor emergency IDs with security administration privileges, but which cannot access and update system data sets:\n\nADMIN Authority: \nACID(ALL)\nDATA(ALL) \nOTRAN(ALL)\nMISC1(INSTDATA,SUSPEND,TSSSIM,NOATS) \nMISC2(TSO,TARGET) \nMISC8(PWMAINT,REMASUSP) \nMISC9(GENERIC) FACILITY(BATCH, TSO, ROSCOE, CICS, xxxx) \nWhere 'xxxx' is a facility the application security team grants access into for their application users. \n\nAn additional class of userids can exist to perform all operating system functions except ESM administration.\n\nThese 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:\n\nData set permissions for the emergency ACIDs will be permitted as follows:\n\nTSS PER(acid) DSN(*****) ACCESS(ALL) ACTION(AUDIT)\n\nSecurity Bypass Attributes NODSNCHK, NOVOLCHK, and NORESCHK will not be given to the Emergency ACIDs.\n\nAll emergency ACID(s) are to be implemented with logging to provide an audit trail of their activities.\n\nAll 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.\n\nAll 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.\n\nAll 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.\n\n1) Review the access authorizations for all emergency ACIDs to ensure that all access permitted to these ACIDs is reviewed and approved by the ISSO.\n2) If emergency ACIDs are utilized, ensure they are restricted to performing only the operating system recovery functions or the ESM administration functions.\n\nIf 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.\n\nNote: 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.","fixText":"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.\n\nTSS PER(acid) DSN(*****) ACCESS(ALL) ACTION(AUDIT)\n\nSecurity Bypass Attributes NODSNCHK, NOVOLCHK, and NORESCHK will not be given to the Emergency ACIDs.\n\nAll emergency ACID(s) are to be implemented with logging to provide an audit trail of their activities.\n\nAll 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.\n\nAll 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.\n\nAll 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.   \n\nIf no emergency userids are in use on the system, develop and document a procedure to manage emergency access to the system.","ccis":["CCI-000213"]},{"vulnId":"V-223926","ruleId":"SV-223926r1137691_rule","severity":"medium","ruleTitle":"CA-TSS ACIDs must not have access to FAC(*ALL*).","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) DATA(BASIC)\n\nIf any ACID(s) is (are) assigned FACILITY(*ALL*), this is a finding.","fixText":"The ISSO will ensure that blanket access to all facilities; FACILITY(ALL), is never granted.\n\nReview all access to FACILITY(*ALL*). Evaluate the impact of correcting the deficiency. Develop a plan of action and remove access to FAC(*ALL*).\n\nExample:\nTSS REM(acid) FAC(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-223927","ruleId":"SV-223927r1137691_rule","severity":"medium","ruleTitle":"The CA-TSS ALL record must have appropriate access to Facility Matrix Tables.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Review the ALL record for the assignment of FACILITY.\n\nIf CA-Top Secret facilities are granted via the ALL record, with the exception of DFHSM/HSM, this is a finding. \n\nThe DFHSM/HSM FACILITY can be determined by reviewing FACLIST for the FACILITY that contains INITPGM=ARC.","fixText":"Review ALL record for FACILITY access. Evaluate the impact of correcting the deficiency. Develop a plan of action and remove access.","ccis":["CCI-000213"]},{"vulnId":"V-223928","ruleId":"SV-223928r1137691_rule","severity":"medium","ruleTitle":"Data set masking characters allowing access to all data sets must be properly restricted in the CA-TSS security database.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer the accesses to the TSS masking character (*, *., and/or **) for data sets. \n\nIf the following guidance is true, this is not a finding.\n\nIf the TSS data set access authorizations restrict READ access to auditors, this is not a finding.\n\nIf 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.\n\nIf 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.\n\nIf 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.","fixText":"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.\n\nThe 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.\n\n(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.)\n\nAuditors may require READ access to all data sets.\nDASD administrators, Trusted Started Tasks, emergency users, and DASD batch users that require READ and/or greater access to perform maintenance to all data sets.\nIf CA VTAPE is installed on the system, READ access can be given to the CA VTAPE STCs and/or batch users.\nAll accesses authorizations will be logged. The exception is the logging requirement is not required for Trusted Started Tasks.\n\nThe following commands are provided as a sample for implementing data set controls:\n\nTSS ADDTO(msca) DATASET(*.)\nTSS PERMIT(smplsmpl) DATASET(*.) ACCESS(READ) ACTION(AUDIT)\nTSS PERMIT(CA VTape STC) DATASET(*.) ACCESS(READ) ACTION(AUDIT)\nTSS PERMIT(dasbsmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(dasdsmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(emersmpl) DATASET(*.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(tstcsmpl) DATASET(*.) ACCESS(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-223929","ruleId":"SV-223929r1137691_rule","severity":"high","ruleTitle":"IBM z/OS DASD Volume access greater than CREATE found in the CA-TSS database must be limited to authorized information technology personnel requiring access to perform their job duties.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS VOLUME(*) \n\nFor each volume identified issue WHOHAS (<volume id>)\n\nIf 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.\n\nIf access authorization for volumes exceeds the requirements without justification, this is a finding.\n\nNOTE: 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.","fixText":"Ensure that DASD VOLUME access authorization greater than CREATE is not permitted unless authorized by the ISSO.\n\nReview all access to DASD VOLUMEs. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the required changes.\n\n*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.\n\nDomain Level DASD/Storage administrators access should be granted VOL(*ALL*)ACC(ALL)ACTION(AUDIT)PRIVPGM(list of privileged programs)","ccis":["CCI-000213"]},{"vulnId":"V-223930","ruleId":"SV-223930r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS Sensitive Utility Controls must be properly defined and protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer to the table of Sensitive Utilities resources and/or generic equivalent as detail in the table below.\n\nIf the TSS resource access authorizations for the following sensitive utilities restrict access to the appropriate personnel, this is not a finding.\n\nSensitive Utility Controls\nProgram Product Function \nAHLGTF z/OS System Activity Tracing \nHHLGTF\nIHLGTF \n\nICPIOCP z/OS System Configuration \nIOPIOCP\nIXPIOCP\nIYPIOCP\nIZPIOCP \n\nBLSROPTR z/OS Data Management \n\nDEBE OS/DEBE Data Management \n\nDITTO OS/DITTO Data Management \n\nFDRZAPOP FDR Product Internal Modification \n\nGIMSMP SMP/E Change Management Product \n\nICKDSF z/OS DASD Management \n\nIDCSC01 z/OS IDCAMS Set Cache Module \n\nIEHINITT z/OS Tape Management \n\nIFASMFDP z/OS SMF Data Dump Utility \n\nIND$FILE z/OS PC to Mainframe File Transfer\n (Applicable only for classified systems) \n\nCSQJU003 IBM WebSphereMQ\nCSQJU004\nCSQUCVX\nCSQ1LOGP \nCSQUTIL \n\nWHOIS z/OS Share MOD to identify user name from USERID. \nRestricted to data center personnel only.\n\nIf the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding.\n\nIf the TSS resource logging is correctly specified, this is not a finding.","fixText":"Ensure that the following are properly specified in the ACP.\n\nNote: 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.\n\nEnsure 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:\n\nSensitive Utility Controls\nProgram Product Function \nAHLGTF z/OS System Activity Tracing \nHHLGTF\nIHLGTF \n\nICPIOCP z/OS System Configuration \nIOPIOCP\nIXPIOCP\nIYPIOCP\nIZPIOCP \n\nBLSROPTR z/OS Data Management \n\nDEBE OS/DEBE Data Management \n\nDITTO OS/DITTO Data Management \n\nFDRZAPOP FDR Product Internal Modification \n\nGIMSMP SMP/E Change Management Product \n\nICKDSF z/OS DASD Management \n\nIDCSC01 z/OS IDCAMS Set Cache Module \n\nIEHINITT z/OS Tape Management \n\nIFASMFDP z/OS SMF Data Dump Utility \n\nIND$FILE z/OS PC to Mainframe File Transfer\n (Applicable only for classified systems) \n\nCSQJU003 IBM WebSphereMQ\nCSQJU004\nCSQUCVX\nCSQ1LOGP \nCSQUTIL \n\nWHOIS z/OS Share MOD to identify user name from USERID. \n Restricted to data center personnel only.\n\nThe TSS resources as designated in the above table are owned and/or DEFPROT is specified for the resource class.\n\nThe TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table.\n\nThe following commands are provided as a sample for implementing resource controls:\n\nTSS ADD(dept-acid) PROGRAM(AHLGTF)\nTSS PERMIT(stcgsmpl) PROGRAM(AHLGTF) ACTION(AUDIT)","ccis":["CCI-000213"]},{"vulnId":"V-223931","ruleId":"SV-223931r991591_rule","severity":"medium","ruleTitle":"IBM z/OS Started tasks must be properly defined to CA-TSS.","description":"Started procedures have system generated job statements that do not contain the user, group, or password statements. To enable the started procedure to access the same protected resources that users and groups access, started procedures must have an associated USERID. If a USERID is not associated with the started procedure, the started procedure will not have access to the resources.\n\nTo ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.","checkContent":"Refer to the site security plan, the system administrator, and system libraries to determine list of stated tasks available on the system.\n\nIf the following guidance is true, this is not a finding.\n\n -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.\n\n -Every ACID with the STC Facility has a corresponding entry defined in the STC record.\n\n -Every ACID defined in the STC record has a corresponding user ACID defined to TSS with the STC Facility.\n\n -All STC ACIDs will have a password generated in accordance with STIG requirements.\n\n -All STC ACIDs will be sourced to the internal reader (e.g., ADD(stc-acid) SOURCE(INTRDR).\n\n -The STC ACIDs may have the NOSUSPEND attribute.","fixText":"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:\n\nAll 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.\n\nTSS ADD(stc-acid) FACILITY(STC BATCH)\n\nEach 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.\n\nTSS REP(stc-acid) PASSWORD(xxxxxxxx,0)\n\nEnsure 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. \n\nAll STC ACIDs will be sourced to the internal reader. This control will further protect the unauthorized use of STC ACIDs.\n\nTSS ADD(stc-acid) SOURCE(INTRDR)\n\nEvery STC will be defined to the STC table, associated with a specific procedure, and granted minimum access.\n\nTSS ADD(STC) PROCNAME(stc-proc) ACID(stc-acid)\n\nNote: 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:\n\nAll 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.\n\nTSS ADD(stc-acid) FACILITY(STC BATCH)\n\nEach 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.\n\nTSS REP(stc-acid) PASSWORD(xxxxxxxx,0)\n\nEnsure 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. \n\nAll STC ACIDs will be sourced to the internal reader. This control will further protect the unauthorized use of STC ACIDs.\n\nTSS ADD(stc-acid) SOURCE(INTRDR)\n\nEvery STC will be defined to the STC table, associated with a specific procedure, and granted minimum access.\n\nTSS ADD(STC) PROCNAME(stc-proc) ACID(stc-acid)\n\nNote: The STC ACIDs may have the NOSUSPEND attribute to exempt an STC ACID from suspension for excessive violations.","ccis":["CCI-000366"]},{"vulnId":"V-223932","ruleId":"SV-223932r991589_rule","severity":"medium","ruleTitle":"The CA-TSS CANCEL Control Option must not be specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.\n\nThe CANCEL Control Option allows security administrators to use the O/S CANCEL command to bring the TSS address space down.","checkContent":"From the ISPF Command enter:\nTSS MODIFY STATUS\n\nIf the CANCEL Control Option is not specified, this is not a finding.","fixText":"Remove the CANCEL sub-option from the Control Options list.\n\nTSS MODIFY(control_option [(suboption_list)])","ccis":["CCI-000366"]},{"vulnId":"V-223933","ruleId":"SV-223933r991589_rule","severity":"medium","ruleTitle":"The CA-TSS HPBPW Control Option must be set to three days maximum.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"From the ISPF Command enter:\nTSS MODIFY STATUS\n\nIf the HPBPW Control Option value is set to (3) days maximum, this is not a finding.\n\nIf the HPBPW Control Option value is set to greater than (3) days, this is a finding.","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-223934","ruleId":"SV-223934r991589_rule","severity":"medium","ruleTitle":"The CA-TSS INSTDATA Control Option must be set to 0.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"From the ISPF Command enter:\nTSS MODIFY STATUS\n\nIf the INSTDATA Control Option is set to NONE this is not a finding.","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-223935","ruleId":"SV-223935r991589_rule","severity":"medium","ruleTitle":"The CA-TSS OPTIONS Control Option must include option 4 at a minimum.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the OPTIONS Control Option contains at a minimum option number (4), this is not a finding.","fixText":"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.\n\nThe OPTIONS Control Option must contain at a minimum option number (4).\n\nExample TSS PARMFILE Control Option entry:\nOPTIONS(4,5,6,12,14)","ccis":["CCI-000366"]},{"vulnId":"V-223936","ruleId":"SV-223936r991589_rule","severity":"medium","ruleTitle":"CA-TSS TEMPDS Control Option must be set to YES.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the TEMPDS Control Option value is set to TEMPDS(YES), this not a finding.","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-223937","ruleId":"SV-223937r991589_rule","severity":"medium","ruleTitle":"The number of CA-TSS control ACIDs must be justified and properly assigned.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) TYPE(SCA) DATA(BASIC)\n\nIf the persons listed agree with the site security plan, this is not a finding.","fixText":"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.\n\nTYPE=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:\n\n-Domain level Information System Security Officer (ISSO) - full administrative authorities and access rights needed to perform required and documented role/responsibilities/function.\n-Assistance Domain Level Information System Security Officer or \"backup\" or ISSO (up to same access as 1).\n-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. \n\nException: 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.","ccis":["CCI-000366","CCI-002145"]},{"vulnId":"V-223938","ruleId":"SV-223938r991589_rule","severity":"medium","ruleTitle":"The number of CA-TSS ACIDs with MISC9 authority must be justified.","description":"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) DATA(ADMIN) \n\nIf 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.","fixText":"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.","ccis":["CCI-000366","CCI-002145"]},{"vulnId":"V-223939","ruleId":"SV-223939r991589_rule","severity":"medium","ruleTitle":"The CA-TSS LUUPDONCE Control Option value specified must be set to NO.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the LUUPDONCE Control Option value is set to \"YES\", this is a finding.","fixText":"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.","ccis":["CCI-000366","CCI-002251"]},{"vulnId":"V-223940","ruleId":"SV-223940r991589_rule","severity":"medium","ruleTitle":"The CA-TSS Automatic Data Set Protection (ADSP) Control Option must be set to NO.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the ADSP Control Option value is not set to \"ADSP(NO)\", this is a finding.","fixText":"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.","ccis":["CCI-000366","CCI-002358"]},{"vulnId":"V-223941","ruleId":"SV-223941r991589_rule","severity":"medium","ruleTitle":"CA-TSS RECOVER Control Option must be set to ON.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the RECOVER Control Option value is not set to \"RECOVER(ON)\", this is a finding.","fixText":"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. \n\nRECOVER(ON)","ccis":["CCI-000366","CCI-000550"]},{"vulnId":"V-223942","ruleId":"SV-223942r958480_rule","severity":"medium","ruleTitle":"IBM z/OS must properly configure CONSOLxx members.","description":"In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"Review each CONSOLxx parmlib member. \n\nIf the following guidance is true, this is not a finding. \n\nThe \"DEFAULT\" statement for each CONSOLxx member specifies \"LOGON(REQUIRED)\" or \"LOGON(AUTO)\".\n\nThe \"CONSOLE\" statement for each console assigns a unique name using the \"NAME\" parameter.\n\nThe \"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.\n\nNote: The site should be able to determine the system consoles. However, it is imperative that the site adhere to the \"DEFAULT\" statement requirement.","fixText":"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.\n\nConfigure 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.\n\nNote: The site should be able to determine the system consoles. However, it is imperative that the site adhere to the \"DEFAULT\" statement requirement.","ccis":["CCI-000382"]},{"vulnId":"V-223943","ruleId":"SV-223943r958480_rule","severity":"medium","ruleTitle":"IBM z/OS must properly protect MCS console userid(s).","description":"In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"Refer to IEASYS00 to determine correct CONSOLxx member.\n\nExamine the CONSOLxx member.\n\nIf the following guidance is true, this is not a finding.\n\nEach console defined in the currently active CONSOLxx parmlib member in EXAM.RPT(PARMLIB) is associated with a valid TSS ACID.\n\nEach console ACID has no special privileges and/or attributes (e.g., BYPASSING, CONSOLE, etc.; excluding VTAM SMCS consoles).\n\nEach 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.\n\nEach 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.\n\nNOTE: 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.","fixText":"Review the MCS console resources defined to z/OS and the ACP, and ensure they conform to those outlined below.\n\nEach console defined in the currently active CONSOLxx parmlib member in EXAM.RPT(PARMLIB) is associated with a valid TSS ACID.\n\nEach console ACID has no special privileges and/or attributes (e.g., BYPASSING, CONSOLE, etc.).\n\nEach console ACID has no accesses to interactive on-line facilities (e.g., TSO, CICS, etc.; excluding VTAM SMCS consoles). \n\nEach console can have the Facility of CONSOLE.\n\nEach 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.\n\nNOTE: 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.\n\nExample: (These are only examples, not requirements.)\n\nTSS CREATE(consnoautolog) TYPE(PROFILE) \nNAME('MCS consoles with no autolog')\nDEPT('SYS1')\n\nTSS CREATE(consautolog) TYPE(PROFILE) -\nNAME('MCS consoles with autolog') -\nDEPT('SYS1')\n\nTSS CREATE(consname) NAME('MCS console name') -\nFACILITY(CONSOLE) PASSWORD(password,0) -\nPROFILE(consgroup)\n\nTSS PER(consautolog) OPERCMDS(MVS.CONTROL) ACCESS(READ)\nTSS PER(consautolog) OPERCMDS(MVS.DISPLAY) ACCESS(READ)\nTSS PER(consautolog) OPERCMDS(MVS.MONITOR) ACCESS(READ)\nTSS PER(consautolog) OPERCMDS(MVS.STOPMN) ACCESS(READ)\n\nTSS PER(consname) SYSCONS(consname) ACCESS(READ)","ccis":["CCI-000382"]},{"vulnId":"V-223944","ruleId":"SV-223944r958482_rule","severity":"medium","ruleTitle":"The CA-TSS CPFRCVUND Control Option value specified must be set to NO.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the \"CPFRCVUND\" Control Option value is set to \"YES\", this is a finding.","fixText":"Configure the CPFRCVUND control option value to (NO). \n\nEvaluate the impact associated with implementation of the control option. \n\nDevelop a plan of action to set the control option setting to \"NO\" and proceed with the change.","ccis":["CCI-000764"]},{"vulnId":"V-223945","ruleId":"SV-223945r958482_rule","severity":"medium","ruleTitle":"The CA-TSS CPFTARGET Control Option value specified must be set to LOCAL.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the CPFTARGET Control Option value specified is not set to \"LOCAL\", this is a finding.","fixText":"Configure the CPFTARGET Control Option value specified set to LOCAL.","ccis":["CCI-000764"]},{"vulnId":"V-223946","ruleId":"SV-223946r958482_rule","severity":"low","ruleTitle":"CA-TSS User ACIDs and Control ACIDs must have the NAME field completed.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST (ACIDs) DATA (BASIC)\n\nIf any ACID does not have the \"NAME\" field completed, this is a finding.","fixText":"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.","ccis":["CCI-000764"]},{"vulnId":"V-223947","ruleId":"SV-223947r958482_rule","severity":"high","ruleTitle":"The CA-TSS PASSWORD(NOPW) option must not be specified for any ACID type.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS 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.\n\nIf PASSWORD(NOPW) is specified for any ACID types (USER, DCA, VCA, ZCA, LSCA, SCA, and MSCA), this is a finding.","fixText":"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.\n\nThe following command is an example of how this can be corrected.\n\nTSS REPLACE(user_ACID) PASSWORD(Text4Pwd,60","ccis":["CCI-000764"]},{"vulnId":"V-223948","ruleId":"SV-223948r958482_rule","severity":"low","ruleTitle":"Interactive ACIDs defined to CA-TSS must have the required fields completed.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST (ACIDs) DATA (BASIC,TSO,CICS)\n\nIf all the fields and information listed below, are not present for all interactive users this is a finding.\n\nFIELD DESCRIPTION VALUE\nFACILITY Validated facilities to use BATCH, TSO, NCPASS, or other interactive Facility\nPASSWORD logon password must have a value\nINSTDATA Installation data optional\nPROFILE Profile(s) optional\nTSOLPROC Default TSO logon PROC optional for TSO users\nTSOLACCT Default TSO logon account may be required for a fee for service.","fixText":"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:\n\nFIELD DESCRIPTION VALUE\nFACILITY Validated facilities to use BATCH, TSO, NCPASS, or other interactive Facility\nPASSWORD logon password must have a value\nINSTDATA Installation data optional\nPROFILE Profile(s) optional\nTSOLPROC Default TSO logon PROC optional for TSO users\nTSOLACCT Default TSO logon account may be required\nfor a fee for service.","ccis":["CCI-000764"]},{"vulnId":"V-223950","ruleId":"SV-223950r958482_rule","severity":"medium","ruleTitle":"CA-TSS Batch ACID(s) submitted through RJE and NJE must be sourced.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"Refer to data obtained from the site installation identifying batch type ACIDs. \n\nIf 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.","fixText":"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) \n\nDevelop a plan of action and implement the changes as specified.","ccis":["CCI-000764"]},{"vulnId":"V-223951","ruleId":"SV-223951r958482_rule","severity":"medium","ruleTitle":"IBM z/OS DASD management ACIDs must be properly defined to CA-TSS.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"Refer to data obtained from the site installation identifying DASD maintenance ACIDs. \n\nIf each DASD Maintenance ACID has batch Facility, this is not a finding.","fixText":"Define all batch ACIDs to the BATCH facility.","ccis":["CCI-000764"]},{"vulnId":"V-223952","ruleId":"SV-223952r998495_rule","severity":"medium","ruleTitle":"CA-TSS user accounts must uniquely identify system users.","description":"To assure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated.\n\nA group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS \"root\" user account, the Windows \"Administrator\" account, the \"sa\" account, or a \"helpdesk\" account.\n\nFor example, the UNIX and Windows operating systems offer a \"switch user\" capability allowing users to authenticate with their individual credentials and, when needed, \"switch\" to the administrator role. This method provides for unique individual authentication prior to using a group authenticator.\n\nUsers (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the operating system without identification or authentication.\n\nRequiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.\n\nSatisfies: SRG-OS-000109-GPOS-00056, SRG-OS-000121-GPOS-00062, SRG-OS-000125-GPOS-00065","checkContent":"Obtain a list of all userids that are shared among multiple users (i.e., not uniquely identified system users).\n\nIf there are no shared userids on this domain, this is not a finding.\n\nIf there are shared userids on this domain, this is a finding.\n\nNOTE: Userid","fixText":"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.","ccis":["CCI-004045","CCI-000804","CCI-000877"]},{"vulnId":"V-223953","ruleId":"SV-223953r998496_rule","severity":"medium","ruleTitle":"CA-TSS security administrator must develop a process to suspend userids found inactive for more than 35 days.","description":"Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.\n\nOperating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) \n\nIf every user shows a LAST-USED=yy.ddd within the past \"35\" days, this is not a finding.\n\nNOTE: VALID FOR INTERACTIVE USERIDS, NOT VALID FOR STARTED TASK USERIDS AND BATCH USERIDS.","fixText":"Develop a procedure to check all userids for inactivity of more than \"35\" days. If found, the information system security officer (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.","ccis":["CCI-003627"]},{"vulnId":"V-223954","ruleId":"SV-223954r998497_rule","severity":"medium","ruleTitle":"The CA-TSS INACTIVE Control Option must be properly set.","description":"Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.\n\nOperating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the INACTIVE Control Option is set to a value of \"0\", this is not a finding.","fixText":"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.\n\nThe INACTIVE Control Option value is set properly with the command:\n\nTSS MODIFY INACTIVE(0)","ccis":["CCI-003627"]},{"vulnId":"V-223955","ruleId":"SV-223955r1137695_rule","severity":"medium","ruleTitle":"The CA-TSS AUTOERASE Control Option must be set to ALL for all systems.","description":"Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection.\n\nThis requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies.\n\nThere may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the AUTOERASE Control Option value is set to (ALL), this is not a finding.","fixText":"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.","ccis":["CCI-001090"]},{"vulnId":"V-223956","ruleId":"SV-223956r958550_rule","severity":"medium","ruleTitle":"CA-TSS DOWN Control Option values must be properly specified.","description":"Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Operating systems that fail suddenly and with no incorporated failure state planning may leave the system available but with a reduced security protection capability. Preserving operating system state information also facilitates system restart and return to the operational mode of the organization with less disruption to mission-essential processes. \n\nAbort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf 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.\n\nIf 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.","fixText":"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.\n\nSetting if ONLY systems personnel are defined in SYS1.UADS: DOWN(BW,SB,TN,OW)\n\nSetting if any non-systems personnel are defined in SYS1.UADS: DOWN(BW,SB,TW,OW)","ccis":["CCI-001190"]},{"vulnId":"V-223957","ruleId":"SV-223957r958808_rule","severity":"high","ruleTitle":"The CA-TSS Facility Control Option must specify the sub option of MODE=FAIL.","description":"Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.\n\nThe organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.\n\nVerification of white-listed software occurs prior to execution or at system startup.\n\nThis requirement applies to operating system programs, functions, and services designed to manage system processes and configurations (e.g., group policies).","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY(FACILITY(ALL))\n\nIf the Facility Control Option does not specifies the sub option of \"MODE=FAIL\" for all facilities, this is a finding.","fixText":"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.","ccis":["CCI-001774"]},{"vulnId":"V-223958","ruleId":"SV-223958r998498_rule","severity":"medium","ruleTitle":"CA-TSS ACID creation must use the EXP option.","description":"Without providing this capability, an account may be created without a password. Nonrepudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon.\n\nTemporary passwords are typically used to allow access when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts which allow the users to log on, yet force them to change the password once they have successfully authenticated.","checkContent":"Ask the system administrator (SA) for the procedures for creating new ACIDs.\n\nIf the procedure contains the \"EXP\" option, this is not a finding.","fixText":"Ensure procedures to create New Acids include the \"EXP\" option.\n\nExample:\nTSS CREATE(USER02) NAME('ANDY POE')\nTYPE(USER)\nDEPARTMENT(PAYDEPT)\nPASSWORD(INITIAL,60,EXP)\nFACILITY(TSO)","ccis":["CCI-002041","CCI-004063"]},{"vulnId":"V-223959","ruleId":"SV-223959r958730_rule","severity":"medium","ruleTitle":"The CA-TSS SUBACID Control Option must be set to U,8.","description":"In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.\n\nSome programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review.","checkContent":"From this ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the SUBACID Control Option values are NOT set to \"SUBACID(U,8)\", this is a finding.","fixText":"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.","ccis":["CCI-002233"]},{"vulnId":"V-223960","ruleId":"SV-223960r958730_rule","severity":"medium","ruleTitle":"CA-TSS must use propagation control to eliminate ACID inheritance.","description":"In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.\n\nSome programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY FACILITY(ALL)\n\nenter\nTSS MODIFY FACILITY(<FACILITY>)\n\nIf no Facility is defined with both the \"MULTIUSER\" and \"ASUBM\" attributes further analysis is not needed.\n\nFor each Facility with \"MULTIUSER\" and \"ASUBM\" attribute, review the @ACIDS report to determine which ACID(s) has (have) the following:\n\n-A Master Facility of the Facility with \"MULTIUSER\" and \"ASUBM\" attribute, and,\n-The Facility of \"BATCH\"\n\nIf 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.","fixText":"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.\n\nThe following Example shows the CONTROL-M STC ACID being owned to the PROPCNTL resource class:\nTSS ADD(deptacid) PROPCNTL(control-m-acid)","ccis":["CCI-002233"]},{"vulnId":"V-223961","ruleId":"SV-223961r958730_rule","severity":"medium","ruleTitle":"IBM z/OS scheduled production batch ACIDs must specify the CA-TSS BATCH Facility, and the Batch Job Scheduler must be authorized to the Scheduled production CA-TSS batch ACID.","description":"In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.\n\nSome programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review.","checkContent":"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.\n\nEnsure that each identified batch ACID is sourced to a specific submission process used only for batch processing. \n\nIf the following guidance is true, this is not a finding.\n\n-The job scheduler is cross-authorized to the batch ACIDs.\n-The Facility of BATCH is specified for each batch ACID.\n-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.\n-The batch ACIDS may have the NOSUSPEND attribute.","fixText":"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.","ccis":["CCI-002233"]},{"vulnId":"V-223962","ruleId":"SV-223962r958732_rule","severity":"medium","ruleTitle":"CA-TSS ADMINBY Control Option must be set to ADMINBY.","description":"Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.","checkContent":"From ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the ADMINBY Control Option value is not set or set to \"NOADMBY\", this is a finding.","fixText":"Ensure ADMINBY control option is set to \"ADMINBY\" to record who when and where information in the ACID security record for administrative changes.\n\nEvaluate 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.","ccis":["CCI-002234"]},{"vulnId":"V-223963","ruleId":"SV-223963r958732_rule","severity":"medium","ruleTitle":"CA-TSS LOG Control Option must be set to (SMF,INIT, SEC9, MSG).","description":"Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\n\nIf the LOG Control Option is NOT set to (SMF,INIT, SEC9, MSG), this is a finding.","fixText":"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.\n\nLOG(SMF,INIT, SEC9, MSG)","ccis":["CCI-002234"]},{"vulnId":"V-223964","ruleId":"SV-223964r958732_rule","severity":"medium","ruleTitle":"CA-TSS MSCA ACID password changes must be documented in the change log.","description":"Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.","checkContent":"From ISPF Command Shell enter: \nExec the CA-TSS TSSAUDIT Utility using CHANGES Control Statement.\nNote: If running Quest NC-Pass, validate that the MSCA ACID has the FACILITY of NCPASS and SECURID resource in the ABSTRACT resource class.\n\nIf the MSCA password changes are documented in the change log, this is not a finding.","fixText":"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.","ccis":["CCI-002234"]},{"vulnId":"V-223965","ruleId":"SV-223965r958726_rule","severity":"medium","ruleTitle":"The IBM z/OS IEASYMUP resource must be protected in accordance with proper security requirements.","description":"Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS IBMFAC(IEASYMUP)\n\nIf the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding.\n\nEnter\nTSS WHOHAS IBMFAC(IEASYMUP)\n\nIf 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.","fixText":"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.\n\nLimit access to the IEASYMUP resources to above personnel with UPDATE and/or greater access.\n\nThe following commands are provided as a sample for implementing resource controls:\n\nTSS ADD(ADMIN) IBMFAC(IEASYMUP)\n\nTSS PERMIT(<dasdsmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT)\nTSS PERMIT(<syspsmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT)\nTSS PERMIT(<tapesmpl>) IBMFAC(IEASYMUP) ACC(U) ACTION(AUDIT)","ccis":["CCI-002235"]},{"vulnId":"V-223966","ruleId":"SV-223966r958726_rule","severity":"medium","ruleTitle":"CA-TSS Default ACID must be properly defined.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST STC\n\nIf *DEF* has action of *FAIL* this is not a finding.\n\nIf the default ACID is defined enter:\nTSS List(<defined ACID>)\n\nIf the ACID has no access to resources and no facility access and sourced to the internal reader, this is not a finding.\n\nIf any of the above is untrue, this is a finding.","fixText":"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.\n\nAll 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:\n\nTSS ADD(STC) PROCNAME(DEFAULT) ACID(FAIL)\n\nIf a valid requirement exists to establish a default STC, the following restrictions also apply:\n\na. The ISSO will maintain the written request, justification, and authorization.\n\nb. The STC's ACID will have no other facilities permitted to it.\n\nc. The STC's ACID will have a permission of DSN(*****) ACCESS(NONE).\n\nTSS PERMIT(stc-acid) DSN(*****) ACCESS(NONE)\n\nd. The STC's ACID will not have any permission to the resources available to TSS.\n\ne. The STC's ACID will be sourced to the internal reader:\n\nADD(stc-acid) SOURCE(INTRDR)\n\nf. An entry will be made in the STC table identifying the default ACID name as follows (\"stc-acid\" site defined):\n\nTSS ADD(STC) PROCNAME(DEFAULT) ACID(stc-acid)","ccis":["CCI-002235"]},{"vulnId":"V-223967","ruleId":"SV-223967r958726_rule","severity":"high","ruleTitle":"The CA-TSS BYPASS attribute must be limited to trusted STCs only.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(STC)\n\nIf 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.\n\nGuidelines for reference:\n\n Assign the TRUSTED attribute when one of the following conditions applies:\n-The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation.\n-Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem.\n-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.\n\nAdditionally 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.","fixText":"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.\n\nTrusted STCs:\n\nWhile 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.\n\nGuidelines for reference:\n\n Assign the TRUSTED attribute when one of the following conditions applies:\n-The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation.\n-Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem.\n-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.\n\nAdditionally 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.","ccis":["CCI-002235"]},{"vulnId":"V-223968","ruleId":"SV-223968r958726_rule","severity":"medium","ruleTitle":"CA-TSS MSCA ACID must perform security administration only.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) DATA(ALL,PA) TYPE(SCA)\n\nIf the MSCA ACID has access limited to performing security administration functions only, this is not a finding.\n\nBelow 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.\n\nACCESSORID = MSCA NAME = \"primary SCA\"\nTYPE = MASTER\nFACILITY = BATCH \nPROFILES = SECURID\nATTRIBUTES = AUDIT,CONSOLE,NOATS \ndata set = %. *.\ndata set = ***** +.\nVOLUMES = *(G)\nXA data set = SYS3.TSS.BACKUP\nACCESS = UPDATE\nACTION = AUDIT \n----------- ADMINISTRATION AUTHORITIES\nRESOURCE = *ALL*\nACCESS = ALL\nACID = *ALL*\nFACILITIES = *ALL*\nLIST DATA = *ALL*,PROFILES,PASSWORD,SESSKEY\nMISC1 = *ALL*\nMISC2 = *ALL*\nMISC4 = *ALL*\nMISC8 = *ALL*\nMISC9 = *ALL*\n\nNOTE 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.\n\nNOTE 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.","fixText":"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.\n\nBelow 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.\n\nACCESSORID = MSCA NAME = \"primary SCA\"\nTYPE = MASTER\nFACILITY = BATCH \nPROFILES = SECURID\nATTRIBUTES = AUDIT,CONSOLE,NOATS \ndata set = %. *.\ndata set = ***** +.\nVOLUMES = *(G)\nXA data set = SYS3.TSS.BACKUP\nACCESS = UPDATE\nACTION = AUDIT \n----------- ADMINISTRATION AUTHORITIES\nRESOURCE = *ALL*\nACCESS = ALL\nACID = *ALL*\nFACILITIES = *ALL*\nLIST DATA = *ALL*,PROFILES,PASSWORD,SESSKEY\nMISC1 = *ALL*\nMISC2 = *ALL*\nMISC4 = *ALL*\nMISC8 = *ALL*\nMISC9 = *ALL*\n\nNOTE 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.\n\nNOTE 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.\n\nNOTE 3: MSCA account must be limited in access, to least privileged access of resources required to function.\n\nNOTE 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.","ccis":["CCI-002235"]},{"vulnId":"V-223969","ruleId":"SV-223969r958726_rule","severity":"high","ruleTitle":"CA-TSS ACIDs granted the CONSOLE attribute must be justified.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"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.\n\nIf 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.","fixText":"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.","ccis":["CCI-002235"]},{"vulnId":"V-223970","ruleId":"SV-223970r958726_rule","severity":"medium","ruleTitle":"CA-TSS ACIDs defined as security administrators must have the NOATS attribute.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"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.\n\nIf all security administrators have the \"NOATS\" attribute, this is not a finding.","fixText":"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.\n\nNOTE: The NOATS attribute may be added to an ACID or an ACID's PROFILE.\n\nThe following command may be issued to determine if the NOATS attribute is defined to an ACID or an ACID's PROFILE:\ntss list(<acid>) data(basic,profile)","ccis":["CCI-002235"]},{"vulnId":"V-223972","ruleId":"SV-223972r958636_rule","severity":"medium","ruleTitle":"CA-TSS VTHRESH Control Option values specified must be set to (10,NOT,CAN).","description":"Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.\n\nSession termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.\n\nConditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use.\n\nThis capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance.","checkContent":"From the ISPF Control Shell enter:\nTSS MODIFY STATUS\n\nIf the VTHRESH Control Option values are not set to \"VTHRRESH(10,NOT,CAN)\", this is a finding.","fixText":"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.","ccis":["CCI-002361"]},{"vulnId":"V-223973","ruleId":"SV-223973r1050767_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration statements must have a proper banner statement with the Standard Mandatory DOD Notice and Consent Banner.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007","checkContent":"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: \n /etc/ftp.data \n SYSFTPD DD statement \n jobname.FTP.DATA \n SYS1.TCPPARMS(FTPDATA) \n tcpip.FTP.DATA \n\nExamine the BANNER statement. \n\nIf 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. \n\nThe 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:\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","fixText":"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:\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.","ccis":["CCI-000048","CCI-000050","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223974","ruleId":"SV-223974r958406_rule","severity":"medium","ruleTitle":"IBM z/OS SMF recording options for the FTP server must be configured to write SMF records for all eligible events.","description":"Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).\n\nSatisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000392-GPOS-00172","checkContent":"If FTPDATA is configured with the following SMF statements, this is not a finding.\n\nFTP.DATA Configuration Statements\nSMF TYPE119\nSMFJES TYPE119\nSMFSQL TYPE119\nSMFAPPE [Not coded or commented out]\nSMFDEL [Not coded or commented out]\nSMFEXIT [Not coded or commented out]\nSMFLOGN [Not coded or commented out]\nSMFREN [Not coded or commented out]\nSMFRETR [Not coded or commented out]\nSMFSTOR [Not coded or commented out]","fixText":"Configure SMF options to conform to the specifications in the FTPDATA Configuration Statements below or that they are commented out.\n\nSMF TYPE119\nSMFJES TYPE119\nSMFSQL TYPE119\nSMFAPPE [Not coded or commented out]\nSMFDEL [Not coded or commented out]\nSMFEXIT [Not coded or commented out]\nSMFLOGN [Not coded or commented out]\nSMFREN [Not coded or commented out]\nSMFRETR [Not coded or commented out]\nSMFSTOR [Not coded or commented out]\n\nThe 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:\n\n70 - Append\n70 - Delete and Multiple Delete\n72 - Invalid Logon Attempt\n70 - Rename\n70 - Get (Retrieve) and Multiple Get\n70 - Put (Store and Store Unique) and Multiple Put\n\nSMF 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.","ccis":["CCI-000067","CCI-002884"]},{"vulnId":"V-223975","ruleId":"SV-223975r1196257_rule","severity":"medium","ruleTitle":"CA-TSS permission bits and user audit bits for HFS objects that are part of the FTP server component must be properly configured.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell, enter:\n\nomvs\n\nAt the input line, enter:\n\ncd /usr/sbin/\nenter\nls -alW\n\nIf the following File permission and user Audit Bits are true, this is not a finding.\n\n/usr/sbin/ftpd 1740 fff\n/usr/sbin/ftpdns 1755 fff\n\ncd \nls -alW\n\nIf the following file permission and user Audit Bits are true, this is not a finding.\n\n/etc/ftp.data 0744 faf\n/etc/ftp.banner 0744 faf\n\nNote: Some of the files listed above are not used in every configuration. The absence of a file is not considered a finding.\n\nThe /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.\n\nThe /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.\n\nThe /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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"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:\n\nFTP Server HFS Object Security Settings\nFile Permission Bits User Audit Bits\n/usr/sbin/ftpd 1740 fff\n/usr/sbin/ftpdns 1755 fff\n/etc/ftp.data 0744 faf\n/etc/ftp.banner 0744 faf\n\nThe /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.\n\nThe /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.\n\nThe /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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nSome 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.\n\nThe following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits:\n\nchmod 1740 /usr/lpp/tcpip/sbin/ftpd\nchaudit rwx=f /usr/lpp/tcpip/sbin/ftpd\nchmod 1755 /usr/lpp/tcpip/sbin/ftpdns\nchaudit rwx=f /usr/lpp/tcpip/sbin/ftpdns\nchmod 0744 /etc/ftp.data\nchaudit w=sf,rx+f /etc/ftp.data\nchmod 0744 /etc/ftp.banner\nchaudit w=sf,rx+f /etc/ftp.banner","ccis":["CCI-000213"]},{"vulnId":"V-223976","ruleId":"SV-223976r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS data sets for the FTP server must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"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.\n\nNote: READ access to all authenticated users is permitted.\n\nIf WRITE and ALLOCATE access to the data set containing the FTP Data configuration file is logged this is not a finding.\n\nIf WRITE and ALLOCATE access to the data set containing the FTP banner file is restricted to systems programming personnel this is not a finding.\n\nNote: READ access to the data set containing the FTP banner file is permitted to all authenticated users.\n\nNotes: The MVS data sets mentioned above are not used in every configuration. Absence of a data set will not be considered a finding.\nThe data set containing the FTP Data configuration file is determined by checking the SYSFTPD DD statement in the FTP started task JCL.\nThe data set containing the FTP banner file is determined by checking the BANNER statement in the FTP Data configuration file.","fixText":"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:","ccis":["CCI-000213"]},{"vulnId":"V-223977","ruleId":"SV-223977r1130288_rule","severity":"medium","ruleTitle":"IBM z/OS FTP Control cards must be properly stored in a secure PDS file.","description":"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Provide 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. The list must indicate which application uses the PDS and access requirements for those PDSs (who and what level of access). Lists/spreadsheet used for documenting the meeting of this requirement must be maintained by the responsible application/AIS team, available upon request and not maintained by the mainframe ISSO.\n\nObtain the list/spreadsheet from the application/AIS team.\n\nAccess to FTP scripts and/or data files located on host system(s) that contain FTP userid and or password will be restricted to individuals responsible for the application connectivity who have a legitimate requirement to know the userid and password on a remote system. \n\nFTP control cards within In-stream JCL, JCL libraries, or open access libraries/data sets is a finding. \n\nIf anyone not listed in the spreadsheet by userid has access of \"Read\" or greater to the FTP control cards, this is a finding.","fixText":"Create a list or spreadsheet of the locations where FTP control cards are stored, who should have access to those libraries, and which applications the FTP control cards are for.\n\nAdd columns for all people permitted access to the secured PDS.\n\nEnsure that the FTP control cards for each FTP are stored in a secure PDS and are not placed in the JCL libraries or in-stream JCL for each FTP.","ccis":["CCI-000202","CCI-000366"]},{"vulnId":"V-223978","ruleId":"SV-223978r958480_rule","severity":"medium","ruleTitle":"IBM z/OS user exits for the FTP server must not be used without proper approval and documentation.","description":"In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"Refer to the Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nRefer to the file(s) allocated by the STEPLIB DD statement in the FTP started task JCL.\n\nRefer to the libraries specified in the system Linklist and LPA.\n\nIf any FTP Server exits are in use, identify them and validate that they were reviewed for integrity and approved by the site AO.\n\nRefer to the following items are in effect for FTP Server user exits:\n\nThe FTCHKCMD, FTCHKIP, FTCHKJES, FTCHKPWD, FTPSMFEX and FTPOSTPR modules are not located in the FTP daemon's STEPLIB, Linklist, or LPA.\n\nNOTE: The ISPF ISRFIND utility can be used to search the system Linklist and LPA for specific modules.\n\nIf both of the above are true, this is not a finding.\n\nIf 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.","fixText":"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:\nFTCHKCMD\nFTCHKIP\nFTCHKJES\nFTCHKPWD\nFTPOSTPR\nFTPSMFEX","ccis":["CCI-000382"]},{"vulnId":"V-223979","ruleId":"SV-223979r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS FTP server daemon must be defined with proper security parameters.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPD Command Shell enter:\nTSS LIST(FTPD) SEGMENT(OMVS) \nNOTE: The JCL member is typically named FTPD\n\nIf the FTPD ACID has the STC facility, this is not a finding.\n\nIf the FTPD ACID has the following z/OS UNIX attributes, this is not a finding.\n\nUID(0), HOME directory '/', shell program /bin/sh.","fixText":"Configure FTP daemon with the following items:\n\n-The FTP daemon is started from a JCL procedure library defined to JES2.\n\nNOTE: The JCL member is typically named FTPD.\n\n-The FTP daemon ACID is FTPD.\n\n-The FTPD ACID has the STC facility.\n\n-The FTPD ACID has the following z/OS UNIX attributes: \nUID(0), HOME directory '/', shell program /bin/sh.\n\nFor example:\nTSS CREATE(FTPD) TYPE(USER) NAME(FTPD) \nDEPT(existing-dept) FACILITY(STC) PASSWORD(password,0)\nTSS ADD(FTPD) DFLTGRP(STCTCPX) GROUP(STCTCPX)\nTSS ADD(FTPD) SOURCE(INTRDR)\nTSS ADD(FTPD) UID(0) HOME(/) OMVSPGM(/bin/sh)\nTSS ADD(FTPD) MASTFAC(TCP)\nTSS ADD(STC) PROCNAME(FTPD) ACID(FTPD)\nTSS PERMIT(FTPD) IBMFAC(BPX.DAEMON) ACCESS(READ)\nTSS PERMIT(FTPD) IBMFAC(BPX.POE) ACCESS(READ)\nTSS PERMIT(FTPD) SERVAUTH(EZB.STACKACCESS.)ACCESS(READ)","ccis":["CCI-000764"]},{"vulnId":"V-223980","ruleId":"SV-223980r970703_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration for the FTP server must have the INACTIVE statement properly set.","description":"Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.","checkContent":"Refer to the file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nIf the INACTIVE statement is coded with a value greater than \"600\", this is a finding.\n\nIf the INACTIVE statement is coded with a value of \"0\", this is a finding.\n\nIf there is no INACTIVE statement coded or the INACTIVE statement is commented out, this is a finding.","fixText":"Code the FTPD configuration file to include the INACTIVE statement with a value between \"1\" and \"600\".","ccis":["CCI-001133"]},{"vulnId":"V-223981","ruleId":"SV-223981r970703_rule","severity":"medium","ruleTitle":"IBM z/OS startup parameters for the FTP server must have the INACTIVE statement properly set.","description":"Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. \n\nTerminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL.\n\nIf all the items below are true, this is not a finding.\n\nIf any of the items below are untrue, this is a finding.\n\nThe following items are in effect for the FTP daemon's started task JCL:\n\n-The SYSTCPD and SYSFTPD DD statements specify the TCP/IP Data and FTP Data configuration files respectively.\n-The ANONYMOUS keyword is not coded on the PARM parameter on the EXEC statement.\n-The ANONYMOUS=logonid combination is not coded on the PARM parameter on the EXEC statement.\n-The INACTIVE keyword is not coded on the PARM parameter on the EXEC statement.\n\nThe 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.\n\nNOTE: Parameters passed on the PARMSTRING parameter override parameters specified in the FTP procedure.\n\nIf an FTP entry is configured in the AUTOLOG statement block in the TCP/IP Profile configuration file, ensure the following items are in effect:\n\n-The ANONYMOUS keyword is not coded on the PARMSTRING parameter.\n-The ANONYMOUS=logonid combination is not coded on the PARMSTRING parameter.\n-The INACTIVE keyword is not coded on PARMSTRING parameter.","fixText":"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.\n\nThe 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.\n\nThe 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.\n\nDuring 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.\n\nThe 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.","ccis":["CCI-001133"]},{"vulnId":"V-223982","ruleId":"SV-223982r958586_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration statements for the FTP server must specify the Standard Mandatory DoD Notice and Consent Banner statement.","description":"Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:\n\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"","checkContent":"Refer to the file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nIf the BANNER statement is not coded or is commented out, this is a finding.","fixText":"Code the FTPD configuration file to include the BANNER statement that points to the Standard Mandatory DoD Notice and Consent Banner statement.","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223985","ruleId":"SV-223985r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2.** resource must be properly protected in the CA-TSS database.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"From the ISPF Command Shell enter:\nWHOOWNS OPERCMDS(JES2)\nNOTE: 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. \n\nIf the JES2. resource is not owned, or is owned inappropriately, in the OPERCMDS class, this is a finding.","fixText":"The JES2. resource must be owned in the OPERCMDS class. \n\nNOTE: 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. \n\nExtended 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:\n\nFor Example:\nThe following command may be used to establish default protection for JES2 system commands defined to the OPERCMDS resource class:\n\nTSS ADDTO(deptacid) OPERCMDS(JES2.)","ccis":["CCI-000213"]},{"vulnId":"V-223986","ruleId":"SV-223986r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS RJE workstations and NJE nodes must be controlled in accordance with STIG requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer to SYS1.PARMLIB (JES2PARM)\nFor each node entry \n\nIf all JES2 defined NJE nodes and RJE workstations have a profile defined in the IBMFAC resource class, this is not a finding.\n\nNotes: 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.\nWorkstation 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.\nNJE. 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.\n\nIf any JES2 defined NJE node or RJE workstation is not owned in the IBMFAC class, this is a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-223987","ruleId":"SV-223987r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 input sources must be controlled in accordance with the proper security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"Refer the JES2PARM member of SYS1.PARMLIB\nReview the following resources in the JESINPUT resource class:\n\nNOTE: 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.\nINTRDR (internal reader for batch jobs)\nnodename (NJE node)\nOFFn.* (spool offload receiver)\nRnnnn (RJE workstation)\nRDRnn (local card reader)\nSTCINRDR (internal reader for started tasks)\nTSUINRDR (internal reader for TSO logons)\n\nNote 1: Nodename is the NAME parameter in the NODE statement. Review the NJE node definitions by searching for \"NODE(\" in the report.\n\nNote 2: OFFn, where n is the number of the offload receiver. Review the spool offload receiver definitions by searching for \"OFF(\" in the report.\n\nNote 3: Rnnnn, where nnnn is the number of the remote workstation. Review the RJE node definitions by searching for \"RMT(\" in the report.\n\nNote 4: RDRnn, where nn is the number of the reader. Review the reader definitions by searching for \"RDR(\" in the report.\n\nFrom the ISPF Command Shell enter:\n\nTSS WHOOWNS JESINPUT(*)\nIf all of the resources above are owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding.\n\nIf any of the above resources are not owned, or are owned inappropriately, in the JESINPUT resource class, this is a finding.","fixText":"Review the following resources in the JESINPUT resource class:\n\nINTRDR (internal reader for batch jobs)\nnodename (NJE node)\nOFFn.* (spool offload receiver)\nRnnnn (RJE workstation)\nRDRnn (local card reader)\nSTCINRDR (internal reader for started tasks)\nTSUINRDR (internal reader for TSO logons)\n\nNote: 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.\n\nNote 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.\n\nNote 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.\n\nNote 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.\n\nNote 4: RDRnn, where nn is the number of the reader. Review the JES2 parameters for reader definitions by searching for \"RDR(\" in the report.\n\nEnsure all of the defined resources above are owned by generic and/or fully qualified entries in the JESINPUT resource class. \n\nFor Example:\n\nThe following commands may be used to establish default protection for resources defined to the JESINPUT resource class:\n\nTSS ADDTO(deptacid) JESINPUT(OFFn.)\n\nGrant read access to authorized users for each of the resources defined to the JESINPUT resource class.\n\nThe 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:\n\nTSS PERMIT(jesopracid) JESINPUT(OFF*.) ACCESS(READ) ACTION(AUDIT) \n\nThe 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).","ccis":["CCI-000213"]},{"vulnId":"V-223988","ruleId":"SV-223988r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 input sources must be properly controlled.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS JESINPUT(*)\nFor each resource owned \n\nIf 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.\n\nIf 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.\n\nFrom the ISPF Command Shell enter:\nTSS LIST RDT(*)\n\nIf the JESINPT RESOURCE does not have DEFPROT as an attribute, this is a finding.","fixText":"Configure access authorization for resources defined to the JESINPUT resource class to be restricted to the appropriate personnel.\n\nGrant read access to authorized users for each of the following input sources:\n\nINTRDR\nnodename\nOFFn.*\nOFFn.JR\nOFFn.SR\nRnnnn.RDm\nRDRnn\nSTCINRDR\nTSUINRDR and/or TSOINRDR\n\nThe 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.","ccis":["CCI-000213"]},{"vulnId":"V-223989","ruleId":"SV-223989r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 output devices must be controlled in accordance with the proper security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer the JES2PARM member of SYS1.PARMLIB\nReview the WRITER resource in the JESINPUT resource class:\n\nNOTE: If the WRITER resource is not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be owned.\n\nFrom the ISPF Command Shell enter:\nTSS WHOOWNS JESINPUT(WRITER)\n\nIf the WRITER resource is owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding.","fixText":"Ensure the following items are in effect:\n\n-The JES2. resource is owned in the WRITER resource class.\n\nFor Example:\nThe following command may be used to establish default protection for resources defined to the WRITER resource class:\nTSS ADDTO(deptacid) WRITER(JES2.)\n\n-The ownership of all WRITER resources is appropriate.\n\nGrant read access to authorized users for each of the following WRITER resource class output destinations:\n\nJES2.LOCAL.devicename\nJES2.LOCAL.OFF*.JT\nJES2.LOCAL.OFF*.ST\nJES2.LOCAL.PRT*\nJES2.LOCAL.PUN*\nJES2.NJE.nodename\nJES2.RJE.devicename\n\nThe 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:\n\nTSS PERMIT(jesopracid) WRITER(JES2.LOCAL.OFF*.ST) -\nACCESS(READ) ACTION(AUDIT)\n\nThe 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).","ccis":["CCI-000213"]},{"vulnId":"V-223990","ruleId":"SV-223990r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 output devices must be properly controlled for classified systems.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"If the Classification of the system is unclassified, this is not applicable.\n\nFrom the ISPF Command Shell enter:\nTSS WHOHAS WRITER(JES2.)\n\nIf the TSS WRITER resource or generic equivalent identified above is defined with access restricted to the appropriate personnel, this is not a finding.\n\nIf the TSS WRITER resource or generic equivalent identified above is not defined with access restricted to the appropriate personnel, this is a finding.\n\nFrom the ISPF Command Shell enter:\nTSS LIST RDT(*)\n\nIf the JESINPUT RESOURCE does not have DEFPROT as an attribute, this is a finding.","fixText":"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.\n\nDefine resources in the ACP's respective WRITER class for each of the following output destinations:\n\nJES2.LOCAL.devicename\nJES2.LOCAL.OFFn.*\nJES2.LOCAL.OFFn.JT\nJES2.LOCAL.OFFn.ST\nJES2.LOCAL.PRTn\nJES2.LOCAL.PUNn\nJES2.NJE.nodename\nJES2.RJE.devicename\n\nThe 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.","ccis":["CCI-000213"]},{"vulnId":"V-223991","ruleId":"SV-223991r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JESSPOOL resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Refer the JES2PARM member of SYS1.PARMLIB. Review the JESSPOOL resource in the JESINPUT resource class:\n\nNOTE: If the JESSPOOL resource is not defined within the JES2 parameters, the resource in the JESINPUT resource class does not have to be owned.\n\nFrom the ISPF Command Shell enter:\n\nTSS WHOOWNS JESINPUT(JESSPOOL)\n\nIf the JESSPOOL resource is owned by generic and/or fully qualified entries in the JESINPUT resource class, this is not a finding.","fixText":"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.\n\nThe following command may be used to establish default protection for resources defined to the JESSPOOL resource class:\n\nTSS ADDTO(deptacid) JESSPOOL(localnodeid.)\n\nDue 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:\n\nTSS PERMIT(ALL) JESSPOOL(localnodeid.%) ACCESS(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-223992","ruleId":"SV-223992r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JESNEWS resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOHAS OPERCMDS(JES2.)\nNOTE: 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. \n\nIf 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.","fixText":"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. \n\nNOTE: 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. \n\nFor example:\n\nThe following command example may be used to allow all valid TOP SECRET users read access to the JES News data set:\n\nTSS PERMIT(ALL) JESSPOOL(localnodeid.jesid.$JESNEWS.*.*.JESNEWS) -\nACCESS(READ)\n\nThe following is a sample command to allow production control personnel with a profile ACID of prodacid to update the JES News data set:\n\nTSS PERMIT(prodacid) OPERCMDS(JES2.UPDATE.JESNEWS) -\nACCESS(CONTROL) ACTION(AUDIT)","ccis":["CCI-000213"]},{"vulnId":"V-223993","ruleId":"SV-223993r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JESTRACE and/or SYSLOG resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS JESSPOOL(*)\n\nIf JESSPOOL localnodeid resource is not defined, this is a finding.\n\nEnter\nTSS WHOHAS JESSPOOL(localnodeid.)\nReview the following resources defined to the JESSPOOL resource class:\n\nlocalnodeid.JES2.$TRCLOG.taskid.*.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.*.SYSLOG or\nlocalnodeid.+BYPASS+.SYSLOG.jobid.-.SYSLOG\n\nNOTE: These resource profiles may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\n\nlocalnodeid.JES2.*.*.*.JESTRACE\nlocalnodeid.+MASTER+.*.*.*.SYSLOG or\nlocalnodeid.+BYPASS+.*.*.*.SYSLOG\n\nNOTE: 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.\n\nIf the access authorization for the resources mentioned above is restricted to the following, this is not a finding.\n\n-ACID(s) associated with external writer(s) can have complete access.\n\nNOTE: 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.\n\n-Systems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access.\n\n-Application Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource.","fixText":"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.\n\nReview the following resources defined to the JESSPOOL resource class:\n\nlocalnodeid.JES2.$TRCLOG.taskid.*.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.*.SYSLOG or\nlocalnodeid.+BYPASS+.SYSLOG.jobid.*.SYSLOG\n\nNOTE: These resource profiles may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\n\nlocalnodeid.JES2.$TRCLOG.\nlocalnodeid.+MASTER+.SYSLOG. or\nlocalnodeid.+BYPASS+.SYSLOG.\n\nNOTE: 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.\n\nEnsure that access authorization for the resources mentioned above is restricted to the following:\n\n-ACID(s) associated with external writer(s) can have complete access.\n\nNOTE: 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.\n\n-Systems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access.\n\n-Application Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource.\n\nFor Example:\n\nTSS ADD(dept-acid) JESSPOOL(localnodeid)\n\nTSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.JES2.$TRCLOG.) ACCESS(ALL)\nTSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.JES2.$TRCLOG.) ACCESS(ALL)\n\nTSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(ALL)\nTSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(ALL)\nTSS PERMIT(<appdsmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(READ)\nTSS PERMIT(<appssmpl>) JESSPOOL(localnodeid.+MASTER+.SYSLOG.) ACCESS(READ)\nor\nTSS PERMIT(<syspsmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(ALL)\nTSS PERMIT(<secasmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(ALL)\nTSS PERMIT(<appdsmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(READ)\nTSS PERMIT(<appssmpl>) JESSPOOL(localnodeid.+BYPASS+.SYSLOG.) ACCESS(READ)","ccis":["CCI-000213"]},{"vulnId":"V-223994","ruleId":"SV-223994r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 spool resources must be controlled in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOHAS JESSPOOL(localnodeid.)\n\nIf the following guidance is true, this is not a finding.\n\nReview 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:\n\nlocalnodeid.useracid.jobname.jobid.dsnumber.name\n\nlocalnodeid - The name of the node on which the SYSIN or SYSOUT data set currently resides.\nuseracid - The user ACID associated with the job. This is the user ACID TSS uses for validation purposes when the job runs.\njobname - The name that appears in the name field of the JOB statement.\njobid - The job number JES2 assigned to the job.\ndsnumber - The unique data set number JES2 assigned to the spool data set. A D is the first character of this qualifier.\nname - 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 (?).\n\nAll 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.\n\nEnsure the following items are in effect:\n\nThe 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.)\n\nThe 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.\n\nCSSMTP 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.\n\nSpooling 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.","fixText":"Configure the following items to be in effect for JESSPOOL resources. The JESSPOOL may have more restrictive security at the direction of the ISSO.\n\nThe JESSPOOL resources may be fully qualified, be specified as generic, or be specified with masking as indicated below:\n\nlocalnodeid.userid.jobname.jobid.dsnumber.name\n\nlocalnodeid - The name of the node on which the SYSIN or SYSOUT data set currently resides.\nuserid - The userid associated with the job. This is the userid used for validation purposes when the job runs.\njobname - The name that appears in the name field of the JOB statement.\njobid - The job number JES2 assigned to the job.\ndsnumber - The unique data set number JES2 assigned to the spool data set. A D is the first character of this qualifier.\nname - 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 (?).\n\nAll 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.\n\nExample:\nTSS ADDTO(deptacid) JESSPOOL(localnode.)\nTSS PERMIT(ALL) JESSPOOL(localnode.%.) ACCESS(ALL)\n\nThe 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.)\n\nExample:\nTSS PERMIT(syspsmpl) JESSPOOL(localnodeid.) ACCESS(ALL) ACTION(AUDIT)\n\nThe 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.\n\nExample:\nTSS PERMIT(Project1-profile) JESSPOOL(localnodeid.UMO) ACCESS(ALL)\n\nIf 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.\n\nCSSMTP 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.\n\nSpooling 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.\n\nThe 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.","ccis":["CCI-000213"]},{"vulnId":"V-223995","ruleId":"SV-223995r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS JES2 system commands must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell, enter:\nTSS WHOHAS OPERCMDS(JES2.)\n\nIf the JES2.** resource is defined to the OPERCMDS class with an access of NONE and all access is logged, this is not a finding.\n\nIf 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.\n\nNOTE: Use the GROUP category specified in the table referenced above as a guideline to determine appropriate personnel access to system commands.","fixText":"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.\n\nSome 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.\n\nTo control access to JES2 system commands, apply the following:\n\nDefine the JES2.** resource in the OPERCMDS class with an access of NONE and all access is logged.\n\nDefine 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.\n\nDefine the JES2 system commands with proper logging as determined in the documented site security plan.\n\nNote: Display commands and others as deemed by the site IAW site security plan may be allowed for all users with no logging. \n\nBuild a command file based on the referenced JES2 Command Table. A sample of the commands in the command file is provided here:\n\nThe following is a sample command to allow operators with a profile ACID of opracid to use the $DS command:\n\nTSS PERMIT(opracid) OPRCMDS(JES2.DISPLAY.STC) ACCESS(READ)\n\nThe following is a sample command to allow operators with a profile ACID of opracid to use the $DM command:\n\nTSS PERMIT(opracid) OPERCMDS(JES2.SEND.MESSAGE) -\nACCESS(READ) ACTION(AUDIT)\n\nThe following is a sample command to allow operators with a profile ACID of opracid to use the $B command:\n\nTSS PERMIT(opracid) OPERCMDS(JES2.BACKSP.DEV) -\nACCESS(UPDATE) ACTION(AUDIT)\n\nThe following is a sample command to allow operators with a profile ACID of opracid to use the $ZI command:\n      \nTSS PERMIT(opracid) OPERCMDS(JES2.HALT.INITIATOR) -\nACCESS(CONTROL) ACTION(AUDIT)\n\nThe following is a sample command to allow operators with a profile ACID of opracid to use the $ZSPOOL command:\n\nTSS PERMIT(opracid) OPERCMDS(JES2.HALT.SPOOL) -\nACCESS(CONTROL) ACTION(AUDIT)","ccis":["CCI-000213"]},{"vulnId":"V-223996","ruleId":"SV-223996r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS Surrogate users must be controlled in accordance with proper security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000326-GPOS-00126","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) DATA(XA)\n\nIf no XA ACID entries exist in the above reports, this is not applicable.\n\nFor each ACID identified in the XA ACID entries, if the following items are true regarding ACID permissions, this is not a finding.\n\n-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.\n-Access authorization is restricted to scheduling tools, started tasks or other system applications required for running production jobs.\n-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).","fixText":"For each ACID identified in the XA ACID entries, ensure the following items are in effect regarding ACID permissions:\n\n-ACID permission (XA ACID) is logged (ACTION = AUDIT), at the discretion of the ISSM/ISSO scheduling tasks may be exempted from logging.\n-ACID permission (XA ACID) is logged (ACTION = AUDIT), for Privileged users (MSCA, SCA, DCA, VCA, ZCA).\n-Access authorization is restricted to scheduling tools, started tasks, or other system applications required for running production jobs.\n\nOther users may have minimal access required for running production jobs with documentation properly approved and filed with the site security official (ISSM or equivalent). \n\nConsider the following recommendations when implementing security for Cross-Authorized ACIDs:\n\nKeep ACID cross authorization of ACIDs outside of those granted to the scheduling software to a minimum number of individuals.\n\nThe simplest configuration is to have no ACID Cross Authorization except for the appropriate Scheduling task/software for production scheduling purposes as documented.\n\nTemporary 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.\n\nAccess 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.\n\nGrant access to the user ACID for each cross-authorized ACID required:\n\nFor Example:\nTSS PERMIT(ACID) ACID(Cross-Authorized ACID) ACTION(AUDIT) \n\nFor production ACIDs being used by CONTROLM:\nTSS PER(CONTROLM)ACID(production user ACID)","ccis":["CCI-000213","CCI-002233"]},{"vulnId":"V-223997","ruleId":"SV-223997r958478_rule","severity":"medium","ruleTitle":"Duplicated IBM z/OS sensitive utilities and/or programs must not exist in APF libraries.","description":"Removal of unneeded or non-secure functions, ports, protocols, and services mitigate the risk of unauthorized connection of devices, unauthorized transfer of information, or other exploitation of these resources.","checkContent":"From an ISPF Command line enter:\nTSO ISRDDN APF\n\nAn APF List results. On the Command line enter:\nDUPlicates (Make sure there is appropriate access. If there is not, you may receive insufficient access errors.)\n\nIf any of the list of Sensitive Utilities exist in the duplicate APF modules returned, this is a finding.\n\nThe following list contains Sensitive Utilities that will be checked.\n\nAHLGTF AMASPZAP AMAZAP AMDIOCP AMZIOCP\nBLSROPTR CSQJU003 CSQJU004 CSQUCVX CSQUTIL\nCSQ1LOGP DEBE DITTO FDRZAPOP GIMSMP\nHHLGTF ICKDSF ICPIOCP IDCSC01 IEHINITT\nIFASMFDP IGWSPZAP IHLGTF IMASPZAP IND$FILE\nIOPIOCP IXPIOCP IYPIOCP IZPIOCP WHOIS\nL052INIT TMSCOPY TMSFORMT TMSLBLPR TMSMULV\nTMSREMOV TMSTPNIT TMSUDSNB","fixText":"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.\n\nComparisons 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.","ccis":["CCI-000381"]},{"vulnId":"V-223998","ruleId":"SV-223998r998499_rule","severity":"medium","ruleTitle":"IBM z/OS required SMF data record types must be collected.","description":"Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.\n\nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209, SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00211, SRG-OS-000468-GPOS-00212, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000474-GPOS-00219, SRG-OS-000475-GPOS-00220, SRG-OS-000476-GPOS-00221, SRG-OS-000477-GPOS-00222, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000255-GPOS-00096, SRG-OS-000365-GPOS-00152, SRG-OS-000348-GPOS-00136, SRG-OS-000303-GPOS-00120, SRG-OS-000327-GPOS-00127, SRG-OS-000392-GPOS-00172","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member.\n\nIf all of the required SMF record types identified below are collected, this is not a finding.\n\nIBM SMF Records to be collected at a minimum:\n\n0 (00) - IPL\n6 (06) - External Writer/ JES Output Writer/ Print Services Facility (PSF)\n7 (07) - [SMF] Data Lost\n14 (0E) - INPUT or RDBACK Data Set Activity\n15 (0F) - OUTPUT, UPDAT, INOUT, or OUTIN Data Set Activity\n17 (11) - Scratch Data Set Status\n18 (12) - Rename Non-VSAM Data Set Status\n24 (18) - JES2 Spool Offload\n25 (19) - JES3 Device Allocation\n26 (1A) - JES Job Purge\n30 (1E) - Common Address Space Work\n32 (20) - TSO/E User Work Accounting\n41 (29) - DIV Objects and VLF Statistics \n42 (2A) - DFSMS statistics and configuration \n43 (2B) - JES Start\n45 (2D) - JES Withdrawal/Stop\n47 (2F) - JES SIGNON/Start Line (BSC)/LOGON\n48 (30) - JES SIGNOFF/Stop Line (BSC)/LOGOFF\n49 (31) - JES Integrity\n52 (34) - JES2 LOGON/Start Line (SNA)\n53 (35) - JES2 LOGOFF/Stop Line (SNA)\n54 (36) - JES2 Integrity (SNA)\n55 (37) - JES2 Network SIGNON\n56 (38) - JES2 Network Integrity\n57 (39) - JES2 Network SYSOUT Transmission\n58 (3A) - JES2 Network SIGNOFF\n60 (3C) - VSAM Volume Data Set Updated\n61 (3D) - Integrated Catalog Facility Define Activity\n62 (3E) - VSAM Component or Cluster Opened\n64 (40) - VSAM Component or Cluster Status\n65 (41) - Integrated Catalog Facility Delete Activity\n66 (42) - Integrated Catalog Facility Alter Activity\n80 (50) - RACF/TOP SECRET Processing\n81 (51) - RACF Initialization\n82 (52) - ICSF Statistics\n83 (53) - RACF Audit Record For Data Sets\n90 (5A) - System Status\n92 (5C) except subtypes 10, 11 - OpenMVS File System Activity\n102 (66) - DATABASE 2 Performance \n103 (67) - IBM HTTP Server\n110 (6E) - CICS/ESA Statistics\n118 (76) - TCP/IP Statistics\n119 (77) - TCP/IP Statistics \n199 (C7) - TSOMON\n230 (E6) - ACF2 or as specified in ACFFDR (vendor-supplied default is 230)\n231 (E7) - TSS logs security events under this record type","fixText":"Ensure that SMF recording options are consistent with those outlined below.\n\nIBM SMF Records to be collected at a minimum:\n\n0 (00) - IPL\n6 (06) - External Writer/ JES Output Writer/ Print Services Facility (PSF)\n7 (07) - [SMF] Data Lost\n14 (0E) - INPUT or RDBACK Data Set Activity\n15 (0F) - OUTPUT, UPDAT, INOUT, or OUTIN Data Set Activity\n17 (11) - Scratch Data Set Status\n18 (12) - Rename Non-VSAM Data Set Status\n24 (18) - JES2 Spool Offload\n25 (19) - JES3 Device Allocation\n26 (1A) - JES Job Purge\n30 (1E) - Common Address Space Work\n32 (20) - TSO/E User Work Accounting\n41 (29) - DIV Objects and VLF Statistics \n42 (2A) - DFSMS statistics and configuration \n43 (2B) - JES Start\n45 (2D) - JES Withdrawal/Stop\n47 (2F) - JES SIGNON/Start Line (BSC)/LOGON\n48 (30) - JES SIGNOFF/Stop Line (BSC)/LOGOFF\n49 (31) - JES Integrity\n52 (34) - JES2 LOGON/Start Line (SNA)\n53 (35) - JES2 LOGOFF/Stop Line (SNA)\n54 (36) - JES2 Integrity (SNA)\n55 (37) - JES2 Network SIGNON\n56 (38) - JES2 Network Integrity\n57 (39) - JES2 Network SYSOUT Transmission\n58 (3A) - JES2 Network SIGNOFF\n60 (3C) - VSAM Volume Data Set Updated\n61 (3D) - Integrated Catalog Facility Define Activity\n62 (3E) - VSAM Component or Cluster Opened\n64 (40) - VSAM Component or Cluster Status\n65 (41) - Integrated Catalog Facility Delete Activity\n66 (42) - Integrated Catalog Facility Alter Activity\n80 (50) - RACF/TOP SECRET Processing\n81 (51) - RACF Initialization\n82 (52) - ICSF Statistics\n83 (53) - RACF Audit Record For Data Sets\n90 (5A) - System Status\n92 (5C) except subtypes 10, 11 - OpenMVS File System Activity\n102 (66) - DATABASE 2 Performance \n103 (67) - IBM HTTP Server\n110 (6E) - CICS/ESA Statistics\n118 (76) - TCP/IP Statistics\n119 (77) - TCP/IP Statistics \n199 (C7) - TSOMON\n230 (E6) - ACF2 or as specified in ACFFDR (vendor-supplied default is 230)\n231 (E7) - TSS logs security events under this record type","ccis":["CCI-000018","CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-001487","CCI-003938","CCI-001875","CCI-002130","CCI-002234","CCI-002884"]},{"vulnId":"V-223999","ruleId":"SV-223999r958402_rule","severity":"medium","ruleTitle":"IBM z/OS Session manager must properly configure wait time limits.","description":"A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.\n\nThe session lock is implemented at the point where session activity can be determined and/or controlled.","checkContent":"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.","fixText":"Configure the session manager in use to initiate a session lock after a 15-minute period of inactivity for all connection types.","ccis":["CCI-000057"]},{"vulnId":"V-224000","ruleId":"SV-224000r1130291_rule","severity":"medium","ruleTitle":"The IBM z/OS BPX.SMF resource must be properly configured.","description":"Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"From the ISPF Command Shell, enter:\nTSS WHOHAS IBMFAC(BPX.SMF)\n\nIf the TSS  rules are as follows, this is not a finding.\n\nBPX.SMF.119.94 - READ allowed for users running the ssh, sftp, or scp client commands.\nBPX.SMF.119.96 - READ allowed for users running the scp or sftp-server server commands.\nBPX.SMF.119.97 - READ allowed for users running the scp or sftp client commands.\n\nThe following profile grants the permitted users the authority to write or test for any SMF record being recorded. Access should be permitted as follows:\nBPX.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.","fixText":"Configure IIBMFAC  resource class for BPX.SMF as follows:\n\nBPX.SMF.119.94 - READ allowed for users running the ssh, sftp, or scp client commands.\nBPX.SMF.119.96 - READ allowed for users running the scp or sftp-server server commands.\nBPX.SMF.119.97 - READ allowed for users running the scp or sftp client commands.\n\nThe following profile grants the permitted users the authority to write or test for any SMF record being recorded. Access should be permitted as follows:\nBPX.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.","ccis":["CCI-000067"]},{"vulnId":"V-224001","ruleId":"SV-224001r958414_rule","severity":"medium","ruleTitle":"IBM z/OS must specify SMF data options to ensure appropriate activation.","description":"Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.\n\nIn order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).\n\nAssociating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.\n\nSatisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000269-GPOS-00103, SRG-OS-000368-GPOS-00154","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. \n\nSUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJP,IEFUSO),\nINTERVAL(SMF,SYNC),NODETAIL)\n\nIf the SMF collection options are specified as stated below with exception of those specified in the above NOTEs, this is not a finding. \n\nThe settings for several parameters are critical to the collection process:\n\nACTIVE Activates the collection of SMF data.\n\nMAXDORM(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.\n\nSID Specifies the system ID to be recorded in all SMF records.\n\nSYS(DETAIL) Controls the level of detail recorded.\n\nSYS(INTERVAL) Ensures the periodic recording of data for long running jobs.\n\nSYS 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.","fixText":"Ensure that collection options for SMF Data are consistent with options specified below.\n\nReview all SMF recording specifications found in SMFPRMxx members. Ensure that SMF recording options used are consistent with those outlined below.\n\nThe settings for several parameters are critical to the collection process:\n\nACTIVE Activates the collection of SMF data.\n\nMAXDORM(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.\n\nSID Specifies the system ID to be recorded in all SMF records.\n\nSYS(DETAIL) Controls the level of detail recorded.\n\nSYS(INTERVAL) Ensures the periodic recording of data for long running jobs.\n\nSYS 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.","ccis":["CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-001464","CCI-001665","CCI-001764"]},{"vulnId":"V-224002","ruleId":"SV-224002r958424_rule","severity":"medium","ruleTitle":"IBM z/OS BUFUSEWARN in the SMFPRMxx must be properly set.","description":"It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.\n\nAudit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.\n\nThis requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member in SYS1.PARMLIB.\n\nIf BUFUSEWARN is set for \"75\" (75%) or less, this is not a finding.","fixText":"Configure the BUFUSEWARN statement in SMFPRMxx to \"75\" (75%) or less.","ccis":["CCI-000139"]},{"vulnId":"V-224003","ruleId":"SV-224003r991589_rule","severity":"medium","ruleTitle":"IBM z/OS PASSWORD data set and OS passwords must not be used.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Ask the system administrator to determine if the system PASSWORD data set and OS passwords are being used.\n\nIf, 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.\n\nIf it is evident that OS passwords are utilized, this is a finding.","fixText":"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.\n\nReview the contents of the PASSWORD data set. Ensure that any protections it provides are provided by the ACP and delete the PASSWORD data set.\n\nAccess 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.","ccis":["CCI-000366"]},{"vulnId":"V-224004","ruleId":"SV-224004r991589_rule","severity":"medium","ruleTitle":"The CA-TSS database must be on a separate physical volume from its backup and recovery data sets.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Refer to the System proclibs for the TSS STC. \n\nIf the Security database is located on the same volume as either the backup, Alternate or Recovery file, this is a finding.","fixText":"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.\n\nIdentify 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.\n\nFile 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.","ccis":["CCI-000366"]},{"vulnId":"V-224005","ruleId":"SV-224005r991589_rule","severity":"medium","ruleTitle":"The CA-TSS database must be backed up on a scheduled basis.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Refer to the TSS Proclib PARMFILE DD to determine the PARM member.\n\nIf the BACKUP is missing or coded with blank or OFF this is a finding. \n\nNote: 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.\n\nFrom the ISPF Command Shell enter:\nTSS MODIFY(Status)\n\nIf the backup parameter is active with a valid time this is not a finding.","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-224006","ruleId":"SV-224006r991593_rule","severity":"medium","ruleTitle":"The IBM z/OS Policy Agent must be configured to deny-all, allow-by-exception firewall policy for allowing connections to other systems.","description":"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"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.","fixText":"Develop a policy application and policy agent to employ a deny-all, allow-by-exception firewall policy for allowing connections to other systems.","ccis":["CCI-000366","CCI-002080"]},{"vulnId":"V-224007","ruleId":"SV-224007r958478_rule","severity":"medium","ruleTitle":"IBM z/OS must not have Inaccessible APF libraries defined.","description":"It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).\n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper APF and/or PROG member.\nExamine each entry and verify that it exists on the specified volume. \n\nIf inaccessible APF libraries exist, this is a finding.\n\nISRDDN APF","fixText":"Review the entire list of APF authorized libraries and remove those that are no longer valid designations.","ccis":["CCI-000381"]},{"vulnId":"V-224008","ruleId":"SV-224008r958478_rule","severity":"medium","ruleTitle":"IBM z/OS inapplicable PPT entries must be invalidated.","description":"It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).\n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.","checkContent":"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:\nTSO ISRDDN LOAD IEFSDPPT\nPress Enter.\n\nInterpret the display as follows:\nExamine contents at offset 8 \n Hex 'x2' - Bypass Password Protection \nHex 'x3' - Bypass Password Protection\nHex 'x4' - No data set Integrity\n Hex 'x5' - No data set Integrity\n Hex 'x6' - Both\n Hex 'x7' - Both \nDetermine Privilege Key at offset 9. A value of hex '70' or less indicates an elevated privilege.\n\nFor 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:\n From an ISPF command line\n TSO ISRDDN LOAD <privileged module>\n Press Enter.\n\n If the return message is \"Load Failed\", make sure there is an entry in PARMLIB member SCHEDxx that revokes the excessive privilege. \n\nIf this is not true, this is a finding.","fixText":"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. \n\nUse the following recommendations and techniques to provide protection for the PPT:\n\nReview 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. \n\nModules 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:\n\nPPT PGMNAME(<program name>)\n\nAssemble documentation regarding these PPT entries, and the ISSO will keep it on file. Include the following in the documentation:\n\n-The product and release for which the PPT entry was made\n-The last date this entry was reviewed to authenticate status\n-The reason the module's privileges are being revoked","ccis":["CCI-000381"]},{"vulnId":"V-224009","ruleId":"SV-224009r958478_rule","severity":"medium","ruleTitle":"IBM z/OS LNKAUTH=APFTAB must be specified in the IEASYSxx member(s) in the currently active parmlib data set(s).","description":"It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).\n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation.\n\nIf \"LNKAUTH=APFTAB\" is not specified, this is a finding.","fixText":"Configure LNKAUTH=APFTAB in the IEASYS00 member of PARMLIB.","ccis":["CCI-000381"]},{"vulnId":"V-224010","ruleId":"SV-224010r1137695_rule","severity":"medium","ruleTitle":"IBM z/OS sensitive and critical system data sets must not exist on shared DASD.","description":"Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection.\n\nThis requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies.\n\nThere may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.","checkContent":"Check HMC, VM, and z/OS on how to validate and determine a DASD volume(s) is shared.\n\nNote: In VM issue the command \"QUEUE DASD SYSTEM\" this display will show shared volume(s) and indicates the number of systems sharing the volume.\n\nValidate all machines that require access to these shared volume(s) have the volume(s) mounted.\n\nObtain a map or list VTOC of the shared volume(s).\n\nCheck if shared volume(s) contain any critical or sensitive data sets.\n\nIdentify 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.\n\nIf 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.\n\nList 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).","fixText":"Configure all identified volumes of shared DASD to be valid within the following.\n\nHMC\nVM\nz/OS\n\nIf 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).\n\nThe 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.","ccis":["CCI-001090"]},{"vulnId":"V-224011","ruleId":"SV-224011r958528_rule","severity":"medium","ruleTitle":"The IBM z/OS Policy Agent must contain a policy that manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial-of-service (DoS) attacks.","description":"DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.","checkContent":"Examine the Policy Agent policy statements. \n\nIf it can be determined that there are policy statements that manages excess capacity, this is not a finding.","fixText":"Develop Policy application and Policy agent to manage excess capacity.","ccis":["CCI-001095"]},{"vulnId":"V-224013","ruleId":"SV-224013r998500_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are created.","description":"Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the creation of operating system user accounts and notifies administrators and information system security officers (ISSOs) that it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the documented process to notify appropriate personnel when accounts are created.\n\nIf there is no documented process, this is a finding.","fixText":"Develop a documented process to notify appropriate personnel when accounts are created.","ccis":["CCI-000015"]},{"vulnId":"V-224014","ruleId":"SV-224014r998501_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are modified.","description":"Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the creation of operating system user accounts and notifies administrators and information system security officers (ISSOs) that it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the documented process to notify appropriate personnel when accounts are modified.\n\nIf there is no documented process, this is a finding.","fixText":"Develop a documented process to notify appropriate personnel when accounts are modified.","ccis":["CCI-000015"]},{"vulnId":"V-224015","ruleId":"SV-224015r998502_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are deleted.","description":"When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual operating system users or for identifying the operating system processes themselves. Sending notification of account disabling events to the system administrator and information system security officers (ISSOs) is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. \n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the documented process to notify appropriate personnel when accounts are deleted.\n\nIf there is no documented process, this is a finding.","fixText":"Develop a documented process to notify appropriate personnel when accounts are deleted.","ccis":["CCI-000015"]},{"vulnId":"V-224016","ruleId":"SV-224016r998503_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are removed.","description":"When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual operating system users or for identifying the operating system processes themselves. Sending notification of account disabling events to the system administrator and information system security officers (ISSOs) is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. \n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the documented process to notify appropriate personnel when accounts are removed.\n\nIf there is no documented process, this is a finding.","fixText":"Develop a documented process to notify appropriate personnel when accounts are removed.","ccis":["CCI-000015"]},{"vulnId":"V-224017","ruleId":"SV-224017r958804_rule","severity":"high","ruleTitle":"Unsupported IBM z/OS system software must not be installed and/or active on the system.","description":"Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level.\n\nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.\n\nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).","checkContent":"This check applies to all products that meet the following criteria:\n\n- Uses authorized and restricted z/OS interfaces by utilizing Authorized Program Facility (APF) authorized modules or libraries.\n- Requires access to system data sets or sensitive information or requires special or privileged authority to run.\n\nFor the products in the above category, refer to the vendor's support lifecycle information for current versions and releases. \n\nIf 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.","fixText":"For all products that meet the following criteria:\n\n- Uses authorized and restricted z/OS interfaces by utilizing Authorized Program Facility (APF) authorized modules or libraries.\n- Requires access to system data sets or sensitive information or requires special or privileged authority to run.\n\nThe ISSO will ensure that unsupported system software for the products in the above category is removed or upgraded prior to a vendor dropping support.\n\nAuthorized 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.","ccis":["CCI-001764"]},{"vulnId":"V-224018","ruleId":"SV-224018r958804_rule","severity":"medium","ruleTitle":"IBM z/OS must not allow nonexistent or inaccessible Link Pack Area (LPA) libraries.","description":"Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level.\n\nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.\n\nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).","checkContent":"From an ISPF Command line enter:\nTSO ISRDDN LPA\n\nReview the list.\n\nIf there are any DUMMY entries, i.e., inaccessible LPA libraries, this is a finding.","fixText":"Review all entries contained in the LPA members for the actual existence of each library. Develop a plan of action to correct deficiencies. \n\nThe 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.\n\nControl over residence in the LPA is specified within the operating system in the following members of the data set SYS1.PARMLIB:\n\n- 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].)\n\n- 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.)\n\n- IEALPAxx specifies the names of modules that will be loaded from the following:\n\n? SYS1.SVCLIB\n? The LPALSTxx concatenation\n? The LNKLSTxx concatenation as a temporary extension to the existing Pageable\n\nLPA (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.)\n\nUse the following recommendations and techniques to control the exposures created by the LPA facility:\n\n-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.","ccis":["CCI-001764"]},{"vulnId":"V-224019","ruleId":"SV-224019r958804_rule","severity":"medium","ruleTitle":"IBM z/OS must not allow nonexistent or inaccessible LINKLIST libraries.","description":"Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level.\n\nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.\n\nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).","checkContent":"From and ISPF Command line enter:\nTSO ISRDDN LINKLIST\n\nReview the list, if there are any DUMMY entries i.e., inaccessible LINKLIST libraries, this is a finding.","fixText":"Review all entries contained in the LINKLIST for the actual existence of each library. Develop a plan of action to correct deficiencies.\n\nThe 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.)\n\nUse the following recommendations and techniques to control the exposures created by the LINKLIST facility:\n\n441-1Avoid inclusion of sensitive libraries in the LNKLSTxx member unless absolutely required.\n\n-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.","ccis":["CCI-001764"]},{"vulnId":"V-224020","ruleId":"SV-224020r958796_rule","severity":"high","ruleTitle":"CA-TSS must be installed and properly configured.","description":"Failure to provide logical access restrictions associated with changes to system configuration may have significant effects on the overall security of the system.\n\nWhen dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the operating system can have significant effects on the overall security of the system.\n\nAccordingly, only qualified and authorized individuals should be allowed to obtain access to operating system components for the purposes of initiating changes, including upgrades and modifications.\n\nLogical access restrictions include, for example, controls that restrict access to workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).","checkContent":"Refer to the active tasks on the system. Use IBM SDSF or the system Log.\n\nIf CA-TSS is active this is not a finding.","fixText":"Ensure that CA-TSS is active on the system.","ccis":["CCI-001813"]},{"vulnId":"V-224021","ruleId":"SV-224021r958752_rule","severity":"medium","ruleTitle":"IBM z/OS SMF collection files (system MANx data sets or LOGSTREAM DASD) must have storage capacity to store at least one weeks worth of audit data.","description":"In order to ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems need to be able to allocate audit record storage capacity.\n\nThe task of allocating audit record storage capacity is usually performed during initial installation of the operating system.","checkContent":"Review the SMF dump procedure in there system.\n\nIf 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.","fixText":"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.","ccis":["CCI-001849"]},{"vulnId":"V-224022","ruleId":"SV-224022r958754_rule","severity":"medium","ruleTitle":"IBM z/OS System Administrators must develop an automated process to collect and retain SMF data.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration.\n\nOff-loading is a common process in information systems with limited audit storage capacity.","checkContent":"Ask the system administrator if there is an automated process is in place to collect and retain all SMF data produced on the system.\n\nIf, 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.\n\nIf it cannot be determined this process exists and is being adhered to, this is a finding.","fixText":"Ensure that an automated process is in place to collect SMF data.\n\nReview SMF data collection and retention processes. Develop processes that are automatically started to dump SMF collection files immediately upon their becoming full.\n\nTo 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:\n\n-Dump each SMF file as it fills up during the normal course of daily processing.\n-Dump all remaining SMF data at the end of each processing day. \n\nEstablish a process using Audit logging.","ccis":["CCI-001851"]},{"vulnId":"V-224023","ruleId":"SV-224023r1169905_rule","severity":"medium","ruleTitle":"The IBM z/OS system must use a time protocol that syncs with an authoritative external time source.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.\n\nOrganizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).","checkContent":"Verify the operating system, for networked systems, compares internal information system clocks at least every 24 hours with a server synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). \n\nIf it does not, this is a finding.","fixText":"Coordinate with system staff to determine the best time protocols available for the z/OS systems at the site. SNT is one protocol available.\nObtain a copy of this sample procedure from SEZAINST and store it in one of the PROCLIB concatenation data sets.\n\nPerform the following to start SNTPD as a procedure:\nInvoke the procedure using the system operator start command. The following sample, SEZAINST(SNTPD), shows how to start SNTPD as a procedure:\n//*\n//* Sample procedure for the Simple Network Time Protocol (SNTP)\n//*\n//* z/OS Communications Server Version 1 Release 13\n//* SMP/E Distribution Name: SEZAINST(EZASNPRO)\n//*\n//* Copyright: Licensed Materials - Property of IBM\n//* 5650-ZOS\n//* Copyright IBM Corp. 2002, 2015\n//*\n//* Status: CSV2R2\n//*\n//SNTPD EXEC PGM=SNTPD,REGION=4096K,TIME=NOLIMIT,\n//PARM='/ -d'\n//SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,LRECL=132,BLKSIZE=132)\n//SYSIN DD DUMMY\n//SYSERR DD SYSOUT=*\n//SYSOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=132,BLKSIZE=132)\n//CEEDUMP DD SYSOUT=*\n//SYSABEND DD SYSOUT=*","ccis":["CCI-004923"]},{"vulnId":"V-224024","ruleId":"SV-224024r1174004_rule","severity":"medium","ruleTitle":"IBM z/OS Time Protocol must be properly configured. IBM z/OS SNTP daemon (SNTPD) permission bits must be properly configured.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.\n\nOrganizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).","checkContent":"Any Time Protocol must be configured to restrict access and/or control to appropriate personnel. \n\nConfigure SNTP as shown below:\n\nFrom the ISPF Command Shell, enter:\ncd /usr/sbin\nls -al\n\nIf the following file permission and user audit bits are true, this is not a finding.\n\n/usr/sbin/sntpd 1740 faf\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"Whichever Time Protocol is used, consult the system programmer for configuration information. If using SNTP 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:\n\n/usr/sbin/sntpd 1740 faf","ccis":["CCI-004923"]},{"vulnId":"V-224025","ruleId":"SV-224025r998506_rule","severity":"medium","ruleTitle":"IBM z/OS PARMLIB CLOCKxx must have the Accuracy PARM coded properly.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems).\n\nOrganizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done in order to determine the time difference.","checkContent":"Refer to the CLOCKxx member of PARMLIB.\n\nIf the ACCURACY parm is not coded, this is a finding.\n\nIf the ACCURACY parm is coded to \"1000\", this is not a finding.","fixText":"Define the CLOCKxx statement to include the ACCURACY parm set to \"1000\".","ccis":["CCI-004926"]},{"vulnId":"V-224026","ruleId":"SV-224026r958902_rule","severity":"medium","ruleTitle":"The IBM z/OS Policy Agent must contain a policy that protects against or limits the effects of denial-of-service (DoS) attacks by ensuring IBM z/OS is implementing rate-limiting measures on impacted network interfaces.","description":"DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.\n\nThis requirement addresses the configuration of the operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.","checkContent":"Examine the \"Policy Agent\" policy statements. \n\nIf 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.","fixText":"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.","ccis":["CCI-002385"]},{"vulnId":"V-224031","ruleId":"SV-224031r991589_rule","severity":"medium","ruleTitle":"IBM z/OS must configure system wait times to protect resource availability based on site priorities.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. \n\nExamine the JWT, SWT, and TWT values.\n\nIf the JWT parameter is greater than \"15\" minutes, and the system is processing unclassified information, review the following items. \n\nIf any of these items is true, this is not a finding.\n\n-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.\n\n-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.\n\n-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:\n -The time-out exception cannot exceed 60 minutes.\n -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.).\n -The requirement must be revalidated on an annual basis.\n\nIf the TWT and SWT values are equal or less than the JWT value, this is not a finding.","fixText":"Configure the SMFPRMxx JWT to \"15\" minutes for classified systems.\n\nThe JWT parameter can be greater than \"15\" minutes if the system is processing unclassified information and the following items are reviewed.\n\n-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.\n\n-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.\n\n-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:\n\n-The time-out exception cannot exceed \"60\" minutes.\n\n-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.).\n\n-The requirement must be revalidated on an annual basis.\n\nConfigure any TWT and or SWT to be equal or less than the JWT.","ccis":["CCI-000366"]},{"vulnId":"V-224032","ruleId":"SV-224032r958404_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager to conceal, via the session lock, information previously visible on the display with a publicly viewable image.","description":"A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.\n\nThe session lock is implemented at the point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.\n\nPublicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information.","checkContent":"Ask the system administrator for the configuration parameters for the session manager in use.\n\nIf there is no session manager in use, this is a finding.\n\nIf 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.","fixText":"Configure the session manager to conceal, via the session lock, information previously visible on the display with a publicly viewable image.","ccis":["CCI-000060"]},{"vulnId":"V-224034","ruleId":"SV-224034r958400_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager to manage retaining a users session lock until that user reestablishes access using established identification and authentication procedures.","description":"A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.\n\nThe session lock is implemented at the point where session activity can be determined.\n\nRegardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user re-authenticates. No other activity aside from re-authentication will unlock the system.","checkContent":"Ask the system administrator for the configuration parameters for the session manager in use.\n\nIf there is no session manager in use, this is a finding.\n\nIf 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.","fixText":"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.)","ccis":["CCI-000056"]},{"vulnId":"V-224035","ruleId":"SV-224035r998507_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator (SA) must develop a procedure to remove or disable temporary user accounts after 72 hours.","description":"If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.\n\nTemporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation.\n\nIf temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DOD-defined time period of 72 hours.\n\nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the procedure to automatically remove or disable temporary user accounts after 72 hours.\n\nIf there is no procedure, this is a finding.","fixText":"Develop a procedure to remove or disable emergency user accounts after the crisis is resolved or 72 hours.","ccis":["CCI-000016","CCI-003628"]},{"vulnId":"V-224036","ruleId":"SV-224036r998508_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator (SA) must develop a procedure to remove or disable emergency accounts after the crisis is resolved or 72 hours.","description":"Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. \n\nEmergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the procedure to automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.\n\nIf there is no procedure, this is a finding.","fixText":"Develop a procedure to remove or disable emergency user accounts after the crisis is resolved or 72 hours.","ccis":["CCI-001682","CCI-003628"]},{"vulnId":"V-224037","ruleId":"SV-224037r998509_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator (SA) must develop a procedure to notify SAs and information system security officers (ISSOs) of account enabling actions.","description":"Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the System Administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.\n\nIn order to detect and respond to events that affect user accessibility and application processing, operating systems must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Ask the SA for the procedure to notify system administrators and ISSOs of account enabling actions. If there is no procedure, this is a finding.","fixText":"Develop a documented procedure to notify SAs and ISSOs of account enabling actions.","ccis":["CCI-000015"]},{"vulnId":"V-224038","ruleId":"SV-224038r958794_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner.","description":"Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security.\n\nDetecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.","checkContent":"Ask the system administrator for the procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner.\n\nIf there is no procedure, this is a finding.","fixText":"Develop a procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner.","ccis":["CCI-001744"]},{"vulnId":"V-224040","ruleId":"SV-224040r958936_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to remove all software components after updated versions have been installed.","description":"Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.","checkContent":"Ask the system administrator for the procedure to remove all software components after updated versions have been installed.\n\nIf there is no procedure, this is a finding.","fixText":"Develop a procedure to remove all software components after updated versions have been installed.","ccis":["CCI-002617"]},{"vulnId":"V-224041","ruleId":"SV-224041r958948_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to shut down the information system, restart the information system, and/or notify the system administrator when anomalies in the operation of any security functions are discovered.","description":"If anomalies are not acted upon, security functions may fail to secure the system. \n\nSecurity function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.\n\nNotifications provided by information systems include messages to local computer consoles, and/or hardware indications, such as lights.\n\nThis capability must take into account operational requirements for availability for selecting an appropriate response. The organization may choose to shut down or restart the information system upon security function anomaly detection.","checkContent":"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.\n\nIf a procedure does not exist, this is a finding.\n\nIf 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.","fixText":"Develop a procedure to shut down the information system, restart the information system, and/or notify the system administrator when anomalies occur.","ccis":["CCI-002702"]},{"vulnId":"V-224042","ruleId":"SV-224042r959008_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to offload SMF files to a different system or media than the system being audited.","description":"The task of allocating audit record storage capacity is usually performed during initial installation of the operating system.","checkContent":"Ask the system administrator for the procedure to offload SMF files to a different system or media than the system being audited.\n\nIf the procedure does not exist, this is a finding.","fixText":"Develop a procedure to offload SMF files to a different system or media than the system being audited.","ccis":["CCI-001851"]},{"vulnId":"V-224043","ruleId":"SV-224043r998511_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager for users to directly initiate a session lock for all connection types.","description":"A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.\n\nThe session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity.","checkContent":"Ask the system administrator for the configuration parameters for the session manager in use.\n\nIf there is no session manager in use this is a finding.\n\nIf the session manager in use does not allow users to directly initiate a session lock for all connection types, this is a finding.","fixText":"Configure the session manager to allow users to directly initiate a session lock for all connection types.","ccis":["CCI-000057"]},{"vulnId":"V-224044","ruleId":"SV-224044r1083018_rule","severity":"high","ruleTitle":"The SSH daemon must be configured to use a FIPS 140-2 compliant cryptographic algorithm.","description":"Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000120-GPOS-00061, SRG-OS-000250-GPOS-00093","checkContent":"Locate the SSH daemon configuration file found in /etc/ssh/ directory.\n\nAlternately:\nFrom the Unix System Services ISPF Shell, navigate to ribbon select tools.\nSelect option 1 - Work with Processes.\n\nIf SSH Daemon is not active, this is not a finding.\n\nExamine SSH daemon configuration file. \nsshd_config\n\nIf there are no Ciphers lines, or the ciphers list contains any cipher not starting with \"aes\", this is a finding.\n\nIf the MACs line is not configured to \"hmac-sha1\" or greater, this is a finding.\n\nExamine the z/OS-specific sshd server systemwide configuration: \nzos_sshd_config\n\nIf any of the following is untrue, this is a finding.\n\nFIPSMODE=YES\nCiphersSource=ICSF\nMACsSource=ICSF","fixText":"Edit the SSH daemon configuration and remove any ciphers not starting with \"aes\". If necessary, add a \"Ciphers\" line using FIPS 140-2 compliant algorithms.\n\nConfigure for message authentication to MACs \"hmac-sha1\" or greater.\n\nEdit the z/OS-specific sshd server systemwide configuration file configuration as follows:\nFIPSMODE=YES\nCiphersSource=ICSF\nMACsSource=ICSF","ccis":["CCI-000068","CCI-000803","CCI-001453"]},{"vulnId":"V-224045","ruleId":"SV-224045r958480_rule","severity":"high","ruleTitle":"IBM z/OS SSH daemon must be configured to only use the SSHv2 protocol.","description":"In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"Locate the SSH daemon configuration file. \nMay be found in /etc/ssh/ directory.\n\nAlternately:\nFrom UNIX System Services ISPF Shell navigate to ribbon select tools.\nSelect option 1 - Work with Processes.\n\nIf SSH Daemon is not active, this is not a finding.\n\nExamine SSH daemon configuration file. \n\nIf the variables \"Protocol 2,1\" or \"Protocol 1\" are defined on a line without a leading comment, this is a finding.","fixText":"Edit the sshd_config file and set the \"Protocol\" setting to \"2\".","ccis":["CCI-000382"]},{"vulnId":"V-224046","ruleId":"SV-224046r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS permission bits and user audit bits for HFS objects that are part of the Syslog daemon component must be configured properly.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From an ISPF \nEnter\ncd /usr/sbin\nEnter\nls -alW\nIf File Permission Bits and User Audit Bits for SYSLOG Daemon HFS directories and files are as below this is not a finding.\n/usr/sbin/syslogd 1740 fff\n\nEnter\ncd /etc/\nEnter\nls -alW\n\nIf File Permission Bits and User Audit Bits for Output log file defined in the configuration file are as below this is not a finding.\n/etc/syslog.conf 0744 faf\n0744 fff\n\nNotes:\nThe /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.\nThe /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:\n_BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf\n\nFor example, in the SYSLOGD started task JCL:\n\n//SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT \n// PARM='POSIX(ON) ALL31(ON)/ -f /etc/syslogd.conf'\n\n//SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT \n// PARM='POSIX(ON) ALL31(ON) /-f //''SYS1.TCPPARMS(SYSLOG)'''\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"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.\n\nLog files should have security that prevents anyone except the syslogd process and authorized maintenance jobs from writing to or deleting them. \n\nA maintenance process to periodically clear the log files is essential. Logging stops if the target file system becomes full.\n\nSYSLOG Daemon HFS Object Security Settings\nFile Permission Bits User Audit Bits\n/usr/sbin/syslogd 1740 fff\n[Configuration File]\n/etc/syslog.conf 0744 faf\n[Output log file defined in the configuration file]\n0744 fff\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nNOTES:\nThe /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.\n\nThe /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:\n\n_BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf\n\nFor example, in the SYSLOGD started task JCL:\n\n//SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT \n// PARM='POSIX(ON) ALL31(ON)/ -f /etc/syslogd.conf'\n\n//SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT \n// PARM='POSIX(ON) ALL31(ON) /-f //''SYS1.TCPPARMS(SYSLOG)'''\n\nThe following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits:\n\nchmod 1740 /usr/lpp/tcpip/sbin/syslogd\nchaudit rwx=f /usr/lpp/tcpip/sbin/syslogd\nchmod 0744 /etc/syslog.conf\nchaudit w=sf,rx+f /etc/syslog.conf\nchmod 0744 /log_dir/log_file\nchaudit rwx=f /log_dir/log_file","ccis":["CCI-000213"]},{"vulnId":"V-224047","ruleId":"SV-224047r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS Syslog daemon must not be started at z/OS initialization.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"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.\n\nIf the Syslog daemon SYSLOGD is started automatically during the initialization of the z/S/ system, this is not a finding.","fixText":"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.\n\nIt 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.","ccis":["CCI-000764"]},{"vulnId":"V-224048","ruleId":"SV-224048r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS Syslog daemon must be properly defined and secured.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(SYSLOGD) SEGMENT(OMVS)\n\nIf the following guidance is true, this is not a finding.\n\n-The Syslog daemon userid is SYSLOGD.\n-The SYSLOGD userid has the STC facility.\n-The SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment.\n-The SYSLOGD started proc is assigned the SYSLOGD userid is in the Started Task Table.\n\nIf Syslog daemon is started from /etc/rc then from the ISPF Command Shell enter:\nOMVS\ncd /etc\ncat rc \n\nIf Syslog daemon is started from /etc/rc then ensure that the \"_BPX_JOBNAME\" and \"_BPX_USERID\" environment variables are assigned a value of SYSLOGD.\n\nIf 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.","fixText":"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.\n\nThe Syslog daemon userid is SYSLOGD.\nThe SYSLOGD userid has the STC facility.\nThe SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment.\n\nTo set up and use as an MVS Started Proc, the following sample commands are provided:\n\nTSS CREATE(SYSLOGD) TYPE(USER) NAME(SYSLOGD) -\nDEPT(existing-dept) FACILITY(STC) -\nPASSWORD(password,0)\nTSS ADD(SYSLOGD) DFLTGRP(stctcpx) GROUP(stctcpx)\nTSS ADD(SYSLOGD) SOURCE(INTRDR)\nTSS ADD(SYSLOGD) UID(0) HOME(/) OMVSPGM(/bin/sh)\n\nThe SYSLOGD started proc is assigned the SYSLOGD userid is in the Started Task Table.\n\nTSS ADD(STC) PROCNAME(SYSLOGD) ACID(SYSLOGD)\n\nIf /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.","ccis":["CCI-000764"]},{"vulnId":"V-224049","ruleId":"SV-224049r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFSMS resources must be protected in accordance with the proper security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"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.\n\nThe TSS resources are owned or DEFPROT is specified for the resource class.\n\nTo 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.\n\nThe resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE is defined with access of NONE.\nThe resource STGADMIN.IGG.CATALOG.SECURITY.BOTH is defined with access of READ.\n\nNote: 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.\n\nIf the resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE and STGADMIN.IGG.CATALOG.SECURITY.BOTH are both defined, ADMIN.IGG.CATALOG.SECURITY.BOTH takes precedence.\n\nSTGADMIN.DPDSRN.olddsname is restricted to system programmers and all access is logged.\n\nThe STGADMIN.IGD.ACTIVATE.CONFIGURATION is restricted to system programmers and all access is logged.\n\nThe STGADMIN.IGG.DEFDEL.UALIAS is restricted to centralized and decentralized security personnel and system programmers and all access is logged.\n\nThe following resources and prefixes may be available to the end user.\n\nSTGADMIN.ADR.COPY.CNCURRNT\nSTGADMIN.ADR.COPY.FLASHCPY\nSTGADMIN.ADR.COPY.TOLERATE.ENQF\nSTGADMIN.ADR.DUMP.CNCURRNT\nSTGADMIN.ADR.DUMP.TOLERATE.ENQF\nSTGADMIN.ADR.RESTORE.TOLERATE.ENQF\nSTGADMIN.ARC.ENDUSER.\nSTGADMIN.IGG.ALTER.SMS\n\nThe following resource is restricted to Application Production Support Team members, Automated Operations, DASD managers, and system programmers.\n\nSTGADMIN.IDC.DCOLLECT\n\nThe following resources are restricted to Application Production Support Team members, DASD managers, and system programmers.\n\nSTGADMIN.ARC.CANCEL\nSTGADMIN.ARC.LIST\nSTGADMIN.ARC.QUERY\nSTGADMIN.ARC.REPORT\nSTGADMIN.DMO.CONFIG\nSTGADMIN.IFG.READVTOC\nSTGADMIN.IGG.DELGDG.FORCE\n\nThe following resource prefixes, at a minimum, are restricted to DASD managers and system programmers.\n\nSTGADMIN.ADR\nSTGADMIN.ANT\nSTGADMIN.ARC\nSTGADMIN.DMO\nSTGADMIN.ICK\nSTGADMIN.IDC\nSTGADMIN.IFG\nSTGADMIN.IGG\nSTGADMIN.IGWSHCDS\n\nThe following Storage Administrator functions prefix is restricted to DASD managers and system programmers and all access is logged.\n\nSTGADMIN.ADR.STGADMIN.","fixText":"Ensure that the following are properly specified in the ESM.\n\nNote: 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.\n\nBelow is listed the access requirements for SMS Resources. Ensure the guidelines for the resources and/or generic equivalent are followed.\n\nThe TSS resources are owned and/or DEFPROT is specified for the resource class.\n\nConfigure resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE with no access.\nNote: 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.\n\nConfigure STGADMIN.IGG.CATALOG.SECURITY.BOTH to have READ access for all.\n\nTSS ADD(ADMIN) IBMFAC(STGADMIN)\nor\nTSS REPLACE(RDT) RESCLASS(IBMFAC) ATTR(DEFPROT)\nThe STGADMIN.DPDSRN.olddsname is restricted to System Programmers and all access is logged.\n\nExample:\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.DPDSRN.olddsname) -\nACCESS(READ) ACTION(AUDIT)\n\nThe STGADMIN.IGD.ACTIVATE.CONFIGURATION is restricted to system programmers and all access is logged.\n\nExample:\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IGD.ACTIVATE.CONFIGURATION) -\nACCESS(READ) ACTION(AUDIT)\n\nThe STGADMIN.IGG.DEFDEL.UALIAS is restricted to system programmers and security personnel and all access is logged.\n\nExample:\nTSS PERMIT(secasmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) -\nACCESS(READ) ACTION(AUDIT)\nTSS PERMIT(secdsmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) -\nACCESS(READ) ACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IGG.DEFDEL.UALIAS) -\nACCESS(READ) ACTION(AUDIT)\n\nThe following resources and prefixes may be available to the end user.\n\nExample:\nSTGADMIN.ADR.COPY.CNCURRNT\nSTGADMIN.ADR.COPY.FLASHCPY\nSTGADMIN.ADR.COPY.TOLERATE.ENQF\nSTGADMIN.ADR.DUMP.CNCURRNT\nSTGADMIN.ADR.DUMP.TOLERATE.ENQF\nSTGADMIN.ADR.RESTORE.TOLERATE.ENQF\nSTGADMIN.ARC.ENDUSER.\nSTGADMIN.IGG.ALTER.SMS\n\nExample:\nTSS PERMIT(endusers) IBMFAC(STGADMIN.ADR.COPY.CNCURRNT.) -\nACCESS(READ)\n\nThe following resource is restricted to Application Production Support Team members, Automated Operations, DASD managers, and system programmers.\n\nSTGADMIN.IDC.DCOLLECT\n\nExample:\nTSS PERMIT(appssmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ)\nTSS PERMIT(autosmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ)\nTSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ)\nTSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ)\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.IDC.DCOLLECT) ACCESS(READ)\n\nThe following resources are restricted to Application Production Support Team members, DASD managers, and system programmers.\n\nExample:\nSTGADMIN.ARC.CANCEL\nSTGADMIN.ARC.LIST\nSTGADMIN.ARC.QUERY\nSTGADMIN.ARC.REPORT\nSTGADMIN.DMO.CONFIG\nSTGADMIN.IFG.READVTOC\nSTGADMIN.IGG.DELGDG.FORCE\n\nExample:\nTSS PERMIT(appssmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ)\nTSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ)\nTSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ)\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ARC.CANCEL) ACCESS(READ)\n\nThe following resource prefixes, at a minimum, are restricted to DASD managers and system programmers.\n\nSTGADMIN.ADR\nSTGADMIN.ANT\nSTGADMIN.ARC\nSTGADMIN.DMO\nSTGADMIN.ICK\nSTGADMIN.IDC\nSTGADMIN.IFG\nSTGADMIN.IGG\nSTGADMIN.IGWSHCDS\n\nExample:\n\nTSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ)\nTSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ)\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ADR) ACCESS(READ)\n\nThe following Storage Administrator functions prefix is restricted to DASD managers and system programmers and all access is logged.\n\nSTGADMIN.ADR.STGADMIN.\n\nExample:\n\nTSS PERMIT(dasbsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) -\nACTION(AUDIT)\nTSS PERMIT(dasdsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) -\nACTION(AUDIT)\nTSS PERMIT(syspsmpl) IBMFAC(STGADMIN.ADR.STGADMIN.) ACCESS(READ) -\nACTION(AUDIT)","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-224050","ruleId":"SV-224050r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFSMS Program Resources must be properly defined and protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"Refer to the load modules residing in the following Load libraries to determine program resource definitions:\nv SYS1.DGTLLIB for DFSMSdfp/ISMF\nv SYS1.DGTLLIB for DFSMSdss/ISMF\nv SYS1.DFQLLIB for DFSMShsm\n\nIf the installation moves these modules to another load library the installation-defined load library must be used in the program protection.\n\nIf the TSS resources are owned or DEFPROT is specified for the resource class, this is not a finding.\n\nIf the TSS resource access authorizations restrict access to the appropriate personnel, this is not a finding.","fixText":"Configure the following to be properly specified in the ACP.\n\nNote: 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.\n\nReference the SMS Program Resources as provided by the following libraries:\nv SYS1.DGTLLIB for DFSMSdfp/ISMF\nv SYS1.DGTLLIB for DFSMSdss/ISMF\nv SYS1.DFQLLIB for DFSMShsm\n\nIf the installation moves these modules to another load library the installation-defined load library must be used in the program protection.\n\nThe TSS resources as designated in the above are owned and/or DEFPROT is specified for the resource class.\n\nThe TSS resource access authorizations restrict access to the appropriate personnel as designated in the above.\n\nThe following commands are provided as a sample for implementing resource controls:\n\nExample:\nTSS ADD(dept-acid) PROGRAM(ACBFUTO2)\nTSS PERMIT(smplsmpl) PROGRAM(ACBFUTO2)\nTSS PERMIT(dasdsmpl) PROGRAM(ACBFUTO2)\nTSS PERMIT(secasmpl) PROGRAM(ACBFUTO2)\nTSS PERMIT(syspsmpl) PROGRAM(ACBFUTO2)\nTSS PERMIT(tstcsmpl) PROGRAM(ACBFUTO2)","ccis":["CCI-000213"]},{"vulnId":"V-224051","ruleId":"SV-224051r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFSMS control data sets must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"Refer to the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets:\n\nSource Control Data Set (SCDS)\nActive Control Data Set (ACDS)\nCommunications Data Set (COMMDS)\nAutomatic Class Selection Routine Source Data Sets (ACS)\nACDS Backup\nCOMMDS Backup\n\nIf 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.\n\nIf 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.\n\nNote: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets.","fixText":"Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets:\n\nSource Control Data Set (SCDS)\nActive Control Data Set (ACDS)\nCommunications Data Set (COMMDS)\nAutomatic Class Selection Routine Source Data Sets (ACS)\nACDS Backup\nCOMMDS Backup\n\nAssign 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:\n\nTSS ADD(user-id) DSN(data name)\n\nEnsure 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.\n\nNote: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets.\n\nPermit access to those personnel who manage the SMS environment, replacing user-id with the userid of the user or a Group profile:\n\nTSS PERMIT(user-id) DSN(data name) ACC(UPDATE) ACTION(AUDIT)\n\nPermit access to those personnel that perform maintenance on these data sets:\n\nTSS PERMIT(user-id) DSN(data name) ACC(ALL) ACTION(AUDIT)","ccis":["CCI-000213","CCI-000549"]},{"vulnId":"V-224052","ruleId":"SV-224052r991589_rule","severity":"medium","ruleTitle":"IBM z/OS using DFSMS must properly specify SYS(x).PARMLIB(IGDSMSxx), SMS parameter settings.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Review the logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), for the following SMS parameter settings:\n\nParameter Key\nSMS\nACDS(ACDS data set name)\nCOMMDS(COMMDS data set name)\n\nIf the required parameters are defined, this is not a finding.","fixText":"Configure the DFSMS-related PDS members and statements specified in the system parmlib concatenation as outlined below:\n\nParameter Key\nSMS\nACDS(ACDS data set name)\nCOMMDS(COMMDS data set name)","ccis":["CCI-000366"]},{"vulnId":"V-224054","ruleId":"SV-224054r958406_rule","severity":"medium","ruleTitle":"IBM z/OS SMF recording options for the SSH daemon must be configured to write SMF records for all eligible events.","description":"SMF data collection is the basic unit of tracking of all system functions and actions. Included in this tracking data are the audit trails from each of the ACPs. If the control options for the recording of this tracking are not properly maintained, then accountability cannot be monitored, and its use in the execution of a contingency plan could be compromised.\n\nSatisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000392-GPOS-00172","checkContent":"Locate the SSH daemon configuration file, which may be found in /etc/ssh/ directory.\n\nAlternately:\nFrom UNIX System Services ISPF Shell, navigate to ribbon select tools.\nSelect option 1 - Work with Processes.\n\nIf SSH Daemon is not active, this is not a finding.\n\nExamine SSH daemon configuration file. \n\nIf ServerSMF is not coded with ServerSMF TYPE119_U83 or is commented out, this is a finding.","fixText":"Configure the SERVERSMF statement in the SSH Daemon configuration file to TYPE119_U83.","ccis":["CCI-000067","CCI-002884"]},{"vulnId":"V-224055","ruleId":"SV-224055r958586_rule","severity":"medium","ruleTitle":"The IBM z/OS SSH daemon must be configured with the Standard Mandatory DoD Notice and Consent Banner.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:\n\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"","checkContent":"Locate the SSH daemon configuration file. \nMay be found in /etc/ssh/ directory.\n\nAlternately:\nFrom UNIX System Services ISPF Shell navigate to ribbon select tools.\nSelect option 1 - Work with Processes.\n\nIf SSH Daemon is not active, this is not a finding.\n\nExamine SSH daemon configuration file.\n\nIf Banner statement is missing or configured to none, this is a finding.\n\nEnsure that the contents of the file specified on the banner statement contain a logon banner.\nThe 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.\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","fixText":"Configure the banner statement to a file that contains the Department of Defense (DoD) logon banner.\n\nEnsure that the contents of the file specified on the banner statement contain a logon banner.\nThe below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. \n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-224056","ruleId":"SV-224056r958406_rule","severity":"medium","ruleTitle":"IBM z/OS PROFILE.TCPIP configuration statements for the TCP/IP stack must be properly coded.","description":"Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL.\n\nIf the following items are in effect for the configuration statements specified in the TCP/IP Profile configuration file, this is not a finding.\n\nNOTE: 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.\n\n-The SMFPARMS statement is not coded or commented out.\n-The DELETE statement is not coded or commented out for production systems.\n-The SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands.\n-The TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand.\n\nIf the TCPCONFIG does not have the TTLS statement coded, this is a finding.\n\nNOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance.","fixText":"Ensure the following items are in effect for the configuration statements specified in the TCP/IP Profile configuration file:\n\nNOTE: 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.\n\n-The SMFPARMS statement is not coded or commented out.\n-The DELETE statement is not coded or commented out for production systems.\n-The SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands.\n-The TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand.\n\nNOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance in STIG ID ITCP0070.\n\nBASE TCP/IP PROFILE.TCPIP CONFIGURATION STATEMENTS\nFUNCTIONS\n\nINCLUDE- Specifies the name of an MVS data set that contains additional PROFILE.TCPIP statements to be used\n- Alters the configuration specified by previous statements\n\nSMFPARMS- Specifies SMF logging options for some TCP applications; replaced by SMFCONFIG\n- Controls collection of audit data\n\nDELETE- Specifies some previous statements, including PORT and PORTRANGE, that are to be deleted\n- Alters the configuration specified by previous statements\n\nSMFCONFIG- Specifies SMF logging options for Telnet, FTP, TCP, API, and stack activity\n- Controls collection of audit data\n\nTCPCONFIG- Specifies various settings for the TCP protocol layer of TCP/IP\n- Controls port access   \n\nTCPCONFIG 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. \n\nNote: If AT-TLS is enabled, you must activate the SERVAUTH class, define the INITSTACK resource profile, and permit users to it.\n\nNOTE: If the INCLUDE statement is coded, the data set specified will be checked for access authorization compliance.","ccis":["CCI-000067"]},{"vulnId":"V-224057","ruleId":"SV-224057r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS permission bits and user audit bits for HFS objects that are part of the Base TCP/IP component must be configured properly.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nomvs\n\nAt the input line enter:\ncd /etc\nenter\nls -alW\n\nIf the following File permission and user Audit Bits are true this is not a finding.\n\n/etc/hosts 0744 faf\n/etc/protocol 0744 faf\n/etc/resolv.conf 0744 faf\n/etc/services 0740 faf\n\ncd /usr\nls -alW\n\nIf the following file permission and user Audit Bits are true this is not a finding.\n\n/usr/lpp/tcpip/sbin 0755 faf\n/usr/lpp/tcpip/bin 0755 faf\n\nNotes: Some of the files listed above are not used in every configuration. The absence of a file is not considered a finding.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"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:\n\nBASE TCP/IP HFS Object Security Settings\nFile Permission Bits User Audit Bits\n/etc/hosts 0744 faf\n/etc/protocol 0744 faf\n/etc/resolv.conf 0744 faf\n/etc/services 0740 faf\n/usr/lpp/tcpip/sbin 0755 faf\n/usr/lpp/tcpip/bin 0755 faf\n\nSome 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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nThe following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits:\n\nchmod 0744 /etc/hosts\nchaudit w=sf,rx+f /etc/hosts\nchmod 0744 /etc/protocol\nchaudit w=sf,rx+f /etc/protocol\nchmod 0744 /etc/resolv.conf\nchaudit w=sf,rx+f /etc/resolv.conf\nchmod 0740 /etc/services\nchaudit w=sf,rx+f /etc/services\nchmod 0755 /usr/lpp/tcpip/bin\nchaudit w=sf,rx+f /usr/lpp/tcpip/bin\nchmod 0755 /usr/lpp/tcpip/sbin\nchaudit w=sf,rx+f /usr/lpp/tcpip/sbin","ccis":["CCI-000213"]},{"vulnId":"V-224058","ruleId":"SV-224058r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS TCP/IP resources must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.","checkContent":"If the following guidance is true, this is not a finding.\n\n-The EZA, EZB, and IST resources of the SERVAUTH resource class are properly owned and/or DEFPROT is specified in the SERVAUTH resource class.\n-No access is given to the EZA, EZB, and IST high level resources of the SERVAUTH resource class.\n-If the product CSSMTP is on the system, no access is given to EZB.CSSMTP of the SERVAUTH resource class.\n-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.\n-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.\n-The EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements.\n-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.\n-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.","fixText":"Develop a plan of action to implement the required changes. Ensure the following items are in effect for TCP/IP resources.\n\nNote: 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.\n\n-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.\n-No access is given to the EZA, EZB, and IST resources of the SERVAUTH resource class.\n-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.\n-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.\n-The EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements.\n-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.\n\nThe 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.\n\nThe following commands are provided as a sample for implementing resource controls:\n\nTSS ADD(ADMIN) SERVAUTH(EZB)\nor\nTSS REPLACE(RDT) RESCLASS(SERVAUTH) ATTR(DEFPROT)\n\nTSS PER(authusers) SERVAUTH(EZB.CSSMTP.sysname.writername.JESnode) ACCESS(READ)\nTSS PER(authusers) SERVAUTH(EZB.FTP.) ACCESS(READ)\nTSS PER(ftpprofile)SERVAUTH(EZB.FTP.sysname.ftpstc.ACCESS.HFS)ACC(READ)\nTSS PER(authusers) SERVAUTH(EZB.NETACCESS.) ACCESS(READ)\nTSS PER(authusers) SERVAUTH(EZB.PORTACCESS.) ACCESS(READ)\nTSS PER(authusers) SERVAUTH(EZB.STACKACCESS.) ACCESS(READ)\nTSS PER(authusers) SERVAUTH(EZB.INITSTACK.) ACCESS(READ)\n\nTSS PER(ftpprofile)SERVAUTH(EZB.STACKACCESS.sysname.TCPIP)ACC(READ)","ccis":["CCI-000213"]},{"vulnId":"V-224059","ruleId":"SV-224059r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS data sets for the Base TCP/IP component must be properly protected.","description":"MVS data sets of the Base TCP/IP component provide the configuration, operational, and executable properties of IBMs TCP/IP system product. Failure to properly secure these data sets may lead to unauthorized access resulting in the compromise of the integrity and availability of the operating system environment, ACP, and customer data.\n\nTo mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"Execute a data set access list for all TCP/IP base components.\n\nIf all of the following items are true, this is not a finding.\n\nWRITE 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).\n\nWRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is restricted to systems programming personnel.\n\nNote: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same access authorization requirements. \n\nWRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is logged.\n\nNote: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same logging requirements.\n\nWRITE and ALLOCATE access to the data set(s) containing the configuration files shared by TCP/IP applications is restricted to systems programming personnel.\n\nNote: For systems running the TSS ACP replace the WRITE and ALLOCATE with WRITE, UPDATE, CREATE, CONTROL, SCRATCH, and ALL.","fixText":"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:\n\nWRITE 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).\n\nWRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is restricted to systems programming personnel.\n\nNote: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same access authorization requirements.\n\nWRITE and ALLOCATE access to the data set(s) containing the Data and Profile configuration files is logged.\n\nNote: If any INCLUDE statements are specified in the Profile configuration file, the named MVS data sets have the same logging requirements.\n\nWRITE and ALLOCATE access to the data set(s) containing the configuration files shared by TCP/IP applications is restricted to systems programming personnel.\n\nNote: For systems running the TSS ACP replace the WRITE and ALLOCATE with WRITE, UPDATE, CREATE, CONTROL, SCRATCH, and ALL.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224060","ruleId":"SV-224060r991589_rule","severity":"medium","ruleTitle":"IBM z/OS Configuration files for the TCP/IP stack must be properly specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Refer to the procedure libraries defined to JES2 and locate the TCPIP JCL member.\n\nNote:\nIf 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.\n\nIf GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA.\n\nIf the PROFILE and SYSTCPD DD statements specify the TCP/IP Profile and Data configuration files respectively, this not a finding.\n\nIf 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.","fixText":"Review the TCP/IP started task JCL to ensure the configuration file names are specified on the appropriate DD statements and parameter option.\n\nDuring 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.\n\nThe 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.\n\nNote:\nIf 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.\n\nIf GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA.\n\nThe 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.","ccis":["CCI-000366"]},{"vulnId":"V-224061","ruleId":"SV-224061r958482_rule","severity":"medium","ruleTitle":"IBM z/OS started tasks for the Base TCP/IP component must be defined in accordance with security requirements.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"Refer to system Proclibs to determine the TCPIP address space(s).\n\nFrom the ISPF Command Shell enter:\nTSS list(<TCPIP STCs>) SEGMENT(OMVS)\n\nFor each TCPIP:\n\nIf all of the following items are true, this is not a finding.\n\nIf any item is untrue, this is a finding.\n\nFrom the ISPF Command Shell enter\nTSS LIST(EZAZSSI) SEGMENT(OMVS)\nIf EZAZSSI STC has the STC facility, this is not finding.\n\n-Named TCPIP or, in the case of multiple instances, prefixed with TCPIP.\n-Has the STC facility. \n\n-z/OS UNIX attributes: \nUID(0), HOME directory '/', shell program /bin/sh \n\nEnsure the following items are in effect for the ACID assigned to the EZAZSSI started task: \n-Named EZAZSSI \n-Has the STC facility.","fixText":"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): \n\n1) Named TCPIP or, in the case of multiple instances, prefixed with TCPIP \n\n2) Has the STC facility\n\n3) z/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh \n\nEnsure the following items are in effect for the ACID assigned to the EZAZSSI started task: \n\n1) Named EZAZSSI \n\n2) Has the STC facility \n\nFor example:\n\nThe 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:\n\nTSS CREATE(TCPIP) TYPE(USER) NAME(TCPIP)\nDEPT(existing-dept) FACILITY(STC) PASSWORD(password,0)\nTSS ADD(TCPIP) DFLTGRP(STCTCPX) GROUP(STCTCPX)\nTSS ADD(TCPIP) SOURCE(INTRDR)\nTSS ADD(TCPIP) UID(0) HOME(/) OMVSPGM(/bin/sh)\nTSS ADD(TCPIP) MASTFAC(TCP)\nTSS ADD(STC) PROCNAME(TCPIP) ACID(TCPIP)\nTSS PERMIT(TCPIP) IBMFAC(BPX.DAEMON) ACCESS(READ)\n\nTSS CREATE(EZAZSSI) TYPE(USER) NAME(EZAZSSI)\nDEPT(existing-dept) FACILITY(STC) PASSWORD(password,0)\nTSS ADD(EZAZSSI) DFLTGRP(STCTCPX) GROUP(STCTCPX)\nTSS ADD(EZAZSSI) SOURCE(INTRDR)\nTSS ADD(EZAZSSI) UID(non-zero) HOME(/) OMVSPGM(/bin/sh)\nTSS ADD(EZAZSSI) MASTFAC(TCP)\nTSS ADD(STC) PROCNAME(EZAZSSI) ACID(EZAZSSI)","ccis":["CCI-000764"]},{"vulnId":"V-224062","ruleId":"SV-224062r958672_rule","severity":"medium","ruleTitle":"IBM z//OS must be configured to restrict all TCP/IP ports to ports, protocols, and/or services as defined in the PPSM CAL and vulnerability assessments.","description":"Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nOperating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"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. \n\nIf 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.","fixText":"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.","ccis":["CCI-002314"]},{"vulnId":"V-224065","ruleId":"SV-224065r958390_rule","severity":"medium","ruleTitle":"IBM z/OS TN3270 Telnet server configuration statement MSG10 text must have the Standard Mandatory DoD Notice and Consent Banner.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:\n\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TN3270 started task JCL.\n\nIf all USS tables referenced in BEGINVTAM USSTCP statements include MSG10 text that specifies the Standard logon banner this is not a finding. \n\nThe 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:\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\n\nDOD 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.","fixText":"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:\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\n\nDOD 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.","ccis":["CCI-000048","CCI-000050"]},{"vulnId":"V-224066","ruleId":"SV-224066r958846_rule","severity":"medium","ruleTitle":"IBM z/OS SMF recording options for the TN3270 Telnet server must be properly specified.","description":"Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).\n\nSatisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000032-GPOS-00013","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL.\n\nIf the following configuration statement settings are in effect in the TCP/IP Profile configuration data set, this is not a finding.\n\nNOTE: 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.\n\n-The TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\n-The TELNETPARMS SMFTERM statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\n\nNote: 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.","fixText":"Code TN3270 configuration file to the requirements specified below.\n\nNOTE: 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.\n\n-The TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\n-The TELNETPARMS SMFTERM statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\n\nNOTE: Effective in z/OS release 1.2, the SMFINIT and SMFTERM statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks.","ccis":["CCI-000067","CCI-002884"]},{"vulnId":"V-224067","ruleId":"SV-224067r1050770_rule","severity":"medium","ruleTitle":"IBM z/OS SSL encryption options for the TN3270 Telnet server must be specified properly for each statement that defines a SECUREPORT or within the TELNETGLOBALS.","description":"Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.\n\nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nEncryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000120-GPOS-00061, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000396-GPOS-00176, SRG-OS-000478-GPOS-00223, SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190, SRG-OS-000478-GPOS-00223","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL.\n\nIf the following items are in effect for the configuration specified in the TCP/IP Profile configuration file, this is not a finding.\n\nNOTE: 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.\n\nNOTE: FIPS 140-2 minimum encryption is the accepted level of encryption and will override this requirement if greater.\n\n-The TELNETGLOBALS block that specifies an ENCRYPTION statement states one or more of the below cipher specifications.\n-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.\n\nCipher Specifications\nSSL_3DES_SHA\nSSL_AES_256_SHA\nSSL_AES_128_SHA","fixText":"Configure the SECUREPORT and TELNETPARMS ENCRYPTION statements and/or the TELNETGLOBALS statement in the PROFILE.TCPIP file to conform to the requirements specified below.\n\nThe TELNETGLOBALS block may specify an ENCRYPTION statement that specifies one or more of the below cipher specifications.\n\nEach 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.\n\nTo 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:\n\nCipher Specifications\nSSL_3DES_SHA\nSSL_AES_256_SHA\nSSL_AES_128_SHA\n\nNote: Always check for the minimum allowed in FIPS 140-2.","ccis":["CCI-000068","CCI-000803","CCI-001453","CCI-002418","CCI-002420","CCI-002421","CCI-002422","CCI-002450","CCI-002890","CCI-003123"]},{"vulnId":"V-224068","ruleId":"SV-224068r991589_rule","severity":"medium","ruleTitle":"IBM z/OS VTAM session setup controls for the TN3270 Telnet server must be properly specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Refer to the TN3270 Profile configuration file identified by the PROFILE DD in the TN3270 procedure.\n\nNOTE: 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.\n\nIf all of the following are true, this is not a finding. \n\nIf any of the above is untrue, this is a finding.\n\n-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.\n-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.\n-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.\n-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.\n-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.\n\nNOTE: 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.","fixText":"Review the BEGINVTAM configuration statements in the PROFILE.TCPIP file. Ensure they conform to the specifications below.\n\nNOTE: 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.\n\nWithin 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.\n\nThe 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.\n\nWithin 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.\n\nAny 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.","ccis":["CCI-000366"]},{"vulnId":"V-224069","ruleId":"SV-224069r970703_rule","severity":"medium","ruleTitle":"IBM z/OS PROFILE.TCPIP configuration for the TN3270 Telnet server must have the INACTIVE statement properly specified.","description":"Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.\n\nSatisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109","checkContent":"Refer to the Profile configuration file specified on the PROFILE DD statement in the TCPIP started task JCL.\n\nNOTE: 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.\n\nTELNETPARMS Block (one defined for each port the server is listening to, typically ports 23 and 992)\n\nIf the TELNETPARMS INACTIVE statement is coded within each TELNETPARMS statement block and specifies a value between \"1\" and \"900\", this is not a finding.\n\nNOTE: Effective in z/OS release 1.2, the INACTIVE statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks.","fixText":"Configure the configuration statements in the PROFILE.Tn3270 to conform to the specifications below:\n\nNOTE: 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.\n\nThe TELNETPARMS INACTIVE statement is coded either within the TELNETGLOBALS or within each TELNETPARMS statement block and specifies a value between \"1\" and \"900\".","ccis":["CCI-001133","CCI-002361"]},{"vulnId":"V-224072","ruleId":"SV-224072r1137691_rule","severity":"medium","ruleTitle":"IBM Z/OS TSOAUTH resources must be restricted to authorized users.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS TSOAUTH(*)\n\nFor each resource defined enter:\nTSS WHOHAS(<tsoauth resource>)\n\nIf the following guidance is true, this is not a finding.\n\n-The ACCT authorization is restricted to security personnel.\n-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.\n-The MOUNT authorization is restricted to DASD batch users only.\n-The OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.).\n-The PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to auditors.\n-The TESTAUTH authorization is restricted to only z/OS systems programming personnel.","fixText":"Configure the TSOAUTH resource class to control sensitive TSO/E commands.\n\nNote: 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.\n\nBelow is listed the access requirements for TSOAUTH resources. Ensure the guidelines for the resources and/or generic equivalent are followed.\n\n-The ACCT authorization is restricted to security personnel.\n-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.\n-The MOUNT authorization is restricted to DASD batch users only.\n-The OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc.).\n-The PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to audit users.\n-The TESTAUTH authorization is restricted to only z/OS systems programming personnel.","ccis":["CCI-000213"]},{"vulnId":"V-224073","ruleId":"SV-224073r958726_rule","severity":"high","ruleTitle":"CA-TSS LOGONIDs must not be defined to SYS1.UADS for non-emergency use.","description":"Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.\n\nPrivileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.","checkContent":"Ask the system administrator to provide a list of all emergency userids available to the site along with the associated function of each.\n\nIf any SYS1.UADS userids are assigned for other than emergency purposes, this is a finding.","fixText":"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.","ccis":["CCI-002235"]},{"vulnId":"V-224074","ruleId":"SV-224074r991589_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX HFS MapName file security parameters must be properly specified.","description":"Removal of unneeded or non-secure functions, ports, protocols, and services mitigate the risk of unauthorized connection of devices, unauthorized transfer of information, or other exploitation of these resources.","checkContent":"Refer to the logical parmlib data sets, example: SYS1.PARMLIB(BPXPRMxx), for the following FILESYSTYPE entry:\n\nFILESYSTYPE TYPE(AUTOMNT) ENTRYPOINT(BPXTAMD)\n\nIf the above entry is not found or is commented out in the BPXPRMxx member(s), this is not applicable.\n\nFrom the ISPF Command Shell enter:\nOMVS\ncd /etc\ncat auto.master\nperform a contents list for the file identified \n Example:\ncat u.map\nNote: The /etc/auto.master HFS file (and the use of Automount) is optional. If the file does not exist, this is not applicable.\n\nNote: 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.\n\nIf each MapName file specifies the \"setuid No\" and \"security Yes\" statements for each automounted directory, this is not a finding.\n\nIf there is any deviation from the required values, this is a finding.","fixText":"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.\n\nThe /etc/auto.master HFS file (and the use of Automount) is optional. \n\nThe 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.\n\nEach MapName file will specify the \"setuid NO\" and \"security YES\" statements for each automounted directory.\n\nIf there is a deviation from the required values, documentation must exist for the deviation.\n\n\"Security NO\" disables security checking for file access. \"Security NO\" is only allowed on test and development domains.\n\n\"Setuid YES\" allows a user to run under a different UID/GID identity. Justification documentation is required to validate the use of \"setuid YES\".","ccis":["CCI-000366"]},{"vulnId":"V-224075","ruleId":"SV-224075r1038966_rule","severity":"medium","ruleTitle":"IBM z/OS NOBUFFS in SMFPRMxx must be properly set (default is MSG).","description":"It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.\n\nAudit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.\n\nThis requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member in SYS1.PARMLIB.\n\nIf NOBUFFS is set to \"HALT\", this is not a finding.\n\nNote: If availability is an overriding concern NOBUFFS can be set to MSG.","fixText":"Configure NOBUFFS to \"HALT\" unless availability is an overriding concern then NOBUFFS can be set to MSG.","ccis":["CCI-000140"]},{"vulnId":"V-224076","ruleId":"SV-224076r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS BPX resource(s) must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS IBMFAC(BPX.)\n\nIf the BPX. resource is properly owned, this is not a finding.\n\nFrom the ISPF Command Shell enter:\nTSS WHOHAS (<each BPX resource>)\n\nIf any item below are untrue, this is a finding.\n\n-There are no TSS rules that allow access to the BPX resource.\n-There are no TSS rules for BPX.SAFFASTPATH defined.\n-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.","fixText":"Because they convey especially powerful privileges, the settings for BPX.DAEMON, BPX.SAFFASTPATH, BPX.SERVER, and BPX.SUPERUSER require special attention. \n\nReview the following items for the IBMFAC resource class: \n\n-The TSS owner defined for the BPX resource. \n-There are no TSS rules that allow access to the BPX resource. \n-There are no TSS rules for BPX.SAFFASTPATH defined. \n\nThe 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. \n\nFor Example:\nThe following commands can be used to provide the required protection:\n\nTSS ADD(ADMIN) IBMFAC(BPX.)\nTSS PERMIT(ALL) IBMFAC(BPX.SAFFASTPATH) ACCESS(NONE)\n\nNOTE:\nThe 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.","ccis":["CCI-000213"]},{"vulnId":"V-224077","ruleId":"SV-224077r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000326-GPOS-00126","checkContent":"From the ISPF Command Shell, enter:\nTSS WHOOWNS SURROGAT(*)\n\nIf the TSS resources and/or generic equivalent for BPX. is not owned, enter:\nTSS LIST RDT\n\nIf the TSS resources and/or generic equivalent for BPX. is not owned or DEFPROT is specified for the resource class, this is a finding.\n\nFrom the ISPF Command Shell, enter:\nTSS WHOHAS SURROGAT(BPX.)\n\nIf 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. \n\nIf the TSS rules for all BPX.SRV.user SURROGAT resources restrict access to authorized users identified in the Site Security Plan, this is not a finding.","fixText":"Ensure that BPX. SRV.userid resources are properly protected and access is restricted to appropriate system tasks or systems programming personnel.\n\nSURROGAT 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.\n\nEnsure there is a TSS owner defined for the (BPX.) SURROGAT class resource.\nFor Example:\nTSS ADD(dept) SURROGAT(BPX.)\n\nEnsure 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.\n\nFor Example:\nTSS PERMIT(<websrv>) SURROGAT(BPX.SRV.<webadm>)\nACCESS(READ)","ccis":["CCI-000213","CCI-002233"]},{"vulnId":"V-224078","ruleId":"SV-224078r1137691_rule","severity":"high","ruleTitle":"IBM z/OS UNIX SUPERUSER resources must be protected in accordance with guidelines.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS WHOOWNS UNIXPRIV(*)\n\nIf the TSS resources and/or generic equivalent for SUPERUSER. is not owned enter:\nTSS LIST RDT\n\nIf the TSS resources and/or generic equivalent for SUPERUSER. is not owned or DEFPROT is specified for the resource class, this is a finding.\n\nFrom the ISPF Command Shell enter:\nTSS WHOHAS SURROGAT(SUPERUSER.)\n\nIf 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.","fixText":"Ensure that all SUPERUSER resources for the UNIXPRIV resource class are restricted to appropriate system tasks and/or system programming personnel.\n\nReview the following items for the UNIXPRIV resource class:\n\n-The TSS owner defined for the SUPERUSER resource.\n-There are no TSS rules that allow access to the SUPERUSER resource.\n-There is no TSS rule for CHOWN.UNRESTRICTED defined.\n-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.","ccis":["CCI-000213"]},{"vulnId":"V-224079","ruleId":"SV-224079r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS data sets or HFS objects must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"Refer to the proper BPXPRMxx member in SYS1.PARMLIB \n\nIf 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.\n\nIf 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.","fixText":"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.\n\n Review the UNIX permission bits on the HFS directories and files and ensure that they conform to the specifications below:\n\nDefine 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).\n\nDefine 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.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224080","ruleId":"SV-224080r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS data sets with z/OS UNIX components must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"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.\n\nMVS DATA SETS WITH z/OS UNIX COMPONENTS\nDATA SET NAME/MASK MAINTENANCE TYPE FUNCTION\nSYS1.ABPX* Distribution IBM z/OS UNIX ISPF panels, messages, tables, clists\nSYS1.AFOM* Distribution IBM z/OS UNIX Application Services\nSYS1.BPA.ABPA* Distribution IBM z/OS UNIX Connection Scaling Process Mgr.\nSYS1.CMX.ACMX* Distribution IBM z/OS UNIX Connection Scaling Connection Mgr.\nSYS1.SBPX* Target IBM z/OS UNIX ISPF panels, messages, tables, clists\nSYS1.SFOM* Target IBM z/OS UNIX Application Services\nSYS1.CMX.SCMX* Target IBM z/OS UNIX Connection Scaling Connection Mgr.","fixText":"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.\n\nMVS DATA SETS WITH z/OS UNIX COMPONENTS\nDATA SET NAME/MASK MAINTENANCE TYPE FUNCTION\nSYS1.ABPX* Distribution IBM z/OS UNIX ISPF panels, messages, tables, clists\nSYS1.AFOM* Distribution IBM z/OS UNIX Application Services\nSYS1.BPA.ABPA* Distribution IBM z/OS UNIX Connection Scaling Process Mgr.\nSYS1.CMX.ACMX* Distribution IBM z/OS UNIX Connection Scaling Connection Mgr.\nSYS1.SBPX* Target IBM z/OS UNIX ISPF panels, messages, tables, clists\nSYS1.SFOM* Target IBM z/OS UNIX Application Services\nSYS1.CMX.SCMX* Target IBM z/OS UNIX Connection Scaling Connection Mgr.\n\nThe 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.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224081","ruleId":"SV-224081r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS data sets used as step libraries in /etc/steplib must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Refer to the pathname from the STEPLIBLIST line in BPXPRMxx member of PARMLIB.\nFrom the ISPF Command shell enter:\nISHELL\n\non the command line:\non the path name line enter:\n/etc/ \n\nFrom the resulting display scroll down to the <stepliblist name> from BPXPRMxx parm.\n\nEnter B for browse on that line.\n\nIf ESM data set rules for libraries specified restrict WRITE or greater access to only systems programming personnel, this is not a finding.\n\nIf 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.","fixText":"Configure the WRITE or greater access to libraries residing in the /etc/steplib to be limited to system programmers only.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-224082","ruleId":"SV-224082r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX HFS permission bits and audit bits for each directory must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"From the ISPF Command Shell enter:\nomvs\n\nenter CD / \n\nenter ls -alW\n\nIf 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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\n SYSTEM DIRECTORY SECURITY SETTINGS\nDIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION\n/ [root] 755 faf Root level of all file systems. Holds critical mount points.\n/bin 1755 fff Shell scripts and executables for basic functions\n/dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation.\n Files are created during system IPL and on a per-demand basis.\n/etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes\n/lib 1755 fff System libraries including dynamic link libraries and files for static linking\n/samples 1755 fff Sample configuration and other files\n/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.\n/u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files\n/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.\n/var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX.","fixText":"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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\n SYSTEM DIRECTORY SECURITY SETTINGS\nDIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION\n/ [root] 755 faf Root level of all file systems. Holds critical mount points.\n/bin 1755 fff Shell scripts and executables for basic functions\n/dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation.\n Files are created during system IPL and on a per-demand basis.\n/etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes\n/lib 1755 fff System libraries including dynamic link libraries and files for static linking\n/samples 1755 fff Sample configuration and other files\n/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.\n/u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files\n/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.\n/var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX.\n\nThe 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:\n\nchmod 0755 /\nchaudit w=sf,rx+f /\nchmod 0755 /bin\nchaudit rwx=f /bin","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224083","ruleId":"SV-224083r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX system file security settings must be properly protected or specified.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"From the ISPF Command Shell enter:\nOMVS\nFor each file listed in the table below enter:\nls -alW /<directory name>/<file name>\n\nIf 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.\n\nNOTE: Some of the files listed are not used in every configuration. Absence of any of the files is not considered a finding.\n\n SYSTEM FILE SECURITY SETTINGS\nFILE PERMISSION BITS USER AUDIT BITS FUNCTION\n/bin/sh 1755 faf z/OS UNIX shell\n Note: /bin/sh has the sticky bit on to improve performance.\n/dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention.\n/dev/null 666 fff A null file; data written to it is discarded.\n/etc/auto.master\nany mapname files 740 faf Configuration files for automount facility\n/etc/inetd.conf 740 faf Configuration file for network services\n/etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment\n/etc/log 744 fff Kernel initialization output file\n/etc/profile 755 faf Environment setup script executed for each user\n/etc/rc 744 faf Kernel initialization script for z/OS UNIX environment\n/etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables\n/etc/table name 740 faf List of z/OS userids and group names with corresponding alias names\n/usr/lib/cron/at.allow\n/usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands\n/usr/lib/cron/cron.allow\n/usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command\n\nNOTE: Some of the files listed are not used in every configuration. Absence of any of the files is not considered a finding.\n\nNOTE: The names of the MapName files are site-defined. Refer to the listing in the EAUTOM report.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"Define the UNIX permission bits and user audit bits on the HFS files as listed in the table below.\n\nSYSTEM FILE SECURITY SETTINGS\nFILE PERMISSION BITS USER AUDIT BITS FUNCTION\n/bin/sh 1755 faf z/OS UNIX shell\n Note: /bin/sh has the sticky bit on to improve performance.\n/dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention.\n/dev/null 666 fff A null file; data written to it is discarded.\n/etc/auto.master\nany mapname files 740 faf Configuration files for automount facility\n/etc/inetd.conf 740 faf Configuration file for network services\n/etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment\n/etc/log 744 fff Kernel initialization output file\n/etc/profile 755 faf Environment setup script executed for each user\n/etc/rc 744 faf Kernel initialization script for z/OS UNIX environment\n/etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables\n/etc/table name 740 faf List of z/OS userids and group names with corresponding alias names\n/usr/lib/cron/at.allow\n/usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands\n/usr/lib/cron/cron.allow\n/usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command\n\nThere 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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nThe 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:\n\nchmod 1755 /bin/sh\nchaudit w=sf,rx+f /bin/sh\nchmod 0740 /dev/console\nchaudit rwx=f /dev/console","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224084","ruleId":"SV-224084r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS HFS directory(s) with OTHER write permission bit set must be properly defined.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"On the OMVS Command line enter the following command string:\nfind / -type d -perm -0002 ! -perm -1000 -exec ls -aldWE {} \\;\n\nIf there are no directories that have the other write permission bit set on without the sticky bit set on, there is no finding.\n\nNOTE: 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\".\n\nIf 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.\n\nNOTE: 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\".\n\nIf 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.\n\nNOTE: 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\".","fixText":"Configure directory permissions as follows\nThere are no directories that have the other write permission bit set on without the sticky bit set on.\n\nNOTE: 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\".\n\nAll directories that have the other write permission bit set on do not contain any files with the setuid bit set on.\n\nNOTE: 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\".\n\nAll directories that have the other write permission bit set on do not contain any files with the setgid bit set on.\n\nNOTE: 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\".","ccis":["CCI-000213"]},{"vulnId":"V-224085","ruleId":"SV-224085r1137691_rule","severity":"high","ruleTitle":"The CA-TSS HFSSEC resource class must be defined with DEFPROT.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nTSS MODIFY STATUS\nIf the Control Option is HFSSEC(OFF), this is Not Applicable.\n\nEnter:\nTSS LIST RDT\nIf the DEFPROT attribute is specified for the HFSSEC resource class in the RDT, this is not a finding.","fixText":"Ensure that the HFSSEC resource class has the attribute DEFPROT.\n\nFor Example:\n\nTSS REPLACE(RDT) RESCLASS(HFSSEC) ATTR(DEFPROT)","ccis":["CCI-000213"]},{"vulnId":"V-224086","ruleId":"SV-224086r991589_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX OMVS parameters in PARMLIB must be properly specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Refer to the IEASYS00 member of SYS1.PARMLIB.\nIf the parameter is specified as OMVS=xx or OMVS=(xx,xx,...) in the IEASYSxx member, this is not a finding.\n\nIf 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.","fixText":"Configure the settings in PARMLIB and /etc for z/OS UNIX security parameters with values that conform to the specifications below:\n\nThe parameter is specified as OMVS=xx or OMVS=(xx,xx,...) in the IEASYSxx member.\n\nNote: 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.","ccis":["CCI-000366"]},{"vulnId":"V-224087","ruleId":"SV-224087r991589_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX BPXPRMxx security parameters in PARMLIB must be properly specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"Refer to the BPXPRM00 member of SYS1.PARMLIB.\nIf the required parameter keywords and values are defined as detailed below, this is not a finding.\n\nParameter Keyword Value\nSUPERUSER BPXROOT\nTTYGROUP TTY\nSTEPLIBLIST /etc/steplib\nUSERIDALIASTABLE Will not be specified.\nROOT SETUID will be specified\nMOUNT NOSETUID\nSETUID (for Vendor-provided files)SECURITY\nSTARTUP_PROC OMVS","fixText":"Define the settings in PARMLIB member BPXPRMxx for z/OS UNIX security parameters values to conform to the specifications below:\nParameter Keyword Value\nSUPERUSER BPXROOT\nTTYGROUP TTY\nSTEPLIBLIST /etc/steplib\nUSERIDALIASTABLE Will not be specified.\nROOT SETUID will be specified\nMOUNT NOSETUIDSETUID (for Vendor-provided files)SECURITY\nSTARTUP_PROC OMVS","ccis":["CCI-000366"]},{"vulnId":"V-224088","ruleId":"SV-224088r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX security parameters in etc/profile must be properly specified.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"From the ISPF Command Shell enter:\nISHELL\n/etc/profile\nIf the final or only instance of the UMASK command in /etc/profile is specified as \"umask 077\", this is not a finding.\n\nIf the LOGNAME variable is marked read-only (i.e., \"readonly LOGNAME\") in /etc/profile, this is not a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-224089","ruleId":"SV-224089r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX security parameters in /etc/rc must be properly specified.","description":"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"From the ISPF Command Shell enter:\nISHELL\n/etc/rc\n\nIf 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.\n\nNOTE: 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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nIf 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.\n\nNOTE: The use of CHAUDIT commands in /etc/rc may not be necessary. If none are found, there is not a finding.\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nIf 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.\n\nNOTE: 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.\n\n SYSTEM DIRECTORY SECURITY SETTINGS\nDIRECTORY PERMISSION BITS USER AUDIT BITS FUNCTION\n/ [root] 755 faf Root level of all file systems. Holds critical mount points.\n/bin 1755 fff Shell scripts and executables for basic functions\n/dev 1755 fff Character-special files used when logging into the OMVS shell and during C language program compilation.\n Files are created during system IPL and on a per-demand basis.\n/etc 1755 faf Configuration programs and files (usually with locally customized data) used by z/OS UNIX and other product initialization processes\n/lib 1755 fff System libraries including dynamic link libraries and files for static linking\n/samples 1755 fff Sample configuration and other files\n/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.\n/u 1755 fff Mount point for user home directories and optionally for third-party software and other local site files\n/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.\n/var 1775 fff Dynamic data used internally by products and by elements and features of z/OS UNIX.\n\n SYSTEM FILE SECURITY SETTINGS\nFILE PERMISSION BITS USER AUDIT BITS FUNCTION\n/bin/sh 1755 faf z/OS UNIX shell\n Note: /bin/sh has the sticky bit on to improve performance.\n/dev/console 740 fff The system console file receives messages that may require System Administrator (SA) attention.\n/dev/null 666 fff A null file; data written to it is discarded.\n/etc/auto.master and\nany mapname files 740 faf Configuration files for automount facility\n/etc/inetd.conf 740 faf Configuration file for network services\n/etc/init.options 740 faf Kernel initialization options file for z/OS UNIX environment\n/etc/log 744 fff Kernel initialization output file\n/etc/profile 755 faf Environment setup script executed for each user\n/etc/rc 744 faf Kernel initialization script for z/OS UNIX environment\n/etc/steplib 740 faf List of MVS data sets valid for set user ID and set group ID executables\n/etc/table name 740 faf List of z/OS userids and group names with corresponding alias names\n/usr/lib/cron/at.allow\n/usr/lib/cron/at.deny 700 faf Configuration files for the at and batch commands\n/usr/lib/cron/cron.allow\n/usr/lib/cron/cron.deny 700 faf Configuration files for the crontab command","fixText":"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:\n\nVerify 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. \n\nImmediately 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.","ccis":["CCI-000213"]},{"vulnId":"V-224090","ruleId":"SV-224090r991589_rule","severity":"medium","ruleTitle":"IBM z/OS Default profiles must not be defined in TSS OMVS UNIX security parameters for classified systems.","description":"Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.","checkContent":"If the system in not classified this is not applicable.\n\nFrom a command line issue the following command:\nTSS MODIFY STATUS\nNote: One must have appropriate access to perform this command (have the site security officer to issue command).\n\nIf system is classified and UNIQUSER is off i.e., (UNIQUSER(OFF) this is not a finding.","fixText":"Ensure that Use of the OMVS default UIDs will not be allowed on any classified system.\n\nSet Control Option UNIQUSER off.","ccis":["CCI-000366"]},{"vulnId":"V-224091","ruleId":"SV-224091r1195292_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX security parameters for restricted network service(s) in /etc/inetd.conf must be properly specified.","description":"In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"From the UNIX System Services ISPF Shell, enter:\n/etc/inetd.conf\n\nIf any Restricted Network Services that are listed below are specified or not commented out, this is a finding.\n\nRESTRICTED NETWORK SERVICES/PORTS\nService Port\nChargen 19\nDaytime 13\nDiscard 9\nEcho 7\nExec 512\nfinger 79\nshell 514\ntime 37\nlogin 513\nsmtp 25\ntimed 525\nnameserver 42\nsystat 11\nuucp 540\nnetstat 15\ntalk 517\nqotd 17","fixText":"Review the settings in the /etc/inetd.conf file to determine if every entry in the file represents a service that is in use. Services that are not in use must be disabled to reduce potential security exposures.\n\nThe following services must be disabled in /etc/inetd.conf unless justified and documented with the information system security officer (ISSO):\n\nRESTRICTED NETWORK SERVICES\n\nService Port\nChargen 19\nDaytime 13\nDiscard 9\nEcho 7\nExec 512\nfinger 79\nshell 514\ntime 37\nlogin 513\nsmtp 25\ntimed 525\nnameserver 42\nsystat 11\nuucp 540\nnetstat 15\ntalk 517\nqotd 17\n\n\n/etc/inetd.conf\n\nThe /etc/inetd.conf file is used by the INETD daemon. It specifies how INETD handles 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.","ccis":["CCI-000382"]},{"vulnId":"V-224092","ruleId":"SV-224092r958482_rule","severity":"medium","ruleTitle":"IBM z/OS attributes of z/OS UNIX user accounts must have a unique GID in the range of 1-99.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"A site can choose to have both an OMVSGRP group and an STCOMVS group or combine the groups under one of these names.\n\nIf OMVSGRP and/or STCOMVS groups are defined and have a unique GID in the range of 1-99, this is not a finding.","fixText":"Define the OMVSGRP group and/or the STCOMVS group to the security database with a unique GID in the range of 1-99.\n\nOMVSGRP 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.","ccis":["CCI-000764"]},{"vulnId":"V-224093","ruleId":"SV-224093r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS user account for the UNIX kernel (OMVS) must be properly defined to the security database.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"If OMVS userid is defined to the ESM as follows, this is not a finding.\n\n-No access to interactive on-line facilities (e.g., TSO, CICS, etc.)\n-Default group specified as OMVSGRP or STCOMVS\n-UID(0)\n-HOME directory specified as \"/\"\n-Shell program specified as \"/bin/sh\"","fixText":"Define OMVS userid to the ESM as specified below:\n\n-No access to interactive on-line facilities (e.g., TSO, CICS, etc.)\n-Default group specified as OMVSGRP or STCOMVS\n-UID(0)\n-HOME directory specified as \"/\"\n-Shell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-224094","ruleId":"SV-224094r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS user account for the z/OS UNIX SUPERUSER userid must be properly defined.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"Refer to system PARMLIB member BPXPRMxx (xx is determined by OMVS entry in IEASYS00.) \n\nDetermine the user ID identified by the SUPERUSER parameter. (BPXROOT is the default).\n\nFrom a command input screen enter:\nLISTUSER (superuser userid) TSO CICS OMVS\n\nIf the SUPERUSER userid is defined as follows, this is not a finding:\n\n- No access to interactive on-line facilities (e.g., TSO, CICS, etc.)\n- Default group specified as OMVSGRP or STCOMVS\n- UID(0)\n- HOME directory specified as \"/\"\n- Shell program specified as \"/bin/sh\"","fixText":"Define the user ID identified in the BPXPRM00 SUPERUSER parameter as specified below:\n\n- No access to interactive on-line facilities (e.g., TSO, CICS, etc.)\n- Default group specified as OMVSGRP or STCOMVS\n- UID(0)\n- HOME directory specified as \"/\"\n- Shell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-224095","ruleId":"SV-224095r958482_rule","severity":"medium","ruleTitle":"The IBM z/OS user account for the UNIX (RMFGAT) must be properly defined.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"RMFGAT is the userid for the Resource Measurement Facility (RMF) Monitor III Gatherer. If RMFGAT is not define this is not applicable.\n\nFrom a command input screen enter:\n\nTSS LIST (RMFGAT) DATA ALL\n\nIf RMFGAT is defined as follows, this is not a finding:\n\n-Default group specified as OMVSGRP or STCOMVS\n-A unique, non-zero UID\n -HOME directory specified as \"/\"\n -Shell program specified as \"/bin/sh\"","fixText":"Define RMFGAT user account is defined as specified below:\n\n-Default group specified as OMVSGRP or STCOMVS\n-A unique, non-zero UID\n-HOME directory specified as \"/\"\n-Shell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-224096","ruleId":"SV-224096r958482_rule","severity":"high","ruleTitle":"IBM z/OS UID(0) must be properly assigned.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) SEGMENT(OMVS)\n\nIf 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.\n\nIf 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.\n\nNOTE: 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.\n\nIf UID(0) is assigned to non-systems or non-maintenance accounts, this is a finding.","fixText":"Ensure that UID(0) is defined/assigned as specified below:\nUID(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.\n\nUID(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.\n\nNOTE: 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.","ccis":["CCI-000764"]},{"vulnId":"V-224097","ruleId":"SV-224097r958482_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX user accounts must be properly defined.","description":"To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"NOTE: This only applies to users of z/OS UNIX (i.e., users with an OMVS profile defined).\n\nFrom the ISPF Command Shell enter:\nTSS LIST(ACIDS) SEGMENT(OMVS)\n\nIf any user account is not defined as follows, this is a finding.\n\n-A unique UID number (except for UID(0) users).\n-A unique HOME directory (UID(0), other system task accounts, and tasks approved by the ISSM are excluded from this rule).\n-Shell program specified as \"/bin/sh\", \"/bin/tcsh\", \"/bin/echo\", or \"/bin/false\".\n\nNOTE: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default; this does not include tasks that are excluded from above).","fixText":"Configure each user account to be defined as specified below:\n\nNOTE: This only applies to users of z/OS UNIX (i.e., users with an OMVS profile defined).\n\n-A unique UID number (except for UID(0) users).\n-A unique HOME directory (UID(0), other system task accounts, and tasks approved by the ISSM are excluded from this rule).\n-Shell program specified as \"/bin/sh\", \"/bin/tcsh\", \"/bin/echo\", or \"/bin/false\".\n\nNOTE: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default; this does not include tasks that are excluded from above).","ccis":["CCI-000764"]},{"vulnId":"V-224098","ruleId":"SV-224098r958482_rule","severity":"medium","ruleTitle":"IBM z/OS attributes of UNIX user accounts used for account modeling must be defined in accordance with security requirements.","description":"To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n\n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and\n\n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.","checkContent":"From the ISPF Command Shell enter:\nTSS LIST(ACIDS) DATA(NAME) SEGMENT(OMVS)\nThis check applies to any user identifier (ACID) used to model OMVS access on the mainframe. This includes OMVSUSR; MODLUSER, and BPX.UNIQUE.USER.\n ENTER \nTSS MODIFY STATUS\n\nIf ANY MODLUSER is specified then UNIQUSER must be specified as \"ON\" in the STATUS.\n\nIf user identifier (ACID) used to model OMVS user account is defined as follows, this is not finding.\n\nA non-writable HOME directory\nShell program specified as \"/bin/echo\", or \"/bin/false\"\n\nNote: The shell program must have one of the specified values. The HOME directory must have a value (i.e., not be allowed to default).","fixText":"Use of the OMVS default UID will not be allowed on any classified system.\n\nDefine 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.\"","ccis":["CCI-000764"]},{"vulnId":"V-224099","ruleId":"SV-224099r958392_rule","severity":"medium","ruleTitle":"The IBM z/OS UNIX Telnet server etc/banner file must have the Standard Mandatory DoD Notice and Consent Banner.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:\n\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"\n\nSatisfies: SRG-OS-000024-GPOS-00007, SRG-OS-000023-GPOS-00006","checkContent":"From UNIX System Services ISPF Shell, enter path \"/etc/otelnet/banner/\".\nIf this file does not contain the banner below, check the UNIX System Services ISPF Shell path /etc/banner.\nIf neither file contains the banner below, this is a finding.\nIf the banner below is contained in either, this is not a finding.\n\nThis 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:\n\nSTANDARD MANDATORY DOD NOTICE AND CONSENT BANNER\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","fixText":"Configure the /etc/otelnet/banner file and ensure the text specifies a logon banner in accordance with DISA requirements.\n\nAlternately, the /etc/banner file may be used in accordance with DISA requirements.","ccis":["CCI-000048","CCI-000050"]},{"vulnId":"V-224100","ruleId":"SV-224100r1137691_rule","severity":"medium","ruleTitle":"The IBM z/OS startup user account for the z/OS UNIX Telnet server must be properly defined.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF Command Shell enter:\nomvs\ncd /etc\ncat inetd.conf\n\nIf the \"otelnetd\" command specifies any user other than \"OMVS\" or \"OMVSKERN\", this is a finding.","fixText":"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.","ccis":["CCI-000213"]},{"vulnId":"V-224101","ruleId":"SV-224101r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS HFS objects for the z/OS UNIX Telnet server must be properly protected.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"From the ISPF Command Shell enter:\nomvs\n\nAt the input line enter:\ncd /usr\nenter\nls -alW\n\nIf the following File permission and user Audit Bits are true, this is not a finding.\n\n/usr/sbin/otelnetd 1740 fff\n\ncd /etc\nls -alW\nIf the following file permission and user Audit Bits are true this is not a finding.\n/etc/banner 0744 faf\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing","fixText":"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:\n\nz/OS UNIX TELNET Server HFS Object Security Settings\nFile Permission Bits User Audit Bits\n/usr/sbin/otelnetd 1740 fff\n/etc/banner 0744 faf\n\nNOTE: 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.\n\nThe following represents a hierarchy for permission bits from least restrictive to most restrictive:\n\n7 rwx (least restrictive)\n6 rw-\n3 -wx\n2 -w-\n5 r-x\n4 r--\n1 --x\n0 --- (most restrictive)\n\nThe possible audit bits settings are as follows:\n\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\nThe following commands can be used (from a user account with an effective UID(0)) to update the permission bits and audit bits:\n\nchmod 1740 /usr/lpp/tcpip/sbin/otelnetd\nchaudit rwx=f /usr/lpp/tcpip/sbin/otelnetd\nchmod 0744 /etc/banner\nchaudit w=sf,rx+f /etc/banner","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224102","ruleId":"SV-224102r958586_rule","severity":"medium","ruleTitle":"The IBM z/OS UNIX Telnet server Startup parameters must be properly specified.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.","checkContent":"From the ISPF Command Shell enter:\nISHELL\n\nEnter /etc/ for a pathname - you may need to issue a CD /etc/\nselect FILE NAME inetd.conf\n\nIf Option -D login is included on the otelnetd command, this is not a finding.\n\nIf Option -c 900 is included on the otelnetd command, this is not a finding.\n\nNOTE: \"900\" indicates a session timeout value of \"15\" minutes and is currently the maximum value allowed.","fixText":"Configure the startup parameters in the inetd.conf file for otelnetd to conform to the specifications below.\n\nThe otelnetd startup command includes the options -D login and -c 900, where:\n\n-D login indicates that messages should be written to the syslogd facility for login and logout activity.\n\n-c 900 indicates that the Telnet session should be terminated after \"15\" minutes of inactivity.\n\nNOTE: \"900\" is the maximum value; any value between \"1\" and \"900\" is acceptable.","ccis":["CCI-000366"]},{"vulnId":"V-224103","ruleId":"SV-224103r958586_rule","severity":"medium","ruleTitle":"The IBM z/OS UNIX Telnet server warning banner must be properly specified.","description":"Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.","checkContent":"From the ISPF Command Shell enter:\nOMVS\ncat inetd.conf\n\nIf the otelnet startup command includes option \"-h\" this is a finding.","fixText":"The otelnetd startup command should not include the option \"-h\", where:\n\n-h indicates that the logon banner should not be displayed.","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-224104","ruleId":"SV-224104r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS System data sets used to support the VTAM network must be properly secured.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"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.\n\nIf the ESM data set rules for all VTAM system data sets restrict access to only network systems programming staff, this is not a finding. \n\nIf TSS data set rules for all VTAM system data sets all READ access to auditors only, this is not a finding.\n\nThese data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements.","fixText":"Configure TSS data set rules for all VTAM system data sets to restrict access to only network systems programming staff.\n\nAuditors may have READ access as documented by and approved by the ISSM.\n\nThese data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements. \n\nThe following sample TSS commands show proper permissions for VTAM data sets (replace \"profile\" with the profile name of the network systems programming staff authorities): \n\nTSS PERMIT(profile) DSN(SYS1.VTAM.) ACC(ALL) \nTSS PERMIT(profile) DSN('SYS1.VTAMLIB.) ACC(ALL) \nTSS PERMIT(profile) DSN(SYS1.VTAM.SISTCLIB.) ACC(ALL) \nTSS PERMIT(profile) DSN(SYS3.VTAM.) ACC(ALL) \nTSS PERMIT(profile) DSN(SYS3.VTAMLIB.) ACC(ALL)","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-224105","ruleId":"SV-224105r991560_rule","severity":"medium","ruleTitle":"IBM z/OS VTAM USSTAB definitions must not be used for unsecured terminals.","description":"If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Ask the system administrator to supply the following information:\n\n- Documentation regarding terminal naming standards.\n- Documentation of all procedures controlling terminal logons to the system.\n- A complete list of all USS commands used by terminal users to log on to the system.\n- Members and data set names containing USSTAB and LOGAPPL definitions of all terminals that can log on to the system (e.g., SYS1.VTAMLST).\n- Members and data set names containing logon mode parameters.\n\nIf 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.\n\nIf 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.","fixText":"Configure USSTAB definitions to be only used for secure terminals.\n\nOnly 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. \n\nUSSTAB 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.","ccis":["CCI-001499"]},{"vulnId":"V-245537","ruleId":"SV-245537r991589_rule","severity":"medium","ruleTitle":"The IBM z/OS TCPIP.DATA configuration statement must contain the DOMAINORIGIN or DOMAIN specified for each TCP/IP defined.","description":"If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data origin authentication verification must be performed to thwart these types of attacks.\n\nEach client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations.\n\nThis is not applicable if DNSSEC is not implemented on the local network.","checkContent":"Refer to the Data configuration file specified on the SYSTCPD DD statement in the TCPIP started task JCL.\n\nNote:\nIf 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.\n\nIf GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA.\n\nIf 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.","fixText":"Configure the TCPIP.DATA file to include the DOMAINORIGIN/DOMAIN (The DOMAIN statement is functionally equivalent to the DOMAINORIGIN Statement).\n\nNote:\nIf 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.\n\nIf GLOBALTCPIPDATA is not specified, the appropriate environment's (Native MVS or z/OS UNIX) search order is used to locate TCPIP.DATA.","ccis":["CCI-000366"]},{"vulnId":"V-251108","ruleId":"SV-251108r1028298_rule","severity":"high","ruleTitle":"The IBM z/OS systems requiring data at rest protection must properly employ IBM DS8880 or equivalent hardware solutions for full disk encryption.","description":"This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. Operating systems handling data requiring \"data at rest\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\n\nSelection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).\n\nUse of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.\n\n\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000405-GPOS-00184, SRG-OS-000404-GPOS-00183, SRG-OS-000396-GPOS-00176","checkContent":"Determine if IBM's DS880 Disks or equivalent hardware solutions are in use.\n\nIf IBMs DS880 Disks or equivalent hardware solutions  are not in use for systems that require \"data at rest\", this is a finding.","fixText":"Employ IBM's DS8880 hardware or equivalent hardware solutions to ensure full disk encryption.","ccis":["CCI-002476","CCI-001199","CCI-002420","CCI-002445","CCI-002446"]},{"vulnId":"V-252554","ruleId":"SV-252554r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS TCP/IP AT-TLS policy must be properly configured in Policy Agent.","description":"If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.\n\nThis requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.\n\nNonlocal maintenance and diagnostic activities are conducted by individuals communicating through an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are carried out by individuals physically present at the information system or information system component and not communicating across a network connection.\n\nThis requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system; for example, the software implementing \"ping,\" \"ls,\" \"ipconfig,\" or the hardware and software implementing the monitoring port of an Ethernet switch.","checkContent":"Use the z/OS UNIX pasearch -t command to query information from the z/OS UNIX Policy Agent. \n\nThe command is issued from the UNIX System Services shell.\n\nExamine the results for AT-TLS initiation and control statements.\n\nIf there are no AT-TLS initiation and controls statements, this is a finding.\n\nVerify the statements specify a FIPS 140-2 compliant value. If none of the following values are present, this is a finding\n\nECDHE_ECDSA_AES_128_CBC_SHA256\nECDHE_ECDSA_AES_256_CBC_SHA384\nECDHE_RSA_AES_128_CBC_SHA256\nECDHE_RSA_AES_256_CBC_SHA384\nTLS_RSA_WITH_3DES_EDE_CBC_SHA\nTLS_RSA_WITH_AES_128_CBC_SHA\nTLS_RSA_WITH_AES_128_CBC_SHA256\nTLS_RSA_WITH_AES_256_CBC_SHA\nTLS_RSA_WITH_AES_256_CBC_SHA256","fixText":"Develop a plan of action to implement the required changes. Ensure the following items are in effect for TCP/IP resources.\n\nDevelop AT-TLS policy. Install in the policy agent.\n\nEnsure the statements specify a FIPS 140-2 compliant value of the following values.\n\nECDHE_ECDSA_AES_128_CBC_SHA256\nECDHE_ECDSA_AES_256_CBC_SHA384\nECDHE_RSA_AES_128_CBC_SHA256\nECDHE_RSA_AES_256_CBC_SHA384\nTLS_RSA_WITH_3DES_EDE_CBC_SHA\nTLS_RSA_WITH_AES_128_CBC_SHA\nTLS_RSA_WITH_AES_128_CBC_SHA256\nTLS_RSA_WITH_AES_256_CBC_SHA\nTLS_RSA_WITH_AES_256_CBC_SHA256","ccis":["CCI-000067"]},{"vulnId":"V-255896","ruleId":"SV-255896r991589_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration statements for the FTP Server must be specified in accordance with requirements.","description":"This requirement is intended to cover both traditional interactive logons to information systems and general accesses to information systems that occur in other types of architectural configurations (e.g., service-oriented architectures).","checkContent":"Refer to the Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nIf the UMASK statement is coded with a value of \"077\", this is not a finding.","fixText":"Configure the FTP configuration to include the UMASK statement with a value of \"077\". \n\nIf the FTP Server requires a UMASK value less restrictive than \"077\", requirements should be justified and documented with the ISSO.","ccis":["CCI-000366"]},{"vulnId":"V-255940","ruleId":"SV-255940r991589_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) Configuration parameters must be correctly specified.","description":"IBM Integrated Crypto Service Facility (ICSF) product has the ability to use privileged functions and/or have access to sensitive data. Failure to properly configure parameter values could potentially the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the CSFPRMxx member in the logical PARMLIB concatenation.\n\nIf the configuration parameters are specified as follows this is not a finding. \n\nREASONCODES(ICSF) \nCOMPAT(NO) \nSSM(NO) \nSSM can be dynamically set by defining the CSF.SSM.ENABLE SAF profile within the XFACILIT resource\nClass. If this profile is not limited to authorized personnel this is a finding.\nCHECKAUTH(YES) \nFIPSMODE(YES,FAIL(YES))\nAUDITKEYLIFECKDS (TOKEN(YES),LABEL(YES)).\nAUDITKEYLIFEPKDS (TOKEN(YES),LABEL(YES)).\nAUDITKEYLIFETKDS (TOKENOBJ(YES),SESSIONOBJ(YES)).\nAUDITKEYUSGCKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)).\nAUDITKEYUSGPKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)).\nAUDITPKCS11USG (TOKENOBJ(YES),SESSIONOBJ(YES),NOKEY(YES),INTERVAL(n)).\n\nDEFAULTWRAP -This parameter can be determined by the site. ENHANCED wrapping specifies the new X9.24 compliant CBC wrapping is used.  \nIf DEFAULTWRAP is not specified, the default wrapping\nmethod 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.","fixText":"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:\n\nREASONCODES(ICSF) \nCOMPAT(NO) \nSSM(NO) \nSSM can be dynamically set by defining the CSF.SSM.ENABLE SAF profile within the XFACILIT resource\nClass. This profile must limited to authorized personnel.\n\nCHECKAUTH(YES) \nFIPSMODE(YES,FAIL(YES))\nAUDITKEYLIFECKDS (TOKEN(YES),LABEL(YES)).\nAUDITKEYLIFEPKDS (TOKEN(YES),LABEL(YES)).\nAUDITKEYLIFETKDS (TOKENOBJ(YES),SESSIONOBJ(YES)).\nAUDITKEYUSGCKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)).\nAUDITKEYUSGPKDS (TOKEN(YES),LABEL(YES),INTERVAL(n)).\nAUDITPKCS11USG (TOKENOBJ(YES),SESSIONOBJ(YES),NOKEY(YES),INTERVAL(n)).\n\n\nDEFAULTWRAP -This parameter can be determined by the site. ENHANCED wrapping specifies the new X9.24 compliant CBC wrapping is used.  \nIf DEFAULTWRAP is not specified, the default wrapping\nmethod 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. \nNote: Other options may be site defined.","ccis":["CCI-000366"]},{"vulnId":"V-255941","ruleId":"SV-255941r1137691_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) install data sets are not properly protected.","description":"IBM Integrated Crypto Service Facility (ICSF) product has the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Verify that access to the IBM IntegrTated Crypto Service Facility (ICSF) install data sets are properly restricted.\n\nExecute a data set list of access to the IBM Integrated Crypto Service Facility (ICSF) install data sets\n \nIf 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.\n\nIf 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.","fixText":"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.\n\nThe 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.\n\nData sets to be protected will be: \nSYS1.CSF\n\nThe following commands are provided as a sample for implementing data set controls:\n\nTSS PERMIT(syspaudt) DSN(SYS1.CSF.) ACCESS(R)\nTSS PERMIT(tstcaudt) DSN(SYS1.CSF.) ACCESS(R)\nTSS PERMIT(icsfusrs) DSN(SYS1.CSF.) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS1.CSF.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(tstcaudt) DSN(SYS1.CSF.) ACCESS(ALL) ACTION(AUDIT)","ccis":["CCI-000213","CCI-002264"]},{"vulnId":"V-255942","ruleId":"SV-255942r958482_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) Started Task name is not properly identified / defined to the system ACP.","description":"IBM Integrated Crypto Service Facility (ICSF) requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.","checkContent":"Review the IBM Integrated Crypto Service Facility (ICSF) STC/Batch ACID(s) for the following:\n\n___\tIs defined with Facility of STC and/or BATCH.\n\n___\tIs sourced to the INTRDR.\n\nc)\tIf all of the above are true this is not a finding\n\nd)\tIf any of the above is untrue this is a finding.","fixText":"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.\n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost 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).\n\nExample:\n\nTSS CRE(CSFSTART) DEPT(Dept) NAME('ICSF STC') -\n\tFAC(STC) PASSWORD(password,0) -\n\tSOURCE(INTRDR)","ccis":["CCI-000764"]},{"vulnId":"V-255943","ruleId":"SV-255943r958482_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.","description":"Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources.  Improper control of product resources could potentially compromise the operating system, ACP, and customer data.","checkContent":"from the ISPF Command Shell enter\n\nTSS LIST(STC)\n\n\nIf the IBM Integrated Crypto Service Facility (ICSF) started task(s) is (are) not defined in the TSS STC record this is a finding.","fixText":"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. \n\nA unique ACID must be assigned for the IBM Integrated Crypto Service Facility (ICSF) started task(s) thru a corresponding STC table entry.\n\nThe following sample set of commands is shown here as a guideline:\n\nTSS ADD(STC) PROCNAME(CSFSTART) ACID(CSFSTART)","ccis":["CCI-000764"]},{"vulnId":"V-255944","ruleId":"SV-255944r991560_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) STC data sets must be properly protected.","description":"IBM Integrated Crypto Service Facility (ICSF) STC data sets have the ability to use privileged functions and/or have access to sensitive data.  Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"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.\n\nIf the TSS data set access authorizations do not restrict READ access to auditors, this is a finding.\n\nIf the TSS data set access authorizations do not restrict WRITE and/or greater access to systems programming personnel, this is a finding.\n\nIf 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.","fixText":"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.\n\nThe 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.\n\n(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.)\n\nThe 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.\n\nNote: Currently on most CSD systems, the CKDSN specifies SYS3.CSF.CKDS and PKDSN specifies SYS3.CSF.PKDS.\n\nThe following commands are provided as a sample for implementing data set controls:\n\nTSS PERMIT(audtaudt) DSN(SYS3.CDS.) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS3.CDS.) ACCESS(R)\nTSS PERMIT(tstcaudt) DSN(SYS3.CDS.) ACCESS(R)\nTSS PERMIT(icsfstc) DSN(SYS3.CDS.) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS3.CDS.) ACCESS(ALL)\nTSS PERMIT(tstcaudt) DSN(SYS3.CDS.) ACCESS(ALL)\nTSS PERMIT(icsfstc) DSN(SYS3.CDS.) ACCESS(ALL)","ccis":["CCI-001499"]},{"vulnId":"V-272878","ruleId":"SV-272878r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFSMS control data sets must reside on separate storage volumes.","description":"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.","checkContent":"Review the logical parmlib data sets, for example SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets:\nActive Control Data Set (ACDS)\nCommunications Data Set (COMMDS)\n\nIf the COMMDS and ACDS SMS data sets identified above reside on different volumes, this is not a finding.\n\nIf the COMMDS and ACDS SMS data sets identified above are collocated on the same volume, this is a finding.","fixText":"Allocate the primary and backup SMS Control data sets on separate volumes.\n\nSource Control Data Set (SCDS) contains an SMS configuration, which defines a storage management policy.\n\nActive Control Data Set (ACDS) contains a copy of the most recently activated configuration. All systems in an SMS complex use this configuration to manage storage.\n\nCommunications Data Set (COMMDS) contains the name of the ACDS containing the currently active storage management policy, the current utilization statistics for each system managed volume, and other system information.\n\nThe ACDS data set will reside on a different volume than the COMMDS data set.\n\nAllocate backup copies of the ADCS and COMMDS data sets on a different shared volume from the primary ACDS and COMMDS data sets.","ccis":["CCI-000366","CCI-000549"]},{"vulnId":"V-275959","ruleId":"SV-275959r1137691_rule","severity":"medium","ruleTitle":"zOSMF resource class(es) must be properly owned in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"OSMF resource class(es) must be properly owned in accordance with security requirements.\n\nFrom the ISPF command shell, enter: \n\nTSS WHOOWNS <CLASS> \n\nIf each of the following classes are properly owned, this is not a finding.\nEJBROLE\nLOGSTRM\nSERVER\nTSOPROC\nZMFAPLA\nZMFCLOUD","fixText":"Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option as specified in the example below:\n\nThe TSS Command WHOOWNS should identify any missing resource classes. \nThe ADDTO (RDT) can be used to define resources to the Resource Descriptor Table.\nEx. TSS ADDTO(RDT) RESCLAS(EJBROLE) ACLS6(READ)\nUse the ADDTO command function to assign appropriate resource ownership.","ccis":["CCI-000213"]},{"vulnId":"V-275960","ruleId":"SV-275960r1169908_rule","severity":"medium","ruleTitle":"zOSMF resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF command shell, enter WHOOWNS as follows:\nEJBROLE *    \nLOGSTRM *\nSERVER *\nTSOPROC *\nZMFAPLA *\nZMFCLOUD *\n\nFor each resource defined, enter:\nTSS  WHOHAS <resource>(resource item> \n\nIf TSS access rules for each resource are restricted to appropriate users as found in Appendix A in the zOSMF Configuration Guide: Security Structures for z/OSMF Requirements for the Security Configuration tables, this is not a finding.","fixText":"Configure ICSF access for resources in accordance with site security plan.","ccis":["CCI-000213"]},{"vulnId":"V-275961","ruleId":"SV-275961r1169902_rule","severity":"medium","ruleTitle":"ICSF resource class(es) must be properly owned in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF command shell, enter:\n\nTSS WHOOWNS <CLASS> \n\nIf each of the following classes are properly owned, this is not a finding:\nCRYPTOZ \nCSFKEYS \nCSFSERV \nGCSFKEYS \nXCSFKEY","fixText":"Evaluate the impact associated with implementation of the control option. Develop a plan of action to implement the control option as specified in the example below:\n\nThe TSS Command WHOOWNS should identify any missing resource classes. \nThe ADDTO (RDT) can be used to define resources to the Resource Descriptor Table. \n\nEx. TSS ADDTO(RDT) RESCLAS(CRYPTOZ) ACLS6(READ)\nUse the ADDTO command function to assign CRYPTOZ appropriate resource ownership.","ccis":["CCI-000213"]},{"vulnId":"V-275962","ruleId":"SV-275962r1169904_rule","severity":"medium","ruleTitle":"ICSF resources must be protected in accordance with security requirements.","description":"To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.\n\nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"From the ISPF command shell, enter WHOOWNS for the following resources:\nCRYPTOZ  \nCSFKEYS  \nCSFSERV  \nGCSFKEYS    \nXCSFKEY  \n\nConsult with the ICSF administrator, security administrator, and site security plan for appropriate access members.\nFor each resource defined, enter:\nTSS <resource name> (*)\n\nIf TSS access rules for each resource are restricted to appropriate users, this is not a finding.","fixText":"Configure ICSF access for resources in accordance with site security plan.","ccis":["CCI-000213"]}]}