{"stig":{"title":"IBM z/OS ACF2 Security Technical Implementation Guide","version":"9","release":"8"},"checks":[{"vulnId":"V-223419","ruleId":"SV-223419r958482_rule","severity":"medium","ruleTitle":"IBM z/OS Certificate Name Filtering must be 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, collect documentation describing each active filter rule and written approval from the ISSM to use the rule.\n\nIssue the following ACF2 commands to list the certificate name filters defined to ACF2:\nSET CONTROL(GSO)\nSHOW CERTMAP\n\nIf no CERTMAP FILTERING TABLES are present, this 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 CERTMAP FILTERING TABLES are present and certificate name filters 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":"Define any Certificate Name Filtering rules when required with documentation and approval by the ISSM.","ccis":["CCI-000764"]},{"vulnId":"V-223420","ruleId":"SV-223420r958448_rule","severity":"medium","ruleTitle":"IBM z/OS must not use Expired Digital Certificates.","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-ACF2 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\nIf the digital certificate information indicates that the issuer's distinguished name leads to a DoD PKI Root Certificate Authority or External Certification Authority (ECA), this is not a finding. \n\nReference the DoD Cyber Exchange website for complete information as to which certificates are acceptable (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":"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-223421","ruleId":"SV-223421r1001089_rule","severity":"medium","ruleTitle":"All IBM z/OS digital certificates in use must have a valid path to a trusted Certification authority.","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.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182","checkContent":"Execute the CA-ACF2 SAFCRRPT using the following as SYSIN input:\nRECORDID(-) DETAIL FIELDS(ISSUER SUBJECT ACTIVE EXPIRE TRUST)\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 CA.","ccis":["CCI-000185","CCI-002470","CCI-004909"]},{"vulnId":"V-223422","ruleId":"SV-223422r958362_rule","severity":"high","ruleTitle":"CA-ACF2 OPTS GSO record must be set to ABORT mode.","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.\n\nSatisfies: SRG-OS-000001-GPOS-00001, SRG-OS-000480-GPOS-00229","checkContent":"From the ISPF Command Shell enter \"ACF\" to enter ACF2 Command shell.\n\nEnter \"SHOW STATE\".\n\nIf the \"GSO OPTS\" record show a \"MODE= ABORT\", this is not a finding.","fixText":"Configure the GSO Option for \"MODE\" to equal \"ABORT\".","ccis":["CCI-000015"]},{"vulnId":"V-223423","ruleId":"SV-223423r1137691_rule","severity":"medium","ruleTitle":"The number of ACF2 users granted the special privilege PPGM must be justified.","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:\nSET LID \nSET VERBOSE \nLIST IF(PPGM)\n\nIf the number of users granted the special privilege PPGM is strictly controlled and limited to systems programmer and operations personnel, this is not a finding.","fixText":"Ensure that access to the special privilege PPGM is kept to a minimum and limited to systems programmer and operations personnel.","ccis":["CCI-000213"]},{"vulnId":"V-223424","ruleId":"SV-223424r1137691_rule","severity":"low","ruleTitle":"The number of ACF2 users granted the special privilege OPERATOR must be kept to a strictly controlled minimum.","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:\nACF\nSET LID \nSET VERBOSE \nLIST IF(OPERATOR)\n\nIf the number of users granted the special privilege OPERATOR is strictly controlled and limited to systems programmer and operations personnel, this not a finding.\n\nIf the number of users granted the special privilege OPERATOR is not strictly controlled and limited to systems programmer and operations personnel, this is a finding.","fixText":"Ensure that access to the special privilege \"OPERATOR\" is kept to a minimum and limited to systems programmer, security manager and operations personnel.","ccis":["CCI-000213"]},{"vulnId":"V-223425","ruleId":"SV-223425r1137691_rule","severity":"low","ruleTitle":"The number of ACF2 users granted the special privilege CONSOLE must be justified.","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:\nACF \nSET LID \nSET VERBOSE \nLIST IF(ACCTPRIV OR CONSOLE OR OPERATOR OR MOUNT) \n\nIf the number of users granted the special privilege CONSOLE is strictly controlled (issued on an as-needed basis), this is not a finding.\n\nIf the number of users granted the special privilege CONSOLE is not strictly controlled (issued on an as-needed basis), this is a finding.","fixText":"Define the CONSOLE attribute with minimum access and it is controlled and documented.\n\nDocumentation providing justification for access is maintained and filed with the ISSO and that unjustified access is removed.","ccis":["CCI-000213"]},{"vulnId":"V-223426","ruleId":"SV-223426r1137691_rule","severity":"medium","ruleTitle":"The number of ACF2 users granted the special privilege ALLCMDS must be justified.","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:\nACF\nSET LID \nSET VERBOSE \nLIST IF(ALLCMDS) \n\nIf the number of users granted the special privilege ALLCMDS is strictly controlled and access is granted on an as needed basis, this is not a finding.\n\nIf the number of users granted the special privilege ALLCMDS is not strictly controlled and access is granted on an as needed basis, this is a finding.","fixText":"Ensure that access to the special privilege ALLCMDS is kept to a minimum and is controlled and documented.\n\nDocumentation providing justification for access is maintained and filed with the ISSO. \n\nRemove any unjustified access.","ccis":["CCI-000213"]},{"vulnId":"V-223427","ruleId":"SV-223427r1137691_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 input line enter:\nSET RESOURCE(OPR)\nSET VERBOSE\nLIST LIKE(MVS-)\n\nNOTE: If CLASMAP defines OPERCMDS as anything other than the default of TYPE(OPR), replace OPR with the appropriate three letters.\n\nIf the MVS resource is defined to the OPERCMDS class with a default access of PREVENT, and all access logged, i.e., MVS.** is defined with access of PREVENT, this is not finding.\n\nIf Access to z/OS system commands 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) as determined in the Documented site Security Plan, this is not a finding.\n\nNote: Display commands and others as deemed by the site IAW site security plan may be allowed for all users with no logging. The (MVS.SEND) Command will not be a finding if used by all.","fixText":"Configure z/OS Sensitive System Commands to be defined to the OPERCMDS resource class. Only limited number of authorized people are able to issue these commands. All access is logged.\n\nConfigure the MVS resource to be defined to the OPERCMDS class with a default access of PREVENT, all access is logged, and access is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users).\n\nNote: Ensure access to z/OS system commands defined in the MVS commands, RACF access authorities, and resource names, in the IBM z/OS MVS System Commands, is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users).\n\nExample for ACF2:\n$KEY(MVS) TYPE(OPR) \nACTIVATE.- UID(sysprgmr) LOG \nACTIVATE.- UID(*) PREVENT \n\nSET R(OPR)\nCOMPILE 'ACF2.MVA.OPR(MVS)' STORE\n\nF ACF2,REBUILD(OPR)","ccis":["CCI-000213"]},{"vulnId":"V-223428","ruleId":"SV-223428r1137691_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 detailed in the table. \n\nIf the ACF2 resources are defined with a default access of PREVENT, this is not a finding.\n\nIf the ACF2 resource access authorizations restrict access to the appropriate personnel according to the site security plan, this not a finding.\n\nIf the ACF2 resource logging is correctly specified, 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. \n                                  Restricted to data center personnel only.","fixText":"Refer to the Site Security plan for Sensitive Programs/Utilities for lists the resources, access requirements, and logging requirements for Sensitive Utilities.\n\nConfigure ACF2 resources to be defined with a default access of PREVENT.\n\nConfigure ACF2 resource access authorizations to restrict access to the appropriate personnel.\n\nConfigure ACF2 resource logging to be correctly specified.\n\nThe following commands are provided as a sample for implementing resource controls:\n\n$KEY(AHLGTF) TYPE(PGM)\nUID(stcg) LOG\nUID(*) PREVENT\n\nF ACF2,REBUILD(PGM)","ccis":["CCI-000213"]},{"vulnId":"V-223429","ruleId":"SV-223429r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 NJE GSO record value must indicate validation options that apply to jobs submitted through a network job entry subsystem (JES2, JES3, RSCS).","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 ACF input screen enter:\nSET CONTROL(GSO)\nLIST LIKE(NJE-)\n\nIf the GSO NJE record values conform to the following requirements, this is not a finding.\n\nSpecifies ACF2 validation options that apply to jobs submitted through a network job entry subsystem (JES2, JES3, RSCS).\n\n DFTLID() INHERIT NODEMASK(-) ENCRYPT VALIN(YES) NOVALOUT\n\nNOTE: For NJE nodes that are incompatible with the XDES algorithm, discrete NJE records will be created with NOENCRYPT.\nNOTE: Local changes will be documented in writing with supporting documentation.","fixText":"Configure ACF2 validation options that apply to jobs submitted through a network job entry subsystem (JES2, JES3, RSCS) as follows:\n\nDFTLID()\nINHERIT\nNODEMASK(-)\nENCRYPT\nVALIN(YES)\nNOVALOUT\n\nNOTE: For NJE nodes that are incompatible with the XDES algorithm, discrete NJE records will be created with NOENCRYPT.\n\nNOTE: Local changes will be justified in writing with supporting documentation.","ccis":["CCI-000213"]},{"vulnId":"V-223430","ruleId":"SV-223430r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must protect Memory and privileged program dumps 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.","checkContent":"From a command input screen enter:\n\nSET RESOURCE (FAC) \nSET VERBOSE\nLIST LIKE (IEAABD-)\nNOTE: If CLASMAP defines FACILITY as anything other than the default of TYPE(FAC), replace FAC with the appropriate three letters.\n\nIf the IEAABD. resource and/or generic equivalent is defined with PREVENT access and that access is not available to any user, this is not a finding.\n\nIf the IEAABD.DMPAUTH. resource and/or generic equivalent is defined and access with SERVICE(READ) is limited to authorized users that have a valid job duties requirement for access, this is not a finding.\n\nIf the IEAABD.DMPAUTH. resource and/or generic equivalent is defined and access with the SERVICE(UPDATE) or greater is restricted to only systems personnel and that 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 ACP.\n\n(Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.)\n\nBelow is listed the access requirements for memory and privileged program dump resources. Ensure the guidelines for the resource type, resources, and/or generic equivalent are followed. When protecting the facilities for dumps lists via the FACILITY resource class, ensure that the following items are in effect:\n\nIEAABD.\nIEAABD.DMPAUTH.\nIEAABD.DMPAKEY.\n\nThe ACF2 resources are defined with a default access of PREVENT.\n\nEnsure that no access is given to IEAABD. resource.\n\nExample:\n$KEY(IEAABD) TYPE(FAC)\n- UID(*) PREVENT\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$KEY(IEAABD) TYPE(FAC)\nDMPAUTH.- UID(sysprgmr) SERVICE(UPDATE) LOG\nDMPAUTH.- UID(authusers) SERVICE(READ)\nDMPAUTH.- UID(*) PREVENT\n\nIEAABD.DMPAKEY. access will be restricted to system programming personnel and access will be logged.\n\nExample:\n$KEY(IEAABD) TYPE(FAC)\nDMPAKEY.- UID(sysprgmr) LOG\nDMPAKEY.- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223431","ruleId":"SV-223431r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 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":"NOTE: If CLASMAP defines TSOAUTH or OPERCMDS as anything other than the default of TYPE(TSO) or TYPE(OPR), replace TSO or OPR below with the appropriate three letters.\n\nIf the CONSOLE resource is not defined to the TSOAUTH resource class, this is not a finding.\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, configure the following for users granted the CONSOLE resource in the TSOAUTH resource class or users assigned the CONSOLE attribute:\n\n Logonids are restricted to the INFO level on the AUTH field specified in the OPERPARM segment of the user profile record.\n Logonids are restricted to READ access to the MVS.MCSOPER.userid resource defined in the OPERCMDS resource class (i.e., resource rules for TYPE(OPR)).\n\nIf all of the above are true, this is not a finding.\n\nIf any of the above are untrue, this is a finding.","fixText":"Configuration should ensure that all users that have access to the CONSOLE resource in the TSOAUTH resource class are properly defined. \n\nEnsure the CONSOLE resource is not defined to the TSOAUTH resource class.\n\nExample:\n$KEY(CONSOLE) TYPE(TSO)\n- UID(*) PREVENT\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 CONSOLE resource in the TSOAUTH resource class or users assigned the CONSOLE attribute:\n\nLogonids are restricted to the INFO level on the AUTH field specified in the OPERPARM segment of the user profile record.\n\nLogonids are restricted to READ access to the MVS.MCSOPER.userid resource defined in the OPERCMDS resource class (i.e., resource rules for TYPE(OPR)).\n\nExample:\n$KEY(MVS) TYPE(OPR)\nMCSOPER.logonid UID(sysprgmr) SERVICE(READ) ALLOW\n\nCOMPILE ' ACF2.MVA.OPR(MVS)' STORE\n\nF ACF2,REBUILD(OPR)","ccis":["CCI-000213"]},{"vulnId":"V-223433","ruleId":"SV-223433r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit access to SYSTEM DUMP data sets to appropriate authorized users.","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":"Ask the system administrator and/or DASD administrator to determine the System Dump data sets. \n\nRefer to data sets SYS1.DUMPxx. Dump data sets can be identified by reviewing the logical parmlib concatenation data sets for the current COMMNDxx member. Find the COM= that specifies the DUMPDS NAME (DD NAME=name-pattern) entry. The name-pattern is used to identify additional Dump data sets.\n\nIf ACF2 data set rules for System Dump data sets do not restrict READ, WRITE, and/or ALLOCATE access to only systems programming personnel, this is a finding.\n\nIf ACF2 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"]},{"vulnId":"V-223434","ruleId":"SV-223434r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 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\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125","checkContent":"Execute a data set 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.\n\nOther user access can be granted as documented and approved by the ISSM.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223435","ruleId":"SV-223435r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 allocate access to system user catalogs must be properly protected.","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 Shell, enter:\nLISTCat USERCATALOG NAME NOPREFIX\n\nReview the ACF2 data set rules for each usercatalog defined.\n\nIf the data set rules for User Catalogs do not restrict ALLOCATE 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:\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 above is true, this is not a finding.\n\nIf the data set rules for User Catalogs do not specify that all (i.e., failures and successes) ALLOCATE access will be logged, this is 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 datasets, WRITE 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 ACF2 rules for allocate access to USER CATALOGS, limited to system programmers only, and all allocate access is logged.\n\nConfigure ACF2 rules for the USER CATALOGS to allow any Products or procedures system programmer access for system-level maintenance that meets 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 datasets WRITE access is required for user operation.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223436","ruleId":"SV-223436r1137691_rule","severity":"medium","ruleTitle":"ACF2 Classes required to properly security the z/OS UNIX environment must be ACTIVE.","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:\nACF\nSET CONTROL(GSO)\nSHOW CLASMAP\n\nIf the CLASMAP DEFINITIONS list does not include entries for the FACILITY, SURROGAT, and UNIXPRIV resource classes, this is a finding.\n\nNOTE: TYPE CODES values should be unique for each resource. The default TYPE CODE values should be FAC, SUR, and UNI.","fixText":"Define the CLASMAP DEFINITIONS to include entries for the FACILITY, SURROGAT, and UNIXPRIV resource classes.\n\nNOTE: TYPE CODES values should be unique for each resource. The default TYPE CODE values should be FAC, SUR, and UNI.\n\nExample:\nTSO ACF\nSHOW CLASMAP\n\nACF\nSET CONTROL(GSO)\nINSERT CLASMAP.FACILITY  RESOURCE(FACILITY) RSRCTYPE(FAC)  ENTITYTLN (39)","ccis":["CCI-000213"]},{"vulnId":"V-223437","ruleId":"SV-223437r1137691_rule","severity":"medium","ruleTitle":"Access to IBM z/OS special privilege TAPE-LBL or TAPE-BLP must be limited and/or justified.","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:\nACF\nSET LID\nSET VERBOSE\nLIST IF(TAPE-LBL OR TAPE-BLP)\n\nIf the number of users granted the special privileges TAPE-LBL or TAPE-BLP is strictly controlled and limited to systems programmer and operations personnel, this is not a finding.\n\nIf the number of users granted the special privileges TAPE-LBL or TAPE-BLP is not strictly controlled and limited to systems programmer and operations personnel, this is a finding.","fixText":"The ISSO will ensure Logonids with the TAPE-LBL or TAPE-BLP are kept to a minimum and are controlled and documented.\n\nReview all LOGONIDs with these attributes. \n\nTape label bypass (BLP) privileges will be restricted at the user level. Specify one of the following two logonid privileges to grant a user access to BLP processing:\n\nUser LID Record:\nTAPE-LBL\nTAPE-BLP\n\nIt is possible to grant selected programs to bypass tape label processing regardless of the BLP related privilege of the logonid executing the program. This capability will not be used due to the requirement that accounting of BLP processing be done at the user level. Do not utilize the GSO BLPPGM record.","ccis":["CCI-000213"]},{"vulnId":"V-223438","ruleId":"SV-223438r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit access to System page data sets (i.e., PLPA, COMMON, and LOCALx) to system programmers.","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 data set list of access for System page data sets (i.e., PLPA, COMMON, and LOCALx).\n\nIf the ESM data set rules for System page data sets (i.e., PLPA, COMMON, and LOCALx) do not restrict access to only systems programming personnel, this is 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.\nAuditors may be allowed READ Access as approved by the ISSM.","ccis":["CCI-000213"]},{"vulnId":"V-223439","ruleId":"SV-223439r1137691_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\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 a command input screen enter:\nSET RESOURCE (FAC) \nSET VERBOSE\nLIST LIKE (CSV-)\n\nNOTE: If CLASMAP defines FACILITY as anything other than the default of TYPE(FAC), replace FAC with the appropriate three letters.\n\nIf the ACF2 resources and/or generic equivalent are defined with a default access of PREVENT, this is not a finding.\n\nIf the ACF2 resources and/or generic equivalent identified below will be defined with LOG and SERVICE(UPDATE) access restricted to system programming personnel, this is not a finding.\n\nCSVAPF.\nCSVAPF.MVS.SETPROG.FORMAT.DYNAMIC\nCSVAPF.MVS.SETPROG.FORMAT.STATIC\nCSVDYLPA.\nCSVDYNEX.\nCSVDYNEX.LIST\nCSVDYNL.\nCSVDYNL.UPDATE.LNKLST\nCSVLLA.\n\nIf the ACF2 CSVDYNEX.LIST resource and/or generic equivalent will be defined with LOG and SERVICE(UPDATE) access restricted to system programming personnel, this is not a finding.\n\nIf the ACF2 CSVDYNEX.LIST resource and/or generic equivalent will be defined with SERVICE(READ) access restricted to auditors, this is not a finding.\n\nIf the products CICS and/or CONTROL-O are on the system, the ACF2 access to the CSVLLA resource and/or generic equivalent will be defined with LOG and SERVICE(UPDATE) access restricted to the CICS and CONTROL-O STC logonids, this is not a finding.\n\nIf any software product requires access to dynamic LPA updates on the system, the ACF2 access to the CSVDYLPA resource and/or generic equivalent will be defined with LOG and SERVICE(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, this is not a finding.\n\nNote: In the above, SERVICE(UPDATE) can be substituted with ADD, CONTROL, or LOG/ALLOW. Review the rules definitions in the ACF2 documentation when specifying SERVICE(UPDATE).","fixText":"Configure the Dynamic List resources to be 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\nNote: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The resource class, actual resources, 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 required CSV-prefixed Facility Class resources are listed below. These resources and/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.DELETE.-\nCSVDYNEX.-\nCSVDYNEX.LIST\nCSVDYNL.-\nCSVDYNL.UPDATE.LNKLST\nCSVLLA.-\n\nLimit authority to those resources to z/OS systems programmers. Restrict to the absolute minimum number of personnel with LOG and SERVICE(UPDATE) access.\n\nSample commands are shown here to accomplish one set of resources:\n\n$KEY(CSVAPF) TYPE(FAC) \nMVS.SETPROG.- UID(sysprgmr) LOG\nMVS.SETPROG.FORMAT.DYNAMIC.- UID(sysprgmr) LOG \nMVS.SETPROG.FORMAT.STATIC.- UID(sysprgmr) LOG\nMVS.SETPROG.FORMAT.- UID(sysprgmr) LOG \nMVS.SETPROG.FORMAT.- UID(*) PREVENT\n- UID(sysprgmr) LOG \n- UID(*) PREVENT\n\nSET R(FAC)\nCOMPILE 'ACF2.xxxx.FAC(CSVAPF)' STORE\n\nF ACF2,REBUILD(FAC)\n\nThe CSVDYLPA.ADD resource can be permitted to BMC Mainview, CA 1, and CA Common Services STC logonids with LOG and SERVICE(UPDATE) access.\n\nThe CSVDYLPA.DELETE resource can be permitted to CA 1 and CA Common Services STC logonids with LOG and SERVICE(UPDATE) access.\n\nSample commands are shown here to accomplish one set of resources:\n\n$KEY(CSVDYLPA) TYPE(FAC) \nADD.- UID(sysprgmr) LOG SERVICE(UPDATE)\nADD.- UID(BMC Mainview STC) LOG SERVICE(UPDATE)\nADD.- UID(CA 1 STC) LOG SERVICE(UPDATE)\nADD.- UID(CCS STC) LOG SERVICE(UPDATE)\nDELETE.- UID(sysprgmr) LOG SERVICE(UPDATE)\nDELETE.- UID(CA 1 STC) LOG SERVICE(UPDATE)\nDELETE.- UID(CCS STC) LOG SERVICE(UPDATE)\n- UID(sysprgmr) LOG\n- UID(*) PREVENT\n\nSET R(FAC)\nCOMPILE 'ACF2.xxxx.FAC(CSVDYLPA)' STORE\n\nF ACF2,REBUILD(FAC)\n\nThe CSVDYNEX.LIST resource and/or generic equivalent will be defined with LOG and SERVICE(UPDATE) access restricted to system programming personnel.\n\nThe CSVDYNEX.LIST resource and/or generic equivalent will be defined with SERVICE(READ) access with ALLOW restricted to auditors.\n\nSample commands are shown here to accomplish this:\n\n$KEY(CSVDYNEX) TYPE(FAC) \nLIST.- UID(sysprgmr) LOG\nLIST.- UID(auditor) SERVICE(READ) ALLOW\n- UID(sysprgmr) LOG \n- UID(*) PREVENT\n\nSET R(FAC)\nCOMPILE 'ACF2.xxxx.FAC(CSVDYNEX)' STORE\n\nF ACF2,REBUILD(FAC)\n\nThe CSVLLA resource can be permitted to CICS and CONTROL-O STC logonids with LOG and SERVICE(UPDATE) access.\n\nSample commands are shown here to accomplish one set of resources:\n\n$KEY(CSVLLA) TYPE(FAC) \n- UID(sysprgmr) LOG\n- UID(CICS STC logonids) LOG SERVICE(UPDATE)\n- UID(CONTROL-O STC logonid) LOG SERVICE(UPDATE)\n- UID(*) PREVENT\n\nSET R(FAC)\nCOMPILE 'ACF2.xxxx.FAC(CSVLLA)' STORE\n\nF ACF2,REBUILD(FAC)","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223440","ruleId":"SV-223440r1137691_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-000324-GPOS-00125","checkContent":"Refer to AXRxx member of PARMLIB \nFor 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 UPDATE and/or ALTER access (i.e., successes and failures).","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223441","ruleId":"SV-223441r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 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\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":"The ACF2 data set rules for SYS1.UADS restrict ALLOCATE access to only z/OS systems programming personnel.\n\nThe ACF2 data set rules for SYS1.UADS restrict READ and/or WRITE access to z/OS systems programming personnel and/or security personnel.\n\nThe ACF2 data set rules for SYS1.UADS restrict READ access to auditors as documented in the Security Plan.\n\nThe ACF2 data set rules for SYS1.UADS specify that all (i.e., failures and successes) data set access authorities (i.e., READ, WRITE, ALLOCATE, and CONTROL) will be logged.\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.\n\nSYS1.UADS WRITE or Greater authority is limited to the systems programming staff. \n\nREAD and/or WRITE 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 dataset access is logged.","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223442","ruleId":"SV-223442r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 must limit all system PROCLIB data sets 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 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 ensure that 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 are restricted 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 is what 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...\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-223443","ruleId":"SV-223443r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 access to the System Master Catalog 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":"Refer to SYSCATxx member of SYS1.NUCLEUS.\nMultiple SYSCATxx members may be defined if so refer to Master Catalog message for IPL.\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:\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. \nIf the above is true, this is not a finding.\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 master catalog to only allow access above \"READ\" to systems programmers and those authorized by the Site Security Plan.\n\nConfigure ESM rules for the system master catalog to allow access above \"READ\" to systems programmers ONLY.\n\nConfigure ESM rules for the system 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. \nAll greater than read access must be logged.","ccis":["CCI-000213"]},{"vulnId":"V-223444","ruleId":"SV-223444r1137691_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":"Refer to the proper CONSOLxx member of SYS1.PARMLIB.\n\nFrom a ACF Command screen enter:\nACF\nSET RESOURCE(CON)\nSET VERBOSE\nLIST LIKE(-) \n\nNOTE: If CLASMAP defines CONSOLE as anything other than the default of TYPE(CON), replace CON below with the appropriate three letters.\n\nIf each console in the CONSOLxx member is defined to ACF2 with a corresponding resource rule for TYPE(CON), this is not a finding.\n\nIf each TYPE(CON) rule is defined with PREVENT access by default, this is not a finding.\n\nIf the logonid associated with each console has READ access to the corresponding resource defined in the CONSOLE resource class, this is not a finding.\n\nIf access authorization for CONSOLE resources restricts READ access to operations and system programming personnel or authorized personnel, this is not a finding.","fixText":"Configuration should ensure that all MCS consoles are defined to the CONSOLE resource class and READ access is limited to operators and system programmers.\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 ACF2 with a corresponding resource rule for TYPE(CON). \n\nEach TYPE(CON) rule is defined with PREVENT access by default.\n\nThe logonid associated with each console has READ access to the corresponding resource defined in the CONSOLE resource class.\n\nAccess authorization for CONSOLE resources restricts READ access to operations and system programming personnel or authorized personnel.\n\nExample:\n$KEY(MZNC20) TYPE(CON) \nUSERDATA(CONSOLE ID SECURITY) \nUID(sysprgmr) ALLOW\nUID(oper) ALLOW\nUID(MZNC20) ALLOW DATA(MZNC20 CONSOLE LOGONID ACCESS REQUIREMENTS) \nUID(*) PREVENT\n\nSET R(CON)\nCOMPILE 'ACF2.MZN.CON(MZNC20)' STORE\n\nF ACF2,REBUILD(CON)","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223445","ruleId":"SV-223445r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 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":"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 SYS1.NUCLEUS do not restrict WRITE and/or ALLOCATE access to only z/OS systems programming personnel.\n\nThe ACP data set rules for SYS1.NUCLEUS do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE 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 update and allocate access to SYS1.NUCLEUS to be limited to system programmers only and all update and allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223446","ruleId":"SV-223446r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 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 any of the following is true, this is a finding.\n\n- The ACF2 data set rules for SYS1.LPALIB do not restrict WRITE and/or ALLOCATE access to only z/OS systems programming personnel.\n- The ACF2 data set rules for SYS1.LPALIB do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE 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 update and allocate access to SYS1.LPALIB to be limited to system programmers only and all update and allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223447","ruleId":"SV-223447r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 must limit Write or greater access to SYS1.IMAGELIB to system programmers.","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\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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\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\n The ACP data set rules for SYS1.IMAGELIB allow inappropriate access.\n\n The ACP data set rules for SYS1.IMAGELIB do not restrict WRITE and/or ALLOCATE access to only systems programming personnel.\n\n The ACP data set rules for SYS1.IMAGELIB do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE access will be logged.","fixText":"Configure WRITE and/or ALLOCATE access to SYS1.IMAGELIB to be limited to system programmers only and all update and allocate 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-223448","ruleId":"SV-223448r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 must limit Write or greater access to Libraries containing EXIT modules to system programmers only.","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.\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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\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":"Examine the system for active exit modules. You may need system administrator help for this. Third-party software products 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 UPDATE and ALLOCATE 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 UPDATE and ALLOCATE 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. See 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 update and alter 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-223449","ruleId":"SV-223449r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 must limit Write and Allocate 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\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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"From Any ISPF input line, enter:\nTSO ISRDDN APF \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\n- The ACP data set rules for APF libraries do not restrict WRITE and/or ALLOCATE access to only z/OS systems programming personnel.\n- The ACP data set rules for APF libraries do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE 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 Update and Allocate access to all APF-authorized libraries to be limited to system programmers only and all update and alter access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223450","ruleId":"SV-223450r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 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 and/or ALLOCATE access to only z/OS systems programming personnel.\n\nThe ACP data set rules for LPA libraries do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE 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 update and allocate access to all LPA libraries to be limited to system programmers only and all update and allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223451","ruleId":"SV-223451r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit Write and Allocate access to LINKLIST 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","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 and/or ALLOCATE 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 and/or ALLOCATE 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 update and allocate access to LINKLIST libraries to be limited to system programmers only and all update and allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223452","ruleId":"SV-223452r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit Write and allocate 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\n- The data set name and associated SREL for each SMP/E CSI used to maintain this system.\n- The data set name of all SMP/E TLIBs and DLIBs used for installation and production support. A comprehensive list of the SMP/E DDDEFs for all CSIs may be used if valid.\n\nThe ACF2 data set rules for system-level product installation libraries (e.g., SMP/E CSIs) do not restrict WRITE and/or ALLOCATE 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-223453","ruleId":"SV-223453r1137691_rule","severity":"high","ruleTitle":"CA-ACF2 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\nACF2 data set rules for SYS1.SVCLIB restrict WRITE and/or ALLOCATE access to only z/OS systems programming personnel.\n\nACF2 data set rules for SYS1.SVCLIB specify that all (i.e., failures and successes) WRITE and/or ALLOCATE access will be logged.","fixText":"Configure update and allocate access to SYS1.SVCLIB to be limited to system programmers only and all Update and Allocate 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-223454","ruleId":"SV-223454r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 Access to SYS1.LINKLIB must be properly protected.","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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\n\nThe operating system or software configuration management utility must enforce control of software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125, SRG-OS-000362-GPOS-00149","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, UPDATE and ALTER 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) UPDATE and/or ALTER access will be logged this is a finding.","fixText":"Configure the ESM rules for SYS1.LINKLIB limit access to system programmers only and all update and allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-003980","CCI-002235"]},{"vulnId":"V-223455","ruleId":"SV-223455r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 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\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-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 site personnel (e.g., systems programmers and batch jobs that perform SMF processing), this is a finding.\n\nIf the ESM dataset rules for the SMF dump/backup files do not 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 the 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":"Define WRITE or greater access to data sets used to back up and/or dump SMF collection files to be limited to system programmers and/or batch jobs that perform SMF dump processing. Ensure that all data set access is logged.\n\nDefine data set rules for the SMF dump/backup files to restrict UPDATE access to others approved by the ISSM.\n\nDefine READ Access to data sets used to back up and/or dumpSMF collection files to be limited to auditors and others approved by the ISSM.\n\nEnsure that all WRITE or greater access authority to SMF history files will be logged using the ESM's facilities.\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 data sets used to back up and/or dump SMF Collection Files.\n\nIn z/OS systems, SMF data is the ultimate record of system activity. Therefore, SMF data is of the most sensitive and critical nature. While the length of time for which SMF data will be retained is not specifically regulated, it is imperative that the information is available for the longest possible time period in case of subsequent investigations. The statute of limitations varies according to the nature of a crime. It may vary by jurisdiction, and some crimes are not subject to a statute of limitations. Apply the following guidelines to the retention of SMF data for all DOD systems:\n\n(a) Retain at least two (2) copies of the SMF data.\n(b) Maintain SMF data for a minimum of one year.\n(c) All WRITE or greater access authority to SMF history files will be logged using the ACP's facilities. Only systems programming personnel and batch jobs that perform SMF functions will be authorized to update the SMF files.","ccis":["CCI-000213","CCI-001314","CCI-002235"]},{"vulnId":"V-223456","ruleId":"SV-223456r958726_rule","severity":"high","ruleTitle":"CA-ACF2 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 SYS1.UADS userids are limited and reserved for emergency purposes only, this is not 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-223457","ruleId":"SV-223457r958726_rule","severity":"medium","ruleTitle":"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 ACF Command screen enter:\nSET RESOURCE(FAC)\nLIST IEASYMUP\n\nIf the accesses for IEASYMUP resources and/or generic equivalent are properly restricted, this is not a finding.\n\nThe ACF2 resources are defined with a default access of PREVENT.\nThe ACF2 resource access authorizations  specify SERVICE(UPDATE) and/or greater access to only DASD administrators, Tape Library personnel, and system programming personnel.\nThe ACF2 resource  access authorizations specify logging.","fixText":"Configure the System level symbolic resources to be 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 the above personnel with LOG and SERVICE(UPDATE) and/or greater access.\n\nThe following commands are provided as a sample for implementing resource controls:\n\n$KEY(IEASYMUP) TYPE(FAC)\n- UID(<dasd>) SERVICE(UPDATE) LOG\n- UID(<sysprgmr>) SERVICE(UPDATE) LOG\n- UID(<tape librarian>) SERVICE(UPDATE) LOG\n- UID(*) PREVENT\n\nSET R(FAC)\nCOMPILE 'ACF2.FAC(IEASYMUP)' STORE\n\nF ACF2,REBUILD(FAC)","ccis":["CCI-002235"]},{"vulnId":"V-223458","ruleId":"SV-223458r958726_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit Update and Allocate access to system backup files to system programmers and/or batch jobs that perform DASD backups.","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":"Collect from the storage management group the identification of the DASD backup files and all associated storage management userids/LIDs/ACIDs.\n\nIf ESM data set rules for system DASD backup files do not restrict UPDATE and ALLOCATE 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-002235"]},{"vulnId":"V-223459","ruleId":"SV-223459r958726_rule","severity":"medium","ruleTitle":"ACF2 PPGM GSO record value must specify protected programs that are only executed by privileged users.","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 ACF command screen enter:\nSET CONTROL(GSO)\nLIST LIKE(PPGM-)\n\nRefer to the table of Sensitive Utilities resources and/or generic equivalent as detailed in the table. \n\nIf all applicable programs or their generic equivalent referenced below are represented by GSO PPGM record values, 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. \n                                   Restricted to data center personnel only.","fixText":"Configure the PPGM GSO value indicating protected programs that are only executed by privileged users in the table below.\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\nDefine protected programs that can only be executed by privileged users.\n\nPGM MASK(pgm mask1, ...,pgm-mask255)\n\nExample:\nSET C(GSO)\nINSERT PPGM PGM-MASK(<program name or generic equivalent>) \n\nF ACF2,REFRESH(PPGM)","ccis":["CCI-002235"]},{"vulnId":"V-223462","ruleId":"SV-223462r958736_rule","severity":"medium","ruleTitle":"The CA-ACF2 PSWD GSO record values for MAXTRY and PASSLMT 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-forcing, is reduced. Limits are imposed by locking the account.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nSHOW PSwdopts\n\nIf \"MAXTRY\" is set to \"3\", this is not a finding.\n\nIf \"PASSLMT\" is set to \"3\", this is not a finding.","fixText":"Configure the GSO option \"MAXTRY\" to equal \"3\".\nConfigure the GSO option \"PASSLMT\" to equal \"3\".","ccis":["CCI-002238"]},{"vulnId":"V-223463","ruleId":"SV-223463r1050836_rule","severity":"high","ruleTitle":"IBM z/OS SYS1.PARMLIB 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\nWithout 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-000324-GPOS-00125, SRG-OS-000337-GPOS-00129, SRG-OS-000362-GPOS-00149","checkContent":"Execute a data set list of access to SYS1.PARMLIB concatenation.\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, UPDATE, and ALTER 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) UPDATE and/or ALTER access will be logged, this is a finding.","fixText":"Configure access rules for SYS1.PARMLIB concatenation as follows:\n\nSystems programming personnel will be authorized to update and alter the SYS1.PARMLIB concatenation.\nDomain-level security administrators can be authorized to update the SYS1.PARMLIB concatenation.\nSystem-Level Started Tasks, authorized Data Center personnel, and auditor can be authorized read access by the information system security officer (ISSO).\nAll update and alter access is logged.","ccis":["CCI-000171","CCI-000213","CCI-001499","CCI-003980","CCI-001914","CCI-002235"]},{"vulnId":"V-223464","ruleId":"SV-223464r958796_rule","severity":"high","ruleTitle":"CA-ACF2 must be installed, functional, 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. You can use IBM SDSF or the system Log.\n\nIf CA-ACF2 is active, this is not a finding.","fixText":"Assure that CA-ACF2 is active on the system.","ccis":["CCI-001813"]},{"vulnId":"V-223465","ruleId":"SV-223465r1137691_rule","severity":"medium","ruleTitle":"CA-ACF2 must limit Write and allocate 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\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000324-GPOS-00125, SRG-OS-000259-GPOS-00100","checkContent":"The ACF2 data set rules for the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) do not restrict WRITE and/or ALLOCATE access to only z/OS systems programming personnel.\n\nThe ACF2 data set rules for the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) allow inappropriate access not documented and approved by the ISSO.\n\nIf both of the above are untrue, this is not a finding.\n\nIf either of the above are true, 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.\n\nAccess other than this should be documented and approved by the ISSO.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223466","ruleId":"SV-223466r1137691_rule","severity":"low","ruleTitle":"CA-ACF2 must limit Write or greater access to libraries that contain PPT modules to system programmers only.","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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\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' : \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\n-The ESM data set rules for libraries that contain PPT modules do not restrict UPDATE and ALLOCATE access to only z/OS systems programming personnel.\n-The ESM data set rules for libraries that contain PPT modules do not specify that all UPDATE and ALLOCATE access will be logged.","fixText":"Configure the Update and Allocate access to libraries containing PPT modules to be limited to system programmers only and all Update and Allocate access is logged.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223467","ruleId":"SV-223467r991589_rule","severity":"medium","ruleTitle":"The EXITS GSO record value must specify the module names of site written ACF2 exit routines.","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 ACF Command enter:\nSET CONTROL(GSO)\nLIST LIKE(EXIT-)\n\nIf the GSO EXITS record values conform to the following requirements, this is not a finding.\n\nSpecifies the module names of site written ACF2 exit routines.\n\nNOTE: The DSNPOST exit is optional and is not required to be specified in the GSO EXITS record. DSNPOST(module) SEVPRE(SEVPRE01) SEVPOST(SEVPST01)\nNOTE: No other exits are authorized at this time.\nNOTE: Local changes will be documented in writing with supporting documentation.\n\nIf there is any deviation from the above requirements in the GSO EXITS record values, this is a finding.","fixText":"Configure the EXITS GSO value to specify the module names of site written ACF2 exit routines.\n\nSpecifies the module names of site written ACF2 exit routines.\n\nNOTE: The DSNPOST exit is optional and is not required to be specified in the GSO EXITS record.\n\nDSNPOST(module) SEVPRE(SEVPRE01) SEVPOST(SEVPST01)\n\nExample:\nSET C(GSO)\nINSERT EXITS DSNPOST(module) SEVPRE(SEVPRE01) SEVPOST(SEVPST01)\n\nF ACF2,REFRESH(EXITS)\n\nNOTE: No other exits are authorized at this time.\n\nNOTE: Local changes will be justified in writing with supporting documentation.","ccis":["CCI-000366"]},{"vulnId":"V-223468","ruleId":"SV-223468r991589_rule","severity":"medium","ruleTitle":"The CA-ACF2 LOGONID with the REFRESH attribute must have procedures for utilization.","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 ACF Command screen enter:\nSET LID \nLIST IF(REFRESH)\n\nIf procedures exist to utilize the logonid with the REFRESH attribute to refresh ACF2 global options, this is not a finding.\n\nExample of a suggested procedure follows:\n\nWhen the ISSO determines it necessary to refresh the ACF2 global options, the ISSO will do the following:\n\n-Activate the REFRESH ID with the following setting(s):\nNOSUSPEND\nNOPSWD EXP\nPASSWORD(new password)\n\n-Instruct Operations to perform the REFRESH.\n\n-Deactivate the REFRESH ID with the following setting:\nSUSPEND\n\nIf no procedures exist in accordance with the STIG requirements to utilize the logonid with the REFRESH attribute to refresh ACF2 global options, this is a finding.","fixText":"Review security procedures for defining LOGONIDs and develop documentation of requirements for the LOGONID associated with the REFRESH attribute. \n\nExample of a suggested procedure follows:\nWhen the ISSO determines it necessary to refresh the ACF2 global options, the ISSO will do the following:\n\n-Activate the required REFRESH ID with the following setting(s):\n     NOSUSPEND\n     NOPSWD EXP\n     PASSWORD(new password)\n\n-Instruct Operations to perform the REFRESH using the newly activated REFRESH ID.\n-After refresh is completed.\n\n-Deactivate the REFRESH ID with the following setting:\nSUSPEND\n\nThis procedure should be documented in the Site Security Plan.","ccis":["CCI-000225","CCI-000366"]},{"vulnId":"V-223469","ruleId":"SV-223469r991589_rule","severity":"medium","ruleTitle":"IBM z/OS TSO GSO record values must be set to the values 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 ACF Command screen enter:\nSET CONTROL(GSO)\nLIST TSO\n\nIf the GSO TSO record values conform to the following requirements, this is not a finding.\n\nACCOUNT(1)\nBYPASS(#)\nCHAR(BS)\nCMDLIST()\nNOIKJEFLD1\nLINE(ATTN)\nLOGONCK\nPERFORM(0)\nPROC(site defined)\nNOQLOGON\nREGION(site defined)\nSUBCLSS()\nSUBHOLD()\nSUBMSG()\nTIME(0)\nTSOSOUT(A)\nUNIT(SYSDA)\nWAITIME(1-60)","fixText":"Configure the GSO TSO record values to conform to the following requirements.\n\nACCOUNT(1)\nBYPASS(#)\nCHAR(BS)\nCMDLIST()\nNOIKJEFLD1\nLINE(ATTN)\nLOGONCK\nPERFORM(0)\nPROC(site defined)\nNOQLOGON\nREGION(site defined)\nSUBCLSS()\nSUBHOLD()\nSUBMSGC()\nTIME(0)\nTSOSOUT(A)\nUNIT(SYSDA)\nWAITIME(1-60)\n\nExample:\nSET C(GSO)\nINSERT TSO ACCOUNT(1) BYPASS(#) CHAR(BS) CMDLIST() NOIKJEFLD1 LINE(ATTN) LOGONCK PERFORM(0) PROC(IKJACCNT) NOQLOGON REGION(4,096) SUBCLSS() SUBHOLD() SUBMSGC() TIME(0) TSOGNAME() TSOSOUT(A) UNIT(SYSDA) WAITIME(60) \n\nF ACF2,REFRESH(TSO)","ccis":["CCI-000366","CCI-001133"]},{"vulnId":"V-223470","ruleId":"SV-223470r991589_rule","severity":"medium","ruleTitle":"IBM z/OS procedures must restrict ACF2 LOGONIDs with the READALL attribute to auditors and/or authorized users.","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 ACF Command line enter:\nSET LID\nLIST IF(READALL)\n\nIf procedures are in place to ensure logonids with the READALL attribute are used and controlled in accordance with the DISA requirements, this is not a finding.\n\nThe READALL privilege is available for actual auditing of system data. It gives the capability of looking at every data set on the system despite the data set rules. Its use is strongly discouraged. Always grant access through the use of standard data set access rules. Under no circumstances will the privilege be used as a convenience to the person maintaining the rule sets. Only use this privilege when absolutely necessary, and only give it to auditors. Remove the privilege once the audit is complete. Fully document the granting and revoking of the access.","fixText":"Develop procedures to control Logonids with the READALL attribute.\n\nThe READALL privilege is available for actual auditing of system data. It gives the capability of looking at every data set on the system despite the data set rules. Its use is strongly discouraged. Always grant access through the use of standard data set access rules. Under no circumstances will the privilege be used as a convenience to the person maintaining the rule sets. Only use this privilege when absolutely necessary, and only give it to auditors. Remove the privilege once the audit is complete. Fully document the granting and revoking of the access.","ccis":["CCI-000366"]},{"vulnId":"V-223471","ruleId":"SV-223471r991589_rule","severity":"medium","ruleTitle":"IBM z/OS must have the RULEVLD and RSRCVLD attributes specified for LOGONIDs with the SECURITY attribute.","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 ACF Command screen enter:\nSET LID\nLIST IF(SECURITY)\n\nIf all logonids with the SECURITY attribute also have the RULEVLD and RSRCVLD attributes specified, this not a finding.\n\nIf any logonid with the SECURITY attribute does not have the RULEVLD and/or RSRCVLD attributes specified, this is a finding.","fixText":"Configure Logonids with the SECURITY attribute to have the RULEVLD and RSRCVLD attributes specified.\n\nIf a logonid is granted the SECURITY privilege, it is mandatory that RULEVLD and RSRCVLD attributes will also be specified for the logonid.\n\nExample:\nSET LID\nCHANGE logonid RULEVLD RSRCVLD","ccis":["CCI-000366"]},{"vulnId":"V-223472","ruleId":"SV-223472r991589_rule","severity":"medium","ruleTitle":"IBM z/OS LOGONIDs with the AUDIT or CONSULT attribute must be properly scoped.","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 ACF Command Screen enter:\nSET LID\nLIST IF(AUDIT)\n\nIf all logonids with the attributes AUDIT and/or CONSULT also do not have the SCPLIST attribute specified properly according to job function and areas of responsibility, this is a finding.\n\nNOTE: SCPLST attributes are not required for Logonids with the attributes AUDIT or CONSULT if the security ISSM/ISSO determines it requires ability to view the entire ACF2 environment. SCPLST attributes are not required for Auditors, Domain Level Security Admin Logonids, and BATCH Logonids that review the entire ACF2 environment to include GSO records, data set and resource rules, etc. or run audit reports.","fixText":"Configure logonids with the AUDIT or CONSULT attributes are restricted by a SCPLIST attribute that restricts authority based on job function and area of responsibility.\n\nThe following user attributes allow viewing of the ACF2 databases for the purpose of inspecting users, data set access rules, and Infostorage records. When granted to a logonid, restrict the scope of the following attributes using an associated SCPLIST (scope list) record:\n\nAUDIT\nCONSULT\n\nNOTE: SCPLST attributes are not required for Logonids with the attributes AUDIT or CONSULT if the security ISSM/ISSO determines it requires ability to view the entire ACF2 environment. SCPLST attributes are not required for Auditors, Domain Level Security Admin Logonids, and BATCH Logonids that review the entire ACF2 environment to include GSO records, data set and resource rules, etc. or run audit reports.","ccis":["CCI-000366"]},{"vulnId":"V-223473","ruleId":"SV-223473r991589_rule","severity":"medium","ruleTitle":"IBM z/OS LOGONID with the ACCTPRIV attribute must be restricted to the ISSO.","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 ACF Command screen enter:\nSET LID\nLIST IF(ACCTPRIV)\n\nIf logonids with the ACCTPRIV attribute specified are not assigned to the security administrator, this is a finding.","fixText":"Configure logonids with the ACCTPRIV attribute to be only reserved for use by the Security manager.\n\nThe ACCTPRIV attribute cannot be scoped, and will be restricted exclusively to a site security administrator:\n\nExample:\nSET LID\nCHANGE logonid ACCTPRIV","ccis":["CCI-000366"]},{"vulnId":"V-223474","ruleId":"SV-223474r991589_rule","severity":"medium","ruleTitle":"IBM z/OS batch jobs with restricted ACF2 LOGONIDs must have the PGM(xxxxxxxx) and SUBAUTH attributes or the SOURCE(xxxxxxxx) attribute assigned to the corresponding LOGONIDs.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF command screen enter:\nSET LID \nSET VERBOSE \nLIST IF(RESTRICT)\n\nIf the logonids that are associated with batch jobs have the RESTRICT attribute, then the logonids must also have the PGM(xxxxxxxx) and SUBAUTH attributes, or the SOURCE(xxxxxxxx) attribute specified.\n\nIf all restricted logonids have the PGM(xxxxxxxx) and SUBAUTH attributes, and/or the SOURCE(xxxxxxxx) attribute, this is not a finding.\n\nIf the PGM(xxxxxxxx) and SUBAUTH attributes or the SOURCE(xxxxxxxx) attribute is not specified for any restricted logonids, this is a finding.","fixText":"All batch jobs scheduled via an automation process will use the //*LOGONID xxxxxxxx card in the JCL stream to identify the userid. Use restricted logonids with the following parameter coded:\n\nRESTRICT\n\nOne or both of the following will also be specified:\n\nPGM(xxxxxxxx) and SUBAUTH\nSOURCE(xxxxxxxx)\n\nThe use of default IDs prevents the identification of tasks with individual users as mandated by policy, and prevents adequate accountability. Default IDs for batch processing will not be used.\n\nThe use of USER= can also be used in the jobcard to identify the userid to be used for a job's processing.","ccis":["CCI-000366"]},{"vulnId":"V-223475","ruleId":"SV-223475r991589_rule","severity":"medium","ruleTitle":"CA-ACF2 RULEOPTS GSO record values must be set to the values 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 ACF Command enter:\nSET CONTROL(GSO)\nLIST RULEOPTS\n\nIf the following options are defined, this is not a finding.\n\nNO$NOSORT \nCENTRAL\nCHANGE\nDECOMP(AUDIT SECURITY) | DECOMP(AUDIT) | DECOMP(SECURITY)\n\nThe other RULEOPTS values should be assigned carefully as they affect the Rules and Infostorage databases.","fixText":"Configure the GSO RULEOPTS record values to conform to the following requirements.\n\nNO$NOSORT \nCENTRAL\nCHANGE\nDECOMP(AUDIT SECURITY) | DECOMP(AUDIT) | DECOMP(SECURITY)\n\nThe other RULEOPTS values should be assigned carefully as they affect the Rules and Infostorage databases.\n\nExample:\nSET C(GSO)\nINSERT RULEOPTS NO$NOSORT CENTRAL CHANGE NOCOMPDYN DECOMP(AUDIT SECURITY)  \nF ACF2,REFRESH(RULEOPTS)","ccis":["CCI-000366","CCI-000368"]},{"vulnId":"V-223476","ruleId":"SV-223476r991589_rule","severity":"medium","ruleTitle":"The CA-ACF2 GSO OPTS record value 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 ACF Command enter:\nSET CONTROL(GSO)\nLIST OPTS\n\nIf the GSO OPTS record values conform to the following requirements, this is not a finding.\n\nBLPLOG\nNOCMDREC\nCONSOLE(NOROLL)\nCPUTIME(LOCAL)\nDATE(MDY)\nNODDB\nDFTLID()\nDFTSTC()\nINFOLIST(none | AUDIT | SECURITY | SECURITY, AUDIT)\nJOBCK\nMAXVIO(10)\nNOTIFY\nRPTSCOPE\nSHRDASD\nSTAMPSMF\nSTC\nTAPEDSN\nTEMPDSN\nNOUADS\nNOVTAMOPEN","fixText":"Define the global options available to the system.\n\nBLPLOG\nNOCMDREC\nCONSOLE(NOROLL)\nCPUTIME(LOCAL)\nDATE(MDY)\nNODDB\nDFTLID()\nDFTSTC()\nINFOLIST(none | AUDIT | SECURITY | SECURITY, AUDIT)\nJOBCK\nMAXVIO(10)\nNOTIFY\nRPTSCOPE\nSHRDASD\nSTAMPSMF\nSTC\nTAPEDSN\nTEMPDSN\nNOUADS\nNOVTAMOPEN\n\nExample:\nSET C(GSO)\nINSERT OPTS BLPLOG NOCMDREC CONSOLE(NOROLL) CPUTIME(LOCAL) DATE(MDY) NODDB DFTLID() DFTSTC() INFOLIST(SECURITY, AUDIT) JOBCK MAXVIO(10)\nMODE(ABORT) NOTIFY RPTSCOPE SHRDASD STAMPSMF STC TAPEDSN TEMPDSN NOUADS NOVTAMOPEN\n\nF ACF2,REFRESH(OPTS)","ccis":["CCI-000366"]},{"vulnId":"V-223477","ruleId":"SV-223477r1001097_rule","severity":"medium","ruleTitle":"CA-ACF2 must prevent the use of dictionary words for passwords.","description":"If the operating system allows the user to select passwords based on dictionary words, then this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.","checkContent":"From the ISPF Command Shell enter:\nACF to enter ACF2 Command shell\nenter SHOW STATE\n\nIf \"PSWDRSV = NO\", this is a finding.\n\nIf \"PSWDRSVW = NO\", this is a finding.\n\nSHOW PSwdopts\n\nReserved Words and Prefixes\nAPPL APR ASDF AUG BASIC\nCADAM DEC DEMO FEB FOCUS\nGAME IBM JAN JUL JUN\nLOG MAR MAY NET NEW\nNOV OCT PASS ROS SEP\nSIGN SYS TEST TSO VALID\nVTAM XXX 1234","fixText":"Configure the GSO record to include PSWDRSV and PSWDRSVW.","ccis":["CCI-004061","CCI-004065","CCI-000366"]},{"vulnId":"V-223478","ruleId":"SV-223478r991589_rule","severity":"medium","ruleTitle":"CA-ACF2 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.","checkContent":"From the ACF Command screen, enter:\nSET CONTROL(GSO)\nSHOW  DDSN\n\nExexute the ISPF Data Set List Utility for each dataset listed to determine the volume. \n\nIf the ACF2 database is not located on the same volume as either its alternate or backup file, this is not a finding.\n\nIf the ACF2 database is collocated with either its alternate or backup, this is a finding.","fixText":"Configure the placement of ACF2 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 ACF2 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 ACF2 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 ACF2 database should not also cause the loss of the ACF2 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 ACF2 database and its alternate or backup file.","ccis":["CCI-000366"]},{"vulnId":"V-223479","ruleId":"SV-223479r991589_rule","severity":"medium","ruleTitle":"CA-ACF2 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.","checkContent":"From the ACF Command enter:\nSET CONTROL(GSO)\nSHOW SYSTEMS\n\nIf based on the information provided, it can be determined that the ESM database is being backed up on a regularly scheduled basis, this is not a finding.\n\nIf it cannot be determined that the ESM database is being backed up on a regularly scheduled basis, this is a finding.","fixText":"Configure ACF2 GSO option to ensure that procedures are in place to back up all ACP files needed for recovery on a scheduled basis.\n\nAt a minimum, this means nightly backup of the ACP databases and of other critical security files (such as the ACP parameter file). More frequent backups (two or three times daily) will reduce the time necessary to effect recovery. The ISSO will verify that the backup job(s) run successfully.","ccis":["CCI-000366"]},{"vulnId":"V-223480","ruleId":"SV-223480r991589_rule","severity":"medium","ruleTitle":"ACF2 REFRESH attribute must be restricted to security administrators' LOGON ID only.","description":"Users with the refresh attribute have the ability to effect changes to ESM global system options. Unauthorized use could result in the compromise of the confidentiality, integrity, and availability of the operating system, ESM or customer data.\n\nActivity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF Command screen enter:\nSET LID\nLIST IF(REFRESH)\n\nIf logonids exist with the REFRESH attribute not assigned to a site security administrator, this is a finding.","fixText":"Define any logonid with the REFRESH attribute to be assigned to a site security administrator only.\n\nExample:\nSET LID\nCHANGE logonid REFRESH","ccis":["CCI-000366"]},{"vulnId":"V-223481","ruleId":"SV-223481r991589_rule","severity":"medium","ruleTitle":"ACF2 maintenance LOGONIDs must have corresponding GSO MAINT records.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF Command screen enter:\nSET LID\nLIST IF(MAINT)\n\nSET CONTROL(GSO)\nLIST LIKE(MAINT-)\n\nIf every maintenance logonid has a corresponding GSO MAINT record, this is not a finding.","fixText":"Ensure that an associated GSO maintenance record exists for each special user logonid identifying the program(s) that it is permitted to access and the library where the program(s) resides.\n\nDefine associated GSO MAINT record for each special user logonid, identifying the program(s) that it is permitted to access and the library where the program(s) resides.\n\nEvery maintenance logonid has a corresponding GSO MAINT record.\n\nExample:\n\nSET C(GSO)\nINSERT MAINT.DFSMSHSM LIBRARY(SYS1.LINKLIB) LID(HSMDFDSS) PGM(ADRDSSU) \n\nF ACF2,REFRESH(MAINT)","ccis":["CCI-000366"]},{"vulnId":"V-223482","ruleId":"SV-223482r991589_rule","severity":"medium","ruleTitle":"ACF2 LOGONIDs with the NON-CNCL attribute specified in the associated LOGONID record must be listed as trusted and must be specifically approved.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF command screen enter:\nSET LID \nSET VERBOSE \nLIST IF(NON-CNCL)\n\nIf only logonids associated with trusted STCs have the NON-CNCL attribute specified, this is not a finding.\n\nTRUSTED STCs:\nSTCs that are listed as z/OS started tasks and address spaces in the IBM z/OS MVS Initialization and Tuning Reference. \n\nGuidelines for reference:\n\nAssign 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.\n \nAny other started tasks not listed or not covered by the guidelines are a finding unless approval by the Authorizing Official AO.","fixText":"Review all LOGONIDs with the NON-CNCL attribute. Ensure that only STCs in the trusted list 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:\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:\nAssign 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.\n\nThese STCs will be given the following attribute to facilitate access while logging any accesses they would not ordinarily be granted by the access rule sets:\n\nNON-CNCL\n\nExample:\nSET LID\nCHANGE logonid STC NON-CNCL","ccis":["CCI-000366"]},{"vulnId":"V-223483","ruleId":"SV-223483r991589_rule","severity":"medium","ruleTitle":"ACF2 LOGONIDs with the ACCOUNT, LEADER, or SECURITY attribute must be properly scoped.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF command screen enter:\nSET LID\nLIST IF(ACCOUNT)\nLIST IF(LEADER)\nLIST IF(SECURITY)\n\nReview all logonids for specific groups with the attributes ACCOUNT, LEADER, or SECURITY. \n\nIf each has the SCPLIST attribute specified properly according to job function and areas of responsibility, this is not a finding.\n\nNOTE: SCPLST attributes are not required for Domain Level Security Admin Logonids and BATCH Logonids that administer and modify the entire ACF2 environment to include GSO records, data set and resource rules, etc. or run audit reports.","fixText":"The following user attributes allow update of the ACF2 databases for administering users, data set access rules, and Infostorage records. When granted to a logonid, restrict the scope of the following attributes using an associated SCPLIST (scope list) record:\n\nACCOUNT\nLEADER\nSECURITY\n\nNOTE: SCPLST attributes are not required for Domain Level Security Admin Logonids and BATCH Logonids that administer and modify the entire ACF2 environment to include GSO records, data set and resource rules, etc. or run audit reports.","ccis":["CCI-000366"]},{"vulnId":"V-223484","ruleId":"SV-223484r991589_rule","severity":"medium","ruleTitle":"ACF2 LOGONIDs associated with started tasks that have the MUSASS attribute and the requirement to submit jobs on behalf of its users must have the JOBFROM attribute as required.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF command screen enter:\nSET LID \nSET VERBOSE \nLIst IF(MUSASS  & STC)\n\nIf any started task logonid that has the MUSASS attribute and the requirement to submit jobs on behalf of its users does not have the JOBFROM attribute, this is a finding.","fixText":"Ensure that if MUSASS has the requirement to submit jobs on behalf of its users, the STC logonid has the JOBFROM attribute specified.\n\nIf the MUSASS has the requirement to submit jobs on behalf of its users, the STC logonid will also have the following attribute:\n\nJOBFROM\n\nExample:\n\nSET LID\nCHANGE logonid STC JOBFROM","ccis":["CCI-000366"]},{"vulnId":"V-223485","ruleId":"SV-223485r991589_rule","severity":"medium","ruleTitle":"IBM z/OS Started Tasks must be properly identified and defined to ACF2.","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\nFrom the ACF command screen enter:\nSET LID \nSET VERBOSE \nLIST IF(STC)\n\nIf all logonids identified as started tasks have the STC attribute specified, this is not a finding.","fixText":"All started tasks will be assigned an individual logonid. The logonid for a Started Task Control (STC) will be granted the minimum privileges necessary for the STC to function. In addition to the default LID field settings, all STC logonids will have the following field setting:\n\nSTC\n\nExample:\nSET LID\nINSERT logonid STC","ccis":["CCI-000764"]},{"vulnId":"V-223486","ruleId":"SV-223486r991589_rule","severity":"medium","ruleTitle":"ACF2 emergency LOGONIDS with the REFRESH attribute must have the SUSPEND attribute specified.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"From the ACF Command screen enter:\nSET LID\nLIST IF(REFRESH)\n\nIf the logonid is an emergency logonid and the REFRESH attribute is not in SUSPEND status, this is a finding.","fixText":"The emergency logonids with the REFRESH attribute must be in SUSPEND status unless actually in use.\n\nExample:\nSET LID\nCHANGE logonid SUSPEND","ccis":["CCI-000366"]},{"vulnId":"V-223487","ruleId":"SV-223487r991589_rule","severity":"medium","ruleTitle":"ACF2 BACKUP GSO record must be defined with a TIME value specifies greater than 00 unless the database is shared and backed up on another system.","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 ACF command screen enter:\nSET CONTROL(GSO)\nLIST LIKE(BACKUP-)\n\nIf the GSO BACKUP record values conform to the following requirements, this is not a finding.\n\nExample: \nCPUID() PRISPACE(5) SECSPACE(5) STRING(S ACFBKUP) TIME(00:01) WORKUNIT(VIO)\n\nIf there is any deviation from the above requirements in the GSO BACKUP record values, this is a finding.","fixText":"Configure the BACKUP GSO value to specify a time field and Time(00:00 ) is not specified unless the database is shared and backed up on another system.\n\nCPUID() PRISPACE(5) SECSPACE(5) STRING(S ACFBKUP) TIME(00:01) WORKUNIT(VIO)\n\nExample: \nSET C(GSO)\nINSERT BACKUP CPUID() PRISPACE(5) SECSPACE(5) STRING(S ACFBKUP) TIME(00:01) WORKUNIT(VIO) \n\nF ACF2,REFRESH(BACKUP)","ccis":["CCI-000366","CCI-000537"]},{"vulnId":"V-223488","ruleId":"SV-223488r991589_rule","severity":"low","ruleTitle":"ACF2 APPLDEF GSO record if used must have supporting documentation indicating the reason it was used.","description":"Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems. It also permits outbound connections that may facilitate exfiltration of DoD data.","checkContent":"From the ACF Command screen enter:\nSET CONTROL(GSO)\nLIST LIKE(APPLDEF-)\n\nIf the GSO APPLDEF record does not exist, this is not a finding.\n\nIf the GSO APPLDEF record does exist and no supporting documentation is available, this is a finding.","fixText":"For any APPLDEF GSO record used, it must have supporting documentation indicating the reason it was used.\n\nThe APPLDEF record is optional.","ccis":["CCI-000366","CCI-000368"]},{"vulnId":"V-223489","ruleId":"SV-223489r958804_rule","severity":"medium","ruleTitle":"ACF2 MAINT GSO record value if specified must be restricted to production storage management user.","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 the ACF Command screen enter:\nSET CONTROL(GSO)\nLIST LIKE(MAINT-)\n\nIf the GSO MAINT record values conform to the following requirements, this is not a finding.\n\nSpecifies the logonid, program, and library combinations used for system maintenance functions. \nNOTE: For logonids that match environments described in records, no SMF logging records will be created. \nNOTE: Entries will be restricted to production storage management user accounts and programs. \n\nIf there is any deviation from the above requirements in the GSO MAINT record values, this is a finding.","fixText":"Configure the MAINT GSO value to be specified as restricted to production storage management user accounts and programs.\n\nSpecifies the logonid, program, and library combinations used for system maintenance functions.\nNOTE: For logonids that match environments described in records, no SMF logging records will be created.\nNOTE: Entries will be restricted to production storage management user accounts and programs.","ccis":["CCI-001764"]},{"vulnId":"V-223490","ruleId":"SV-223490r958804_rule","severity":"medium","ruleTitle":"ACF2 LINKLST GSO record if specified must only contains trusted system data sets.","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 the ACF Command screen enter:\nSET CONTROL(GSO)\nLIST LINKLST\n\nIf the GSO LINKLST record values conform to the following requirements, this is not a finding.\n\nSpecifies one or more partitioned data sets considered part of the system link (SYS1.LINKLIB) during data set access validation. Only trusted system data sets will be listed. Application libraries will never be included. \n\nExample: \nLIBRARY(SYS1.LINKLIB SYS2A.FDR.LOADLIB) \n\nIf there is any deviation from the above requirements in the GSO LINKLST record values, this is a finding.","fixText":"Configure the LINKLIST GSO value if specified only contains trusted system data sets.\n\nSpecifies one or more partitioned data sets considered part of the system link (SYS1.LINKLIB) during data set access validation.\n\nOnly trusted system data sets will be listed. Application libraries will never be included.\n\nExample:\nSET C(GSO)\nINSERT LINKLST LIBRARY(SYS1.LINKLIB SYS2A.FDR.LOADLIB)\n\nF ACF2,REFRESH(LINKLST)","ccis":["CCI-001764"]},{"vulnId":"V-223491","ruleId":"SV-223491r958480_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 the correct CONSOLxx member. \n\nExamine the CONSOLxx member.\n\nVerify that the MCS console logonids are properly restricted. \n\nIf the following guidance is true, this is not a finding.\n\nEach console defined in the currently active CONSOLxx parmlib member is associated with a valid ACF2 logonid.\n\nEach console logonid has no special privileges and/or attributes (e.g., ACCOUNT, SECURITY, etc.).\n\nEach console logonid has no accesses to interactive online facilities (e.g., TSO, CICS, etc., excluding VTAM SMCS consoles).\n\nEach console logonid 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 logonids may be given with SERVICE(READ) to MVS.CONTROL, MVS.DISPLAY, MVS.MONITOR, and MVS.STOPMN OPERCMDS resources.\n\nNOTE: Execute the JCL in CNTL(ACFRPTRX) using the ACF2 console userids in the LID statements in the SYSIN input. This report lists all occurrences of these userids within the ACF2 database, including data set and resource access lists.","fixText":"Define all consoles identified in the currently active CONSOLxx parmlib member in EXAM.RPT(PARMLIB) to be defined to the ESM.\n\nReview the MCS console resources defined to z/OS and the ESM and ensure they conform to those outlined below.\n\nEach console defined in the currently active CONSOLxx parmlib member is associated with a valid ACF2 logonid.\n\nEach console logonid has no special privileges and/or attributes (e.g., ACCOUNT, SECURITY, etc.,  excluding VTAM SMCS consoles).\n\nEach console logonid has no accesses to interactive online facilities (e.g., TSO, CICS, etc.).\n\nEach console logonid 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 logonids may be given with SERVICE(READ) to MVS.CONTROL, MVS.DISPLAY, MVS.MONITOR, and MVS.STOPMN OPERCMDS resources.\n\nNOTE: If LOGON(AUTO) is specified in the currently active CONSOLxx parmlib member, additional access may be required. Permissions for the console logonids may be given with SERVICE(READ) to MVS.CONTROL, MVS.DISPLAY, MVS.MONITOR, and MVS.STOPMN OPERCMDS resources.\n\nExample:\nINSERT MVAC20 NAME(MVA CONSOLE C20) PASSWORD(xxxxxxxx)\n\n$KEY(MVS) TYPE(OPR)\nMCSOPER.- UID(MVAC20) SERVICE(READ) ALLOW\nCONTROL.- UID(MVAC20) SERVICE(READ) ALLOW DATA(FOR LOGON(AUTO))\nMONITOR.- UID(MVAC20) SERVICE(READ) ALLOW DATA(FOR LOGON(AUTO))\nSTOPMN.- UID(MVAC20) SERVICE(READ) ALLOW DATA(FOR LOGON(AUTO))\nDISPLAY.- UID(*) SERVICE(READ) ALLOW\n- UID(*) PREVENT\n\nSET R(OPR)\nCOMPILE ' ACF2.MVA.OPR(MVS)' STORE\n\nF ACF2,REBUILD(OPR)\n\n$KEY(consname) TYPE(CON)\nUID(MVAC20) SERVICE(READ) ALLOW\n\nSET R(CON)\nCOMPILE ' ACF2.MVA.CON(consname)' STORE\n\nF ACF2,REBUILD(CON)","ccis":["CCI-000382"]},{"vulnId":"V-223492","ruleId":"SV-223492r958480_rule","severity":"medium","ruleTitle":"ACF2 BLPPGM GSO record must not be defined.","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 ISPF Command Shell enter:\nACF\nSET CONTROL(GSO)\nLIST BLPPGM\n\nIf the BLPPGM record is defined, this is a finding.","fixText":"The BLPPGM GSO value indicates that ACF2 does not control the programs authorized to use tape bypass label processing (BLP).\n\nDelete the BLPPGM from GSO options.","ccis":["CCI-000382"]},{"vulnId":"V-223493","ruleId":"SV-223493r958482_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 ACF command screen enter:\nSET PROFILE(USER) DIVISION(OMVS) \nSET VERBOSE \nLIST LIKE(-) \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":"Assure that UID(0) is defined 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-223494","ruleId":"SV-223494r958482_rule","severity":"medium","ruleTitle":"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":"From the ISPF Command Shell enter:\nACF\nSET LID\nSET VERBOSE\nLIST OMVS SECTION(ALL) PROFILE(OMVS)\n\nIf OMVS is defined as follows, this is not a finding.\n\nNo access to interactive on-line facilities (e.g., TSO, CICS, etc).\nDefault group specified as OMVSGRP or STCOMVS\nUID(0)\nHOME directory specified as \"/\"\nShell program specified as \"/bin/sh\"\n\nIf OMVS is not defined as specified in above, this is a finding.","fixText":"Define the OMVS (IBM default name for USS Kernel), as specified below:\n\nNo access to interactive on-line facilities (e.g., TSO, CICS, etc.)\nDefault group specified as OMVSGRP or STCOMVS\nUID(0)\nHOME directory specified as \"/\"\nShell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-223495","ruleId":"SV-223495r958482_rule","severity":"medium","ruleTitle":"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 the ISPF Command Shell enter:\nACF\nSET LID\nSET VERBOSE\nLIST RMFGAT SECTION(ALL) PROFILE(OMVS)\n\nIf RMFGAT is defined as follows, this is not a finding:\nDefault group specified as OMVSGRP or STCOMVS\nA unique, non-zero UID\nHOME directory specified as \"/\"\nShell program specified as \"/bin/sh\"","fixText":"Define the RMFGAT user account as specified below:\nDefault group specified as OMVSGRP or STCOMVS\nA unique, non-zero UID\nHOME directory specified as \"/\"\nShell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-223496","ruleId":"SV-223496r958482_rule","severity":"medium","ruleTitle":"ACF2 LOGONIDs must be defined with 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 an ACF Command Screen enter:\nSET LID\nLIST *\n\nIf the below listed fields are complete for all logonids, this is not a finding.\n\nNAME User's name\nUID-String All fields defined in the ACFFDR @UID macro\n\nNOTE: A completed NAME field that can either be traced back to a current DD Form 2875 or a Vendor Requirement (example: A Started Task). \n\nNOTE: A user may be required to have more than one logonid but users must not share userids.","fixText":"Define every user to ACF2 with a unique userid. (ACF2 calls this a logonid.) To ACF2, a user is an individual, a started task, or a batch job.\n\nEvery user will be fully identified within ACF2. Complete the following fields for every logonid:\n\nNAME - User's name\nUID-String - All fields defined in the ACFFDR @UID macro\n\nAll fields that comprise the standard UID string will be filled out for each user as a logonid is added.\n\nExample:\nSET LID\nINSERT logonid UID(uid string) NAME(user name)","ccis":["CCI-000764"]},{"vulnId":"V-223497","ruleId":"SV-223497r958482_rule","severity":"medium","ruleTitle":"CA-ACF2 defined user accounts must uniquely identify system users.","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.\n\nSatisfies: SRG-OS-000104-GPOS-00051, 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: Userids should be able to be traced back to a current DD Form 2875 or a Vendor Requirement (example: A Started Task).","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-000764","CCI-000804","CCI-000877"]},{"vulnId":"V-223498","ruleId":"SV-223498r1001099_rule","severity":"medium","ruleTitle":"CA-ACF2 userids found inactive for more than 35 days must be suspended.","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:\nACF\n\nIf every user shows an ACC-DATE=mm/dd/yy 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 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-223499","ruleId":"SV-223499r1001101_rule","severity":"medium","ruleTitle":"CA-ACF2 PWPHRASE GSO record must be properly defined.","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 in determining 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\nSpecial characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.","checkContent":"From the ISPF Command Screen enter:\nACF\nSET CONTROL(GSO)\nLIST PWPHRASE\nIf the following options are in effect, this is not a finding.\n\nIf any of the options deviate from the following, this is a finding.\n\nThe GSO PWPHRASE record will conform to the following requirements.\n\nALPHA(1 or greater)\nHISTORY(10-32)\nMAXDAYS(1-60)\nMINDAYS(1)\nMINLEN(15-100)\nNUMERIC(1 or greater)\nSPECIAL(1 or greater)\nSPECLIST(character list)\nWARNDAYS(1-10)\n\nNote: The SPECLIST special characters will be specified at a minimum. Characters will conform to the allowable list defined in CA ACF2 for z/OS Administration Guide.","fixText":"Configure the PWPHRASE GSO values to be set to the values specified.\n\nEnsure the GSO PWPHRASE record values conform to the following requirements:\n\nALPHA(1 or greater)\nHISTORY(10-32)\nMAXDAYS(1-60)\nMINDAYS(1)\nMINLEN(15-100)\nNUMERIC(1 or greater)\nSPECIAL(1 or greater)\nSPECLIST(character list)\nWARNDAYS(1-10)\n\nNote: The SPECLIST special characters will be specified at a minimum. Characters will conform to the allowable list defined in CA ACF2 for z/OS Administration Guide.\n\nExample:\nSET C(GSO)\nINSERT PWPHRASE NOALLOW ALPHA(1) HISTORY(10) MAXDAYS(60) MINDAYS(1) MINLEN(15) NUMERIC(1) SPECIAL(1) SPECLIST(& * =) WARNDAYS(10)\n\nF ACF2,REFRESH(PWPHRASE)","ccis":["CCI-004066"]},{"vulnId":"V-223500","ruleId":"SV-223500r1001103_rule","severity":"medium","ruleTitle":"CA-ACF2 must enforce password complexity by requiring that at least one special character be used.","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 in determining 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\nSpecial characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf PSWDPLST is coded as defined in CA ACF2 for z/OS Administration Guide, this is not a finding.","fixText":"Configure Password option PSWDPLST as defined in CA ACF2 for z/OS Administration Guide.","ccis":["CCI-004066","CCI-004065"]},{"vulnId":"V-223501","ruleId":"SV-223501r1001105_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require at least one uppercase character be used.","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.","checkContent":"From the ISPF Command Shell enter:\nACF to enter ACF2 Command shell\nenter \nSET CONTROL(GSO)\nLIST PSWD\nIf NOPSWDUC is listed, this is a finding.","fixText":"Configure the GSO option \"PSWDUC\" to \"YES\".","ccis":["CCI-004066"]},{"vulnId":"V-223502","ruleId":"SV-223502r1001108_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require at least one numeric character be used.","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.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"PSWDALPH\" is coded, this is not a finding.","fixText":"Configure the Password options to include \"PSWDALPH\".","ccis":["CCI-004066"]},{"vulnId":"V-223503","ruleId":"SV-223503r1001109_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require at least one lowercase character be used.","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.","checkContent":"From the ISPF Command Shell enter:\nACF to enter ACF2 Command shell\nenter SET CONTROL(GSO)\n\nLIST PSWD\n\nIf \"NOPSWDLC\" is listed, this is a finding.","fixText":"Configure the GSO option \"PSWDLC\" to \"YES\".","ccis":["CCI-004066"]},{"vulnId":"V-223504","ruleId":"SV-223504r1001111_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require the change of at least 50 percent of the total number of characters when passwords are changed.","description":"If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.\n\nThe number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.\n\nIf the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least eight characters.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"PSWDSIM\" is set to \"4\", this is not a finding.","fixText":"Configure the Password option \"PSWDSIM\" to \"4\".","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-223505","ruleId":"SV-223505r1001113_rule","severity":"high","ruleTitle":"ACF2 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 an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf the \"GSO PSWD\" record option \"PSWDENCT\" is set to \"XDES\" or null, this is a finding.\n\nSET MSYSID(-)\n\nLIST PSWD\n\nFor CA-ACF2 R16 and above:\n\nIf option \"NOONEPWALG\" is specified, and there is no transition plan with a definite completion date filed with the information system security manager (ISSM), this is a finding.","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\nConfigure the \"GSO PSWD\" record option \"PSWDENCT\" to \"AES1\".\n\nFor CA-ACF2 Release16 and above:\n\nConfigure \"GSO PSWD\" record option \"PSWDENCT\" to \"AES1\" or \"AES2\".\n\nConfigure the \"GSO PSWD\" to \"ONEPWALG\".\n\nNote: If you are using VM Database Synchronization you cannot use \"ONEPWALG\". VM does not support the AES algorithms.\n\nDevelop a transition plan with a definite completion date for z/VM; file with the ISSM.\n\nIf all systems that are sharing the logonid or infostorage databases are not running with the same \"PSWDENCT\" value you cannot use \"ONEPWALG\".\n\nDevelop a transition plan that contains a definite completion date to migrate all logonid and infostorage databases to one \"PSWDENCT\" value; file with the ISSM.\n\nConsult the CA-ACF2 administration guide for converting to \"AES1\" or \"AES2\" and using \"ONEPWALG\".","ccis":["CCI-004062","CCI-000197"]},{"vulnId":"V-223506","ruleId":"SV-223506r1038967_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require a 60-day maximum password lifetime restriction.","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 an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"PSWDMAX\" is set to \"60\", this is not a finding.","fixText":"Configure Password option \"PSWDMAX\" to \"60\" days.","ccis":["CCI-004066"]},{"vulnId":"V-223507","ruleId":"SV-223507r1001117_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to require 24 hours/one day as the minimum password lifetime.","description":"Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"PSWDMIN\" is set \"1\", this is not a finding.","fixText":"Configure Password option \"PSWDMIN\" to minimum of \"1\" day.","ccis":["CCI-004066"]},{"vulnId":"V-223508","ruleId":"SV-223508r1001119_rule","severity":"medium","ruleTitle":"ACF2 PSWD GSO record value must be set to prohibit password reuse for a minimum of five generations or more.","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 an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"PSWDXHIST\" is not specified, this is a finding.\n\nIf \"PSWDXHIST#\" is set to \"5\" or greater, this is not a finding.","fixText":"Configure Password option \"PSWXHST\" is coded and \"PSWXHST#\" is \"5\" or greater.","ccis":["CCI-004061","CCI-004065"]},{"vulnId":"V-223509","ruleId":"SV-223509r958470_rule","severity":"medium","ruleTitle":"ACF2 TSOTWX GSO record values must be set to obliterate the logon password on TWX devices.","description":"To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the operating system must not provide any information allowing an unauthorized user to compromise the authentication mechanism.\n\nObfuscation of user-provided information that is typed into the system is a method used when addressing this risk.\n\nDisplaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.","checkContent":"From the ISPF Command Shell enter:\nACF <enter>\nSET CONTROL(GSO)\nLIST TSOTWX\n\nIf the GSO TSOTWX record values conform to the following requirements, this is not a finding.\n\nCR(15)\nIDLE(17)\nLENGTH(8)\nM1(X)\nM2(N)\nM3(Z)\nM4(M)\nSTRING()","fixText":"Define a cross out mask to obliterate the logon password on TWX devices.\n\nCR(15)\nIDLE(17)\nLENGTH(8)\nM1(X)\nM2(N)\nM3(Z)\nM4(M)\nSTRING()\n\nExample:\nSET C(GSO)\nINSERT TSOTWX CR(15) IDLE(17) LENGTH(8) M1(X) M2(N) M3(Z) M4(M) STRING()\n\nF ACF2,REFRESH(TSOTWX)","ccis":["CCI-000206"]},{"vulnId":"V-223510","ruleId":"SV-223510r958470_rule","severity":"medium","ruleTitle":"ACF2 TSOCRT GSO record values must be set to obliterate the logon to ASCII CRT devices.","description":"To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the operating system must not provide any information allowing an unauthorized user to compromise the authentication mechanism.\n\nObfuscation of user-provided information that is typed into the system is a method used when addressing this risk.\n\nDisplaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.","checkContent":"From the ISPF Command Shell enter:\nACF\nSET CONTROL(GSO) <enter>\nLIST TSOCRT\n\nIf the GSO TSOCRT record values conform to the following requirements, this is not a finding.\n\nSTRING(A12FA11C1A270C0D)","fixText":"Define a clear string used to obliterate the logon to ASCII CRT devices.\n\nSTRING(A12FA11C1A270C0D)\n\nExample:\nSET C(GSO)\nINSERT TSOCRT STRING(A12FA11C1A270C0D)\n\nF ACF2,REFRESH(TSOCRT)","ccis":["CCI-000206"]},{"vulnId":"V-223511","ruleId":"SV-223511r958470_rule","severity":"medium","ruleTitle":"ACF2 TSO2741 GSO record values must be set to obliterate the logon password on 2741 devices.","description":"To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the operating system must not provide any information allowing an unauthorized user to compromise the authentication mechanism.","checkContent":"From the ISPF Command Shell enter:\nACF <enter>\nSET CONTROL(GSO)\nLIST TSO2741\n\nIf the GSO TSO2741 record values conform to the following requirements, this is not a finding.\n\nBS(16)\nLENGTH(8)\nM1(X)\nM2(N)\nM3(Z)\nM4(M)\nSTRING()","fixText":"Define a cross out string used to obliterate the logon password on 2741 devices.\n\nEnsure the GSO TSO2741 record values conform to the following requirements.\n\nBS(16)\nLENGTH(8)\nM1(X)\nM2(N)\nM3(Z)\nM4(M)\nSTRING()\n\nExample:\nSET C(GSO)\nINSERT TSO2741 BS(16) LENGTH(8) M1(X) M2(N) M3(Z) M4(M) STRING()\n\nF ACF2,REFRESH(TSO2741)","ccis":["CCI-000206"]},{"vulnId":"V-223512","ruleId":"SV-223512r958552_rule","severity":"medium","ruleTitle":"ACF2 SECVOLS GSO record value must be set to VOLMASK(). Any local changes are justified and documented with the ISSO.","description":"The SECVOLS record defines the DASD and tape volumes for which CA-ACF2 provides volume-level protection. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\n\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST SECVOLS\n\nIf the GSO SECVOLS record values conform to the following requirements, this is not a finding.\n\nVOLMASK() \n\nNOTE: Local changes will be documented in writing with supporting documentation. \n\nIf there is any deviation from the above requirements in the GSO SECVOLS record values, this is a finding.","fixText":"Define the GSO SECVOLS record values to conform to the following requirements.\n\nVOLMASK() \n\nExample:\nSET C(GSO)\nINSERT SECVOLS VOLMASK() \n\nF ACF2,REFRESH(SECVOLS)","ccis":["CCI-000368","CCI-001199"]},{"vulnId":"V-223513","ruleId":"SV-223513r958552_rule","severity":"medium","ruleTitle":"ACF2 RESVOLS GSO record value must be set to Volmask(-). Any other setting requires documentation justifying the change.","description":"The RESVOLS record defines DASD and mass storage volumes for which CA ACF2 is to provide protection at the data set name level.\nInformation at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\n\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.","checkContent":"From an ACF command screen, enter:\nSET CONTROL(GSO)\nLIST RESVOLS\n\nIf the GSO RESVOLS record values conform to the following requirements, this is not a finding.\n\nVOLMASK(-) \n\nNOTE: Local changes will be documented in writing with supporting documentation. \n\nIf there is any deviation from the above requirements in the GSO RESVOLS record values, this is a finding.","fixText":"Define the GSO RESVOLS record values to conform to the following requirements.\n\nVOLMASK(-) \n\nExample:\nSET C(GSO)\nINSERT RESVOLS VOLMASK(-) \n\nF ACF2,REFRESH(SECVOLS)","ccis":["CCI-000368","CCI-001199"]},{"vulnId":"V-223514","ruleId":"SV-223514r958518_rule","severity":"high","ruleTitle":"ACF2 security data sets and/or databases must be properly protected.","description":"An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.\n\nSecurity functions are 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. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.\n\nDevelopers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.\n\nPreventing 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-000134-GPOS-00068, SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125","checkContent":"Determine all associated ACF2 security data sets and/or databases.\n\nIf the ACF2 data set rules for ACF2 security data sets and/or databases restrict READ access to auditors and DASD batch, this is not a finding.\n\nIf the ACF2 data set rules for ACF2 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 ACP maintenance, this is not a finding.\n\nIf all (i.e., failures and successes) data set access authorities (i.e., READ, WRITE, ALLOCATE, and CONTROL) for ACP security data sets and/or databases are logged, this is not a finding.","fixText":"Configure ACF2 READ and/or greater access rules for ACF2 files and/or databases as limited to system programmers and/or security personnel, and/or batch jobs that perform ACP maintenance. \n\nREAD access can be given to auditors and DASD batch. All accesses to ACP files and/or databases are logged.","ccis":["CCI-000213","CCI-001084","CCI-001499","CCI-002235"]},{"vulnId":"V-223515","ruleId":"SV-223515r1137695_rule","severity":"medium","ruleTitle":"ACF2 AUTOERAS GSO record value must be set to indicate that ACF2 is controlling the automatic physical erasure of VSAM or non VSAM data sets.","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 an ACF command screen, enter:\nSET CONTROL(GSO)\nLIST AUTOERAS\n\nIf the GSO AUTOERAS record values conform to the following requirements, this is not a finding.\n\nAll Systems: PROCESS(ACF2) NON-VSAM VSAM VOLS(-)","fixText":"Configure the AUTOERASE GSO value to indicate that ACF2 is controlling the automatic physical erasure of VSAM or non-VSAM data sets.\n\nExample:\nSET C(GSO)\nINSERT AUTOERAS PROCESS(ACF2 NON-VSAM VSAM VOLS(-) \n\nF ACF2,REFRESH(AUTOERAS)","ccis":["CCI-001090"]},{"vulnId":"V-223517","ruleId":"SV-223517r958406_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":"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\nSMF data collection is the basic unit of tracking of all system functions and actions. Included in this tracking data are the audit records from each of the ACPs and system. If the required SMF data record types are not being collected, then accountability cannot be monitored, and its use in the execution of a contingency plan could be compromised.\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 those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities 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.\n\nSatisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000392-GPOS-00172","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\nIf 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-223518","ruleId":"SV-223518r1137691_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":"Refer to the FTP server Started task (usually FTPD). Refer to the data set defined on the SYSFTPD DD statement.\n\nIf the 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\nRefer to the BANNER statement in the FTP Data configuration file. If the BANNER statement refers to an MVS data set and 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\nIf READ access to the data set containing the FTP banner file is permitted to all authenticated users, this is not a finding.\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.","fixText":"Review the data set access authorizations defined to the ESM for the FTP.DATA and FTP.BANNER files. Configure these data sets to be protected as follows:\n\nThe data set containing the FTP.DATA configuration file allows read access to all authenticated users and all other access is restricted to systems programming personnel.\n\nAll write and allocate access to the data set containing the FTP.DATA configuration file is logged.\n\nThe data set containing the FTP banner file allows read access to all authenticated users and all other access is restricted to systems programming personnel.","ccis":["CCI-000213"]},{"vulnId":"V-223519","ruleId":"SV-223519r1195303_rule","severity":"medium","ruleTitle":"IBM z/OS permission bits and user audit bits for HFS objects that are part of the FTP Server component must be properly configured.","description":"MVS data sets of the FTP Server provide the configuration and operational characteristics of this product. Failure to properly secure these data sets may lead to unauthorized access resulting in the compromise of the integrity and availability of customer data and some system services.","checkContent":"From the ISPF Command shell, enter:\nomvs\nAt the input line enter:\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":"Ensure the UNIX permission bits and user audit bits on the HFS directories and files for the FTP Server 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-223520","ruleId":"SV-223520r958390_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\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\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 as specified below 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"]},{"vulnId":"V-223522","ruleId":"SV-223522r958586_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration statements for the FTP Server must specify the BANNER statement.","description":"The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Refer to the Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nIf the BANNER statement is coded, this is not a finding.","fixText":"Configure the FTP.DATA CONFIGURATION STATEMENT to include the following:\n\nBANNER [An HFS file, e.g., /etc/ftp.banner]","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223523","ruleId":"SV-223523r991589_rule","severity":"medium","ruleTitle":"IBM z/OS FTP Control cards must be properly stored in a secure PDS file.","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":"Provide a 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 PDSes (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 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 those individuals responsible for the application connectivity and who have a legitimate requirement to know the userid and password on a remote system. \n\nFTP Control Cards within In-stream JCL, within JCL libraries or open access libraries/data sets is a finding. \n\nIf there is anyone not listed within the spreadsheet by userid that 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\nMake sure that the FTP control Cards for each FTP are stored in a secure PDS and that they are not placed in the JCL libraries or in the in-stream JCL for each FTP.","ccis":["CCI-000366"]},{"vulnId":"V-223525","ruleId":"SV-223525r958482_rule","severity":"medium","ruleTitle":"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 ISPF Command enter:\nACF\nSET LID\nLIST LIKE(FTP-) SECTION(ALL) PROFILE(OMVS)\nNOTE: The JCL member is typically named FTPD.\n\nIf all of the following are true, this is not a finding.\n\nIf any of the following is untrue, this is a finding.\n\nThe FTP daemon logonid is FTPD.\nThe FTPD logonid is defined with the STC attribute.\nThe FTPD logonid has the following z/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh.","fixText":"Define the FTP daemon to run under its own user account. Specifically, it does not share the account defined for the z/OS UNIX kernel.\n\nDefine the FTP Server daemon account, privileges, and access authorizations to the ACP using the requirements below.\n\nThe following commands can be used to create the user account that is required for the FTP daemon:\n\nSET LID\nINSERT FTPD NAME(FTPD) GROUP(STCTCPX) STC\n\nSET PROFILE(USER) DIVISION(OMVS)\nINSERT FTPD UID(0) HOME(/) PROGRAM(/bin/sh)\n\nF ACF2,REBUILD(USR),CLASS(P)","ccis":["CCI-000764"]},{"vulnId":"V-223526","ruleId":"SV-223526r970703_rule","severity":"medium","ruleTitle":"IBM z/OS startup parameters for the FTP Server must be defined in the SYSTCPD and SYSFTPD DD statements for configuration files.","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:\nThe SYSTCPD and SYSFTPD DD statements specify the TCP/IP Data and FTP Data configuration files respectively.\nThe ANONYMOUS keyword is not coded on the PARM parameter on the EXEC statement.\nThe ANONYMOUS=logonid combination is not coded on the PARM parameter on the EXEC statement.\nThe INACTIVE keyword is not coded on the PARM parameter on the EXEC statement.\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:\nThe ANONYMOUS keyword is not coded on the PARMSTRING parameter.\nThe ANONYMOUS=logonid combination is not coded on the PARMSTRING parameter.\nThe 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-223527","ruleId":"SV-223527r970703_rule","severity":"medium","ruleTitle":"IBM z/OS FTP.DATA configuration for the FTP Server must have 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 Data configuration file specified on the SYSFTPD DD statement in the FTP started task JCL.\n\nIf the INACTIVE statement is coded with a value between 1 and 900 (seconds) this is not a finding.","fixText":"Configure the FTP.DATA CONFIGURATION STATEMENT to include the following:\n\nINACTIVE [A value between 1 and 900]","ccis":["CCI-001133"]},{"vulnId":"V-223528","ruleId":"SV-223528r1137691_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 ACF command screen enter:\nSet RESOURCE(SPL)\nList like(localnodeid-)\n\nIf the following resources in the JESSPOOL resource class (i.e., TYPE(SPL)) are configured as noted below, this is not a finding.\n\nlocalnodeid.JES2.$TRCLOG.taskid.-.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.-.SYSLOG or\nlocalnodeid.+BYPASS+.SYSLOG.jobid.-.SYSLOG\n\nNOTE: These resource rules may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\nlocalnodeid.JES2.-.-.-.JESTRACE\nlocalnodeid.+MASTER+.-.-.-.SYSLOG or\nlocalnodeid.+BYPASS+.-.-.-.SYSLOG\n\nNOTE: 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 access authorization for the resources mentioned above is restricted to the following, this is not a finding.\n\nLogonid(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\nSystems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access.\n\nApplication Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource.","fixText":"NOTE: If CLASMAP defines JESSPOOL as anything other than TYPE(SPL), replace SPL below with the appropriate three letters.\n\nConfigure the following resources in the JESSPOOL resource class (i.e., TYPE(SPL)):\n\nlocalnodeid.JES2.$TRCLOG.taskid.-.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.-.SYSLOG or\nlocalnodeid.+BYPASS+.SYSLOG.jobid.-.SYSLOG\n\nNOTE: These resource rules may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\nlocalnodeid.JES2.-.-.-.JESTRACE\nlocalnodeid.+MASTER+.-.-.-.- or\nlocalnodeid.+BYPASS+.-.-.-.-\n\nNOTE: 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\nConfigure access authorization for the resources mentioned above is restricted to the following:\n\nLogonid(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\nSystems personnel and security administrators responsible for diagnosing JES2 and z/OS problems can have complete access.\n\nApplication Development and Application Support personnel responsible for diagnosing application problems can have READ access to the SYSLOG resource.\n\nExample:\nSET R(SPL)\n$KEY(localnodeid) TYPE(SPL)\n-.SYSLOG.-.-.- UID(sysprgmr) ALLOW\n-.SYSLOG.-.-.- UID(seca) ALLOW\n-.SYSLOG.-.-.- UID(appdudt) SERVICE(READ) ALLOW\n-.SYSLOG.-.-.- UID(apps) SERVICE(READ) ALLOW\n-.$TRCLOG.-.-.- UID(sysprgmr) ALLOW\n-.$TRCLOG.-.-.- UID(seca) ALLOW\n- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223529","ruleId":"SV-223529r1137691_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":"From the ACF command screen enter:\nSET CONTROL(GSO)\nLIST LIKE(CLASMAP-) {to determine the resource class for JESSPOOL}\n\nNOTE: If CLASMAP defines JESSPOOL as anything other than TYPE(SPL), replace SPL below with the appropriate three letters.\n\nSET RESOURCE(SPL)\nLIST LIKE(-)\n\nIf the following resources are defined to the JESSPOOL resource class (i.e., TYPE(SPL)) with a default access of PREVENT, this is not a finding.\n\nlocalnodeid.-\nlocalnodeid.JES2.$TRCLOG.taskid.-.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.-.SYSLOG\n\nThese resource rules may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\nlocalnodeid.JES2.-.-.-.JESTRACE\nlocalnodeid.+MASTER+.-.-.-.-\n\nReview 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\nIf the following resource is defined to the JESSPOOL resource class (i.e., TYPE(SPL)) with a default access of READ, this is not a finding.\nlocalnodeid.jesid.$JESNEWS.taskid.Dnewslvl.JESNEWS\njesid The logonid associated with your JES2 system.\n\nNOTE: This resource rule may be more generic as long as it pertains directly to the JESNEWS data set. For example:\nlocalnodeid.jesid.$JESNEWS.-.-.JESNEWS","fixText":"NOTE: If CLASMAP defines JESSPOOL as anything other than TYPE(SPL), replace SPL below with the appropriate three letters.\n\nConfigure the CLASMAP record to define the JESSPOOL resource class.\n\nExample:\nSHOW CLASMAP\n\nThe following resources are defined to the JESSPOOL resource class (i.e., TYPE(SPL)) with a default access of PREVENT:\nlocalnodeid.-\nlocalnodeid.JES2.$TRCLOG.taskid.-.JESTRACE\nlocalnodeid.+MASTER+.SYSLOG.jobid.-.SYSLOG\n\nExample:\n$KEY(localnodeid) TYPE(SPL)\n- UID(*) PREVENT\n\nThese resource rules may be more generic as long as they pertain directly to the JESTRACE and SYSLOG data sets. For example:\nlocalnodeid.JES2.-.-.-.JESTRACE\nlocalnodeid.+MASTER+.-.-.-.-\n\nReview 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 resource is defined to the JESSPOOL resource class (i.e., TYPE(SPL)) with a default access of READ:\nlocalnodeid.jesid.$JESNEWS.taskid.Dnewslvl.JESNEWS\n\njesid The logonid associated with your JES2 system.\n\nThis resource rule may be more generic as long as it pertains directly to the JESNEWS data set. For example:\nlocalnodeid.jesid.$JESNEWS.-.-.JESNEWS","ccis":["CCI-000213"]},{"vulnId":"V-223530","ruleId":"SV-223530r1137691_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 ACF command screen enter:\nSET RESOURCE(OPR)\nLIST LIKE(JES-)\n\nIf the JES2.UPDATE.JESNEWS resource is defined to the OPERCMDS resource class with a default access of PREVENT, this is not a finding.\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\nIf access authorization to the JES2.UPDATE.JESNEWS resource in the OPERCMDS class restricts DELETE service 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 the resource rules for the OPERCMDS resource class (i.e., TYPE(OPR)) and ensure the following items are in effect:\n\n1) The JES2.UPDATE.JESNEWS resource is defined to the OPERCMDS resource class with a default access of PREVENT.\n\n2) Access authorization to the JES2.UPDATE.JESNEWS resource in the OPERCMDS class restricts DELETE service to the appropriate personnel (i.e., users responsible for maintaining the JES News data set) and all access is logged.\n\nExample:\n$KEY(JES2) TYPE(OPR)\nUPDATE.JESNEWS UID(SYSPROG) SERVICE(READ,UPDATE) LOG\nUPDATE.JESNEWS UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223531","ruleId":"SV-223531r1137691_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":"NOTE: If CLASMAP defines OPERCMDS as anything other than TYPE(OPR), replace OPR below with the appropriate three letters.\n\nFrom the ACF command screen enter:\nSET RESOURCE(OPR)\nLIST LIKE(JES-)\n\nIf the JES2.- resource is defined to the OPERCMDS class with a default access of PREVENT and all access is logged, this is not a finding.\n\nIf access to JES2 system commands defined in the table in the IBM JES2 Initialization and Tuning Guide titled \"JES2 commands with profile names and minimum required authority\" is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users), this is not a finding.\n\nIf all elevated access to JES2 system commands is logged, this is not a finding.","fixText":"Review the GSO definitions. If CLASMAP defines OPERCMDS as anything other than TYPE(OPR), replace OPR below with the appropriate three letters.\n\nReview resource rules for TYPE(OPR).\n\nDefine the JES2.- resource is defined to the OPERCMDS class with a default access of PREVENT and all access is logged.\n\nDefine access to JES2 system commands defined in the JES2 system commands defined in the table in the IBM JES2 Initialization and Tuning Guide entitled 'JES2 commands with profile names and minimum required authority' is restricted to the appropriate personnel (e.g., operations staff, systems programming personnel, general users).\n\nDefine access to specific JES2 system commands is logged as indicated in the table JES2 system commands defined in the table in the IBM JES2 Initialization and Tuning Guide titled \"JES2 commands with profile names and minimum required authority\".\n\nAssure that elevated access is logged.\n\nSome ACF2 Examples:\n$KEY(JES2) TYPE(OPR)\nCANCEL.BAT UID(oper) SERVICE(READ,UPDATE) LOG\nDISPLAY.JOB UID(*) SERVICE(READ) LOG\nSTART.INITIATOR UID(oper) SERVICE(DELETE) LOG\nSTART.LINE UID(oper) SERVICE(DELETE) LOG \nSTOP.INITIATOR UID(oper) SERVICE(DELETE) LOG\nSTOP.LINE UID(oper) SERVICE(DELETE) LOG \n- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223532","ruleId":"SV-223532r1137691_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 there ACF Command screen enter:\nSET RESOURCE(SPL)\nLIST LIKE(localnodeid-)\n\nIf the accesses to the JESSPOOL resources are properly restricted using the following guidance, this is not a finding.\n\nNOTE: If CLASMAP defines JESSPOOL as anything other than TYPE(SPL), replace SPL below with the appropriate three letters.\n\nReview the JESSPOOL report for resource rules with the following naming convention. These rules may be fully qualified, be specified as generic, or be specified with masking as indicated below:\n\nlocalnodeid.logonid.jobname.jobid.dsnumber.name\n\nlocalnodeid - The name of the node on which the SYSIN or SYSOUT data set currently resides.\nlogonid - The logonid associated with the job. This is the logonid ACF2 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 have access to their own JESSPOOL resources.\n\nThe localnodeid. resource will be restricted to only system programmers, operators, and automated operations personnel, with access to allow all SERVICEs or any combination of SERVICE(...). 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, SERVICE(READ, UPDATE, DELETE, ADD). 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 JESSPOOL resources as defined below.\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\nThe CLASMAP defines JESSPOOL as TYPE(SPL).\n\nExample:\nSHOW CLASMAP\n\nBy default a user has access only to that user's own JESSPOOL resources. However, situations exist where a user legitimately requires access to jobs that run under another user's userid. In particular, if a user routes SYSOUT to an external writer, the external writer should have access to that user's SYSOUT. \n\nThe localnodeid. resource will be restricted to only system programmers, operators, and automated operations personnel with access to allow all SERVICEs or any combination of SERVICE(READ, UPDATE, DELETE, ADD). All access will be logged. (localnodeid. resource includes all generic and/or masked permissions, example: localnodeid.-.-, localnodeid.-, etc)\n\nExample:\nSET R(SPL)\n$KEY(localnode) TYPE(SPL)\n- UID(sysprgmr) SERVICE(UPDATE,READ) LOG\n- UID(*) PREVENT\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, SERVICE(READ, UPDATE, DELETE, ADD). 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:\nSET R(SPL)\n$KEY(localnode) TYPE(SPL)\nUMO- UID(UML03IGUSRZSS***UMO) SERVICE(UPDATE,READ) LOG\n- UID(*) PREVENT\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 must be removed.","ccis":["CCI-000213"]},{"vulnId":"V-223533","ruleId":"SV-223533r1137691_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\nVerify that the accesses for WRITER resources are restricted.\n\nIf the following guidance is true, this is not a finding.\n\nThe ACF2 resources and/or generic equivalent are defined with a default access of PREVENT.\n\nThe ACF2 resources and/or generic equivalent identified below will be defined with access restricted to the operators and system programming personnel:\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\nNOTE: Common sense should prevail during the analysis. For example, access to the offload output destinations should be limited to only systems personnel (e.g., operations staff/system programmers) on a classified system.","fixText":"Configure the 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-223534","ruleId":"SV-223534r1137691_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":"From the ACF input screen enter:\nSET CONTROL(GSO)\nLIST LIKE(CLASMAP-) [To determine the resource class for WRITER]\n\nNOTE: If CLASMAP defines WRITER as anything other than TYPE(WTR), replace WTR below with the appropriate three letters.\n\nSET RESOURCE(WTR)\nLIST LIKE(-)\n\nIf the JES2.- resource is defined to the WRITER resource class with a default access of PREVENT, this is not a finding.\n\nIf the other resources mentioned below are protected by generic and/or fully qualified rules defined to the WRITER resource class with a default access of PREVENT, this is not a finding.\n\nIf the ACF2 resources and/or generic equivalent identified below are defined with access restricted to the appropriate personnel, this is not a finding.\n\nNOTE: A default access of READ is allowed for output destinations that are permitted to route output for all users. Currently, there is no guidance on which output destinations are appropriate for a default access of READ. However, common sense should prevail during the analysis. For example, a default access of READ would typically be inappropriate for RJE, NJE, and offload output destinations.\n\nJES2 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\nOFFn, where n is the number of the offload transmitter. Determine the numbers by searching for OFF( in the JES2 parameters.\n\nPRTn, where n is the number of the local printer. Determine the numbers by searching for PRT( in the JES2 parameters.\n\nPUNn, where n is the number of the local card punch. Determine the numbers by searching for PUN( in the JES2 parameters.\n\nNodename 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.\n\nRnnnn.PRm, where nnnn is the number of the remote workstation and m is the number of the printer. Determine the numbers by searching for .PR in the JES2 parameters.\n\nRnnnn.PUm, where nnnn is the number of the remote workstation and m is the number of the punch. Determine the numbers by searching for .PU in the JES2 parameters.","fixText":"NOTE: If CLASMAP defines WRITER as anything other than TYPE(WTR), replace WTR below with the appropriate three letters.\n\nConfigure the WRITER resource class (i.e., TYPE(WTR)) as follows with:\n\nJES2.- (backstop profile)\nJES2.LOCAL.OFFn.- (spool offload transmitter)\nJES2.LOCAL.OFFn.ST (spool offload SYSOUT transmitter)\nJES2.LOCAL.OFFn.JT (spool offload job transmitter)\nJES2.LOCAL.PRTn (local printer)\nJES2.LOCAL.PUNn (local punch)\nJES2.NJE.nodename (NJE node)\nJES2.RJE.Rnnnn.PRm (remote printer)\nJES2.RJE.Rnnnn.PUm (remote punch)\n\nEnsure the following items are in effect: \n\nThe JES2.- resource is defined to the WRITER resource class with a default access of PREVENT.\n\nThe other resources mentioned above are protected by generic and/or fully qualified rules defined to the WRITER resource class with a default access of PREVENT.\n\nNOTE: A default access of READ is allowed for output destinations that are permitted to route output for all users. Currently, there is no guidance on which output destinations are appropriate for a default access of READ. However, common sense should prevail during the analysis. For example, a default access of READ would typically be inappropriate for RJE, NJE, and offload output destinations.\n\nExamples:\n$KEY(JES2) TYPE(WTR) \nLOCAL.OFF- UID(*) PREVENT \nLOCAL.OFF-.JT UID(*) PREVENT\nLOCAL.OFF-.ST UID(oper) SERVICE(READ) ALLOW\nLOCAL.OFF-.ST UID(sysprgmr) SERVICE(READ) ALLOW\nLOCAL.OFF-.ST UID(seca) SERVICE(READ) ALLOW\nLOCAL.OFF-.ST UID(*) PREVENT \nLOCAL.PRT- UID(*) SERVICE(READ) ALLOW\nLOCAL.PUN- UID(*) PREVENT \nNJE.- UID(*) SERVICE(READ) ALLOW\nRJE.- UID(sysprgmr) SERVICE(READ) ALLOW \nRJE.- UID(*) PREVENT \n- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223535","ruleId":"SV-223535r1137691_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.\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 ACF input screen enter:\nSET CONTROL(GSO)\nLIST LIKE(CLASMAP-) \nOr\nSHOW CLASMAP {to determine the resource type for JESINPUT}\nNOTE: If CLASMAP defines JESINPUT as anything other than TYPE(INP), replace INP below with the appropriate three letters.\n\nSET RESOURCE(INP)\nLIST LIKE(-)\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\nNodename is the NAME parameter in the NODE statement. Review the NJE node definitions by searching for NODE( in the JES2 parameters.\n\nOFFn, where n is the number of the offload receiver. Review the spool offload receiver definitions by searching for OFF( in the JES2 parameters.\n\nRnnnn, where nnnn is the number of the remote workstation. Review the RJE node definitions by searching for RMT( in the JES2 parameters.\n\nRDRnn, where nn is the number of the reader. Review the reader definitions by searching for RDR( in the JES2 parameters.\n\nIf the resources mentioned below are protected by generic and/or fully qualified rules defined to the JESINPUT resource class this is not a finding.\n\nIf a default access of PREVENT is specified for all resources this is not a finding.\n\nIf the ACF2 resources and/or generic equivalent identified below are defined with access restricted to the appropriate personnel this is not a finding.\n\nNOTE: Use common sense during the analysis. For example, access to the offload input sources should be limited to systems personnel (e.g., operations staff).\n\nNOTE: A default access of READ is allowed for input sources that are permitted to submit jobs for all users. No guidance on which input sources are appropriate for a default access of READ. However, common sense should prevail during the analysis. For example, a default access of READ would typically be inappropriate for RJE, NJE, offload, and STC input sources.\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)","fixText":"NOTE: If CLASMAP defines JESINPUT as anything other than TYPE(INP), replace INP below with the appropriate three letters.\n\nConfigure resources in the JESINPUT resource class (i.e., TYPE(INP)) granting read access to authorized users for each of the following input resources:\nINTRDR (internal reader for batch jobs)\nnodename (NJE node)\nOFFn.- (spool offload receiver)\nOFFn.JR (spool offload job receiver)\nOFFn.SR (spool offload SYSOUT receiver)\nRnnnn.RDm (RJE workstation)\nRDRnn (local card reader)\nSTCINRDR (internal reader for started tasks)\nTSUINRDR (internal reader for TSO logons)\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.\n\nNodename is the NAME parameter value specified on the NODE statement. Review the JES2 parameters for NJE node definitions by searching for NODE( in the JES2 parameters.\n\nOFFn, where n is the number of the offload receiver. Determine the numbers by searching for OFF( in the JES2 parameters.\n\nRnnnn.RDm, where nnnn is the number of the remote workstation and m is the number of the reader. Determine the numbers by searching for .RD in the JES2 parameters.\n\nRDRnn, where nn is the number of the reader. Determine the numbers by searching for RDR( in the JES2 parameters.\n\nEnsure the following items are in effect:\n\nThe CLASMAP record defines the JESINPUT resource class.\n\nExample:\nSHOW CLASMAP\n\nThe resources mentioned in (b) are protected by generic and/or fully qualified rules defined to the JESINPUT resource class.\n\nA default access of PREVENT is specified for all resources.\n\nNOTE: A default access of READ is allowed for input sources that are permitted to submit jobs for all users. Currently, there is no guidance on which input sources are appropriate for a default access of READ. However, common sense should prevail during the analysis. For example, a default access of READ would typically be inappropriate for RJE, NJE, offload, and STC input sources.\n\nExamples:\n$KEY(STCINRDR) TYPE(INP)\n- UID(*) PREVENT \n\n$KEY(TSUINRDR) TYPE(INP)\n- UID(*) PREVENT \n\n$KEY(RDR*****) TYPE(INP)\n$MEMBER(RDR#####) \n- UID(*) PREVENT \n\n$KEY(OFF*****) TYPE(INP) \n$MEMBER(OFF#####) \nJR UID(oper) SERVICE(READ)\nJR UID(*) PREVENT \nSR UID(oper) SERVICE(READ)\nSR UID(*) PREVENT \n- UID(oper) SERVICE(READ) \n- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223536","ruleId":"SV-223536r1137691_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":"Review the ACFGSO report executionuserid.SUBMIT resources. These are usually defined to CLASMAP as TYPE(SUR).\nNOTE: If CLASMAP defines SURROGAT as anything other than TYPE(SUR), replace SUR below with the appropriate three letters.\n\nIf no executionuserid.SUBMIT resources are defined to the SURROGAT resource class, this is not applicable.\n\nIf executionuserid.SUBMIT resources are defined to the SURROGAT resource class, review resource rules for TYPE(SUR). If the following items are in effect, this is not a finding.\n\nAll executionlogonid.SUBMIT resources defined to the SURROGAT class specify a default access of PREVENT.\n\nAll resource access is logged; at the discretion of the ISSM/ISSO, scheduling tasks may be exempted.\n\nAccess 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).","fixText":"All executionuserid.SUBMIT resources defined to the SURROGAT resource class specify a default of no access; all resource access is logged (at the discretion of the ISSM/ISSO scheduling tasks may be exempted) and access authorization is restricted to the minimum number of personnel required for running production jobs.\n\nEnsure the CLASMAP defines SURROGAT as TYPE(SUR).\n\nNOTE: If CLASMAP defines SURROGAT as anything other than TYPE(SUR), replace SUR below with the appropriate three letters.\n\nEnsure the following items are in effect:\n\nAll executionlogonid.SUBMIT resources defined to the SURROGAT class specify a default access of PREVENT.\n\nAll resource access is logged except for scheduling tasks.\n\nAccess 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 Executionuserid.SUBMIT resources:\n\nKeep the use of Executionuserid.SUBMIT resources outside of those granted to the scheduling software to a minimum number of individuals.\n\nThe simplest configuration is to only use Executionuserid.SUBMIT 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, Executionuserid.SUBMIT usage should not become the default for all jobs submitted by individual userids (i.e., system programmer must use their assigned individual userids for software installation, duties, whereas using a Executionuserid.SUBMIT resource would normally be 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\nExample:\n\n$KEY(SRR) TYPE(SUR) \nSUBMIT UID(*******STC******CONTROLM) ALLOW\n- UID(*) PREVENT","ccis":["CCI-000213","CCI-002233"]},{"vulnId":"V-223537","ruleId":"SV-223537r958406_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 cyber attacks 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":"Review the FACILITY resource class for BPX.SMF. \n\nIf the ACF2 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 Facility resource class for BPX.SMF as follows:\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-223539","ruleId":"SV-223539r958478_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:\n TSO ISRDDN LOAD IEFSDPPT \n Press Enter.\n\nInterpret the display as follows:\nExamine contents at offset 8 \nHex 'x2' - Bypass Password Protection \nHex 'x3' - Bypass Password Protection\nHex 'x4' - No data set Integrity\nHex 'x5' - No data set Integrity\nHex 'x6' - Both\nHex '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:\nFrom an ISPF command line:\n TSO ISRDDN LOAD <privileged module>\n Press Enter.\n\nIf the return message is \"Load Failed\", make sure there is an entry in PARMLIB member SCHEDxx that revokes the excessive privilege, if this is not true, this is a finding.","fixText":"Review the PPT and define all entries associated with non-existent 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-223540","ruleId":"SV-223540r1001142_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process 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 SA and information system security officer (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\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-223541","ruleId":"SV-223541r1001140_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process 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 modify an existing account. Notification of account modification is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the modification of operating system user accounts and notifies the SA and information system security officer (ISSO) of changes. 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-223542","ruleId":"SV-223542r1001138_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process 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 SA and information system security officer (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\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":"Develop a documented develop a 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-223543","ruleId":"SV-223543r1001137_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a process 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 SAs 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-223544","ruleId":"SV-223544r1001122_rule","severity":"medium","ruleTitle":"IBM z/OS Required SMF data record types must be collected.","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\nSMF data collection is the basic unit of tracking of all system functions and actions. Included in this tracking data are the audit records from each of the ACPs and system. If the required SMF data record types are not being collected, then accountability cannot be monitored, and its use in the execution of a contingency plan could be compromised.\n\nSatisfies: SRG-OS-000004-GPOS-00004, 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-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000255-GPOS-00096, SRG-OS-000303-GPOS-00120, SRG-OS-000327-GPOS-00127, SRG-OS-000365-GPOS-00152, SRG-OS-000392-GPOS-00172, 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-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","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-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-001487","CCI-003938","CCI-002130","CCI-002234","CCI-002884"]},{"vulnId":"V-223545","ruleId":"SV-223545r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS special privileges must be assigned on an as-needed basis to LOGONIDs associated with STCs and LOGONIDs that need to execute TSO in batch.","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:\nACF\nSET LID \nSET VERBOSE\nLIST IF(ACCTPRIV OR CONSOLE OR OPERATOR OR MOUNT)\n\nIf the ACCTPRIV privilege is restricted to security personnel, this is not a finding.\n\nIf the CONSOLE and OPERATOR privileges are restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc), this is not a finding.\n\nIf the MOUNT privilege is restricted to DASD batch users only, this is not a finding.","fixText":"Review all Logonids for the following and ensure that only authorized users with justification are given access to the privileges.\n\nThe ACCTPRIV privilege is restricted for used to the domain level security personnel (ISSO/ISSM).\n\nThe CONSOLE and OPERATOR privileges are restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc).\n\nThe MOUNT privilege is restricted to DASD batch users only on an as-needed basis to execute TSO in batch.\n\nEnsure that all privileges are kept to a minimum and are controlled and documented.","ccis":["CCI-000213"]},{"vulnId":"V-223546","ruleId":"SV-223546r958414_rule","severity":"medium","ruleTitle":"IBM z/OS must specify SMF data options to assure 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\nSMF 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-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","checkContent":"Refer to IEASYS00 member in SYS1.PARMLIB Concatenation. Determine proper SMFPRMxx member. \n\nIf the following SMF collection options are specified as stated below, 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 - 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 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 listed.","ccis":["CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-001464","CCI-001665"]},{"vulnId":"V-223547","ruleId":"SV-223547r958752_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 the system.\n\nIf the output data sets in the procedure have storage capacity to store at least one week's worth of audit data, this is not a finding.","fixText":"Make sure output file and dump procedures allow storage capacity to store one week's worth of audit data.","ccis":["CCI-001849"]},{"vulnId":"V-223548","ruleId":"SV-223548r958754_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":"The ISSO will ensure that an automated process is in place to collect SMF data.\n\nReview SMF data collection and retention processes. Verify processes 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, the site will 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\nDump each SMF file as it fills up during the normal course of daily processing.\n\n- Dump all remaining SMF data at the end of each processing day, or \n- Establish a process using Audit logging.","ccis":["CCI-001851"]},{"vulnId":"V-223549","ruleId":"SV-223549r958424_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.\n\nSatisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000343-GPOS-00134, SRG-OS-000344-GPOS-00135","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","CCI-001855","CCI-001858"]},{"vulnId":"V-223550","ruleId":"SV-223550r1038966_rule","severity":"medium","ruleTitle":"IBM z/OS NOBUFFS in SMFPRMxx must be properly set (Default is MSG).","description":"It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.\n\nWhen availability is an overriding concern, other approved actions in response to an audit failure are as follows: \n\n1) If the failure was caused by the lack of audit record storage capacity, the operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner.\n\n2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.","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-223551","ruleId":"SV-223551r1169916_rule","severity":"medium","ruleTitle":"IBM z/OS Time Protocol 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. \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-223552","ruleId":"SV-223552r1169917_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-223553","ruleId":"SV-223553r1001127_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. 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":"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-004922","CCI-004926"]},{"vulnId":"V-223554","ruleId":"SV-223554r958434_rule","severity":"medium","ruleTitle":"IBM z/OS SMF collection files (i.e., SYS1.MANx) access must be limited 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, ACF2, and customer data.\n\nUnauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.\n\nAudit 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 ACF2 data set rules for the SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) restrict ALLOCATE access to only z/OS systems programming personnel.\n- The ACF2 data set rules for the SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) restrict WRITE access to z/OS systems programming personnel and/or batch jobs that perform SMF dump processing and others as approved by the ISSM.\n- The ACF2 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 ACF2 data set rules for SMF data collection files (e.g., SYS1.MAN* or IFASMF.SYS1.*) specify that all (i.e., failures and successes) WRITE and/or ALLOCATE access is logged.","fixText":"Ensure that WRITE or greater 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.\n\nREAD 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 and/or ALLOCATE access are logged.\n\nEnsure read access failures are logged.","ccis":["CCI-000162","CCI-000163","CCI-000164","CCI-000213","CCI-001314","CCI-001493","CCI-001494","CCI-001495","CCI-002235"]},{"vulnId":"V-223556","ruleId":"SV-223556r991589_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-223557","ruleId":"SV-223557r991589_rule","severity":"medium","ruleTitle":"IBM z/OS must configure system waittimes to protect resource availability based on site priorities.","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":"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\nIf 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\nA 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 ISSA 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\nThe 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\nThe time-out exception cannot exceed 60 minutes. A letter of justification fully documenting the user requirement(s) must be submitted and approved by the site ISSM or ISSO. In addition, this letter must identify an alternate means of access control for the terminal(s) involved (e.g., a room that is locked at all times, a room with a cipher lock to limit access, a password protected screen saver set to 30 minutes or less, etc). The requirement must be revalidated on an annual basis.\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\nIf 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\nA 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\nThe 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\nThe time-out exception cannot exceed 60 minutes. A letter of justification fully documenting the user requirement(s) must be submitted and approved by the site ISSM or ISSO. In addition, this letter must identify an alternate means of access control for the terminal(s) involved (e.g., a room that is locked at all times, a room with a cipher lock to limit access, a password protected screen saver set to 30 minutes or less, etc). The requirement must be revalidated on an annual basis.\n\nConfigure any TWT and or SWT to be equal or less than the JWT.","ccis":["CCI-000366"]},{"vulnId":"V-223558","ruleId":"SV-223558r991589_rule","severity":"medium","ruleTitle":"IBM z/OS Emergency LOGONIDs must be properly defined.","description":"Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours.\n\nDepending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).","checkContent":"Ask the system administrator to provide a list of all emergency logonids available to the site along with the associated function of each.\nIf there are no emergency logonids defined, ask the system administrator for an alternate documented procedure to handle emergencies. If there are no emergency logonids and no documented emergency procedure, this is a finding.\n\nIf emergency logonids exist, at a minimum, a logonid will exist with the security administration attributes specified in accordance with the following requirements:\n\nFor emergency IDs with security administration privileges, but which cannot access and update system data sets:\n\nACCOUNT\n\nJCL\nJOB\nMONITOR\nNONON CNCL\nRULEVLD\nRSRCVLD\nSECURITY\nTSO\nTSOPROC(xxxxxxxx)\nTSOACCT(none)\n\nAn additional class of logonids can exist to perform all operating system functions except ESM administration.\n\nThese emergency logonid/logonid(s) will have ability to access and update all system data sets, but will not have security administration privileges. See the following requirements:\n\nJCL\nJOB\nMONITOR\nNON CNCL (Will force logging of all activity.)\nTSO\nTSOPROC(xxxxxxxx)\nTSOACCT(none)\n\nAll emergency logonid/logonid(s) are to be implemented with logging to provide an audit trail of their activities.\n\nAll emergency logonid/logonid(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 logonid/logonid(s) will have distinct, different passwords in SYS1.UADS and in the ESM, 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 ESM.\n\nAll emergency logonid/logonid(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 logonid is released for use, its password is to be reset by the ISSO within 12 hours.\n\nIf all the emergency logonid items above are true, this is not a finding.\n\nIf any item above is untrue, this is a finding.","fixText":"Ensure that Emergency Logonids use these fields to enforce restrictions for Emergency logonids. \n\nTwo classes of emergency logonids may exist. The following privileges and specifications will be used for these logonids:\n\nNote: Only the emergency logonid with the security administration logonid attributes is required.\n\n(1) For emergency IDs with the ability to access and update all system data sets, but which do not have security administration privileges:\n\nNOFSRETAIN\nJCL\nJOB\nMONITOR\nNON CNCL (Will force logging of all activity.)\nTSO\nTSOPROC(xxxxxxxx)\nTSOACCT(none)\n\nExample:\n\nSET LID\nINSERT logonid NOFSRETAIN JCL JOB MONITOR NON-CNCL TSO TSOPRC(xxxxxxxx) TSOACCT(none)\n\n(2) For emergency IDs with security administration privileges, but which cannot access and update system data sets:\n\nACCOUNT\nNOFSRETAIN\nJCL\nJOB\nMONITOR\nNONON CNCL\nRULEVLD\nRSRCVLD\nSECURITY\nTSO\nTSOPROC(xxxxxxxx)\nTSOACCT(none)\n\nExample:\n\nSET LID\nINSERT logonid ACCOUNT NOFSRETAIN JCL JOB MONITOR RULEVLD RSRCVLD NONON-CNCL SECURITY TSO TSOPRC(xxxxxxxx) TSOACCT(none)   \n\nIf no emergency logonids are in use on the system, develop and document a procedure to manage emergencies access to the system.","ccis":["CCI-000366"]},{"vulnId":"V-223560","ruleId":"SV-223560r991593_rule","severity":"medium","ruleTitle":"IBM z/OS Policy Agent must employ a deny-all, allow-by-exception firewall policy for allowing connections to other systems.","description":"Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems. It also permits outbound connections that may facilitate exfiltration of DoD data.","checkContent":"Examine the Policy Agent policy statements. \n\nIf 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-223561","ruleId":"SV-223561r958804_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- Require 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- Require 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 which is NO longer supported is a CAT I vulnerability. The customer and site will be given six months to mitigate the risk, come up with a supported solution, or obtain a formal letter approving such risk/software.","ccis":["CCI-001764"]},{"vulnId":"V-223562","ruleId":"SV-223562r958804_rule","severity":"medium","ruleTitle":"IBM z/OS must not allow non-existent 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.\n\nIf there are any DUMMY entries i.e., inaccessible LINKLINK 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\n-Avoid 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 non-existent libraries. The ISSO should modify and/or delete the rules associated with these libraries.","ccis":["CCI-001764"]},{"vulnId":"V-223563","ruleId":"SV-223563r958804_rule","severity":"medium","ruleTitle":"IBM z/OS must not allow non-existent 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 and 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 should 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-223564","ruleId":"SV-223564r958478_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. Examine 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-223565","ruleId":"SV-223565r958478_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":"Failure to specify LINKAUTH=APFTAB allows libraries other than those designated as APF to contain authorized modules which could bypass security and violate the integrity of the operating system environment. This expanded authorization list inhibits the ability to control inclusion of these modules.","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-223566","ruleId":"SV-223566r958478_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.\n\nThe organization must perform a periodic scan/review of the application (as required by CCI-000384) and disable functions, ports, protocols, and services deemed to be unneeded or non-secure.","checkContent":"From an ISPF Command line enter:\nTSO ISRDDN APF\n\nAn APF List results\nOn the command line enter:\nDUPlicates (make sure there is appropriate access, if not you may receive insufficient access errors)\n\nIf any of the list of Sensitive Utilities exist in the duplicate APF modules return, 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-223567","ruleId":"SV-223567r958480_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.\n\nMCS consoles can be used to issue operator commands. Failure to properly control access to MCS consoles could result in unauthorized personnel issuing sensitive operator commands. This exposure may threaten the integrity and availability of the operating system environment, and compromise the confidentiality of customer data.","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. \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-223568","ruleId":"SV-223568r1001134_rule","severity":"medium","ruleTitle":"IBM z/OS must use ICSF or SAF Key Rings for key management.","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.\n\nSatisfies: SRG-OS-000067-GPOS-00035, SRG-OS-000068-GPOS-00036","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\nIf any files are found, this is a finding.","fixText":"Define all Keys/Certificates to ICSF or the security database. Remove any .kdb and .jks files.","ccis":["CCI-000186","CCI-000187","CCI-004910"]},{"vulnId":"V-223569","ruleId":"SV-223569r1028288_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":"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\n\nThis 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 they 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-001199","CCI-002450","CCI-002475","CCI-002476"]},{"vulnId":"V-223570","ruleId":"SV-223570r1137695_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 bel 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), thereby 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-223571","ruleId":"SV-223571r958902_rule","severity":"medium","ruleTitle":"IBM z/OS Policy agent must contain a 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.","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 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 application and policy agent 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-223572","ruleId":"SV-223572r958528_rule","severity":"medium","ruleTitle":"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. If 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-223573","ruleId":"SV-223573r958400_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 reauthenticates. No other activity aside from reauthentication must 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":"Configure the session manager to retain a user's session lock until that user reestablishes access using established identification and authentication procedures.","ccis":["CCI-000056"]},{"vulnId":"V-223574","ruleId":"SV-223574r958794_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-223575","ruleId":"SV-223575r958404_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager that 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-223576","ruleId":"SV-223576r958402_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager to manage session lock after a 15-minute period of inactivity.","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 reauthenticates. No other activity aside from reauthentication must 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 initiate session lock after a 15-minute period of inactivity this is a finding.","fixText":"Configure the session manager to initiate a session lock after a 15-minute period of inactivity.","ccis":["CCI-000057"]},{"vulnId":"V-223577","ruleId":"SV-223577r1001129_rule","severity":"medium","ruleTitle":"The IBM z/OS system administrator (SA) must develop a procedure to automatically 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 automatically remove or disable temporary user accounts after 72 hours.","ccis":["CCI-000016","CCI-003628"]},{"vulnId":"V-223578","ruleId":"SV-223578r958508_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to automatically 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 system administrator 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"]},{"vulnId":"V-223579","ruleId":"SV-223579r1001132_rule","severity":"medium","ruleTitle":"IBM z/OS system administrator must develop a procedure to notify system administrators (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 SA 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.","checkContent":"Ask the SA for the procedure to notify SAs and ISSOs of account enabling actions.\n\nIf no procedures are in place, this is a finding.","fixText":"Develop and document a procedure to notify SAs and ISSOs of account enabling actions.","ccis":["CCI-000015"]},{"vulnId":"V-223581","ruleId":"SV-223581r958936_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-223582","ruleId":"SV-223582r958948_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-223583","ruleId":"SV-223583r1001144_rule","severity":"medium","ruleTitle":"IBM z/OS must employ a session manager configured 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 (SA) 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 manage to allow users to directly initiate a session lock for all connection types.","ccis":["CCI-000057"]},{"vulnId":"V-223584","ruleId":"SV-223584r1001090_rule","severity":"medium","ruleTitle":"ACF2 system administrator must develop a procedure to disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.","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":"Ask the system administrator for the procedure to disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.\n\nIf there is no procedure this is a finding.","fixText":"Develop a procedure to disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.","ccis":["CCI-003627"]},{"vulnId":"V-223585","ruleId":"SV-223585r959008_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":"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 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-223586","ruleId":"SV-223586r958406_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":"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 cyber attacks 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":"Locate the SSH daemon configuration file which may be found in \"/etc/ssh/\" directory.\n\nAlternately:\n\nFrom UNIX System Services ISPF Shell, navigate to ribbon select tools.\n\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-223587","ruleId":"SV-223587r958586_rule","severity":"medium","ruleTitle":"IBM z/OS SSH daemon must be configured with the Department of Defense (DoD) logon banner.","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.\"\n\nSatisfies: SRG-OS-000228-GPOS-00088, SRG-OS-000023-GPOS-00006","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 s 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.\n\nThe banner below 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.\n\nThe banner below 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-000048","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223588","ruleId":"SV-223588r958480_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, 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. If 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-223589","ruleId":"SV-223589r1083012_rule","severity":"high","ruleTitle":"IBM z/OS SSH daemon must be configured to use a FIPS 140-2 compliant cryptographic algorithm.","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","checkContent":"Locate the SSH daemon configuration file, which may be found in \"/etc/ssh/\" directory.\n\nAlternately:\n\nFrom Unix System Services ISPF Shell, navigate to ribbon select tools.\n\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 system-wide configuration file configuration as follows:\nFIPSMODE=YES\nCiphersSource=ICSF\nMACsSource=ICSF","ccis":["CCI-000068","CCI-000803","CCI-001453"]},{"vulnId":"V-223590","ruleId":"SV-223590r1137691_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":"HFS directories and files of the Syslog daemon provide the configuration and executable properties of this product. Failure to properly secure these objects could lead to unauthorized access. This exposure may result in the compromise of the integrity and availability of the operating system environment, ACP, and customer data.","checkContent":"From an ISPF enter:\ncd /usr/sbin\nEnter\nls -alW\n\nIf File Permission Bits and User Audit Bits for SYSLOG Daemon HFS directories and files is as below, this is not a finding.\n\n/usr/sbin/syslogd 1740 fff\n\nEnter:\ncd /etc/\nEnter\nls -alW\n\nIf the 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\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.\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_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":"With the assistance of a systems programmer with UID(0) and/or SUPERUSER access, review the UNIX permission bits and user audit bits on the HFS directories and files for the Syslog daemon. Ensure they 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-223591","ruleId":"SV-223591r958482_rule","severity":"medium","ruleTitle":"IBM z/OS Syslog daemon must 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) to ensure the Syslog daemon is automatically started 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-223592","ruleId":"SV-223592r1196248_rule","severity":"medium","ruleTitle":"IBM z/OS Syslog daemon must be properly defined and secured.","description":"The Syslog daemon, known as syslogd, is a z/OS Unix daemon that provides a central processing point for log messages issued by other z/OS Unix processes. It is also possible to receive log messages from other network-connected hosts. Some of the IBM Communications Server components that may send messages to Syslog are the FTP, z/OS Unix Telnet, DNS, and DHCP servers. The messages may be of varying importance and may include general process information, diagnostic information, critical error notification, and audit-class information. There is a security interest in protecting the syslogd process and its associated data because of the potential to use this information in an audit process. \n\nThe Syslog daemon requires special privileges and access to sensitive resources to provide its system services. Failure to properly define and control the Syslog daemon could lead to unauthorized access. This exposure may result in the compromise of the integrity and availability of the operating system environment, ACP, and customer data.","checkContent":"The Syslog daemon is defined as SYSLOGD.\n\nFrom the ACF command screen enter:\nSET LID\nLIST SYSLOGD\n\nIf the Syslog daemon is not defined, this is a finding.\n\nIf the SYSLOGD logonid is not defined with the STC attribute, this is a finding.\n\nIf the SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment, this is not a finding. \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.","fixText":"Define the Syslog daemon logonid as SYSLOGD with the STC attribute.\n\nTo set up and use as an MVS Started Proc, the following sample commands are provided:\nSET LID\nINSERT SYSLOGD NAME(SYSLOGD STC) GROUP(stctcpx) STC\n\nThe SYSLOGD userid has UID(0), HOME('/'), and PROGRAM('/bin/sh') specified in the OMVS segment.\n\nSET PROFILE(USER) DIVISION(OMVS)\nINSERT SYSLOGD UID(0) HOME(/) PROGRAM(/bin/sh)\n\nF ACF2,REBUILD(USR),CLASS(P)\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-223593","ruleId":"SV-223593r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFSMS resource class(es) must be defined to the GSO CLASMAP record 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\nThe system-wide options control the default settings for determining how the ACP will function when handling requests for access to the operating system environment, ACP, and customer data. The ACP provides the ability to set a number of these fields at the subsystem level. If no setting is found, the system-wide defaults will be used. The improper setting of any one of these fields, individually or in combination with another, can compromise the security of the processing environment. In addition, failure to establish standardized settings for the ACP control options introduces the possibility of exposure during a migration process or contingency plan activation.","checkContent":"From the ISPF Command Shell enter:\nACF\nSET CONTROL(GSO)\nSHOW CLASMAP\n\nIf both MGMTCLAS and STORCLAS resource classes are uniquely defined (i.e., not type SAF), this is not a finding.","fixText":"Define the GSO CLASMAP record with the following definitions:\n\nMGMTCLAS\nSTORCLAS\n\nEnsure both resource classes above are defined uniquely.\n\nExample:\nSHOW SAFDEF\n\nSET CONTROL(GSO)\nINSERT CLASMAP.MGMTCLAS RESOURCE(MGMTCLAS) RSRCTYPE(MGM) ENTITYTLN(8)\nINSERT CLASMAP.STORCLAS RESOURCE(STORCLAS) RSRCTYPE(STR) ENTITYTLN(8\nF ACF2,REFRESH(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-223594","ruleId":"SV-223594r1137691_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.\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 load modules residing in the following Load libraries to determine Program resource definitions:\n SYS1.DGTLLIB for DFSMSdfp/ISMF\n SYS1.DGTLLIB for DFSMSdss/ISMF\n 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 ACF2 resources are defined with a default access of NONE, this is not a finding.\n\nIf the ACF2 resource access authorizations restrict access to the appropriate personnel, this is not a finding. \n\nRefer to the chapter titled 'Protecting the Storage Management Subsystem' in the IBM z/OS DFSMSdfp Storage Administration Guide to assist with guidance on appropriate access.","fixText":"Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.\n\nRefer to the chapter titled \"Protecting the Storage Management Subsystem\" in the IBM z/OS DFSMSdfp Storage Administration Guide. \n\nUse SMS Program Resources tables to determine the resources, access requirements for SMS Program Resources. Ensure the guidelines for the resource type, resources, and/or generic equivalent specified.\n\nThe ACF2 resources as designated in the above table are defined with a default access of PREVENT.\n\nThe ACF2 resource access authorizations restrict access to the appropriate personnel as designated in the above tables.\n\nThe following commands are provided as a sample for implementing resource controls:\n$KEY(ACBFUTO2) TYPE(PGM)\nUID(********) ALLOW\nUID(*) PREVENT\n\nF ACF2,REBUILD(PGM)","ccis":["CCI-000213"]},{"vulnId":"V-223595","ruleId":"SV-223595r1137691_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.\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 logical parmlib data sets, example: SYS1.PARMLIB(IGDSMSxx), to identify the fully qualified file names for the following SMS data sets:\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 ACF2 data set rules for the SCDS, ACDS, COMMDS, and ACS data sets restrict UPDATE and ALLOCATE access to only systems programming personnel, this not is a finding.\n\nIf the ACF2 data set rules for the SCDS, ACDS, COMMDS, and ACS data sets do not restrict UPDATE and ALLOCATE 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":"Configure DFSMS control data sets to restrict UPDATE or ALLOCATE access to system programmers responsible for DASD management. Justification is required for any additional access.\n\nReview the SYS1.PARMLIB(IGDSMSxx) data set to identify the fully qualified file names for the following SMS data sets:\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\nDefine ACF2 data set rules for the SCDS, ACDS, COMMDS, and ACS data sets to restrict UPDATE and ALLOCATE access to only systems programming personnel.\n\nNote: At the discretion of the ISSM, DASD administrators are allowed UPDATE access to the control data sets.\n\nExample:\n$KEY(S3D) \n$PREFIX(SYS3)\nDFSMS.MVA.ACDS UID(uuuuuuuu) R(A) W(L) A(L) E(A)","ccis":["CCI-000213"]},{"vulnId":"V-223596","ruleId":"SV-223596r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS DFMSM resource class(es)must be defined to the GSO SAFDEF record 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:\nACF\nSET CONTROL(GSO)\nSHOW SAFDEF\n\nIf both FACILITY and PROGRAM resource classes are defined, this is not a finding.","fixText":"Define the GSO SAFDEF record with the following definitions:\n\nFACILITY\nPROGRAM\n\nEnsure both resource classes above are defined.\n\nExample:\nSHOW SAFDEF\n\nSET C(GSO)\nINSERT SAFDEF.FAC FUNCRET(4) FUNCRSN(0) ID(FACILITY) MODE(GLOBAL) RACROUTE(REQUEST=AUTH CLASS=FACILITY) RETCODE(4)\n\nF ACF2,REFRESH(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-223597","ruleId":"SV-223597r1137691_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":"From the ISPF Command Shell enter:\nACF\nSET RESOURCE(FAC)\nSET VERBOSE\nLIST LIKE(STG-)\n\nIf all the following guidance is true, this is not a finding.\n\nThe resource rule for FACILITY (FAC) $KEY(STGADMIN) has a default access of PREVENT.\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 resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE is defined with access of PREVENT.\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 = PREVENT.\n\nThe following resources and prefixes may be available to the end-user.\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.\nSTGADMIN.IDC.DCOLLECT\n\nThe following resources are restricted to Application Production Support Team members, DASD managers, and System programmers.\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.\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.\nSTGADMIN.ADR.STGADMIN.","fixText":"Configure access requirements for SMS Resources as follows. Define the guidelines to ensure the resource type, resources, and/or generic equivalent are followed.\n\n(Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.)\n\nThe ACF2 resources are defined with a default access of PREVENT.\n\nEnsure that the following items are in effect:\n\nEnsure that no access is given to the high-level STGADMIN resource.\n\nExample:\n$KEY(STGADMIN) TYPE(FAC)\n- UID(*) PREVENT\n\nEnsure no access is given to resource STGADMIN.IGG.CATALOG.SECURITY.CHANGE.\n\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nIGG.STGADMIN.IGG.CATALOG.SECURITY.CHANGE-UID(*) PREVENT\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 = PREVENT\n\nThe STGADMIN.DPDSRN.olddsname is restricted to System Programmers and all access is logged.\n\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nDPDSRN.- UID(sysprgmr) SERVICE(READ) LOG\nDPDSRN.- UID(*) PREVENT\n\nThe STGADMIN.IGD.ACTIVATE.CONFIGURATION is restricted to System Programmers and all access is logged.\n\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nIGD.ACTIVATE.CONFIGURATION UID(sysprgmr) SERVICE(READ) LOG\nIGD.ACTIVATE.CONFIGURATION UID(*) PREVENT\n\nThe STGADMIN.IGG.DEFDEL.UALIAS is restricted to System Programmers and Security personnel and all access is logged.\n\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nIGG.DEFDEL.UALIAS UID(seca) SERVICE(READ) LOG\nIGG.DEFDEL.UALIAS UID(secd) SERVICE(READ) LOG\nIGG.DEFDEL.UALIAS UID(sysprgmr) SERVICE(READ) LOG\nIGG.DEFDEL.UALIAS UID(*) PREVENT\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\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nADR.COPY.CNCURRNT.- UID(endusers) SERVICE(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:\n$KEY(STGADMIN) TYPE(FAC)\nIDC.DCOLLECT.- UID(apps) SERVICE(READ)\nIDC.DCOLLECT.- UID(auto) SERVICE(READ)\nIDC.DCOLLECT.- UID(dasb) SERVICE(READ)\nIDC.DCOLLECT.- UID(dasd) SERVICE(READ)\nIDC.DCOLLECT.- UID(sysprgmr) SERVICE(READ)\nIDC.DCOLLECT.- UID(*) PREVENT\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\nExample:\n$KEY(STGADMIN) TYPE(FAC)\nARC.CANCEL.- UID(apps) SERVICE(READ)\nARC.CANCEL.- UID(dasb) SERVICE(READ)\nARC.CANCEL.- UID(dasd) SERVICE(READ)\nARC.CANCEL.- UID(sysprgmr) SERVICE(READ)\nARC.CANCEL.- UID(*) PREVENT\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$KEY(STGADMIN) TYPE(FAC)\nADR. - UID(dasb) SERVICE(READ)\nADR.- UID(dasd) SERVICE(READ)\nADR.- UID(sysprgmr) SERVICE(READ)\nADR.- UID(*) PREVENT\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$KEY(STGADMIN) TYPE(FAC)\nADR.STGADMIN.- UID(dasb) SERVICE(READ) LOG\nADR.STGADMIN.- UID(dasd) SERVICE(READ) LOG\nADR.STGADMIN.- UID(sysprgmr) SERVICE(READ) LOG\nADR.STGADMIN.- UID(*) PREVENT","ccis":["CCI-000213","CCI-002235"]},{"vulnId":"V-223598","ruleId":"SV-223598r991589_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-223599","ruleId":"SV-223599r958406_rule","severity":"medium","ruleTitle":"IBM z/OS PROFILE.TCPIP configuration statements for the TCP/IP stack must be coded properly.","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 cyber attacks 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\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 the SMFPARMS statement is not coded or commented out, this is not a finding.\n\nIf the DELETE statement is not coded or commented out for production system, this is not a finding.\n\nIf the SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands, this is not a finding.\n\nIf the TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand, this is not a finding.\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":"Configure the statements in the PROFILE.TCPIP file 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 SMFPARMS statement is not coded or commented out.\nThe DELETE statement is not coded or commented out for production systems.\nThe SMFCONFIG statement is coded with (at least) the FTPCLIENT and TN3270CLIENT operands.\nThe TCPCONFIG and UDPCONFIG statements are coded with (at least) the RESTRICTLOWPORTS operand.\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-223600","ruleId":"SV-223600r958672_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-223601","ruleId":"SV-223601r1137691_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.\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 ACF command screen enter:\nSET RESOURCE(SER)\nSET VERBOSE\nThe SERVAUTH resource class is mapped to the standard resource type SER.\nLIST LIKE (-)\n\nIf no access is given to the EZA, EZB, and IST high level resources of the SERVAUTH resource class, and default access of PREVENT is specified, this is not a finding.\n\nIf the product CSSMTP is on the system, no access is given to EZB.CSSMTP of the SERVAUTH resource class, this is not a finding.\n\nIf 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 email services.\n\nAuthenticated 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\nIf the EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements, this is not a finding.\n\nIf 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, this is not a finding.\n\nIf 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, this is not a finding.","fixText":"Develop a plan of action to implement the required changes. Ensure the following items are in effect for TCP/IP resources.\n\n(Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.)\n\nThe SERVAUTH resource class is mapped to the required resource type SER.\n\nEnsure that the EZA, EZB, and IST resources are defined to the SERVAUTH resource class with a default access of PREVENT.\n\nIf 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 email services.\n\nOnly 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\nThe EZB.STACKACCESS. resource access authorizations restrict access to those started tasks with valid requirements and users with valid FTP access requirements.\n\nThe 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\n$KEY(EZB) TYPE(SER)\n- UID(*) PREVENT\nCSSMTP. - UID(*) PREVENT\nCSSMTP.sysname.writername.JESnode UID(authusers) SERVICE(READ) ALLOW\nFTP.- UID(authusers) SERVICE(READ) ALLOW\nFTP.sysname.ftpstc.ACCESS.HFS UID(ftpprofile) SERVICE(READ) ALLOW\nNETACCESS.- UID(authusers) SERVICE(READ) ALLOW\nPORTACCESS.- UID(authusers) SERVICE(READ) ALLOW\nSTACKACCESS.- UID(authusers) SERVICE(READ) ALLOW\nSTACKACCESS.sysname.TCPIP UID(ftpprofile) SERVICE(READ) ALLOW\nINITSTACK.- UID(authusers) SERVICE(READ) ALLOW\n\nCOMPILE 'ACF2.MVA.SER(EZB)' STORE\n\nF ACF2,REBUILD(SER)","ccis":["CCI-000213"]},{"vulnId":"V-223602","ruleId":"SV-223602r1137691_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\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-223603","ruleId":"SV-223603r1137691_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":"If 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.\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.\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.","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.\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.\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.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-223604","ruleId":"SV-223604r991589_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\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.\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.","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\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.   \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-223605","ruleId":"SV-223605r958482_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":"Verify Logonid(s) assigned to the TCP/IP address space(s), are named TCPIP or, in the case of multiple instances, are prefixed with TCPIP.\n\nFrom an ACF Command screen enter:\nSET LID\nLIST LIKE(TCPIP-)\n\nIf each TCP/IP logonid its defined with STC, MUSASS, and NO-SMC attributes, this is not a finding.\n\nFrom the ACF Command screen enter:\nSET LID\nLIST LIKE(TCPIP-) PROFILE(OMVS)\n\nIf the z/OS UNIX attributes are UID(0), HOME directory '/', shell program /bin/sh, this is not a finding.\n\nFrom an ACF Command screen enter:\nSET LID\nLIST EZAZSSI\n\nIf THE EZAZSSI logonid is defined with STC attribute, this is not a finding.\n\nFrom the ACF Command screen enter:\nSET LID\nLIST EZAZSSI PROFILE(OMVS)\n\nIf the z/OS UNIX attributes are UID(0), HOME directory '/', shell program /bin/sh, this is not a finding.","fixText":"Define the Started tasks for the Base TCP/IP component user accounts with the following characteristics:\n\nNamed TCPIP or, in the case of multiple instances, prefixed with TCPIP\nDefined with the STC, MUSASS, and NO-SMC attributes\nz/OS UNIX attributes: UID(0), HOME directory '/', shell program /bin/sh\n\nNamed EZAZSSI\nDefined with the STC attribute\nz/OS UNIX attributes: UID(non-zero), HOME directory '/', shell program /bin/sh\n\nReview the TCP/IP started task accounts, privileges, and access authorizations defined to the ACP. Ensure they conform to the requirements as outlined below.\n\nThe following commands can be used to create the user accounts that are required for the TCP/IP address space and the EZAZSSI started task:\n\nSET LID\nINSERT TCPIP NAME(TCPIP) GROUP(STCTCPX) STC MUSASS NO-SMC\nINSERT EZAZSSI NAME(EZAZSSI) GROUP(STCTCPX) STC\n\nSET PROFILE(USER) DIVISION(OMVS)\nINSERT TCPIP UID(0) HOME(/) OMVSPGM(/bin/sh)\nINSERT EZAZSSI UID(non-zero) HOME(/) OMVSPGM(/bin/sh)\n\nF ACF2,REBUILD(USR),CLASS(P)\n\nNOTE: At eTrust CA-ACF2 6.4 and above, the PROGRAM field in the user profile record has been renamed to OMVSPGM.\n\nThe following additions to the indicated rule sets can be used to assign the privileges that are required for the TCP/IP address space:\n\n$KEY(BPX) TYPE(FAC)\n...\nDAEMON UID(TCPIP-uid) SERVICE(READ) ALLOW\n\nIf the z/OS host machine has hardware encryption installed and enabled, resources owned by the Integrated Cryptographic Service Facility (ICSF) component have been defined. The following rule set additions are required to allow the TN3270 Telnet Server process to access the ICSF resources. \n\n- $KEY(CSFCKI) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFCKM) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFDEC) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFENC) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFOWH) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFRNG) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFPKB) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFPKX) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFPKE) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFPKD) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFPKI) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFDSG) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n- $KEY(CSFDSV) TYPE(CSF)\n- UID(TCPIP-uid) SERVICE(READ) ALLOW\n\nThe following operator commands are required to complete the updates:\nF ACF2,REBUILD(FAC)\nF ACF2,REBUILD(CSF)\n\nThese commands and definitions assume that the default type code for CSFSERV resources is CSF.","ccis":["CCI-000764"]},{"vulnId":"V-223608","ruleId":"SV-223608r1050840_rule","severity":"medium","ruleTitle":"IBM z/OS PROFILE.TCPIP configuration INACTIVITY statement must be configured to 900 seconds.","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":"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 PROFILE.TCPIP file as 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\nTELNETPARMS Block (one defined for each port the server is listening to, typically ports 23 and 992)\n\nThe TELNETPARMS INACTIVE statement is coded within each TELNETPARMS statement block and specifies a value between 1 and 900.\n\nINACTIVE statements should not be coded with a value greater than 900 or 0. 0 disables the inactivity timer check.\n\nNOTE: Effective in z/OS release 1.2, the INACTIVE statement can appear in both TELNETGLOBAL and TELNETPARM statement blocks.","ccis":["CCI-002361","CCI-001133"]},{"vulnId":"V-223609","ruleId":"SV-223609r958846_rule","severity":"medium","ruleTitle":"IBM z/OS SMF recording options for the TN3270 Telnet Server must be properly specified.","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 those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities 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.\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\nThe TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\nThe 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.","fixText":"Configure the TELNETPARMS SMFINIT and SMFTERM statements in the PROFILE.TCPIP file to conform 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\nThe TELNETPARMS SMFINIT statement is coded with the TYPE119 operand within each TELNETPARMS statement block.\nThe 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-223610","ruleId":"SV-223610r958408_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, non-organization-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-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\nThe TELNETGLOBALS block that specifies an ENCRYPTION statement states one or more of the below cipher specifications.\n\nEach TELNETPARMS block that specifies the SECUREPORT statement, specifies an ENCRYPTION statement that 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-223611","ruleId":"SV-223611r958390_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":"A logon banner can be used to inform users about the environment during the initial logon. In the DISA environment, logon banners are used to warn users against unauthorized entry and the possibility of legal action for unauthorized users, and advise all users that system use constitutes consent to monitoring. Failure to display a logon warning banner without this type of information could adversely impact the ability to prosecute unauthorized users and users who abuse the system.\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 TCPIP 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. 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.\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-223613","ruleId":"SV-223613r991589_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 into 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 following 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-223615","ruleId":"SV-223615r1137691_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:\nACF\nSET RESOURCE(TSO)\nSET VERBOSE\nLIST LIKE(-)\n\nIf the ACCT authorization is restricted to security personnel, this is not a finding.\n\nIf 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, this is not a finding.\n\nIf the MOUNT authorization is restricted to DASD batch users only, this is not a finding.\n\nIf the OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc), this is not a finding.\n\nIf the PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to auditors, this is not a finding.\n\nIf the TESTAUTH authorization is restricted to only z/OS systems programming personnel, this is not a finding.","fixText":"Configure the TSOAUTH resource class to control sensitive TSO/E commands.\n\n(Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.)\n\nBelow is listed the access requirements for TSOAUTH resources. Ensure the guidelines for the resources and/or generic equivalent are followed.\n\nThe ACCT authorization is restricted to security personnel.\n\nThe 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\nThe MOUNT authorization is restricted to DASD batch users only.\n\nThe OPER authorization is restricted to authorized systems personnel (e.g., systems programming personnel, operations staff, etc).\n\nThe PARMLIB authorization is restricted to only z/OS systems programming personnel and READ access may be given to audit users.\n\nThe TESTAUTH authorization is restricted to only z/OS systems programming personnel.","ccis":["CCI-000213"]},{"vulnId":"V-223616","ruleId":"SV-223616r1137691_rule","severity":"high","ruleTitle":"IBM z/OS UNIX SUPERUSER resource 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.","checkContent":"From the ISPF Command Shell enter:\nACF\nRESOURCE(UNI)\nLIST LIKE(SUPER-)\n\nIf the ACF2 rules for the SUPERUSER resource specify a default access of NONE, this is not a finding.\n\nIf there are no ACF2 rules that allow access to the SUPERUSER resource, this is not a finding.\n\nIf there is no ACF2 rule for CHOWN.UNRESTRICTED defined, this is not a finding.\n\nIf the ACF2 rules for each of the SUPERUSER resources listed in the z/OS UNIX System Services Planning, Establishing UNIX Security, specify a default access of NONE, this is not a finding.\n\nIf the ACF2 rules for each of the SUPERUSER resources listed in the UNIXPRIV CLASS RESOURCES Table in the z/OS UNIX System Services Planning, Establishing UNIX Security, restrict access to appropriate system tasks or systems programming personnel, this is not a finding.","fixText":"Configure ACF2 SUPERUSER resources for the UNIXPRIV resource class to restrict to appropriate system tasks and/or system programming personnel.\n\nConfigure the ACF2 rules for the SUPERUSER resource to specify a default access of NONE.\n\nConfigure no ACF2 rules that allow access to the SUPERUSER resource.\n\nConfigure no ACF2 rule for CHOWN.UNRESTRICTED defined.\n\nConfigure the ACF2 rules for each of the SUPERUSER resources listed in the UNIXPRIV CLASS RESOURCES Table in the z/OS UNIX System Services Planning, Establishing UNIX security to specify a default access of NONE.\n\nConfigure the ACF2 rules for each of the SUPERUSER resources listed in the UNIXPRIV CLASS RESOURCES Table in the z/OS UNIX System Services Planning, Establishing UNIX security to restrict access to appropriate system tasks or systems programming personnel.\n\nExample:\nSET R(UNI)\n$KEY(SUPERUSER) TYPE(UNI) \n$MEMBER(SUPRUSER)\nFILESYS UID(sysprgmr LOG \nFILESYS.CHOWN UID(sysprgmr) LOG \nFILESYS.MOUNT UID(sysprog) LOG \nFILESYS.PFSCTL UID(sysprgmr) LOG \nFILESYS.VREGISTER UID(sysprgmr) LOG \nIPC.RMID UID(sysprgmr) LOG \nPROCESS.GETPSENT UID(sysprgmr) LOG \nPROCESS.KILL UID(sysprgmr) LOG \nPROCESS.PTRACE UID(sysprgmr) LOG \nSETPRIORITY UID(sysprgmr) LOG \n- UID(*) PREVENT","ccis":["CCI-000213"]},{"vulnId":"V-223617","ruleId":"SV-223617r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX security parameters in etc/profile 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/profile\n\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-223618","ruleId":"SV-223618r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX security parameters in /etc/rc 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/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:\nf log for failed access attempts\na log for failed and successful access\n- no auditing\n\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. 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":"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. \n\nThere are two specific guidelines that must be followed:\n-Verify that the CHMOD or CHAUDIT command does not result in less restrictive security than what is specified in the table below.\n-Immediately prior to each command that starts a daemon, the _BPX_JOBNAME variable must be set to match the daemon's name (e.g., inetd, syslogd). The use of _BPX_USERID is at the site's discretion, but is recommended.\n\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. 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.","ccis":["CCI-000213"]},{"vulnId":"V-223619","ruleId":"SV-223619r1137691_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.","checkContent":"From the ISPF Command Shell enter:\nACF\nSET RESOURCE(SUR)\nSET VERBOSE\nLIST LIKE(BPX-)\n\nIf the ACF2 rules for all BPX.SRV.user TYPE(SUR) resources specify a default access of NONE, this is not a finding.\n\nIf the ACF2 rules for all BPX.SRV.user TYPE(SUR) resources restrict access to system software processes (e.g., web servers) that act as servers under z/OS UNIX, this is not a finding.\n\nIf the ACF2 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":"Configure BPX. SRV.userid resources to be properly protected and access 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\nThe default access for each BPX.SRV.userid resource must be no access. Access can be permitted only to system software processes that act as servers under OS/390 UNIX (e.g., web servers) and users whose access an approval are identified in the Site Security Plan.\n\nExample:\nSET R(SUR)\n$KEY(BPX) TYPE(SUR) \nSRV.INTERNAL UID(FJB****STC******IMWEBSRV) SERVICE(READ) LOG\nSRV.PRIVATE UID(FJB****STC******IMWEBSRV) SERVICE(READ) LOG \nSRV.PUBLIC UID(FJB****STC******IMWEBSRV) SERVICE(READ) LOG \nSRV.WEBADM UID(FJB****STC******IMWEBSRV) SERVICE(READ) LOG \n- UID(*) PREVENT","ccis":["CCI-000213","CCI-002233"]},{"vulnId":"V-223620","ruleId":"SV-223620r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS HFS directory(s) with other write permission bit set must be properly defined.","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":"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, this is not a 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-223621","ruleId":"SV-223621r1137691_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:\nACF\nSET RESOURCE(FAC)\nSET VERBOSE\nLIST LIKE(BPX-)\n\nIf the ACF2 rules for the BPX resource specify a default access of NONE, this is not a finding.\n\nIf there are no ACF2 rules that allow access to the BPX resource, this is not a finding.\n\nIf there is no ACF2 rule for BPX.SAFFASTPATH defined, this is not a finding.\n\nIf the ACF2 rules for each of the BPX resources listed in z/OS UNIX System Services Planning, Establishing UNIX security, specify a default access of NONE, this is not a finding.\n\nIf the ACF2 rules for each of the BPX resources listed in the in z/OS UNIX System Services Planning, Establishing UNIX security, restrict access to appropriate system tasks or systems programming personnel, this is not a finding.","fixText":"Configure BPX. Resources to be properly protected and access is restricted to appropriate system tasks or systems programming personnel.\n\nConfigure the following items for the FACILITY resource class, TYPE(FAC):\n\nThe ACF2 rules for the BPX resource specify a default access of NONE.\n\nExample:\n$KEY(BPX) TYPE(FAC)\n- UID(*) PREVENT\n\nThere are no ACF2 rules that allow access to the BPX resource.\n\nExample:\n$KEY(BPX) TYPE(FAC)\n- UID(*) PREVENT\n\nThere is no ACF2 rule for BPX.SAFFASTPATH defined.\n\nExample:\n$KEY(BPX) TYPE(FAC)\nSAFFASTPATH UID(*) PREVENT\n\nThe ACF2 rules for each of the BPX resources listed in the General Facility Class BPX Resources Table, in the z/OS UNIX System Services Planning, Establishing UNIX security, specify a default access of NONE.\n\nExample:\n$KEY(BPX) TYPE(FAC)\nDAEMON UID(*) PREVENT\nDEBUG UID(*) PREVENT \nFILEATTR.APF UID(*) PREVENT\nFILEATTR.PROGCTL UID(*) PREVENT\nJOBNAME UID(*) PREVENT\nSAFFASTPATH UID(*) PREVENT\nSERVER UID(*) PREVENT\nSMF UID(*) PREVENT\nSTOR.SWAP UID(*) PREVENT\nSUPERUSER UID(*) PREVENT\nWLMSERVER UID(*) PREVENT\n\nThe ACF2 rules for each of the BPX resources listed in the 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 as specified.\n\nExample:\n$KEY(BPX) TYPE(FAC)\nDAEMON UID(*******STC******FTPD) SERVICE(READ) LOG\nDAEMON UID(*******STC******INETD) SERVICE(READ) LOG \nDAEMON UID(*******STC******NAMED) SERVICE(READ) LOG \nDAEMON UID(*******STC******OMVSKERN) SERVICE(READ) LOG\nDAEMON UID(*******STC******OMVS) SERVICE(READ) LOG \nDAEMON UID(*******STC******OROUTED) SERVICE(READ) LOG \nDAEMON UID(*******STC******OSNMPD) SERVICE(READ) LOG","ccis":["CCI-000213"]},{"vulnId":"V-223622","ruleId":"SV-223622r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX SYSTEM FILE SECURITY SETTINGS must be properly protected or specified.","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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\n\nAccess enforcement mechanisms include access control lists, access control matrices, and cryptography.","checkContent":"From the ISPF Command Shell enter:\nOMVS\n\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\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/tablename    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/tablename     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:\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:\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-223623","ruleId":"SV-223623r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS data sets with z/OS UNIX components must be properly protected.","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.\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 UPDATE and ALLOCATE 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 UPDATE and ALLOCATE access to systems programming personnel.\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.\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.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-223624","ruleId":"SV-223624r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX MVS data sets or HFS objects must be properly protected.","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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.\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 sets referenced in the ROOT and the MOUNT statements in BPXPRMxx restrict update and/or allocate 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 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 update and/or allocate access to systems programming personnel.","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-223625","ruleId":"SV-223625r1137691_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\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100","checkContent":"From the ISPF Command Shell enter:\nomvs\ncd /\nls -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 Tale below, this is not a finding.\n\nSYSTEM 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.\n 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.\n 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 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":"Define the UNIX permission bits and user audit bits on each of the HFS directory in the table below to be equal or more restrictive.\n\nSYSTEM 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.\n 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.\n 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 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\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:\nchmod 0755 /\nchaudit w=sf,rx+f /\nchmod 0755 /bin\nchaudit rwx=f /bin","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-223626","ruleId":"SV-223626r1137691_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 STEPLIBLIST statement in the BPXPRMxx member of PARMLIB. \n\nIf the STEPLIBLIST points to an etc/steplib, go to the ISPF Command Shell and enter:\nOMVS\ncd /etc\ncat <filename>\n\nIf the ESM data set rules for libraries specified in the STEPLIBLIST file do not restrict WRITE and/or ALLOCATE access to only systems programming personnel, this is a finding.\n\nIf the ESM data set rules for libraries specified in the STEPLIBLIST file do not specify that all (i.e., failures and successes) WRITE and/or ALLOCATE access will be logged, this is a finding.","fixText":"Define the STEPLIBLIST with update and allocate access to libraries residing in the /etc/steplib limited to systems programmers only.\n\nThe STEPLIBLIST parameter specifies the pathname of the HFS file that contains the list of MVS data sets used as step libraries for programs that have the set-user-id or set group id permission bit set. \n\nThe use of STEPLIBLIST is at the site's discretion, but if used, the value of STEPLIBLIST will be /etc/steplib. All WRITE and ALLOCATE access to the MVS data sets in the list will be logged and only systems programming personnel will be authorized to update the data sets.","ccis":["CCI-000213","CCI-001499","CCI-002235"]},{"vulnId":"V-223629","ruleId":"SV-223629r991589_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.","checkContent":"Refer to the IEASYS00 member of SYS1.PARMLIB.\n\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-223630","ruleId":"SV-223630r991589_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX HFS MapName files 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.\n\nThe organization must perform a periodic scan/review of the application (as required by CCI-000384) and disable functions, ports, protocols, and services deemed to be unneeded or non-secure.","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\n\nPerform a contents list for the file identified.\nExample:\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\nSecurity NO disables security checking for file access. Security NO is only allowed on test and development domains.\n\nSetuid 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-223631","ruleId":"SV-223631r991589_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX BPXPRMxx security parameters in PARMLIB 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":"Refer to the proper BPXPRMxx member in SYS1.PARMLIB.\n\nIf the required parameter keywords and values are defined as detailed below, this is not a finding.\n\nParameter Keyword Value\n\nSUPERUSER BPXROOT\nTTYGROUP TTY\nSTEPLIBLIST /etc/steplib\nUSERIDALIASTABLE will not be specified.\nROOT SETUID will be specified.\nMOUNT NOSETUID\n              SETUID (for Vendor-provided files)\nSECURITY\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\n\nSUPERUSER BPXROOT\nTTYGROUP TTY\nSTEPLIBLIST /etc/steplib\nUSERIDALIASTABLE will not be specified.\nROOT SETUID will be specified.\nMOUNT NOSETUID\n              SETUID (for Vendor-provided files)\nSECURITY\nSTARTUP_PROC OMVS","ccis":["CCI-000366"]},{"vulnId":"V-223632","ruleId":"SV-223632r958480_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.\n\nSeveral user exit points in the FTP Server component are available to permit customization of its operating behavior. These exits can be used to modify functions such as FTP command usage, client connection controls, post processing tasks, and SMF record modifications. Without proper review and adequate documentation of these exit programs, undesirable operations and degraded security may result. This exposure could lead to unauthorized access impacting data integrity or the availability of some system services, or contribute to the loss of accountability and hamper security audit activities.","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\nIf the following items are in effect for FTP Server user exits, this is not a finding:\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.","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-223633","ruleId":"SV-223633r1195309_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 unless justified and documented with the information system security officer (ISSO), 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 determine if every entry in the file represents a service that is actually in use. Services that are not in use must be disabled to reduce potential security exposures.\n\nThe following services must be disabled in /etc/inetd.conf unless justified and documented with the 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 is to handle service requests on network sockets. Specifically, there is one entry in inetd.conf for each service. Each service entry specifies several parameters. The login_name parameter is of special interest. It specifies the userid under which the forked daemon is to execute. This userid is defined to the ESM and it may require a UID(0) (i.e., superuser authority) value.","ccis":["CCI-000382"]},{"vulnId":"V-223634","ruleId":"SV-223634r958482_rule","severity":"medium","ruleTitle":"IBM z/OS user account for the z/OS UNIX SUPERSUSER 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.) \nDetermine the user ID identified by the SUPERUSER parameter. (BPXROOT is the default).\nFrom a command input screen enter:\nSET LID \nLIST LIKE (superuser userid)\n\nIf the SUPERUSER userid is defined as follows, this is not a finding.\n- No access to interactive on-line facilities (e.g., TSO, CICS, etc.)\n- Default group specified as OMVSGRP or STCOMVS\n\nFrom an ACF command input screen enter:\nSET PROFILE(USER) DIVISION(OMVS) \nSET VERBOSE \nLIST <superuser userid> \n\nIf the SUPERUSER userid is defined as follows, this is not a finding:\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:\nNo access to interactive on-line facilities (e.g., TSO, CICS, etc)\nDefault group specified as OMVSGRP or STCOMVS\nUID(0)\nHOME directory specified as \"/\"\nShell program specified as \"/bin/sh\"","ccis":["CCI-000764"]},{"vulnId":"V-223635","ruleId":"SV-223635r958482_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":"From an ACF Command screen enter:\n\nSET PROFILE(USER) DIV(OMVS)\n\nLI LIKE(-)\n\nIf each user account is defined as follows, this is not a finding.\n\nA unique UID number (except for UID(0) users)\n\nUse the following as a quick test for duplicate UIDs apart from UID 0  \n\nSHOW OMVS USERS(1-2147483647) DUPLICATES\n\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":"Define users of z/OS UNIX (i.e., users with an OMVS profile defined) as follows:\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-223636","ruleId":"SV-223636r958482_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX groups must be defined with a unique GID.","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 an ACF Command screen enter:\nSET PROFILE(GROUP) DIVISION(OMVS)\nLIST LIKE(-)\n\nIf each of the definitions have a unique GID, this is not a finding.","fixText":"Define each UNIX group with a unique GID.","ccis":["CCI-000764"]},{"vulnId":"V-223637","ruleId":"SV-223637r958482_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":"From the ISPF Command Shell enter:\nACF\nSET PROFILE(GROUP) DIVISION(OMVS)\nLIST LIKE(-)\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-223638","ruleId":"SV-223638r958482_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":"If this is a Classified system, this is Not Applicable.\n\nFrom an ACF2 command line enter:\nSET CONTROL(GSO)\nSHOW UNIXOPTS\n\nAlternately:\nRefer to the following report produced by the ACF2 Data Collection:\n- ACF2CMDS.RPT(ACFGSO)\n- ACF2CMDS.RPT(OMVSUSER)\n\nNote: This check applies to any user identifier (LOGONID) used to model OMVS access on the mainframe. This includes any DFTUSER; MODLUSER and BPX.UNIQUE.USER. If MODLUSER is specified then UNIQUSER must be specified.\n\nIf DFTUSER or MODLUSER is not defined in the UNIXOPTS record, this is not a finding.\n\nIf ALL user identifiers (LOGONID) defined to DFTUSER or MODLUSER. or BPX.UNIQUE.USER user account is defined as follows, this is not a 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":"Define DFTUSER or MODLUSER or BPX.UNIQUE.USER user account to be defined as follows:\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).\n\nExample:\nSET PROFILE(USER) DIV(OMVS)\nLIST OMVS\n\nINSERT OMVS HOME(/) OMVSPGM(/bin/false) UID(0)","ccis":["CCI-000764"]},{"vulnId":"V-223639","ruleId":"SV-223639r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS startup user account for the z/OS UNIX Telnet Server must be defined 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 \nCD /etc\nls (to make sure OTELNET is active)\ncat otelnetd.conf\n\nIf the otelnetd command specifies OMVS or OMVSKERN as the user, this is not a finding.\n\nIf the otelnetd command specifies any user other than OMVS or OMVSKERN, this is a finding.","fixText":"Configure the otelnetd startup command in the inetd.conf file to be defined for the z/OS UNIX kernel.","ccis":["CCI-000213"]},{"vulnId":"V-223640","ruleId":"SV-223640r1137691_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\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\n\nIf the following file permission and user Audit Bits are true this is not a finding.\n\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-223641","ruleId":"SV-223641r958392_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX Telnet Server etc/banner file must have the Standard Mandatory DoD Notice and Consent Banner.","description":"A logon banner can be used to inform users about the environment during the initial logon. In the DISA environment, logon banners are used to warn users against unauthorized entry and the possibility of legal action for unauthorized users, and advise all users that system use constitutes consent to monitoring. Failure to display a logon warning banner without this type of information could adversely impact the ability to prosecute unauthorized users and users who abuse the system.\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.\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":"Preferably configure the /etc/otelnet/banner file and ensure the text specifies a logon banner in accordance with DISA requirements.\nAlternately the /etc/banner file may be used in accordance with DISA requirements below.STANDARD 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-000048","CCI-000050"]},{"vulnId":"V-223642","ruleId":"SV-223642r958586_rule","severity":"medium","ruleTitle":"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 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.","checkContent":"From the ISPF Command Shell enter:\nISHELL\n\nEnter /etc/ for a pathname; a CD /etc/ may need to be issued.\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-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223643","ruleId":"SV-223643r958586_rule","severity":"medium","ruleTitle":"IBM z/OS UNIX Telnet Server Startup parameters must be properly specified to display the banner.","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.","checkContent":"From the ISPF Command Shell enter:\nISHELL\n\nEnter /etc/ for a pathname; a CD /etc/ may need to be issued.\nselect FILE NAME inetd.conf\n\nIf Option -h is included on the otelnetd command, this is a finding.","fixText":"Configure the startup parameters in the inetd.conf file for otelnetd to exclude option -h.\n\nNote: -h indicates that the logon banner should not be displayed.","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-223644","ruleId":"SV-223644r1137691_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\nIf 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\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 ACF2 data set rules for all VTAM system data sets do not restrict access to only network systems programming staff, this is a finding.\nIf ACF2 data set rules for all VTAM system data sets do not restrict auditors to READ access only, this is a finding.\n\nThese data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements.","fixText":"Define ACF2 data set rules for all VTAM system data sets to restrict access to only network systems programming staff.\nAuditors may have READ access as documented and approved by ISSM.\n\nThese data sets include libraries containing VTAM load modules and exit routines, and VTAM start options and definition statements.\n\nExample:\n$KEY(SYS1)\nVTAM-.- UID(sysprgmr) R(A) W(L) A(L) E(A)\n\n$KEY(S3V) \n$PREFIX(SYS3)\nVTAM-.- UID(sysprgmr) R(A) W(L) A(L) E(A)","ccis":["CCI-000213","CCI-001499"]},{"vulnId":"V-223645","ruleId":"SV-223645r991560_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 must 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-245535","ruleId":"SV-245535r991589_rule","severity":"medium","ruleTitle":"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 configuration statements specified in the TCP/IP Data configuration file guidance are true, this is not a finding.\n\nDOMAINORIGIN/DOMAIN (The DOMAIN statement is functionally equivalent to the DOMAINORIGIN Statement)","fixText":"Configure the TCPIP.DATA file to include the following:\n\nDOMAINORIGIN/DOMAIN - Specifies the default domain name used for DNS searches.   \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-252547","ruleId":"SV-252547r1137691_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:\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-252705","ruleId":"SV-252705r1001146_rule","severity":"medium","ruleTitle":"IBM z/OS must enforce a minimum eight character password length.","description":"The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.\n\nPassword complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.","checkContent":"From an ACF command screen enter:\nSET CONTROL(GSO)\nLIST PSWD\n\nIf \"MINPSWD\" is set to \"8\", this is not a finding.","fixText":"Configure the Password option \"MINPSWD\" to \"8\".","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-255895","ruleId":"SV-255895r991589_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-255932","ruleId":"SV-255932r991589_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 method will be ORIGINAL for both internal and external tokens. Starting with ICSF FMID HCR77C0, the value for this option can be updated without restarting ICSF by using either the SETICSF command or the ICSF Multi-Purpose service. If this access is not restricted to appropriate personnel, this is a finding.\n\nNote: 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 class. 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\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 method will be ORIGINAL for both internal and external tokens. Starting with ICSF FMID HCR77C0, the value for this option can be updated without restarting ICSF by using either the SETICSF command or the ICSF Multi-Purpose service. This access must be restricted to appropriate personnel.\n\nNote: Other options may be site-defined.","ccis":["CCI-000366"]},{"vulnId":"V-255933","ruleId":"SV-255933r1137691_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) install data sets must be 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":"If the ESM dataset rules for the  IBM Integrated Crypto Service Facility (ICSF) install data sets  does not restrict UPDATE and/or ALTER access to systems programming personnel this is a finding.\n\nIf the ESM  data set rules for  IBM Integrated Crypto Service Facility (ICSF) install data set does not specify that all (i.e., failures and successes) UPDATE and/or ALTER 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\n$KEY(SYS1)\nCSF.- UID(syspaudt) R(A) W(L) A(L) E(A)\nCSF.- UID(tstcaudt) R(A) W(L) A(L) E(A)\nCSF.- UID(icsfusrs) R(A) E(A)","ccis":["CCI-000213","CCI-002234"]},{"vulnId":"V-255934","ruleId":"SV-255934r958482_rule","severity":"medium","ruleTitle":"IBM Integrated Crypto Service Facility (ICSF) Started Task name must be 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":"From the ACF command screen enter:\nSET LID \nSET VERBOSE \nLIST IF(MUSASS)\nLIST IF(STC)\n\nIf the logonid for the IBM Integrated Crypto Service Facility (ICSF) started task does not include MUSASS and/or NO-SMC, this is a finding.","fixText":"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\nINSERT CSFSTART NAME(STC, ICSF) NO-SMC STC","ccis":["CCI-000764"]},{"vulnId":"V-255945","ruleId":"SV-255945r991560_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.  \n If the ACF2 data set access authorizations does not restrict READ access to auditors this is a finding\n\nIf the  ACF2 data set access authorizations does not restrict WRITE and/or greater access to systems programming personnel this is a finding.\n\nIf the ACF2 data set access authorizations does not  restrict WRITE and/or greater access to the product STC(s) and/or batch job(s) this is a finding.","fixText":"Ensure that WRITE and/or greater access to IBM Integrated Crypto Service Facility (ICSF) STC data sets are limited to system programmers and ICSF STC and/or batch jobs only. READ access can be given to auditors at the ISSOs 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\n$KEY(SYS3)\nCSF.-\tUID(syspaudt) R(A) W(A) A(A) E(A)\nCSF.-\tUID(tstcaudt) R(A) W(A) A(A) E(A)\nCSF.-\tUID(icsfstc) R(A) W(A) A(A) E(A)\nCSF.-\tUID(audtaudt) R(A) E(A)","ccis":["CCI-001499"]},{"vulnId":"V-272873","ruleId":"SV-272873r1082835_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, 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-272874","ruleId":"SV-272874r1137691_rule","severity":"medium","ruleTitle":"IBM z/OS RJE workstations and NJE nodes must be defined to the FACILITY 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.\n\nSatisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000326-GPOS-00126","checkContent":"From the ISPF Command Shell, enter:\nACF\nSET RESOURCE(FAC)\nLIST LIKE(*JE)\n\nRefer to SYS1.PARMLIB (JES2PARM).\n\nFor each node entry:\n\nIf all JES2-defined NJE nodes and RJE workstations have a profile defined in the FACILITY 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. Workstation is RMTnnnn, where \"nnnn\" is the number on the RMT statement. Review the JES2 parameters for RJE workstation definitions by searching for RMT( in the report.\n\nNJE.* and RJE.* profiles will force userid and password protection of all NJE and RJE connections respectively. This method is acceptable in lieu of using discrete profiles.","fixText":"Ensure associate LOGONIDs 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 z/OS STIG.","ccis":["CCI-000213"]},{"vulnId":"V-275949","ruleId":"SV-275949r1137691_rule","severity":"medium","ruleTitle":"zOSMF resource class(es) must be defined to the ACF2 GSO CLASMAP record 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\nThe systemwide options control the default settings for determining how the ACP will function when handling requests for access to the operating system environment, ACP, and customer data. The ACP provides the ability to set a number of these fields at the subsystem level. If no setting is found, the systemwide defaults will be used. The improper setting of any one of these fields, individually or in combination with another, can compromise the security of the processing environment. In addition, failure to establish standardized settings for the ACP control options introduces the possibility of exposure during a migration process or contingency plan activation.","checkContent":"From the ISPF Command shell, enter:\nSET CONTROL (GSO)\nSHOW  CLASMAP\n\nIf the CLASMAP records include EJBROLE, LOGSTRM, SERVER, TSOPROC, ZMFAPLA, and ZMFCLOUD resource classes, 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 as specified in the example below.\n\nDefine the GSO CLASMAP records to include the EJBROLE, LOGSTRM, SERVER, TSOPROC, ZMFAPLA, and ZMFCLOUD classes. Ensure resource classes are uniquely defined.\n\nExample:\nACF\nSET CONTROL (GSO)\nINSERT CLASMAP.EJBROLE RESOURCE(EJBROLE) RSRCTYPE(EJB) ENTITYLN(nn)\nF ACF2,REFRESH(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-275951","ruleId":"SV-275951r1195460_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\nThe systemwide options control the default settings for determining how the ACP will function when handling requests for access to the operating system environment, ACP, and customer data. The ACP provides the ability to set a number of these fields at the subsystem level. If no setting is found, the systemwide defaults will be used. The improper setting of any one of these fields, individually or in combination with another, can compromise the security of the processing environment. In addition, failure to establish standardized settings for the ACP control options introduces the possibility of exposure during a migration process or contingency plan activation.","checkContent":"From the ISPF Command Shell, enter:\n\nACF \nSET RESOURCE(<rsctype>)\nList Like(-)\n\nConsult the ICSF administrator, security administrator, and the site security plan for appropriate access.\n\nIf the ACF2 rules for each resource are restrictive to the appropriate users, 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 as specified in the example below.\n\nDefine the GSO CLASMAP records to include the (CRYPTOZ, CSFKEYS, CSFSERV, GCSFKEYS , GXCSFKEY, and XCSFKEY) classes. Ensure resource classes are uniquely defined.\n\nExample:\nACF\nSET CONTROL (GSO)\nINSERT CLASMAP.CSFKEYS  RESOURCE(CSFKEYS) RSRCTYPE(CSK) ENTITYLN(nn)\nF ACF2,REFRESH(ALL)","ccis":["CCI-000213"]},{"vulnId":"V-275964","ruleId":"SV-275964r1169919_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\nThe systemwide options control the default settings for determining how the ACP will function when handling requests for access to the operating system environment, ACP, and customer data. The ACP provides the ability to set a number of these fields at the subsystem level. If no setting is found, the systemwide defaults will be used. The improper setting of any one of these fields, individually or in combination with another, can compromise the security of the processing environment. In addition, failure to establish standardized settings for the ACP control options introduces the possibility of exposure during a migration process or contingency plan activation.","checkContent":"From ISPF command shell enter \"acf\".\nFor  EJBROLE, LOGSTRM,  SERVER, TSOPROC, ZMFAPLA AND ZMFCLOUD resources class, enter\n\nSET RESOURCE (,rsrctype>)\nList like(-)\n\nIf ACF2 access rules for each resource as defined  in the Appendix A in the zOSMF Configuration Guide: Security Structures for z/OSMF Requirements for the Security Configuration tables, are restricted to appropriate users, this is not a finding.","fixText":"Review the requirements for security setup requirements for the Security Configuration Assistant service in the zOSMF Configuration Guide. \n\nConfigure access for resources accordingly.","ccis":["CCI-000213"]},{"vulnId":"V-275965","ruleId":"SV-275965r1137691_rule","severity":"medium","ruleTitle":"ICSF resource class(es) must be defined to the ACF2 GSO CLASMAP record 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\nThe systemwide options control the default settings for determining how the ACP will function when handling requests for access to the operating system environment, ACP, and customer data. The ACP provides the ability to set a number of these fields at the subsystem level. If no setting is found, the systemwide defaults will be used. The improper setting of any one of these fields, individually or in combination with another, can compromise the security of the processing environment. In addition, failure to establish standardized settings for the ACP control options introduces the possibility of exposure during a migration process or contingency plan activation.","checkContent":"From the ISPF Command shell, enter:\nSET CONTROL (GSO)\nSHOW  CLASMAP\n\nIf the CLASMAP records include CRYPTOZ, CSFKEYS, CSFSERV, GCSFKEYS , GXCSFKEY, and XCSFKEY resource classes, 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 as specified in the example below.\n\nDefine the GSO CLASMAP records to include CRYPTOZ, CSFKEYS, CSFSERV, GCSFKEYS , GXCSFKEY, and XCSFKEY classes. Ensure resource classes are uniquely defined.\n\nExample:\nACF\nSET CONTROL (GSO)\nINSERT CLASMAP.EJBROLE RESOURCE(EJBROLE) RSRCTYPE(EJB) ENTITYLN(nn)\nF ACF2,REFRESH(ALL)","ccis":["CCI-000213"]}]}